|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
JMS/MQSeries temporary queue |
« View previous topic :: View next topic » |
Author |
Message
|
jackie |
Posted: Mon Jun 02, 2003 6:59 pm Post subject: JMS/MQSeries temporary queue |
|
|
 Novice
Joined: 01 Jun 2003 Posts: 20 Location: NYC
|
I have been using two NT machines installed MQSeries. One is sending a message to the second one. Upon receiving messages, MDB in the second will process and send its reply back to the first machine using temporary queue out of model queue.
Now, I have third MQ client machine sending its request through the first MQ server to the second. I have been able to send the message from my machine to the first one to the second one. The reply sent back to the first one.
Now when the message is coming from the first one back to my machine, I am having a problem with "Invalid dynamicPrefix: AMQ.*". The temporary queue is being created with AMQ.* prefix anyway. Any insights would be appreciated. |
|
Back to top |
|
 |
bower5932 |
Posted: Tue Jun 03, 2003 8:44 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
There are a couple of JMS programs at:
http://www.developer.ibm.com/tech/sampmq.html
called mqjmsreq.java and mqjmssrv.java. The requester can either use a dynamic queue or a permanent. You might want to look them over and see if you spot anything in relation to your program. |
|
Back to top |
|
 |
jackie |
Posted: Tue Jun 03, 2003 11:41 am Post subject: |
|
|
 Novice
Joined: 01 Jun 2003 Posts: 20 Location: NYC
|
thanks for your kind reply, but here is one more twist. It works fine under MQ bindings. I have installed MQ on two NT machines and between them, no problems with my application which is very similar technique as the example.
However, now I am going one more step higer, I have another developer machine which wants to send a message to machine A which has a target queue to machine B to process. Getting reply from B to A back was successful, but from A to the developer machine is where the problem occurs.
The developer's machine does not have any MQ installed other than MQ admin objects bound with the machine A MQ objects.
And, trying to figure it out. |
|
Back to top |
|
 |
jackie |
Posted: Mon Jun 16, 2003 10:53 am Post subject: |
|
|
 Novice
Joined: 01 Jun 2003 Posts: 20 Location: NYC
|
I found a solution finally and would like to post the result anyway.
The problem was related with authentication among different queue managers. After i did go through "setmqaut ...", it finally showed off its stuff. Glad!!! |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|