You are saying you have SwiftMQ running as an NT service ?
Can you please tell me, how you did it?
Best regards,
At 18:48 5.7.01 +0200, you wrote:
We have our queue receivers running as NT services, and they were done by different people different ways,
handling the threads and all, but the common practice was to :
public void onException(javax.jms.JMSException e)
{
lostConnection = true; // instance var
log.error("onException: ",e); // Log4J Category
errorPauseService(); // wait, with time stored in .properties file
}
and the "main" loop checked the flag and re-connected if needed.
Again, the specifcs depend on the actuall design. Some have the driver, and the listener
be the same class, so it implemented runnable and the loop was in run(). Some seperated them,
and the listener class notifies the driver class. The driver frees the listener, and creates a new one with
a new connection.
We've been messing with quite a few packages to help run as NT services and some work better than
others for certain things. We haven't yet standardized on one yet, so the handling hasn't either.
- -----Original Message-----
- From: Harry Hendrata [mailto:[EMAIL PROTECTED]]
- Sent: Thursday, July 05, 2001 11:17 AM
- To: [EMAIL PROTECTED]
- Subject: [developers] failsafe jms-client
- could you post the exception listener implementation?
- ----- Original Message -----
- From: Vago, John N
- To: [EMAIL PROTECTED]
- Sent: Tuesday, July 03, 2001 12:00 AM
- Subject: [developers] failsafe jms-client
- We just implement the ExceptionListener interface and
- try to re-connect when OnException() is called.
------------------------------------------------------ SwiftMQ developers mailing list * http://www.swiftmq.com To unsubscribe from this list, send an eMail to [EMAIL PROTECTED] and write in the body of your message: UNSUBSCRIBE developers Archive: http://www.mail-archive.com/developers@mail.iit.de/
