Last updated on MARCH 08, 2017
Applies to:Oracle Containers for J2EE - Version: 10.1.3.3.0
Information in this document applies to any platform.
***Checked for relevance on 27-Aug-2011***
There is a J2EE application with MDBs. The MDBs can connect to the external TIBCO EMS via resource adapter. The problem is if the TIBCO EMS server is down, the application cannot be deployed to OC4J 10.1.3.3 container. Or, if the application was previously deployed successfully, the
application cannot be restarted because the MDBs cannot be started.
Is there a way to work around this, so even though the external JMS server is down, the application
can still be successfully deployed or restarted?
The issue can be reproduced by :
1. creating an application with MDB which needs to connect to an external JMS server;
2. turning off external JMS server and deploying the application to OC4J
--> the deployment process will fail with error:
Sep 1, 2009 10:16:03 AM application : dt is in failed state
Sep 1, 2009 10:16:04 AM Operation failed with error: Unable to find tibcojms/aeso.xacf:
java.lang.InstantiationException: Error looking up resource 'aeso.xacf': Failed to query JNDI:
Failed to connect to any server at: tcp://testtibcojms1:7342, tcp://testtibcojms2:7342
The error messages make sense because EJBs (including MDBs) are instantiated and activated when
the application is deployed. So the question is:
Is there a way to lazily instantiate/activate the EJBs so the deployment process can complete?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms