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

Question

I have a WebLogic cluster on which I've deployed numerous topics and applications that use them. My applications uniformly show themselves in a Warning status. Looking at Monitoring on the deployment, I see the MDB application connects to Server #1, but on server #2 it shows this:

MDB application appName is NOT connected to messaging system.

My JMS Server is targetted to a migratable target, which is in turn targetted to the #1 server and has a cluster identified. And messages sent to either server all flow as expected. I just don't know why these deployments show in a Warning state.

WebLogic 11g

Answer 1

I don't like unanswered questions, so I'm going to answer this one.

The problem is resolved, though I was not involved in its resolution. At present the problem only exists for the length of time it takes the JMS subsystem to fully initialize. During that period (with many queues, it can take a while) the JNDI system throws errors and the apps are truly in warning state. Once the JMS is fully initialized, everything goes green.

My belief is that someone corrected something in the JMS Server / Cluster config. I'll never know what it was.