| Author |
Message
|
| tborrome |
 Posted: Fri Feb 07, 2003 7:24 am Post subject: WAS 5.0 Embedded Messaging ? |
 |
|
Novice
Joined: 03 Apr 2002
Posts: 17
|
Has anyone tried WAS 5.0 embedded messaging ? I believe this uses WebSphere MQ 5.3 for queuing and seems to have a different built-in publish-subscribe broker different from MQ's MA0C pub/sub. Can anyone confirm this ?
Also, I tried the pub-sub broker but couldnt get durable subscriptions to work. Does WAS 5.0 embedded messaging support durable subscriptions ?
I'm getting the exception when I createDurableSubscriber ...
com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: 3157 Reason code 3157
at
com.ibm.mq.jms.MQBrokerSubscriptionEngine.openDurableSubscription(MQBrokerSubscriptionEngine.java:1208)
at
com.ibm.mq.jms.MQTopicSession.createDurableSubscriber(MQTopicSession.java:776)
at
com.ibm.mq.jms.MQTopicSession.createDurableSubscriber(MQTopicSession.java:615)
at MySubscriber.startSubscriber(MySubscriber.java:36)
at MySubscriber.main(MySubscriber.java:116)
All I'm doing is ...
InitialContext ctx = getInitialContext(this.url, this.jndiFactory);
TopicConnectionFactory tconFactory = (TopicConnectionFactory)
ctx.lookup(this.jmsFactory);
tcon = tconFactory.createTopicConnection();
tcon.setClientID("test");
Topic Topic = (Topic) ctx.lookup(this.jmsTopic);
tsession = tcon.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
tsubscriber = tsession.createDurableSubscriber(Topic,"test");
I'm using a Websphere TopicConnectionFactory defined under WebSphere JMS Provider, and I made sure the port is QUEUED not DIRECT.
If its nondurable it works. Is there anything else I'm missing? Do I have
to do something in MQ side for durable subscriptions ?
thanks,
T |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Thu Feb 13, 2003 5:20 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I can confirm that the WAS embedded JMS has a different broker than MA0C. It has a version of the WebSphere MQ Event Broker. However, I'm not sure about the durable subscribers. I haven't tried it yet myself. |
|
| Back to top |
|
|
| kingdon |
| Posted: Fri Feb 14, 2003 1:15 am Post subject: |
|
|
Acolyte
Joined: 14 Jan 2002
Posts: 63
Location: UK
|
Durable subcsriptions are tested and supported. The spec' only permits one active connection to a durable subscription at a time, so it would be worth checking that this is how it is being used (i.e. you're not making the connection from an environment where the app server could spawn multiple copies behind your back).
Other things that might be worth checking are that the topic connection factory contains an explicit queue manager name (the default should work, but I've seen it cause a problem in some circumstances), and that the Topic actually contains a topic name.
Cheers,
James. |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Fri Feb 14, 2003 1:27 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Try looking at the event broker documentation for these error messages:
http://publibfp.boulder.ibm.com/epubs/pdf/gipyal00.pdf
3157
MQRCCF_ALREADY_JOINED
A Join registration option was specified
but the subscriber identity was already
a member of the subscription’s identity
set.
Have you already got an identical 'test' subscription?
Cheers,
Vicky |
|
| Back to top |
|
|
| gerrie |
| Posted: Tue Feb 03, 2004 5:02 am Post subject: Re: WAS 5.0 Embedded Messaging ? |
|
|
Newbie
Joined: 03 Feb 2004
Posts: 2
|
If have exactly the same problem, but only in one special case:
The problem occurs when I set the durable subscriber queue of a topic to something like SYSTEM.JMS.D.MYDOMAIN.* (known as the multi-queue approach).
In all other cases it works fine!
I'm using Websphere MQ v5.3 on Win2000. Broker: MA0C (MQ Series Pub/Sub broker)
Is this a bug?
Gerrie |
|
| Back to top |
|
|
| gerrie |
| Posted: Tue Feb 03, 2004 10:10 am Post subject: Re: WAS 5.0 Embedded Messaging ? |
|
|
Newbie
Joined: 03 Feb 2004
Posts: 2
|
After upgrading to the latest CSD (WebSphere MQ v5.3 CSD5) it works fine ...
Gerrie |
|
| Back to top |
|
|
|
|
