arindam-bandyopadhyay / issue-test

0 stars 0 forks source link

Creation of Durable Subscriber in IBM MQ fails #17

Open arinban opened 6 years ago

arinban commented 6 years ago

Using IBM MQ 6.0. Generic RA is deployed in the application server and a web application is also deployed. The EJB in the application creates a durable subscriber. The appropriate topic connection factory and topics are defined in IBM MQ.

The following code throws an exception sometimes - createDurableSubscriber(topic, "genra15")

where 'genra15' is the client id value. The same is specified while creating the topic connection factory in IBM MQ.

The code was working fine. When it failed I decreased the length of the client id value. It passed initially and then started failing again.

The error message is :

javax.enterprise.system.stream.err|_ThreadID=19;|com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: MQRCCF_SUBSCRIPTION_LOCKED Reason code 3156 at com.ibm.mq.jms.MQBrokerSubscriptionEngine.openDurableSubscription(MQB rokerSubscriptionEngine.java:1294) at com.ibm.mq.jms.MQMigrateSubscriptionEngine.openDurableSubscription(MQ MigrateSubscriptionEngine.java:547) at com.ibm.mq.jms.MQSession.createDurableSubscriber(MQSession.java:5365) at com.ibm.mq.jms.MQSession.createDurableSubscriber(MQSession.java:5185) at com.sun.genericra.outbound.SessionAdapter.createDurableSubscriber(Ses sionAdapter.java:308) at com.sun.ejte.j2ee.genericra.test15.ejb.GenericRA15Bean.receiveTextMes sage(GenericRA15Bean.java:116)

Seems to be an IBM MQ issue - http://www-1.ibm.com/support/docview.wss?uid=swg21116114

Environment

Operating System: All Platform: All

Affected Versions

[current]

arinban commented 6 years ago

Original Issue:https://github.com/javaee/glassfish-genericjmsra/issues/10 Raised By:@glassfishrobot Created at:Wed Nov 30 08:31:40 IST 2005 Assigned To:@glassfishrobot

arinban commented 6 years ago

@glassfishrobot Commented on Wed Nov 30 08:31:40 IST 2005 Reported by sushmita

arinban commented 6 years ago

@glassfishrobot Commented on Sun Dec 04 12:04:51 IST 2005 binod said: Note that clientID should not be used within a J2EE application. Can submitter confirm that this issue appear, even when the clientID is configured just as a connection pool property

arinban commented 6 years ago

@glassfishrobot Commented on Wed Nov 30 08:31:40 IST 2005 Was assigned to binod

arinban commented 6 years ago

@glassfishrobot Commented on Mon Apr 24 13:01:25 IST 2017 This issue was imported from java.net JIRA GENERICJMSRA-10