| Author |
Message
|
| bd_mq |
 Posted: Wed Apr 12, 2006 4:40 pm Post subject: Reason Code 2019 on TopicSession.createSubscriber |
 |
|
Newbie
Joined: 12 Apr 2006
Posts: 4
|
In need of a fresh set of eyes...
I have a app using JMS with WMQ 6.0 as the JMS provider. WMQ is running on Red Hat EL. App uses client mode and both point-to-point and publish/suscribe. When app runs in Tomcat on Windows box, all is well. When app runs in WAS on separate Linux box, we get the below error at startup when trying to create the suscriber. App works in WAS on same Linux box when ActiveMQ is the JMS provider.
| Code: |
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2019
at com.ibm.mq.MQSPIQueueManager.spiCancelDeferred(MQSPIQueueManager.java:182)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.cancelDeferredMessage(MQBrokerSubscriptionEngine.java:2945)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.openSubscription(MQBrokerSubscriptionEngine.java:433)
at com.ibm.mq.jms.MQMigrateSubscriptionEngine.openSubscription(MQMigrateSubscriptionEngine.java:197)
at com.ibm.mq.jms.MQSession.createTSubscriber(MQSession.java:4985)
at com.ibm.mq.jms.MQTopicSession.createSubscriber(MQTopicSession.java:786) |
| Code: |
User(mqm) Program(amqrmppa)
AMQ6125: An internal WebSphere MQ error has occurred.
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
|
Based on other suggestions/postings, I've looked at various things from bugs in the code (objects being closed by other threads, etc.) to unsupported codesets between the systems. All with no luck.
Any pointers appreciated. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Apr 12, 2006 7:21 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Do you have RFP 1 installed ? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 13, 2006 3:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Have you first confirmed that you can establish an plain MQ client connection from the Linux box?
What version of WAS are you running? Is it 6.x?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bd_mq |
| Posted: Thu Apr 13, 2006 9:31 am Post subject: |
|
|
Newbie
Joined: 12 Apr 2006
Posts: 4
|
I did confirm that I can establish a plain MQ client connection from the Linux box.
WAS is version 6.0.2.
RPF 1 is not installed. Will that help? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 13, 2006 9:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Depending on who you listen to, you may have to establish a connection to the default WAS 6 messaging, and bridge that to MQ.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bd_mq |
| Posted: Thu Apr 13, 2006 10:59 am Post subject: |
|
|
Newbie
Joined: 12 Apr 2006
Posts: 4
|
I believe I have found the problem.
I'm using WMQ 6 and WAS 6, but it looks like WAS 6 is shipped with WMQ 5.3 JAR files. A quick test confirmed. Now I just have to figure out to upgrade WAS 6 to support WMQ 6. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 13, 2006 2:10 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Now if you are connecting via a client connection there is a little feature with V6. You better use a JAAS principal and pass that for the connection or use the connect form:
conn = qcf.createConnection(usr,pwd);
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
