I could use a recommendation for working around a problem that arises when we try to start a listener container that has been stopped for a long time (ex: hours).
Here is the stack trace:
I'm still looking into why the connection gets closed (NMS 1.1 has a "keepalive" feature so technically the connection should not get dropped even when we stop accepting messages for awhile) but in the meantime is there any way to get the listener stared when this happens?
[2008-10-15 01:16:04,654] [GC.GTP.#1] [WARN ] [(null)] [(null)] [AbstractListenerContainer] Ignoring Connection start exception - assuming already started
Apache.NMS.ActiveMQ.ConnectionClosedException: The connection is already closed!
at Apache.NMS.ActiveMQ.Connection.CheckConnected() in c:\code\3rdparty\apache\activemq\nms\trunk\src\main\csharp\Connection.cs:line 400
at Apache.NMS.ActiveMQ.Connection.Start() in c:\code\3rdparty\apache\activemq\nms\trunk\src\main\csharp\Connection.cs:line 114
at Spring.Messaging.Nms.Connections.CloseSupressingConnection.Start() in c:\code\3rdparty\spring.net\trunk\src\Spring\Spring.Messaging.Nms\Messaging\Nms\Connections\SingleConnectionFactory.cs:line 489
at Spring.Messaging.Nms.Listener.AbstractListenerContainer.StartSharedConnection() in c:\code\3rdparty\spring.net\trunk\src\Spring\Spring.Messaging.Nms\Messaging\Nms\Listener\AbstractListenerContainer.cs:line 496