I get the following trace in the Jaguar log file when attempting to make an
inter-orb call from a Jaguar component to a visibroker orb:

****************************************************************************
Mar 17 15:06:30 2000: org.omg.CORBA.TRANSIENT:
Mar 17 15:06:30 2000: at
com.sybase.CORBA.iiop.Connection.ping(Connection.java:1467)
Mar 17 15:06:30 2000: at
com.sybase.CORBA.iiop.Connection.openConnection(Connection.java:724)
Mar 17 15:06:30 2000: at
com.sybase.CORBA.iiop.Connection.connect(Connection.java:938)
Mar 17 15:06:30 2000: at
com.sybase.CORBA.iiop.Connection.<init>(Connection.java:993)
Mar 17 15:06:30 2000: at
com.sybase.CORBA.iiop.Connection.connect(Connection.java:1128)
Mar 17 15:06:30 2000: at
com.sybase.CORBA.iiop.Connection.request(Connection.java:1177)
Mar 17 15:06:30 2000: at
com.sybase.CORBA.ObjectRef.__request(ObjectRef.java:113)
Mar 17 15:06:30 2000: at
com.sybase.CORBA.ObjectRef._is_a(ObjectRef.java:218)
Mar 17 15:06:30 2000: at
bank.AccountManagerHelper.narrow(AccountManagerHelper.java:29)
Mar 17 15:06:30 2000: at
com.gtms.testtool.componenttesterImpl.observerTest(componenttesterImpl.java:
104)
Mar 17 15:06:30 2000: at
com.gtms.testtool._sk_testtool_GTMSComponentTester.invoke(_sk_testtool_GTMSC
omponentTester.java:46)
Mar 17 15:06:30 2000: System exception 'TRANSIENT' thrown by component
'testtool/GTMSComponentTester' method 'observerTest'
----------------------------------------------------------------------------
---
IIOP putMessage Hexadecimal [padding] (interpretation) ISO 8859-1
encoding
--------------- - ---------------------------------------- -----------------
---
putOctet > 47 (71) G
putOctet > 49 (73) I
putOctet > 4F (79) O
putOctet > 50 (80) P
putOctet > 01 (1) .
putOctet > 00 (0) .
putBoolean > 00 (FALSE) .
putOctet > 01 (1) .
putULong > 00000000 (0) ....
putMessage | GIOP version = 1.0

| flags = 0 ('>' big endian)

| message type = 1 (Reply)
putReply | service context length:
putULong > 00000000 (0) ....
putReply | request id:
putULong > 0000042E (1070) ....
putReply | reply status (SYSTEM_EXCEPTION):
putULong > 00000002 (2) ....
putReply | reply body:
putULong > 00000020 (32) ...
putString > 49444C3A6F6D672E6F72672F434F5242412F5452
IDL:omg.org/CORBA/TR
414E5349454E543A312E3000 ANSIENT:1.0.
putULong > 00000000 (0) ....
putULong > 00000001 (1) ....
endMessage | message size = 56 (after 12 byte header)

****************************************************************************
I'm using an IOR for the call like this to get the remote object reference:

String s_ior = "IOR:00<rest of IOR here>";

_coAccountMgr = AccountManagerHelper.narrow(_orb.string_to_object(s_ior));

If I use a bad IOR, or if my visi server is down, I get
OBJECT_DOES_NOT_EXIST or COMM_FAILURE exceptions. When I use the correct
IOR, I get the above TRANSIENT corba exception. Any thoughts would be
greatly appreciated as this is high priority. Thanks.

Phil