RP/TUX 8.1/TUX 9.1 - cnsbind cores when federating namespaces
(Doc ID 777178.1)
Last updated on JANUARY 19, 2018
Applies to:Oracle Tuxedo / Tuxedo / 8.1,9.1
Information in this document applies to any platform
DESCRIPTION: Customer is trying to get a CORBA C++ client to talk to EJBs via WTC. They are using cnsbind -C to federate the two namespaces (i.e., JNDI and CORBA CoS Naming) so that they can generate CORBA object references for the EJBs that they can use to invoke them via RMI-IIOP. They report that in the context binding done by cnsbind -C the command fails and a core dump is produced. Test reproducer: 1. Configure simpappcns example (examples.wtc.corba.simpappcns). 2. Boot WLS examplesServer 3. Boot Tuxedo from $TUXDIR/samples/wtc/simpappcns. 4. Make sure through dmadmin that domains TUXDOM and examples are connected . 5. In $APPDIR run: cnsbind -C -o EJBNaming.ior JNDI The EJBNaming.ior content is: corbaloc:tgiop:examplesServer/NameService This command fails with the core. Without the -C, the cnsbind doesn't core dump, but the IOR is simply imported as an [object], as shown by cnsls. This would (presumably) not allow them to see the EJBs in JNDI. CONFIGURATION: Tuxedo 8.1 with RP248 HPUX 11.0 (32-bit) PA-RISC WebLogic Server 8.1 with Service Pack 4
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document