Peter M. Goldstein wrote:
Steve,I did a little digging into James and can confirm that James is doing what it should do. The problem appears to be in the Merlin dissassembly process. When a component is terminated, Merlin makes sure that any compoennts consuming the comoponent's services are terminated before the target of the original termination request. I'm runing some test and I've spotted an inconsitency - the connection component is being terminated as a result of a termination request for James (which is incorrect) - more digging to do on my side.
During test I discovered that James was logging a disposal error
resulting from releasing the ports for the SMTP, POP3 and Remote Admin
services during the sutdown phase. I checked the cause ant it was that
the disconnect was being invoked twice. I didn't dig into why.
Which then raises the question - why are the connection being disconnect
twice?
I'll do some digging.
No idea why you'd be seeing this. There is just the single disconnect in the dispose() method of the AbstractHandlerFactory. Obviously, dispose() should be called just once for each service.
:-(
Cheers, Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
