[jboss-jira] [JBoss JIRA] (WFLY-4894) ORB error message seen on shutdown time to time - "IOP01210228: (BAD_OPERATION) This ORB instance has been destroyed, so no operations can be performed on it"

[Kabir Khan (JIRA)]

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

Kabir Khan updated WFLY-4894:
-----------------------------
    Fix Version/s: 10.0.0.Final


I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.

> ORB error message seen on shutdown time to time - "IOP01210228: (BAD_OPERATION) This ORB instance has been destroyed, so no operations can be performed on it"
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-4894
>                 URL: https://issues.jboss.org/browse/WFLY-4894
>             Project: WildFly
>          Issue Type: Bug
>          Components: IIOP
>            Reporter: Ondra Chaloupka
>            Assignee: Tomasz Adamski
>             Fix For: 10.0.0.Final
>
>
> As jira WFLY-4548 describes there could be seen IIOP errors during server shutdown. As issue was fixed it seemed that the trouble went away. Unfortunatelly in some more testing I'm hitting the exception once again when running crash server tests with transactions under jts.
> {code}
> WARNING [javax.enterprise.resource.corba._INITIALIZING_.rpc.presentation] (Thread-87) "IOP01210228: (BAD_OPERATION) This ORB instance has been destroyed, so no operations can be performed on it": org.omg.CORBA.BAD_     OPERATION:   vmcid: SUN  minor code: 228  completed: No
>  at com.sun.corba.se.impl.logging.ORBUtilSystemException.orbDestroyed(ORBUtilSystemException.java:586)
>  at com.sun.corba.se.impl.logging.ORBUtilSystemException.orbDestroyed(ORBUtilSystemException.java:608)
>  at com.sun.corba.se.impl.orb.ORBImpl.checkShutdownState(ORBImpl.java:1329)
>  at com.sun.corba.se.impl.orb.ORBImpl.isDuringDispatch(ORBImpl.java:1340)
>  at com.sun.corba.se.impl.oa.poa.POAImpl.destroy(POAImpl.java:959)
>  at com.arjuna.orbportability.internal.orbspecific.oa.implementations.POABase.destroyRootPOA(POABase.java:68)
>  at com.arjuna.orbportability.oa.core.OA.destroyRootPOA(OA.java:97)
>  at com.arjuna.orbportability.RootOA.destroy(RootOA.java:91)
>  at com.arjuna.ats.internal.jts.orbspecific.javaidl.recoverycoordinators.ORBRunner.run(ORBRunner.java:59)
> {code}
> The scenario is something:
>  - starting server under profile standalone-full.xml with in-vm ActiveMQ messaging
>  - setting server via CLI
>  - setting transaction running under JTS
>  - deploy application containing MDB reading message from ActiveMQ
>  - crash server
>  - start again and doing recovery
>  - stop server (now the exception is shown)



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)