|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
Queue Destination in WAS console |
View previous topic :: View next topic |
Author |
Message
|
vennela |
Posted: Tue Oct 26, 2004 10:18 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Oct 26, 2004 11:27 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Hrm.
I'm using WSAD5.12... something may actually be hosed with my installation, I'm not sure.
When I try and do this with a WAS 5.0 Test Environment server, I end up losing my Server Configuration completely.
*poof*. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
bamboozled_by_MQ |
Posted: Tue Oct 26, 2004 7:55 pm Post subject: |
|
|
Voyager
Joined: 07 Jan 2004 Posts: 75
|
it appears it can only be set as an administrative task, not within the app.
( JMSC.MQJMS_CLIENT_NONJMS_MQ )
this is wierd, it isn't working for you either and it is blowing up Jeff's configuration.
still investigating..
let me know if you find anything
thx |
|
Back to top |
|
 |
vennela |
Posted: Wed Oct 27, 2004 12:12 pm Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Is there any specific reason that you are defining the JNDI JMS objects and then doing a look up. Because you can define them inline in your program.
This is from the manual in chapter 10.
Quote: |
The second, and more powerful, form is based on “uniform resource identifiers”
(URI). This form allows you to specify remote queues (queues on a queue
manager other than the one to which you are connected). It also allows you to
set the other properties contained in a com.ibm.mq.jms.MQQueue object.
The URI for a queue begins with the sequence queue://, followed by the name
of the queue manager on which the queue resides. This is followed by a further
“/”, the name of the queue, and optionally, a list of name-value pairs that set
the remaining Queue properties. For example, the URI equivalent of the
previous example is:
ioQueue = session.createQueue("queue:///SYSTEM.DEFAULT.LOCAL.QUEUE");
Note that the name of the queue manager is omitted. This is interpreted as the
queue manager to which the owning QueueConnection is connected at the time
when the Queue object is used.
The following example connects to queue Q1 on queue manager HOST1.QM1, and
causes all messages to be sent as non-persistent and priority 5:
ioQueue = session.createQueue("queue://HOST1.QM1/Q1?persistence=1&priority=5"); |
In your case you can use the queue name like
queue://HOST1.QM1/Q1?targetclient=1
Hope this helps. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Oct 27, 2004 2:23 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20763 Location: LI,NY
|
Check out the resources file for the corresponding JNDI definition of the queue. If the TargetClient="MQ" does not stick in the console, edit and modify the xml resources file and change it there. Then it will stick...
Enjoy  |
|
Back to top |
|
 |
bamboozled_by_MQ |
Posted: Thu Oct 28, 2004 8:59 am Post subject: |
|
|
Voyager
Joined: 07 Jan 2004 Posts: 75
|
I GOT IT!!!
thanks everyone. it is actually spooky how much you people know.
I'm excited because Im learning so much, I want to be part of "you people"
I hope I can return the favor one day.
one question:
so is this a bug?
if not what is causing this?
just wanted to know. |
|
Back to top |
|
 |
|
|
|
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
|
|
|
|