[jacorb-bugs] [Bug 967] New: ClientGIOPConnection/closeAllowReopen and threads

[bugzilla-daemon at jacorb.org]

http://www.jacorb.org/bugzilla/show_bug.cgi?id=967

            Bug ID: 967
           Summary: ClientGIOPConnection/closeAllowReopen and threads
           Product: JacORB
           Version: 3.3
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: ORB
          Assignee: jacorb-bugs at lists.spline.inf.fu-berlin.de
          Reporter: jacorb at goots.org

Currently, if for instance, a server is killed the client receives a 
COMM_FAILURE then the transport is closed down and the GIOP layer is 
kept 'open'.


However, the problem is that with this scenario we get a 
ClientMessageReceptor thread stuck in receive messages loop. Of course, 
if the client object is _release'd this would go away.

If the GIOP connection is closed in 
ClientGIOPConnection::closeAllowReopen i.e. close() is called (after 
being called from streamClosed) then the thread is released into the 
pool and the transport and giop layer are closed down.
However, this does not negate the possibility of calling the client 
object again - it should simply attempt to call the server again, 
reopening the connection/transport if required.

There appears to be a trade-off here between object creation/gc versus 
threads. If the client does not call release, it can cause thread pool
exhaustion as many threads are simply locked up waiting.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spline.inf.fu-berlin.de/pipermail/jacorb-bugs/attachments/20131015/17496145/attachment.html>