Why is deploying applications to WebLogic MDB applications in an alert state?

I have a WebLogic cluster on which I have deployed many topics and applications that use them. My applications are evenly displayed in a warning state. Looking at the Monitoring during deployment, I see that the MDB application is connecting to server # 1, but on server # 2 it shows this:

MDB application appName is NOT connected to messaging system.

My JMS server is configured for a migrated target, which, in turn, targets server # 1 and identifies the cluster. And messages sent to any server arrive as expected. I just do not know why these deployments are displayed in a warning state.

Weblogic 11g

+5
source share
2 answers

,

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

weblogic-application.xml, start-mdbs-with-application , MDBs , , .

, JMS JDBC, , , " " ( StartupClassMBeans LoadBeforeAppActivation "true" ").

, JMS JDBC, " " ( StartupClassMBeans LoadBeforeAppDeployments "true" ).

: http://docs.oracle.com/cd/E13222_01/wls/docs81/ejb/message_beans.html 12c

+3

, .

, . , JMS. ( , ) JNDI , . JMS , .

, - - JMS Server/Cluster. , .

+1

All Articles