[JBoss JIRA] (WFLY-4549) Not possible to reload server when JTS transactions are active
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFLY-4549?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski reassigned WFLY-4549:
------------------------------------
Assignee: Ondřej Chaloupka (was: Tomasz Adamski)
Fix Version/s: 9.0.0.CR2
Resolution: Done
> Not possible to reload server when JTS transactions are active
> --------------------------------------------------------------
>
> Key: WFLY-4549
> URL: https://issues.jboss.org/browse/WFLY-4549
> Project: WildFly
> Issue Type: Bug
> Components: IIOP, Transactions
> Affects Versions: 9.0.0.Beta2
> Reporter: Ondřej Chaloupka
> Assignee: Ondřej Chaloupka
> Fix For: 9.0.0.CR2
>
>
> Reloading WFLY server with active JTS transactions fails.
> I have tried to run reload operation just after server started and when some attribute which needs reload was changed (e.g. {{/subsystem=datasources/data-source=ExampleDS:write-attribute(name=spy, value=true)}}) and in both cases server was started with errors
> {code}
> WARN [com.arjuna.ats.jts] (MSC service thread 1-4) 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:195)
> 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:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed
> at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:148)
> 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:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.RuntimeException: ARJUNA012364: RecoveryActivator init failed for com.arjuna.ats.internal.jts.orbspecific.recovery.RecoveryEnablement
> at com.arjuna.ats.internal.arjuna.recovery.RecActivatorLoader.startRecoveryActivators(RecActivatorLoader.java:67)
> 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)
> ... 5 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (WFLY-4548) Error messages on server shutdown when JTS is used
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFLY-4548?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski updated WFLY-4548:
---------------------------------
Fix Version/s: 9.0.0.CR2
> Error messages on server shutdown when JTS is used
> --------------------------------------------------
>
> Key: WFLY-4548
> URL: https://issues.jboss.org/browse/WFLY-4548
> Project: WildFly
> Issue Type: Bug
> Components: IIOP, Transactions
> Affects Versions: 9.0.0.Beta2
> Reporter: Ondřej Chaloupka
> Assignee: Ondřej Chaloupka
> Fix For: 9.0.0.CR2
>
>
> During time of shutting down WFLY server when JTS transactions are enabled I experience these two [1] [2] errors/exceptions being shown in server log/console.
> The first one [1] is shown each time when JTS is configured and server is put to be stopped.
> The second one [2] is intermittent and probably it could be shown when JTA is under use as well.
> [1]
> {code}
> WARNING [javax.enterprise.resource.corba._INITIALIZING_.rpc.presentation] (Thread-84) "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}
> [2]
> {code}
> INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-5) ARJUNA032018: Destroying TransactionManagerService
> INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA032014: Stopping transaction recovery manager
> ERROR [stderr] (Thread-98) Exception in thread "Thread-98" java.lang.NullPointerException
> ERROR [stderr] (Thread-98) at com.sun.corba.se.impl.oa.poa.POAImpl$DestroyThread.run(POAImpl.java:566)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (WFLY-4548) Error messages on server shutdown when JTS is used
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFLY-4548?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski updated WFLY-4548:
---------------------------------
Git Pull Request: https://github.com/jbosstm/narayana/pull/843, https://github.com/wildfly/wildfly/pull/7508, https://github.com/wildfly/wildfly/pull/7510, https://github.com/wildfly/wildfly/pull/7548, https://github.com/wildfly/wildfly/pull/7552 (was: https://github.com/jbosstm/narayana/pull/843, https://github.com/wildfly/wildfly/pull/7508, https://github.com/wildfly/wildfly/pull/7510)
> Error messages on server shutdown when JTS is used
> --------------------------------------------------
>
> Key: WFLY-4548
> URL: https://issues.jboss.org/browse/WFLY-4548
> Project: WildFly
> Issue Type: Bug
> Components: IIOP, Transactions
> Affects Versions: 9.0.0.Beta2
> Reporter: Ondřej Chaloupka
> Assignee: Ondřej Chaloupka
>
> During time of shutting down WFLY server when JTS transactions are enabled I experience these two [1] [2] errors/exceptions being shown in server log/console.
> The first one [1] is shown each time when JTS is configured and server is put to be stopped.
> The second one [2] is intermittent and probably it could be shown when JTA is under use as well.
> [1]
> {code}
> WARNING [javax.enterprise.resource.corba._INITIALIZING_.rpc.presentation] (Thread-84) "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}
> [2]
> {code}
> INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-5) ARJUNA032018: Destroying TransactionManagerService
> INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA032014: Stopping transaction recovery manager
> ERROR [stderr] (Thread-98) Exception in thread "Thread-98" java.lang.NullPointerException
> ERROR [stderr] (Thread-98) at com.sun.corba.se.impl.oa.poa.POAImpl$DestroyThread.run(POAImpl.java:566)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (WFLY-4548) Error messages on server shutdown when JTS is used
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFLY-4548?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski reassigned WFLY-4548:
------------------------------------
Assignee: Ondřej Chaloupka (was: Tomasz Adamski)
Resolution: Done
> Error messages on server shutdown when JTS is used
> --------------------------------------------------
>
> Key: WFLY-4548
> URL: https://issues.jboss.org/browse/WFLY-4548
> Project: WildFly
> Issue Type: Bug
> Components: IIOP, Transactions
> Affects Versions: 9.0.0.Beta2
> Reporter: Ondřej Chaloupka
> Assignee: Ondřej Chaloupka
>
> During time of shutting down WFLY server when JTS transactions are enabled I experience these two [1] [2] errors/exceptions being shown in server log/console.
> The first one [1] is shown each time when JTS is configured and server is put to be stopped.
> The second one [2] is intermittent and probably it could be shown when JTA is under use as well.
> [1]
> {code}
> WARNING [javax.enterprise.resource.corba._INITIALIZING_.rpc.presentation] (Thread-84) "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}
> [2]
> {code}
> INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-5) ARJUNA032018: Destroying TransactionManagerService
> INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA032014: Stopping transaction recovery manager
> ERROR [stderr] (Thread-98) Exception in thread "Thread-98" java.lang.NullPointerException
> ERROR [stderr] (Thread-98) at com.sun.corba.se.impl.oa.poa.POAImpl$DestroyThread.run(POAImpl.java:566)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (JGRP-1925) support ipv6 in FixedMembershipToken
by Robert Bissett (JIRA)
[ https://issues.jboss.org/browse/JGRP-1925?page=com.atlassian.jira.plugin.... ]
Robert Bissett commented on JGRP-1925:
--------------------------------------
Suggestion for the fix: because addresses can contain either "::" or ":0:" which are equivalent, and may or may not have zone indices (<address>%<index>), what we've done is create an InetAddress address for the incoming join source and use InetAddress#equals to compare to the list of allowed addresses. The string comparison that's currently used may fail for two addresses that are actually equivalent.
> support ipv6 in FixedMembershipToken
> ------------------------------------
>
> Key: JGRP-1925
> URL: https://issues.jboss.org/browse/JGRP-1925
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 3.6.3
> Reporter: Robert Bissett
> Assignee: Bela Ban
> Fix For: 3.6.4
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (JBJCA-1271) Tracer improvements
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1271?page=com.atlassian.jira.plugin... ]
Jesper Pedersen updated JBJCA-1271:
-----------------------------------
Description:
* Add confidential mode to tracer
- Enabled w/ system property 'ironjacamar.tracer.confidential' set to true
* Record callstacks for connection listener lifecycle events
- Enabled w/ system property 'ironjacamar.tracer.callstacks' set to true
* Record ManagedConnection
* Create ManagedConnection to ConnectionListener report
* Add -ignore-incomplete flag
* Add -no-sdedit flag
* Add a report about transaction interaction
was:
* Add confidential mode to tracer
- Enabled w/ system property 'ironjacamar.tracer.confidential' set to true
* Record callstacks for connection listener lifecycle events
- Enabled w/ system property 'ironjacamar.tracer.callstacks' set to true
* Record ManagedConnection
* Create ManagedConnection to ConnectionListener report
* Add -ignore-incomplete flag
* Add -no-sdedit flag
> Tracer improvements
> -------------------
>
> Key: JBJCA-1271
> URL: https://issues.jboss.org/browse/JBJCA-1271
> Project: IronJacamar
> Issue Type: Task
> Components: AS, Core
> Reporter: Jesper Pedersen
> Assignee: Jesper Pedersen
> Fix For: 1.2.5.Final
>
>
> * Add confidential mode to tracer
> - Enabled w/ system property 'ironjacamar.tracer.confidential' set to true
> * Record callstacks for connection listener lifecycle events
> - Enabled w/ system property 'ironjacamar.tracer.callstacks' set to true
> * Record ManagedConnection
> * Create ManagedConnection to ConnectionListener report
> * Add -ignore-incomplete flag
> * Add -no-sdedit flag
> * Add a report about transaction interaction
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months