[Bug 1000] New: COMM_FAILUREs in simple multithreaded client/server test starting with JacORB 3.4

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

            Bug ID: 1000
           Summary: COMM_FAILUREs in simple multithreaded client/server
                    test starting with JacORB 3.4
           Product: JacORB
           Version: 3.4
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: ORB
          Assignee: [email protected]
          Reporter: [email protected]

Created attachment 453
  --> http://www.jacorb.org/bugzilla/attachment.cgi?id=453&action=edit
Debug log

I have a simple multithreaded client to singlethreaded server test that works
fine from JacORB 2.4 - 3.3 which started throwing COMM_FAILUREs at me starting
with JacORB 3.4 (but also in 3.5).

The test implements a trivial client for the following IDL:
interface Foo
{
  string get_string(in long tid);
};

The server creates and activates a single servant and executes ORB#run in the
main thread.
The client resolves the servant reference, starts 2 threads and calls the
servant's get_string() method 10 times in each thread.
The client uses DII and the server DSI.

When running this with either JacORB 3.4 or 3.5 at a certain point in the
iterations COMM_FAILUREs appear. Detailed logging seems to suggest connections
are being unexpectedly closed at some point.

Attached a debug log of a fairly typical testrun.

Any ideas why this may have started happening from JacORB 3.4?

-- 
You are receiving this mail because:
You are the assignee for the bug.

_______________________________________________
jacorb-bugs mailing list
[email protected]
https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-bugs