[jacorb-bugs] [Bug 975] New: A client fails to receive replies from reconnected server instances

bugzilla-daemon at jacorb.org bugzilla-daemon at jacorb.org
Thu Jan 30 09:04:07 CET 2014


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

            Bug ID: 975
           Summary: A client fails to receive replies from reconnected
                    server instances
           Product: JacORB
           Version: 3.4
          Hardware: All
                OS: All
            Status: NEW
          Severity: blocker
          Priority: P5
         Component: ORB
          Assignee: jacorb-bugs at lists.spline.inf.fu-berlin.de
          Reporter: matej.sekoranja at ijs.si

Created attachment 429
  --> http://www.jacorb.org/bugzilla/attachment.cgi?id=429&action=edit
Client/server code that demonstrates the problem.

A PERSISTENT, USER_ID POA configured server that runs on a fixed port causes
a reconnection failure to the clients. In fact clients do reconnect and send a
request the server, however they are unable to receive any responses.

This can be reproduced deterministically on 3.4. Version 2.2.4 does not suffer
from this problem. Only client side is affected (running 2.2.4 client against
3.4 sever works).

I've created a simple isolated code that shows the problem with detailed
instructions in README (attached).

In short:
1. Start a server.
2. Start a client.
3. A client sends a request to the server, gets response back. Waits until you
press ENTER key.
4. While the client is waiting, you restart the server.
5. Press ENTER key.
6. The client sends a request to the server, the server receives it.
7. Client gets no response back (blocks).

-----

Detailed analysis: 

When the server shuts down the client detects a connection loos, however it
keeps a connection objects in a ClientConnectionManager connection pool;
meanwhile the server gets restarted.

When the client tries to invoke an two-way operation on the server, it founds
an instance in its ClientConnectionManager connection pool. It checks the
connection status, detects it's not connected, successfully reconnects and
sends a request to the server. However, a receiver task (MessageReceiver) is
not restarted what makes the client unable to receive any responses from the
server.

-- 
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/20140130/6997e82f/attachment.html>


More information about the jacorb-bugs mailing list