JDK 1.4 ORB vs. JacORB and thread management policy
843793Aug 9 2002 — edited Sep 19 2002
I stopped using Orbix because it wasn't able to communicate reliably
with a C++ TAO server. The JDK 1.4 ORB seems to "work". But it is
slow and memory-hungry. 70% of the CPU time of my client goes into
marshalling and unmarshalling, as far as I can tell using various
profiling tools. Worse, when the CPU is saturated, further
incoming CORBA requests cause further thread spawns, which cause
further cycle scarcity, which cause more thread spawns, etc.
I have two questions:
1) In your experience, does JacORB perform better than the ORB that
comes with JDK 1.4.0.
2) Can I have finer control over the Thread policy, beyond choosing
between ORB_CTRL_MODEL and SINGLE_THREAD_MODEL? I'd like to
specify a connection queue size, and a max number of threads in the
pool.
Thank you.
Juan Leon