Durable Subscriber

Hi:

I've been using Openjms quite happily for the past year.  I have been using 
non-persistent messages on a single topic without any problems at all.  I 
now need to use persistent messaging to a durable subscriber.  Basically, if 
the client runs into a problem, it needs to deactivate itself and allow 
messages to build up in the database.  Once the client knows that the 
problem has passed, it needs to reestablish its connection and pick up where 
it left off.

To deactivate, I am attempting to close the subscriber.  I find that this 
just hangs.  I have also attempted to null out the references to the topic, 
session and subscriber and then when I try to recreate these I get a message 
that the durable subscriber already exists.  However, if I exist the app 
completely and start up again, all is well.  I had thought of setting the 
messagelistener of the subscriber to null, but I would much prefer to 
understand what is best practice here.

Thnx.

Josh




-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642