Consumer is not getting listed for JMS Queue

Sometimes even though the JMS Queue and ConnectionFactory is existing in the JMS Module and the JMSAdpater Outbound connection pool JNDI  rightly points to the ConnectionFactory, still we may encounter issues like the consumer is not getting listed for the queue even after the BPEL consumer code deployed properly

In such cases follow this below rules

• Check the persistent store is created and targeted to the SOA Managed Server
• Check the JMS server is referring to the above persistent store and targeted to the SOA Managed Server
• Ensure the JMS Module has a subdeployment , which is targetted to the above JMSServer
• Ensure the ConnectionFactory/Queue/Topic has targettted to the above subdeployment
• Finally ensure the queue is existing in the JNDI tree. (console->Environment->Servers->SOAManagedServer->JNDI tree Icon)

Only if the Queue/Topic/ConnectionFactory exist in the Managed Servers JNDI tree , the consumer component can connect to it