Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

JMS Connect Error when publishing to Topic

SA-11543

Summary



User has a requirement for a message to be published to a topic on MQ Server. Connect JMS rule helps connect to the MQ Server. The follow error is received when running a test activity.

Fail: Couldn't send JMS message: com.ibm.msg.client.jms.DetailedIllegalStateException: JMSWMQ2007: Failed to send a message to destination <topic>. JMS attempted to perform an MQPUT or MQPUT1; however WebSphere MQ reported an error. Use the linked exception to determine the cause of this error.


Error Messages



2015-05-21 15:04:57,454 [ WebContainer : 4] [ STANDARD] [ LRMSandbox:01.01.01] (nector.Rule_Connect_JMS.Action) ERROR <ip1>|<ip2>|<Rule-Connect-JMS> Couldn't send JMS message: com.ibm.msg.client.jms.DetailedIllegalStateException: JMSWMQ2007: Failed to send a message to destination <topic>. JMS attempted to perform an MQPUT or MQPUT1; however WebSphere MQ reported an error. Use the linked exception to determine the cause of this error.
com.ibm.msg.client.jms.DetailedIllegalStateException: JMSWMQ2007: Failed to send a message to destination <topic>. JMS attempted to perform an MQPUT or MQPUT1; however WebSphere MQ reported an error. Use the linked exception to determine the cause of this error.
at com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:496)
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:236)
at com.ibm.msg.client.wmq.internal.WMQMessageProducer.checkJmqiCallSuccess(WMQMessageProducer.java:1112)


Steps to Reproduce



Configure Connect-JMS with Websphere MQ 7.5.

Root Cause



The root cause of this problem is defect/misconfiguration in the operating environment.  Websphere MQ needs to be configured according to the IBM documentation. 

Resolution



Pega uses generic JMS API. All the exceptions are due to the MQ server security configuration. Additionally, configure the environment's URL resource url/initialization/explicittempdir at the JVM level for Pega engine to work correctly.
Suggest Edit

Published July 14, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us