|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Problem with JMS handles |
« View previous topic :: View next topic » |
Author |
Message
|
tleichen |
Posted: Mon Mar 24, 2008 7:17 am Post subject: Problem with JMS handles |
|
|
Yatiri
Joined: 11 Apr 2005 Posts: 663 Location: Center of the USA
|
We have noticed that our JMS applications have multiple (very many) handles to the same queues, mainly SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE, SYSTEM.JMS.REPORT.QUEUE and SYSTEM.BROKER.CONTROL.QUEUE. It is not unusual for me to see 30 or 40 handles going from the same PID. Is this a flaw in JMS, or does this say something about the way the JMS application is written? BTW, this is on a Windows platform with the JMS apps talking via a client connection. Keep in mind, I'm not a Java expert.  _________________ IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Mar 24, 2008 2:06 pm Post subject: Re: Problem with JMS handles |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
tleichen wrote: |
We have noticed that our JMS applications have multiple (very many) handles to the same queues, mainly SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE, SYSTEM.JMS.REPORT.QUEUE and SYSTEM.BROKER.CONTROL.QUEUE. It is not unusual for me to see 30 or 40 handles going from the same PID. Is this a flaw in JMS, or does this say something about the way the JMS application is written? BTW, this is on a Windows platform with the JMS apps talking via a client connection. Keep in mind, I'm not a Java expert.  |
I would expect this to be normal. Especially if nobody defined in the jndi a different queue for the subscription messages to come to.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
tleichen |
Posted: Tue Mar 25, 2008 6:46 am Post subject: Re: Problem with JMS handles |
|
|
Yatiri
Joined: 11 Apr 2005 Posts: 663 Location: Center of the USA
|
Yes, but we supposedly don't have that many apps using MQ on these systems. Another note... we are using version 5.3. Also, within the MQ channel display, I see many presumably "orphaned" channel connections that still say they are in a RUNNING state, even though the last message timestamp on them is many hours or even days ago.  _________________ IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Mar 25, 2008 2:46 pm Post subject: Re: Problem with JMS handles |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
tleichen wrote: |
Yes, but we supposedly don't have that many apps using MQ on these systems. Another note... we are using version 5.3. Also, within the MQ channel display, I see many presumably "orphaned" channel connections that still say they are in a RUNNING state, even though the last message timestamp on them is many hours or even days ago.  |
Well your apps or network are not well behaved.
a) your apps are not closing the connection correctly
b) your network suffers from interruptions or microcuts.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
tleichen |
Posted: Tue Apr 01, 2008 6:45 am Post subject: Re: Problem with JMS handles |
|
|
Yatiri
Joined: 11 Apr 2005 Posts: 663 Location: Center of the USA
|
fjb_saper wrote: |
I would expect this to be normal. Especially if nobody defined in the jndi a different queue for the subscription messages to come to.
Enjoy  |
Looking back on this, I think this is something I would like to try for various reasons. How is this done? Do you simply define the queue and put it in the TCF parameters, or is there more to it than that? Also, is it the TCF parms that go to the broker, or what is it that defines these as broker queues?  _________________ IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Apr 01, 2008 6:21 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
The subscriber queue is in the definition of the topic. As the topic is often defined in JNDI this is where I would look first.
You can use JMSAdmin with a file JNDI for that.
Now in your program display the topic name and you will see the URI form...
Also if you use WebSphere Message Broker, or MQBroker you should be able to use RFHUtil for your subscription... You can then use a QCF with a QueueReceiver to get the published messages off the queue. You will see the topic in the messages' Destination. You will just not be able to filter on any of it using a QCF....
Enjoy  _________________ MQ & Broker admin |
|
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
|
|
|
|