<< I wonder what IBM is up to... | Home | Comment feed for developerWork blogs? >>

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?

Tags : ,
Responses[1] RSS feed for responses to this blog entry
Posted by Mikkel Flindt Heisterberg on 15 March 2007 09:42:52 CET #


Avatar: Michael Bourak
Reply

Re: TCP connection leakage with Corba sessions?

Comment from Michael Bourak on 16 March 2007 10:36:24 CET #
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)

Add a comment Send a TrackBack