BES 6.0.x - MarshalException with CORBA BAD_PARAM error when external clients trying to get connection from BES Connection Pool using JNDI lookup

Problem:

• Product Name : BES Application Server
• Product version: 6.0 and 6.0 RP1
• Component: JDBC, JNDI, External JDBC clients
• Platform: ALL

When the external client trying to get the database connection from BES Connection Pool, the following exception is thrown:

(Please note that application-specific stack trace is left out for brevity):

java.sql.SQLException: javax.naming.NamingException: java.rmi.MarshalException:
CORBA BAD_PARAM 0[]; nested exception is:
 org.omg.CORBA.BAD_PARAM: vmcid: 0x0 minor code: 0 completed: No
 at com.inprise.visitransact.jdbc2.InpriseDataSource.getVendorDataSource(InpriseDataSource.java:163)
 at com.inprise.visitransact.jdbc2.PooledConnectionHolder$DirectStrategy.getNewPooledConnection(PooledConnectionHolder.java:990)
 at com.inprise.visitransact.jdbc2.PooledConnectionHolder.(PooledConnectionHolder.java:125)
 at com.inprise.visitransact.jdbc2.GenericConnectionPool.doCreateNewElement(GenericConnectionPool.java:100)
 at com.inprise.visitransact.jdbc2.GenericPool.getPooledObject(GenericPool.java:554)
 at com.inprise.visitransact.jdbc2.GenericConnectionPool.getPooledConnection(GenericConnectionPool.java:88)
 at com.inprise.visitransact.jdbc2.InpriseDataSource.getConnection(InpriseDataSource.java:335)
 at com.inprise.visitransact.jdbc2.InpriseDataSource.getConnection(InpriseDataSource.java:368)
 ...
 ...
 ...

The following is the typical configuration when the above-mentioned exception occurred:

• There is a DAR file deployed successfully on one of the BES Partitions. (DAR containing JNDI object definitions for Oracle 10g server)
• The Oracle's JDBC Driver (ojdbc14.jar) deployed successfully on that Partition.
• There is one of the following external clients to communicate to Oracle 10g after getting database connection using JNDI lookup from Partition"s Connection Pool.

• A Standalone Java Client
• A Servlet or JSP deployed on another BES Partition

Resolution

However, it is confirmed that this does not occur in the following cases:

• BES 6.0.1 with classes12.jar from Oracle 9i installation
• BES 6.5 while trying to connect to Oracle 10g

Hence, BES 6.0.x customers migrating to Oracle 10g are advised to upgrade to BES 6.5 and above, since Oracle 10g is not certified/supported for BES 6.0.x.