[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jacorb-bugs
Subject:    [jacorb-bugs] [Bug 733] New: "oneway" messages can be silently
From:       bugzilla-daemon () inf ! fu-berlin ! de
Date:       2006-11-02 14:04:17
Message-ID: E1GfdB3-0006iY-00 () berners ! inf ! fu-berlin ! de
[Download RAW message or body]

http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=733

           Summary: "oneway" messages can be silently dropped under some
                    conditions
           Product: JacORB
           Version: 2.2.4
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P1
         Component: POA
        AssignedTo: tie@xtradyne.de
        ReportedBy: Serguei.Kolos@cern.ch
         QAContact: jacorb-bugs@lists.spline.inf.fu-berlin.de


I'm using omniORB C++ client sending a lot of oneway messages to the JacORB
server. Very often some of the messages are silently dropped because the
jacorb.poa.queue_wait JacORB configuration option is set by default to "off".
The issue is that if the POA request queue is full this setting should cause
TRANSIENT exception to be sent back to the client but this does not work for
"oneway" communication.
As a result messages get lost without any sign on the client or server side.

One more related point is:
It is of course my personal opinion but I believe that even for two-way
communications the default setting for the jacorb.poa.queue_wait parameter
should be "on". For most of the applications it is much more affordable to wait
some time instead of bothering with exception handling and request
retransmittion. The ones which would prefer to get a quick but bad response are
clearly a minority according to my experience.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.


[prev in list] [next in list] [prev in thread] [next in thread]