[omniORB] Single-threaded behaviour changed between omniORB3 & omniORB4?

[Donnacha Forde]

Platform Mix: 
Solaris 8
gcc 3.2.1
omniORB-4.0.0

Has the default thread behaviour for dispatching
requests changed between omniORB3 and omniORB4? Even
for oneway calls?

I understand that the default behaviour is a server is
single-threaded, regardless of how many threads the
orb uses underneath the covers. In other words,
requests are delivered serially to your object/method
(unless you code it to be otherwise). 

I'm seeing behaviour contrary to this in a process
that supports a callback object (that supports a
oneway method). Occasionally, the method is being
invoked in parallel (i.e. at least two threads are
executing the method).

Now, it may just be the nature of the thread error but
it's only revealed itself since I began using
omniORB4.

Any ideas?

Regards, 
Donnacha


__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com