org.jacorb.poa.POA._getChildPOA seems to make an assumption that any 
application writer will only have ONE java corba process PER MACHINE.  It logs 
the following type of exception when you try to connect to ANOTHER java corba 
process with a DIFFERENT POA name on the SAME machine:
[jacorb] ERROR : org.omg.CORBA.OBJECT_NOT_EXIST: no adapter activator exists 
for BackupFileReadServiceImplPOA
Not only that, but it prints a long stack dump on every attempt to connect to 
the other jvm on the SAME machine, REGARDLESS of whether that connection can or 
can't be made.  (Stack trace shown at end of bug description).
This is on a _non_exist call.  Although _non_exist will return me either true 
or false, depending on whether the object is really up or not, this 
excessive/wrong ERROR logging is filling up our own error log file with 
extraneous, NON-ERRORS.
*** Although I know that there is a facility to redirect jacorb errors to 
jacORB's own log file, I really don't want this.  I want the jacorb errors 
interspersed with our own errors so we can see the connection between what we 
were doing at the time and what caused jacorb to generate errors.
Here is a typical stack trace, of which we have hundreds generated every few 
minutes:  (There is more, but I've only printed what is relevant:
[NeMoWFault]:[jacorb] ERROR : org.omg.CORBA.OBJECT_NOT_EXIST: no adapter 
activator exists for BackupFileReadServiceImplPOA
12/04 10:44:13:ERR:[NeMoWFault]:	at org.jacorb.poa.POA._getChildPOA
(Unknown Source)
12/04 10:44:13:ERR:[NeMoWFault]:	at org.jacorb.orb.ORB.findPOA(Unknown 
Source)
12/04 10:44:13:ERR:[NeMoWFault]:	at org.jacorb.orb.Delegate.resolvePOA
(Unknown Source)
12/04 10:44:13:ERR:[NeMoWFault]:	at 
org.jacorb.orb.Delegate.is_really_local(Unknown Source)
12/04 10:44:13:ERR:[NeMoWFault]:	at org.jacorb.orb.Delegate.non_existent
(Unknown Source)
12/04 10:44:13:ERR:[NeMoWFault]:	at 
org.omg.CORBA.portable.ObjectImpl._non_existent(Unknown Source)

***** Please note that BackupFileReadServiceImplPOA is what we're trying to 
connect to.  However, the process that is trying to make the connect to 
BackupFileReadServiceImplPOA is NeMoWFaultImplPOA, which is a different named 
POA.
**** This error will be dumped regardless of whether 
BackupFileReadServiceImplPOA is up or not.  IN this case, it WAS up.