RP/TUX 8.0, TUX 8.1 - WTC CORBA.INTERNAL error in transactional EJB to Corba call (Doc ID 771850.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo / Tuxedo / 8.0, 8.1
Information in this document applies to any platform

Goal

TUX 8.0 on WLS 6.1 SP3
Calling a modified version of the cnssimpapp Tuxedo8.0 Corba Service via WTC from an WLS EJB (simpappcns sample) with
transactions (RequiresNew) fails. The cnssimpapp has been modified so the EJB on WLS has as transactional setting
"RequiresNew" for the remote interface and the cnssimpapp (simple_server) on Tuxedo 8.0 is modified to be
able to participate in a transaction. The Tuxedo8.0 ULOG shows no failure/error information. WLS/WTC Debug information
shows that a call to Tuxedo, after the NameService lookup seems to succeed, fails with an XATMI_FAILURE. Checking with
tmadmin psr shows that the cns is called from WLS/WTC, but not the simple_server. 

The Java client throws following exceptions:
Remote exception encountered: java.rmi.RemoteException: EJB Exception:; nested exception is:
        java.rmi.RemoteException: Can't call TUXEDO CORBA server: org.omg.CORBA.
INTERNAL:   minor code: 0 completed: Maybe

Start server side stack trace:
java.rmi.RemoteException: EJB Exception:; nested exception is:
        java.rmi.RemoteException: Can't call TUXEDO CORBA server: org.omg.CORBA.
INTERNAL:   minor code: 0 completed: Maybe
java.rmi.RemoteException: Can't call TUXEDO CORBA server: org.omg.CORBA.INTERNAL
:   minor code: 0 completed: Maybe
        at examples.wtc.corba.simpappcns.ToupperCorbaBean.Toupper(ToupperCorbaBe
an.java:152)
        at examples.wtc.corba.simpappcns.ToupperCorbaBean_lzt2si_EOImpl.Toupper(
ToupperCorbaBean_lzt2si_EOImpl.java:37)
        at examples.wtc.corba.simpappcns.ToupperCorbaBean_lzt2si_EOImpl_WLSkel.i
nvoke(Unknown Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:274)
        at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:22)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End  server side stack trace
; nested exception is:
        java.rmi.RemoteException: Can't call TUXEDO CORBA server: org.omg.CORBA.
INTERNAL:   minor code: 0 completed: Maybe

Start server side stack trace:
java.rmi.RemoteException: Can't call TUXEDO CORBA server: org.omg.CORBA.INTERNAL
:   minor code: 0 completed: Maybe
        at examples.wtc.corba.simpappcns.ToupperCorbaBean.Toupper(ToupperCorbaBe
an.java:152)
        at examples.wtc.corba.simpappcns.ToupperCorbaBean_lzt2si_EOImpl.Toupper(
ToupperCorbaBean_lzt2si_EOImpl.java:37)
        at examples.wtc.corba.simpappcns.ToupperCorbaBean_lzt2si_EOImpl_WLSkel.i
nvoke(Unknown Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:274)
        at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:22)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End  server side stack trace

End statefulSession.Client...

When the EJB is deployed with transactional setting "Supports" the call to Tuxedo Corba via WTC succeeds
(original scenario csnsimpapp sample).

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms