[jacorb-developer] Client Connection Management: is there a leak?

[Wagner, Marcus (Marcus)]

Thanks, I will give it a try.


-----Ursprüngliche Nachricht-----
Von: jacorb-developer-bounces~marcuswagner=avaya.com at lists.spline.inf.fu-berlin.de [mailto:jacorb-developer-bounces~marcuswagner=avaya.com at lists.spline.inf.fu-berlin.de] Im Auftrag von Chun Tat David Chu
Gesendet: Donnerstag, 12. Juni 2014 14:54
An: Discussions concerning CORBA development with JacORB
Betreff: Re: [jacorb-developer] Client Connection Management: is there a leak?

I think there's couple things you could do.

1) On your client side, when you are finish with all your calls to the server then you can invoke '_release()' on your CORBA object to release the connection.

2) Take a look at the JacORB 3.4 programming guide that you can download from the JacORB website, particularly section 3.3 on the Configuration Properties.  You could set these properties and I think it should be able to help your situation.
On Client side
- jacorb.connection.client.idle_timeout : Client-side timeout. This is set to non-zero in order to close the connection after specified number of milliseconds idle time. Only connections that don’t have pending messages are closed, unless jacorb.connection.client.timeout ignores pending messages is turned on.
On Server side
- jacorb.connection.server.timeout : Maximum time in milliseconds that a server keeps a connection open if nothing happens

Good luck...

- dc


On Thu, Jun 12, 2014 at 5:00 AM, Wagner, Marcus (Marcus) < marcuswagner at avaya.com> wrote:

> 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  -
> jacorb-developer at lists.spline.inf.fu-berlin.de
> https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-develope
> r
>
_______________________________________________
jacorb-developer maillist  -  jacorb-developer at lists.spline.inf.fu-berlin.de
https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer