MQRCCF_ALREADY_JOINED returned from mqrc.exe, can't find explanation....

[Paul Ivers]

I get the following Java exception when I call createDurableSubscriber and
then using mqrc.exe, I get
"3157 0x00000c55 MQRCCF_ALREADY_JOINED", but can't
find this error explained anywhere (including API programming manual).

Any idea what this means? Running in a Web Application, WSAD5 WS5 test
environment. Queues are working fine.

com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: 3157
Reason code 3157

at
com.ibm.mq.jms.MQBrokerSubscriptionEngine.openDurableSubscription(MQBrokerSu
bscriptionEngine.java:1208)

at
com.ibm.mq.jms.MQTopicSession.createDurableSubscriber(MQTopicSession.java:77
6)

at
com.ibm.mq.jms.MQTopicSession.createDurableSubscriber(MQTopicSession.java:61
5)

at
com.ibm.ejs.jms.JMSTopicSubscriberHandle.<init>(JMSTopicSubscriberHandle.jav
a:208)

at
com.ibm.ejs.jms.JMSTopicSessionHandle.createDurableSubscriber(JMSTopicSessio
nHandle.java:289)

Thanks

[Gareth Matthews]

Paul,

I am unsure where exactly this is documented but the return code you are
seeing is indicating that the broker already has a durable subscriber
registered with the subscription name you are supplying. This could be
because you have created the durable subscriber and then not called the
unsubscribe() method or because the application may have crashed before it
got a chance to do so.

You will need to unsubscribe the subscription before you can recreate the
durable subscriber.

Hope this helps,
Gareth Matthews

"Paul Ivers" <paul_...@us.ibm.com> wrote in message
news:b96mho$n18$1...@news.boulder.ibm.com...

[Gareth Matthews]

Actually, to correct myself (thanks James) - this is not caused by trying to
call createDurableSubscriber() using a subscription name that is already in
use - this being the whole point of what durable subscribers are designed to
do (I.e. create a durable subscriber, receive some messages, close the
subscriber and then re-open the subscriber - using the same method call
createDurableSubscriber() and continue).

This error therefore could be coming out if you have not closed an existing
durable subscriber using that subscription name, maybe because one is still
connected.

My apologies for any confusion caused by my earlier post,
Gareth Matthews

"Gareth Matthews" <matthew...@nospam.hotmail.com> wrote in message
news:b97u4n$38g4$1...@news.boulder.ibm.com...

[Paul Ivers]

....I've been angling at this problem for a couple days now without success.
I appreciate the attempt at help.....

I was bringing the server up and down alot so it makes sense that somehow I
could've screwed-up the MQ with respect to a subscription, so after reading
your note I uninstalled MQ embedded, restarted, re-installed, restarted, AND
created a new TopicConnectionFactory andTopicDestination...but STILL get the
error.

Again, thanks, but still doesn't work. Very frustrating....

"Gareth Matthews" <matthew...@nospam.hotmail.com> wrote in message

news:b98dun$28m6$1...@news.boulder.ibm.com...

[Paul Ivers]

....I've been angling at this problem for a couple days now without success.
I appreciate the attempt at help.....

I was bringing the server up and down alot so it makes sense that somehow I
could've screwed-up the MQ with respect to a subscription, so after reading
your note I uninstalled MQ embedded, restarted, re-installed, restarted,AND

setup a new TopicConnectionFactory and TopicDestination...but STILL get the
error.

Again, thanks, but still doesn't work.

"Gareth Matthews" <matthew...@nospam.hotmail.com> wrote in message
news:b98dun$28m6$1...@news.boulder.ibm.com...

[Gareth Matthews]

Paul,

So just so I understand this problem fully....

You have a test application running in the WSAD5 test environment that is
calling createDurableSubscriber that is failing with the 3157 error.

Do you get this error on the first call to createDurableSubscriber after
starting the server?
If not, are you sure all your applications are closing the durable
subscriber with the close() call when they are finished with it?

If this does occur on the first call, then that would be strange that
something is still hanging around even after a server restart. You could try
changing the subscription name and seeing if that allows your application to
function again - it may be that the continued 'up and down' of the server
has caused the subscription to have gotten into a state where it cannot be
used - which is probably a problem in itself if it is the case. If this does
not solve the problem, or if changing the name works for some time and then
causes it to fail again, you may have to contact your IBM service
representative.

Please feel free to post any findings you have, any info on the code logic
or setup may also help.
Thanks,

Gareth Matthews

"Paul Ivers" <paul_...@us.ibm.com> wrote in message

news:b98jd4$3ghu$1...@news.boulder.ibm.com...