| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SYSTEM.JMS.REPORT.QUEUE |
« View previous topic :: View next topic » |
| Author |
Message
|
| gpklos |
 Posted: Wed Aug 12, 2009 11:45 am Post subject: SYSTEM.JMS.REPORT.QUEUE |
 |
|
Centurion
Joined: 24 May 2002
Posts: 108
|
I'm curious about the SYSTEM.JMS.REPORT.QUEUE queue. When a client subscriber makes a connection to the queue manager via a client connection and to the subscriber queue, does MQ automatically connect their client to SYSTEM.JMS.REPORT.QUEUE. We have an Oracle application that makes a connection to our queue manager which runs the basic MQ pub sub broker. He makes a connection to the subscriber queue and also seems to make numerous connections to the SYSTEM.JMS.REPORT.QUEUE queue. And he never cleans them up. Is this something the oracle application should clean up itself? I'm trying to figure out if this is a problem with MQ or an application issue. We are running MQ version 6.0.2.5 on windows. It seems that when the oracle application makes his initial connection to MQ and to the subscriber queue, he opens up 2 more connections to the SYSTEM.JMS.REPORT.QUEUE queue, but never cleans them up. Also, is this queue more for MQ's use or for the applications to use?
Thanks I appreciate any input.
Gary |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Aug 12, 2009 2:36 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
This seems to be more of an application issue.
You may need to specifically close the connection.
Usually the queues should disconnect when you close the session.
Make sure the application correctly releases resources before shutting down.
As well be very careful with how the developers coded a web application.
Poor coding can lead to a resource leak... 
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gpklos |
| Posted: Thu Aug 13, 2009 3:21 am Post subject: |
|
|
Centurion
Joined: 24 May 2002
Posts: 108
|
Thanks for the reply. I do tend to agree it is an application issue, but I still don't know whether the application is directly opening the SYSTEM.JMS.REPORT.QUEUE or does MQ do that on behalf of the subscriber automatically. The applications people don't understand why the SYSTEM.JMS.REPORT.QUEUE is open for input from their application code (which is from Oracle). As long as I know that MQ doesn't automatically do that for them, then I can confidently say the Oracle application is opening the SYSTEM.JMS.REPORT.QUEUE by design. And if I can say that then I know it is the applications problem and not MQ's. Would you agree?  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Aug 13, 2009 3:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| gpklos wrote: |
| Thanks for the reply. I do tend to agree it is an application issue, but I still don't know whether the application is directly opening the SYSTEM.JMS.REPORT.QUEUE or does MQ do that on behalf of the subscriber automatically. The applications people don't understand why the SYSTEM.JMS.REPORT.QUEUE is open for input from their application code (which is from Oracle). As long as I know that MQ doesn't automatically do that for them, then I can confidently say the Oracle application is opening the SYSTEM.JMS.REPORT.QUEUE by design. And if I can say that then I know it is the applications problem and not MQ's. Would you agree? |
Not necessarily. I thing the SYSTEM.JMS.REPORT.QUEUE may get opened because they are using a topic connection or have registered for a topic.
Now if they do not close correctly that connection you may have a resource leak that could translate into non closed connections on SYSTEM.JMS.REPORT.QUEUE. ...
With a tool like MO71 you can display the queue and see with the Queue Usage who has it open and what for.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gpklos |
| Posted: Thu Aug 13, 2009 6:04 pm Post subject: |
|
|
Centurion
Joined: 24 May 2002
Posts: 108
|
Thanks, so it sounds like you are saying that MQ possibly does open a connection automatically to that queue whenever someone makes a connection to a topic. So even though they may not be directly opening a connection to that queue, when they don't close properly then it could leave a connection out there to the queue. Oracle supposedly has a fix to try to clean up connections. I guess we will see if that cleans up the connections to the SYSTEM.JMS.REPORT.QUEUE. Thanks for your input.
Gary |
|
| 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
|
|
|
|
