| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Channels keep running, even though connection has been stop |
« View previous topic :: View next topic » |
| Author |
Message
|
| middlewareonline |
 Posted: Mon Jan 20, 2003 2:40 pm Post subject: Channels keep running, even though connection has been stop |
 |
|
Acolyte
Joined: 09 Jul 2001
Posts: 73
|
We are using MQ JMS in Stateless Session EJB''s with Weblogic server.
Each bean does createConnection, createSession, createSender, send
creteReceiver, get and close/stop all the handles (inlcuding connection).
Closing/Stopping is done in finally block (so it is getting executed).
We see that the netstat on the client machine increases and remains even
after the EJB''s have done stop on the connection. We are setting useconnpool
in JMSAdmin to ""Y"". But, I don''t think that is what is causing the problem.
The SVRCONN channels keep running long after the client has completed the
send/receive/close sequence. The HB interval is 300 on SVRCONN channels. We
are using MQ Series Classes for Java (MA88) version 5.2 ( NOT 5.3) on sun
solaris. Also, the number of ESTABLISH connection is NOT equal to the
SVRCONN channel instances. We see more connections opened on Client machines
than there are Schannel running on the queue manager machines (also, fewer
amqcrsta processes).
Any pointers as to why the conenctions still show in ESTABLISHED state and
channels keep running.
Thank you.
Chris |
|
| Back to top |
|
 |
| yaakovd |
| Posted: Thu Jan 23, 2003 6:34 am Post subject: |
|
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
Server Connection chanel is not disconnected automatically.
We fixed this problem in past...
//All objects from javax.jms.*
protected QueueConnection connection;
protected QueueSession sessionSender;
protected QueueSession sessionReceiver;
protected QueueSender sender;
protected QueueReceiver receiver;
public synchronized boolean isConnected() {
return connection != null;
}
public synchronized void disconnect() throws Exception {
if (!isConnected()) {
return;
}
if (sessionSender != null) {
sessionSender.close();
}
if (sessionReceiver != null) {
sessionReceiver.close();
}
if (connection != null) {
connection.stop();
connection.close();
}
sender = null;
receiver = null;
sessionSender = null;
sessionReceiver = null;
connection = null;
}
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| Back to top |
|
|
| middlewareonline |
| Posted: Fri Jan 24, 2003 7:12 am Post subject: |
|
|
Acolyte
Joined: 09 Jul 2001
Posts: 73
|
Thank you for your input. Have you used USECONNPOOL (Y) option of JMSAdmin or w/o it. I know it probably has no bearing on it in your case.
_________________
---------------------------------------------
IBM & SUN (J2EE) Certified Consultants,
http://www.MiddlewareOnline.com
A "SARVAM" Online Portal
http://www.SARVAM.com
--------------------------------------------- |
|
| 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
|
|
|
|
