[jboss-jira] [JBoss JIRA] (WFLY-11218) IIOP call does not work with transaction started on client side when run on IBM JDK

James Perkins (Jira) issues at jboss.org
Mon May 20 11:50:00 EDT 2019


     [ https://issues.jboss.org/browse/WFLY-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins updated WFLY-11218:
---------------------------------
    Labels: blocker-WF17 blocker-WF18  (was: blocker-WF17)


> IIOP call does not work with transaction started on client side when run on IBM JDK
> -----------------------------------------------------------------------------------
>
>                 Key: WFLY-11218
>                 URL: https://issues.jboss.org/browse/WFLY-11218
>             Project: WildFly
>          Issue Type: Bug
>          Components: IIOP
>    Affects Versions: 14.0.0.Final, 15.0.0.Beta1
>         Environment: IBM JDK 8
>            Reporter: Ivan Straka
>            Assignee: Tomasz Adamski
>            Priority: Blocker
>              Labels: blocker-WF17, blocker-WF18
>
> Issue is valid only for IBM JDK 8...scenario works on oracle jdk 8 and 11 and openjdk 8.
> Scenario (using CORBA):
> # start transaction
> # lookup
> # IIOP call
> # EJB perform a basic operation and return (no failure is expected)
> IIOP call fails with following exception:
> {code:java}
> java.lang.NullPointerException: null
> 	at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.sentFullMessage(CorbaMessageMediatorImpl.java:429)
> 	at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.sendCancelRequestIfFinalFragmentNotSent(CorbaMessageMediatorImpl.java:394)
> 	at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.endRequest(CorbaClientRequestDispatcherImpl.java:895)
> 	at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.releaseReply(CorbaClientDelegateImpl.java:167)
> 	at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:253)
> 	at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:139)
> 	at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:91)
> 	at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:408)
> 	at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:274)
> 	at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:132)
> 	at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:61)
> 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:695)
> 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:324)
> 	at javax.naming.InitialContext.init(InitialContext.java:255)
> 	at javax.naming.InitialContext.<init>(InitialContext.java:227)
> 	at org.jboss.as.test.jbossts.client.utils.TxUtil.lookupIIOP(TxUtil.java:93)
> 	at org.jboss.as.test.jbossts.client.utils.TxUtil.lookupIIOP(TxUtil.java:103)
> 	at org.jboss.as.test.jbossts.crashrec.test.JMSCrashRecoveryTestCase.lookupCrashBeanOverIIOP(JMSCrashRecoveryTestCase.java:164)
> 	at org.jboss.as.test.jbossts.crashrec.test.JMSCrashRecoveryTestCase.callCrashTest(JMSCrashRecoveryTestCase.java:126)
> {code}
> When transaction is not started on client side, IIOP call works smoothly.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the jboss-jira mailing list