[jacorb-developer] Running out of Threads

Wagner, Marcus (Marcus) marcuswagner at avaya.com
Mon Feb 3 10:47:54 CET 2014


Thanks for your help,

Actually  there are no _release()'s at one point in code. I will spend a try...


Regards


> -----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 Nick Cross
> Gesendet: Freitag, 31. Januar 2014 17:03
> An: Discussions concerning CORBA development with JacORB
> Betreff: Re: [jacorb-developer] Running out of Threads
> 
> 
> On 31/01/14 14:34, Wagner, Marcus (Marcus) wrote:
> > I cannot retest with the current version easily, because it is a
> > production system, where we cannot simply replace components. (we
> > changed from 2.2.4 to 2.3.1, but there was no effect; PS: I even don't
> > think, that this is an error within JacORB.)
> >
> > As I am not the "inventor" of the process, I am not sure if
> > _release() is called every time. What I need to say is, I cannot
> > reproduce the system in the lab, so there need to be "some"
> > _releases() in the code.
> >
> > I need one hint. When does the ClientReceptor pool comes in place. Is
> > this when I am a server, that hosts CORBA objects. Or am I working
> > with this pool when I am a client that uses remote CORBA server
> > objects? The information when the ClientReceptor pool is used in an
> > methods round-trip is very helpful for me, because then I know in
> > which part I need to search for a _release().
> 
> The latter.
> 
> Regards
> 
> Nick
> _______________________________________________
> jacorb-developer maillist  -  jacorb-developer at lists.spline.inf.fu-berlin.de
> https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer


More information about the jacorb-developer mailing list