[omniORB] Omniorb vs. Jacorb interoperability

[Wilson Jimmy - jiwils]

What does your interface look like, and what types of data are you sending
the server? 

We use JacORB on the client side to talk to TAO servers (omniORB has only
been used in testing...sigh).  The JacORB client-side does indeed multiplex,
but this is only a problem when the server side takes a long time and/or the
amount of data being sent across the wire is extremely large.  In the past 3
years, we have only had a single situation where JacORB did not perform due
to client-side multiplexing, however in that situation, something akin to
single-threaded behavior did appear to be happening (obviously).  We have
been investigating how to add an omniORB-like connection model to JacORB for
these types of situations, and I have posted to the JacORB mailing list
about this specific issue.

If you want to talk more specifically about JacORB, you can mail me
directly.  I am sure that this list does not care about Java ORBs too much!
;)

Jimmy
-- 
James "Jimmy" Wilson
Software Developer, Acxiom Corporation

-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Renzo
Tomaselli
Sent: Thursday, September 16, 2004 4:09 AM
To: Omniorb list
Subject: [omniORB] Omniorb vs. Jacorb interoperability

Hi all,
    one of our projects deals with interfacing a multithread java client
application with a server process written in C++, using Omniorb 4.03. On the
client side, we have several concurrent threads.
Being tired with protocol errors we got from java Openorb, then we switched
to Jacorb, latest version. It seems working, but the server process debugger
says there is always one active thread at the time, servicing upcalls from
the client (e.g. strong serialization).
We left "maxServerThreadPerConnection" to its default of 100 and on the
other hand, the Jacorb manual states that only one connection is opened to
the same target (unlike Omniorb). It should multiplex concurrent messages
along this connection (not clearly stated, though).
While I guess it shouldn't be an Omniorb problem, I wonder if anybody had
similar troubles with Jacorb.
Thanks,

Renzo Tomaselli


_______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list


**********************************************************************
The information contained in this communication is
confidential, is intended only for the use of the recipient
named above, and may be legally privileged.
If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, 
distribution, or copying of this communication is strictly
prohibited.
If you have received this communication in error,
please re-send this communication to the sender and
delete the original message or any copy of it from your
computer system. Thank You.