Hi,

Jay SenSharma

Jay SenSharma

Many times we see that our applications  MDBs are  getting started before the Application Server’s all resource activation,  Which causes many resource lookups which our MDB does while activating itself… So Please specify in your “weblogic-application.xml” file witht the following Tag:
<start-mdbs-with-application>false</start-mdbs-with-application>

By default, an MDB starts processing messages as soon as it is deployed, even if its target WebLogic Server instance has not completed booting. This can cause an MDB application to access uninitialized services or applications during the boot process, and to fail. To avoid this problem, set start-mdbs-with-application to false in weblogic-application.xml.

Setting start-mdbs-with-application to false forces MDBs to defer starting until after the server instance opens its listen port, near the end of the server boot up process.
Example:


<strong><ejb></strong>
<strong><start-mdbs-with-application>false</start-mdbs-with-application></strong>
<strong></ejb></strong>

———————————-

If you DONOT have any option to change/Edit  your “weblogic-application.xml” file then …

If you want to perform startup tasks after JMS and JDBC services are available, but before applications and modules have been activated, you can select the Run Before Application Deployments option in the Administration Console (or set the StartupClassMBean’s LoadBeforeAppActivation attribute to “true”).

If you want to perform startup tasks before JMS and JDBC services are available, you can select the Run Before Application Activations option in the Administration Console (or set the StartupClassMBean’s LoadBeforeAppDeployments attribute to “true”).

.

.

Thanks

Jay SenSharma

If you enjoyed this post, please considerleaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.