Hello Terry,

The JDK 1.4 ORB works pretty well for us. We stumbled about two obstacles:
* the poa's active object map does not scale - you cannot export too many
objects
* the ORB does a reverse DNS lookup of each client connection in a critical
section; if your DNS
happens to hang, your ORB will too

We're not using any advanced features beyond POA ServantLocator. No nameservice
or initial references.

The unfortunate end of the story: the ORB seems to have been rewritten completely
in Java 5 and we're
experiencing ugly hangs here. That's our showstopper to Java 5 so far. So
right now we're considering JacORB instead ...

Can it be so hard? All I actually want is a library that allows me to do
efficient RPC with a byte[] payload; that does proper
connection handling, thread-pooling, SSL, and allows me to have multiple
outstanding requests on one connection that return in
any order - the latter rules out the popular HTTP remoting protocols for me.

Cheers
Matthias

Hi Terry,

++ Does any CORBA export know which one to choose now Sun ORB or Jac ORB?
++
++ So far I know:
++ Advantage of JacORB: stable, scalable, well documented, with excellent
++ configuration files,  suppors debugging print out at specified level. But
++ the deployment is not easy since there are more than 5 jar files to include.
++
++ However Sun's ORB is much easier for deployment on the client side. However
++ some people indicate the Sun's implementation is buggy. Previously there was
++ a problem with name service but fortuately I don't use name service at all.
++
++ So my question is :   Is there any reason why I should not use the Sun's
++ ORB?

Sun's ORB is VERY buggy and poorly supported - you'll go nuts if you
have to do anything non-trivial with it.  I recommend using JacORB.

Take care,

       Doug