Question
Accenture Technology Solutions Pte Ltd
SG
Last activity: 8 Nov 2019 15:23 EST
Connect JMS Error - javax.naming.NamingException: JBAS011843
1. PEGA 74 is deployed on JBOSS, we are connecting to IBM WMQ from JBOSS.(Created Connection definition rule and admin objects successfully)
2. Created Rule-Connect-JMS with Resource reference according to the below PEGA article.
3. Able to read the message from MQ server using the Message Explorer from Connect-JMS rule. (Refer the attached JPEG file ReadMessage.JPG.)
4. But, when I try to "Put Message" to the MQ using the Connect-JMS , its throwing NamingException(refer the attached logs Connect JMS.txt and Screenshot ConnectJmsError.JPG)
Any help will be much appreciated.
Cognizant Technology Limited
IN
Hi Kanneesh,
Please try with the custom activity only for connecting to the JMS Connector and this will be the solution for this problem.
Capgemini
SE
Hi Kannesh,
Were you able to resolve the issue? Did you include any client jar files for this? we are also facing a similar issue in our application.
Pegasystems Inc.
US
You need to follow Redhat document: https://access.redhat.com/documentation/en-us/jboss_enterprise_application_platform/6.2/html/administration_and_configuration_guide/deploy_the_websphere_mq_resource_adapter.
As a cautionary note, Pega has not invested MQ explorer from a long time and as far as I know no plan to do so either. From my experience, only Websphere application server works well. I would recommend use native tools (e.g., IBM MQ explorer, which is freely available) for similar tasks.
Capgemini
SE
Thanks KevinZheng_GCS for your response and suggestion. The issue is we are not using IBM MQ , rather its a remote ActiveMQ which is sitting in another JBOSS server and we have been provided a broker url which should be used to send the messages from PEGA. Somehow we have not managed to do that yet. I have tried using
a JMS bridge from our JBOSS to the remote broker,
JNDI look up on the broker and use pooled connection factory
The Pega server is not able to look up the JMS destinations using the JNDI details.