Why are my WebLogic clustered MDB app deployments in warning state? -


i have weblogic cluster on i've deployed numerous topics , applications use them. applications uniformly show in warning status. looking @ monitoring on deployment, see mdb application connects server #1, on server #2 shows this:

mdb application appname not connected messaging system. 

my jms server targetted migratable target, in turn targetted #1 server , has cluster identified. , messages sent either server flow expected. don't know why these deployments show in warning state.

weblogic 11g

this can avoided using parameter below

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

in weblogic-application.xml, setting start-mdbs-with-application false forces mdbs defer starting until after server instance opens listen port, near end of server boot process.

if want perform startup tasks after jms , jdbc services available, before applications , modules have been activated, can select run before application deployments option in administration console (or set startupclassmbean’s loadbeforeappactivation attribute “true”).

if want perform startup tasks before jms , jdbc services available, can select run before application activations option in administration console (or set startupclassmbean’s loadbeforeappdeployments attribute “true”).

refer :http://docs.oracle.com/cd/e13222_01/wls/docs81/ejb/message_beans.html applicable versions till 12c , later


Comments

Popular posts from this blog

javascript - Enclosure Memory Copies -

php - Replacing tags in braces, even nested tags, with regex -