I'm having a little problem shutting down my OpenJMS
client after the
server has been stopped.

Here are a few steps to reproduce the problem:

1- Start OpenJMS server
2- Start the JMS client
3- Shudown OpenJMS server
4- In client close everything (subscriber, connection and
session)

After the last step the java program will not exit even
though all
threads have exited. When doing a "kill -QUIT" in Linux
the following
non-daemon thread shows up:

"EventManagerThread" prio=1 tid=0x0x8643510
nid=0x5042 in Object.wait()
[4da13000..4da13830]
at java.lang.Object.wait(Native Method)
- waiting on <0x44471570> (a java.lang.Object)
at java.lang.Object.wait(Object.java:426)
at org.exolab.jms.events.BasicEventManager.run
(Unknown Source)
- locked <0x44471570> (a java.lang.Object)
at java.lang.Thread.run(Thread.java:536)

Note that the process exits properly when the OpenJMS
server is still
running.

Environment:
OpenJMS 0.7.5
java version "1.4.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.4.1_02-b06)
Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed
mode)
RedHat 8
The client is a subscriber that implements the
MessageListener and
ExceptionListener interfaces.

Any help would be appreciated.

Thanks,
Francis



----------------------------------------------------------------------
Date: 2003-08-08 07:52

Message:
Logged In: YES
user_id=557161

Fixed in CVS. This will be available in the 0.7.6 release.

The connection implementation wasn't shutting down the
event service when the physical connection to the server
was lost.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=785039&group_id=54559