TCP connection leakage with Corba sessions?

Saw an interesting post (how to close lotus.domino.Session in Java application?) on from a developer who is wondering how to avoid TCP connection leakage with a lotus.domino.Session pool. Only thing I could come up with is recycle() and nullifying. I haven’t had problems with connection leakage in similar situations but I guess it is possible.

Does anyone know of a way to force closure of the TCP connection?

One thought on “TCP connection leakage with Corba sessions?”

Comments are closed.