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?
see here http://www-128.ibm.com/developerworks/lotus/library/ls-Java_access_2/index.html
The part name “connection pooling” which talks about pooling multiple connections on a single (or defined) number of TCP connection. I think it may at least help.
(it’s not a pool of domino session like I first thought it was)