JMS MDB connection to messaging system failed
SummaryAfter upgrade from PRPC 6.3 SP1 to Pega 7.2.1, JMS MDB listeners connecting to JMS Sonic queue fail to successfully verify test connection.
In Weblogic deployment, error details show: "MDB application prpc_wls_jee4_updated is NOT connected to messaging system."
Error MessagesTest connectivity error message:
Couldn't resolve JMS connection factory object 'java:comp/env/jms/pega/repl/Send_XACF' from JNDI server at , javax.naming.NameNotFoundException: While trying to look up comp/env/jms/pega/repl/Send_XACF in /app/ejb/prbeans.jar/#EngineBMT.; remaining name 'comp/env/jms/pega/repl/Send_XACF'
Weblogic deployment warning message:
MDB application prpc_wls_jee4_updated is NOT connected to messaging system."
Steps to ReproduceTest connection for Connect-JMS rule.
Root CauseMissing configuration.
ResolutionPerform the following local changes:
- First, make sure all Sonic client jars (as documented by the Sonic vendor) are in the Weblogic classpath, for example <wls server>/lib directory).
- Second, add the following element in the weblogic-ejb-jar.xml (based on that generated by Pega engine) inside the element <message-driven-descriptor>:
<connection-factory-jndi-name>jndi name of the connection factory</connection-factory-jndi-name>
Published November 16, 2016 - Updated November 22, 2016