TCP connection leakage with Corba sessions?

Saw an interesting post (how to close lotus.domino.Session in Java application?) on notes.net 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?

Domino Session Tester updated

The Domino Session Tester mentioned yesterday has been updated so you can test whether the user in question can connect to a particular database. You can also test access a particular document (based on UNID). The download on the original post now points to the new version.

The new command line switches are -s (server), -d (database) and -u (universal id).