[jboss-jira] [JBoss JIRA] (WFLY-5261) Can't reload server when JTS transactions are used
Tom Jenkinson (JIRA)
issues at jboss.org
Fri Sep 18 11:17:00 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13110484#comment-13110484 ]
Tom Jenkinson commented on WFLY-5261:
-------------------------------------
Thanks for recording that Tomasz. My immediate question is although it affects that stream, do we need to make a WFLY 9 change now as I don't think a release is scheduled? Maybe we could just put it on master and then if a 9.0.2 is announced we can backport at that time? Just a suggestion as there is no 9.0.2 scheduled that I am aware of.
> Can't reload server when JTS transactions are used
> --------------------------------------------------
>
> Key: WFLY-5261
> URL: https://issues.jboss.org/browse/WFLY-5261
> Project: WildFly
> Issue Type: Bug
> Components: IIOP, Transactions
> Affects Versions: 9.0.1.Final, 10.0.0.Beta2
> Reporter: Ondřej Chaloupka
> Assignee: Tomasz Adamski
> Priority: Critical
> Attachments: server.log, standalone-full.jts.xml
>
>
> It seems that issue WFLY-4549 was not fully fixed. The reload for the server that uses JTS transactions does not work properly. The error [1] is still shown.
> [1]
> {code}
> WARN [com.arjuna.ats.jts] (MSC service thread 1-2) ARJUNA022083: JacOrbRCServiceInit - Failed to start RC service: java.lang.NullPointerException
> at com.sun.corba.se.impl.orb.ORBImpl.checkShutdownState(ORBImpl.java:1329)
> at com.sun.corba.se.impl.orb.ORBImpl.getCorbaContactInfoListFactory(ORBImpl.java:1889)
> at com.sun.corba.se.impl.orbutil.ORBUtility.makeClientDelegate(ORBUtility.java:678)
> at com.sun.corba.se.impl.orbutil.ORBUtility.makeObjectReference(ORBUtility.java:687)
> at com.sun.corba.se.impl.ior.ObjectReferenceProducerBase.make_object(ObjectReferenceProducerBase.java:60)
> at com.sun.corba.se.spi.oa.ObjectAdapterBase.makeObject(ObjectAdapterBase.java:142)
> at com.sun.corba.se.impl.oa.poa.POAImpl.create_reference_with_id(POAImpl.java:1353)
> at com.arjuna.ats.internal.jts.orbspecific.javaidl.recoverycoordinators.JavaIdlRCServiceInit.startRCservice(JavaIdlRCServiceInit.java:196)
> at com.arjuna.ats.internal.jts.orbspecific.recovery.RecoveryEnablement.startRCservice(RecoveryEnablement.java:141)
> at com.arjuna.ats.internal.arjuna.recovery.RecActivatorLoader.startRecoveryActivators(RecActivatorLoader.java:66)
> at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.<init>(RecoveryManagerImple.java:102)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.initialize(RecoveryManager.java:226)
> at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.start(RecoveryManagerService.java:65)
> at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:145)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list