| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| lot of socket entries in var/<qmgrname>/@ipcc/ssem |
« View previous topic :: View next topic » |
| Author |
Message
|
| pulak |
 Posted: Thu Aug 05, 2004 2:36 am Post subject: lot of socket entries in var/<qmgrname>/@ipcc/ssem |
 |
|
Newbie
Joined: 05 Aug 2004
Posts: 1
Location: Tokyo
|
Hello,
I have java application which connects to MQ for putting the message.
My program runs continuous in a day and executes block of a code after each sleep.
In a block of a code,my application connect to QueueManager and disconnect(qmgr.disconnect()) while coming out before going for sleep.
This program is executing with out any problem for a while.
However our MQ support is warning us that we are creating lot of socket entries, as we can see in /var/mqm/qmgrs/<qmgrname>/@ipcc/ssem
As of now, it has created around 75,000 socket entries against a safe limit of 250-300 socket entries.
Can somebody tell me, why it's creating so many socket entries and what's the impact of this in a long run.
Any help in this will be really helpful to us.
Thanks in advance.
_________________
Pulak Chakravarty |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Aug 05, 2004 4:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
How long is your application sleeping?
In Java, it would be better to build a connection pool of some sort and not disconnect unless you need to. Java connections don't get closed or garbage collected very rapidly.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Aug 05, 2004 5:25 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| What version of the WMQ code are you running? |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Thu Aug 05, 2004 6:44 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
Sniff, sniff. It smells as though you never disconnect but just keep on establishing new connections. Why are you disconnecting (or think you are disconnecting) before you go to sleep?
I have written many Java applications that do similar things to what you are doing. There are 2 ways to handle it:
1) After the app. wakes from its sleep do isConnected() call. If you have lost the connection then reconnect and reopen the queues.
2) Wait for an exception to happen after you wake from your sleep. Typically, it is 2009 (Connection Broken). If an exception is thrown then reconnect and reopen the queues.
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| 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
|
|
|
|
