[omniORB] oneway calls delivery sequence

[Ivanov, Roumen]

Hi,
 
we have been using omniORB 3.0.3 for a long time in our implementation of
something similar to the notification service.
The messages have seq-numbers assigned to them and are sent using oneway
calls from the same thread.
 
After migrating to omniORB 4.0.3 (all default policies and flags) I’m
observing, that sometimes, newer messages from same client come on the other
side after older ones.
For examle:
received msg 1.
received msg 2.
received msg 3.
received msg 4.
received msg 5.
received msg 7. 
received msg 6. !!!!! The sequence is broken.
received msg 8.
 
This happens only when a bunch of messages has been sent.
Indeed I still could not confirm on which side this happens.
 
Guessing something, I tried setting maxGIOPConnectionPerServer = 1 for both
sides, but it didn’t help.
 
Reading the CORBA specification I couldn’t find anything, that confirms or
negates some sequence break for oneway calls.
 
I need some help in understanding what could be causing this?
Is this expected behaviour with oneway calls (with some change in omniORB
4)?
What could I do in order to prevent breaking the order?  (the calls should
remain oneway)
 
Thanks in anticipation,
Roumen
 


--------------------------------------------------------------------------------
The information contained herein is confidential and is intended solely for the
addressee. Access by any other party is unauthorised without the express
written permission of the sender. If you are not the intended recipient, please
contact the sender either via the company switchboard on +44 (0)20 7623 8000, or
via e-mail return. If you have received this e-mail in error or wish to read our
e-mail disclaimer statement and monitoring policy, please refer to 
http://www.drkw.com/disc/email/ or contact the sender. 3167
--------------------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20050331/29929ca3/attachment.htm