Client Connection Management: is there a leak?

Hi,

by now I am using JacORB 2.3.1. I have the problem, that my server process is running out of ClientRequestProcessor. Using JacORB 3.4, I do not have this problem anymore, but I am running out of native Threads.

Now I have found the following paragraph in the documentation:
16.2 Connection Management
When a client wants to invoke a remote object, it needs to send the request over a connection to the server. If the connection isn't present, it has to be created. In JacORB, this will only happen once for every combination of host name and port. Once the connection is established, all requests and replies between client and server will use the same connection.

This may be a good solution when you have a client application that connects to server processes. But I have a server and clients register callbacks at the server. As clients always use different IP's and ports, I assume, that the list of connections in the server is getting longer and longer without the chance to reuse any of the cached connections.
Am I right?
Is there a way to get rid of unused client connections?


Regards Marcus
_______________________________________________
jacorb-developer maillist  -  [email protected]
https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer