Orphaned connection issue/keepalive HELP!!

2004-02-19 Thread Larry Murray
We run MQ 2.1 on OS/390

On windows and unix boxes lives a mutant version of code that executes MQ
Connects...opens...puts  ect  to the QMGR on the OS390.

We constantly have a buildup of connections that are unused for hours and
days.
To our installation, these are orphaned connections and cannot be reused.

The programmer who maintains the client code on the windows/unix boxes
tells
me that JAVA treats a connection as an object. If an object is not used for
a short
time(I know...not very descriptive..his words...and I am a mainframe
jockey) JAVA
will kill the object(connection)
When the connection is thus killed, MQ on the mainframe does not know it is
dead
and continues to carry the connection as active.

Is there something I can add to my mainframe system to determine if the
connection
is still active on the other end(windows/unix) and if not, drop the
connection on the mainframe side?

ThanksLarry

Larry Murray
Putnam Investments
Tech Services
1-617-760-3270

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Orphaned connection issue/keepalive HELP!!

2004-02-19 Thread Taylor, Neil
Use the TCP Keepalive setting, assuming you are using tcp.  It is a qmgr config item.

Neil

-Original Message-
From: Larry Murray [mailto:[EMAIL PROTECTED]
Sent: 19 February 2004 14:35
To: [EMAIL PROTECTED]
Subject: Orphaned connection issue/keepalive HELP!!


We run MQ 2.1 on OS/390

On windows and unix boxes lives a mutant version of code that executes MQ
Connects...opens...puts  ect  to the QMGR on the OS390.

We constantly have a buildup of connections that are unused for hours and
days.
To our installation, these are orphaned connections and cannot be reused.

The programmer who maintains the client code on the windows/unix boxes
tells
me that JAVA treats a connection as an object. If an object is not used for
a short
time(I know...not very descriptive..his words...and I am a mainframe
jockey) JAVA
will kill the object(connection)
When the connection is thus killed, MQ on the mainframe does not know it is
dead
and continues to carry the connection as active.

Is there something I can add to my mainframe system to determine if the
connection
is still active on the other end(windows/unix) and if not, drop the
connection on the mainframe side?

ThanksLarry

Larry Murray
Putnam Investments
Tech Services
1-617-760-3270

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive