Question
ATIT
SA
Last activity: 25 Jun 2020 8:03 EDT
JMS MDB Listener - Need class details for Remote Tibco EMS Topic
Hi All,
We are trying to Configure a JMS MDB Listener to listen to a Remote TIBCO EMS Topic.
Got Topic Name along with hostname.
As per suggestions in article https://community.pega.com/support/support-articles/unable-configure-custom-jms-mdb-listener-jboss-eap-6x modified the ejb-jar xml with snippets but the article was referring to a HornetQ and i have to connect to Tibco EMS.
Can someone who faced similar issue provide the classname related to tibco.
attached the snippets which i have updated.
Environment details:
Pega CS 7.1.4 on Pega 7.1.9
Server - Jboss 6.X
Pegasystems Inc.
US
This is more a question for Redhat: see this link: https://access.redhat.com/solutions/121553. Since you are using JBoss EAP, you should have a login to access the article.
ATIT
SA
Thanks for sharing the Link.
I have gone through it and I think it talks about replacing the HornetQ with TIBCO as the Messaging middleware for Jboss.
But our requirement here is not to do that. We just want to connect to a Remote TIBCO EMS Topic for consuming messages placed in it.
The messages on the TIBCO Topic will be consumed by multiple systems apart from Pega.
Accepted Solution
Updated: 25 Jun 2020 8:03 EDT
ATIT
SA
We have tried few more scenarios to make this work.
Created a generic resource adapter as suggested by below article.
Configured the MDB Listener and generated the MDB descriptor fragments as suggested by the below article.
We have tried few more scenarios to make this work.
Created a generic resource adapter as suggested by below article.
Configured the MDB Listener and generated the MDB descriptor fragments as suggested by the below article.
As per PDN post which we found, https://collaborate.pega.com/question/jboss-ibm-mq-pega-722-unable-start-mdb-listener where it said not to update the existing prbeans.jar and create a custommdb jar for this jms specific requirement. Followed the steps as suggested in this article (which is of MQ integration). After doing the changes we are getting below error during server start up. The server is restarted but without listeners.
17:43:07,726 INFO [org.jboss.resource.adapter.jms.inflow.JmsActivation] (default-threads - 1) Attempting to reconnect [email protected]([email protected] destination=java:global/remoteJMS/AA.UK.T.RQ.TS.MDM.MatchAndMerge.XML destinationType=javax.jms.Topic acknowledgeMode=Auto-acknowledge subscriptionDurability=true reconnectInterval=10 reconnectAttempts=-1 user=null maxMessages=1 minSession=1 maxSession=15 connectionFactory=java:global/remoteJMS/XATCF)
17:43:07,727 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] (default-threads - 1) Unable to reconnect [email protected]([email protected] destination=java:global/remoteJMS/AA.UK.T.RQ.TS.MDM.XML destinationType=javax.jms.Topic acknowledgeMode=Auto-acknowledge subscriptionDurability=true reconnectInterval=10 reconnectAttempts=-1 user=null maxMessages=1 minSession=1 maxSession=15 connectionFactory=java:global/remoteJMS/XATCF): java.lang.NoClassDefFoundError: javax/jms/JMSContext
at com.tibco.tibjms.naming.TibjmsContext$Messenger.<init>(TibjmsContext.java:316) [tibjms.jar:8.2.2]
at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:651) [tibjms.jar:8.2.2]
at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:491) [tibjms.jar:8.2.2]
at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_60]
at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_60]
at org.jboss.as.naming.ExternalContextObjectFactory$LookupByStringContext.lookup(ExternalContextObjectFactory.java:177)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:226)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:174)
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:245)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:183)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_60]
at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_60]
at org.jboss.resource.adapter.jms.inflow.JmsActivation.lookup(JmsActivation.java:562) [generic-jms-ra-jar-1.0.7.Final-redhat-1.jar:1.0.7.Final-redhat-1]
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:385) [generic-jms-ra-jar-1.0.7.Final-redhat-1.jar:1.0.7.Final-redhat-1]
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupActivation(JmsActivation.java:312) [generic-jms-ra-jar-1.0.7.Final-redhat-1.jar:1.0.7.Final-redhat-1]
at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:258) [generic-jms-ra-jar-1.0.7.Final-redhat-1.jar:1.0.7.Final-redhat-1]
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:545) [generic-jms-ra-jar-1.0.7.Final-redhat-1.jar:1.0.7.Final-redhat-1]
at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:218)
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:808)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:828)
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.ClassNotFoundException: javax.jms.JMSContext from [Module "org.jboss.genericjms.provider:main" from local module loader @3caeaf62 (finder: local module finder @e6ea0c6 (roots: /opt/jboss/EAP-6.4.0/modules,/opt/jboss/EAP-6.4.0/modules/system/layers/base))]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.6.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.6.Final-redhat-1]
.
Can someone help us with this if they faced similar issue ?
ATIT
SA
Issue is resolved now by adding jms-2.0 jar along with other 2 tibco jars in module.xml.
Also replace the connectionfactory name instead of XATCF with the actual connectionfactory name of the topic. In our case it was TopicConnectionFactory.