[omniORB] Bug? Calls serialization in omni4.0.1

[baileyk at schneider.com]

I run both WebSphere (v4 and now v5 too) and omniORB on Solaris E10K
hardware, with system images of up to 12 processors I think.  Sorry I
missed the detail in your post.

Some of the calls to the CORBA server in my app run for quite a long time
(minutes) while others are fast.  I can't say for sure that under load
WebSphere never opens more than one connection to omniORB, but in testing
it sure appeared to multiplex all calls on a single connection.  If all
these calls were serialized it would be a disaster.

Have you turned tracing on in the omniORB server (with thread tracing) and
verified that concurrent requests are being handled sequentailly by a
single thread?  Your first post quoted some CPU utilization numbers which
suggest such, but are you sure?  Maybe there's something else going on?

Kendall



                                                                                                                             
                      Dmitry Davidovich                                                                                      
                      <DmitryD at enigma.c        To:       "'baileyk at schneider.com'" <baileyk at schneider.com>                   
                      om>                      cc:       "'omniorb-list at omniorb-support.com'"                                
                                                <omniorb-list at omniorb-support.com>                                           
                      07/01/2003 10:04         Fax to:                                                                       
                      AM                       Subject:  RE: [omniORB] Bug? Calls serialization  in omni4.0.1                
                                                                                                                             
                                                                                                                             




I stated that I use  -ORBoneCallPerConnection 0 command line option.
My tests started from WebSphere 4 as a client and I observed the same
problem.
How do you configure WebSphere and omni? Do you run it on Win2k multi CPU?

Dmitry

-----Original Message-----
From: baileyk at schneider.com [mailto:baileyk at schneider.com]
Sent: Tuesday, 01 July 2003 16:17
To: Dmitry Davidovich
Cc: 'omniorb-list at omniorb-support.com'
Subject: Re: [omniORB] Bug? Calls serialization in omni4.0.1



Your test does not reflect the behavior of the Java client ORB, I think.
AFAIK omniORB will not multiplex calls to a server over a single
connection.  There is a config parameter called "oneCallPerConnection"
which defaults to 1.  I've never changed it, but setting it to zero may get
your test case to behave more like the Java ORB.  I use WebSphere ->
omniORB and it does not serialize the requests even though WebSphere is
multiplexing the requests over a single connection.

Kendall