| Author |
Message
|
| smeunier |
 Posted: Thu Apr 12, 2007 1:25 pm Post subject: Using non-default SYSTEM.JMS queue errors |
 |
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
I have a subsriber, that when I set: factory.setBrokerSubQueue method to anything other than the default JMS subscriber queue (i.e. SYSTEM.JMS.D.SUBSCRIBER.QUEUE) So for instanace I set it to SYSTEM.JMS.D.R3
I get the following error.
javax.jms.JMSException: MQJMS3021: Invalid subscriber queue prefix: SYSTEM.JMS.D.R3
According to documentation found by googling this topic, I just need to prefix with SYSTEM.JMS.D and it should work. I have tried may variations with the same results.
Any ideas? My intention is to have multiple application durable subscribers, subscribe to their own static subscription queues(do not want to use dynamic queues). |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Apr 12, 2007 1:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you tried going one . further?
Like SYSTEM.JMS.D.SUBSCRIBER.R3 ?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smeunier |
| Posted: Fri Apr 13, 2007 4:46 am Post subject: |
|
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
| Yes, I have tried that and about every other variation known to mankind. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri Apr 13, 2007 5:08 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri Apr 13, 2007 5:14 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| smeunier |
| Posted: Fri Apr 13, 2007 5:31 am Post subject: |
|
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
So hears the deal. My subscriber has a switch for Durable/non-Durable subscriptions. I had it set to Non-Durable and was trying to subscribe to a durable queue (Doh!). Hence the message on the prefix mismatch. Apparently type matching is done at the session level when a subscriber is created and the subscription is being registered.
Operator error! My apologies. But lessoned learned. |
|
| Back to top |
|
|
|
|
