[JBoss JIRA] (JBTM-2284) XID.toString broken: indexing mistake in array
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBTM-2284?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated JBTM-2284:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1166754
> XID.toString broken: indexing mistake in array
> ----------------------------------------------
>
> Key: JBTM-2284
> URL: https://issues.jboss.org/browse/JBTM-2284
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Affects Versions: 4.17.15
> Environment: EAP 6.2.4 with JBoss JTS module in version 4.17.15
> Reporter: Christian von Kutzleben
> Assignee: Tom Jenkinson
> Fix For: 4.17.24
>
>
> com.arjuna.ats.internal.jta.xa.XID
>
> public String toString ()
> {
> //...
> stringBuilder.append(", ");
> for (int i = 0; i < bqual_length; i++) {
> stringBuilder.append(gtrid_length+data[i]);
> }
> //...
> }
>
> correct: stringBuilder.append(data[i+gtrid_length]);
> The result is, that the Xid instances logged in log files are corrupted and multiple different Xid share the same String representation, which makes the logging information unusable
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (JBTM-2216) Extraneous warning message observed in XARecoveryModule.xaRecoverySecondPass if the first pass has already failed
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBTM-2216?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated JBTM-2216:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1166754
> Extraneous warning message observed in XARecoveryModule.xaRecoverySecondPass if the first pass has already failed
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-2216
> URL: https://issues.jboss.org/browse/JBTM-2216
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: JTA
> Affects Versions: 4.17.20, 4.17.21, 5.0.2
> Environment: JBoss EAP 6.3
> Reporter: Tom Ross
> Assignee: Tom Jenkinson
> Fix For: 4.17.23, 5.0.4
>
>
> When using AMQ failover protocol, the Narayana recovery process generates the following exception:
> {noformat}
> 10:19:36,053 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://ragga:61616?trace=true
> 10:21:46,139 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://ragga:61616?trace=true
> 10:21:46,139 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: Failover transport not connected: unconnected
> at org.apache.activemq.TransactionContext.recover(TransactionContext.java:656)
> at org.apache.activemq.ra.LocalAndXATransaction.recover(LocalAndXATransaction.java:135)
> at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.recover(XAResourceWrapperImpl.java:177)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:548) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:187) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1]
> 10:21:56,165 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016008: Local XARecoveryModule.xaRecovery - caught exception: java.lang.NullPointerException
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:619) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1]
> {noformat}
> Although the first message may be expected if the resource manager throws an exception in XAResource::recover(), the second message does not add any further assistance in resolving the issue and should be removed as noise.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server"
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1683:
-------------------------------------
>From http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana...
{quote}
2014-11-21 10:37:47,584 [0x00000f80] DEBUG (HybridSocketEndpointQueue:221 ) - waiting message with time 50
2014-11-21 10:37:47,584 [0x00000474] DEBUG (SocketServer :274 ) - connection from 127.0.0.1:60866
2014-11-21 10:37:47,577 [0x000007e0] TRACE (TxXAResourceManagerFactory:111 ) - ENTER
2014-11-21 10:37:47,584 [0x000007e0] TRACE (TxXAResourceManagerFactory:126 ) - ENTER
2014-11-21 10:37:47,585 [0x000007e0] TRACE (TxXARecoveryLog :120 ) - destructor
2014-11-21 10:37:47,585 [0x000007e0] TRACE (SynchronizableObject :101 ) - Releasing mutex: 008667A0
2014-11-21 10:37:47,585 [0x000007e0] TRACE (SynchronizableObject :103 ) - released mutex: 008667A0
2014-11-21 10:37:47,585 [0x000007e0] TRACE (TxManagerc :35 ) - <
2014-11-21 10:37:47,585 [0x000007e0] TRACE (SynchronizableObject :56 ) - Acquiring mutex: 1005FE1C
2014-11-21 10:37:47,585 [0x000007e0] TRACE (SynchronizableObject :58 ) - acquired: 1005FE1C
2014-11-21 10:37:47,585 [0x000007e0] TRACE (AtmiBrokerEnv :92 ) - Reference count: 3
2014-11-21 10:37:47,585 [0x000007e0] TRACE (SynchronizableObject :101 ) - Releasing mutex: 1005FE1C
2014-11-21 10:37:47,586 [0x000007e0] TRACE (SynchronizableObject :103 ) - released mutex: 1005FE1C
2014-11-21 10:37:47,586 [0x000007e0] DEBUG (AtmiBrokerServer :630 ) - deleted services
2014-11-21 10:37:47,586 [0x000007e0] TRACE (ConnectionManager :53 ) - closeConnections
{quote}
Tallies up with albanys:
/home/hudson/jobs/narayana-windows2008-catelyn/builds/783/archive/blacktie/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/log/server.log
{quote}
2014-11-21 10:37:47,735 WARN [org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.SocketSenderImpl] (Thread-25 (HornetQ-client-global-threads-27681350)) socket send with java.net.SocketException: Connection reset by peer: socket write error
{quote}
Why are we closing the connection on the client side?
> btadmin tests on windows failed with "Could not start the server"
> -----------------------------------------------------------------
>
> Key: JBTM-1683
> URL: https://issues.jboss.org/browse/JBTM-1683
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie
> Affects Versions: 5.0.0
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.4
>
>
> http://172.17.131.2/job/blacktie-windows2008-taconic/272
> {code}
> Failed tests:
> testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful
> testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server
> testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful
> testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server"
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1683:
-------------------------------------
http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana...
> btadmin tests on windows failed with "Could not start the server"
> -----------------------------------------------------------------
>
> Key: JBTM-1683
> URL: https://issues.jboss.org/browse/JBTM-1683
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie
> Affects Versions: 5.0.0
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.4
>
>
> http://172.17.131.2/job/blacktie-windows2008-taconic/272
> {code}
> Failed tests:
> testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful
> testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server
> testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful
> testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server"
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reopened JBTM-1683:
---------------------------------
> btadmin tests on windows failed with "Could not start the server"
> -----------------------------------------------------------------
>
> Key: JBTM-1683
> URL: https://issues.jboss.org/browse/JBTM-1683
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie
> Affects Versions: 5.0.0
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.0
>
>
> http://172.17.131.2/job/blacktie-windows2008-taconic/272
> {code}
> Failed tests:
> testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful
> testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server
> testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful
> testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server"
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1683:
--------------------------------
Fix Version/s: 5.0.4
(was: 5.0.0)
> btadmin tests on windows failed with "Could not start the server"
> -----------------------------------------------------------------
>
> Key: JBTM-1683
> URL: https://issues.jboss.org/browse/JBTM-1683
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie
> Affects Versions: 5.0.0
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.4
>
>
> http://172.17.131.2/job/blacktie-windows2008-taconic/272
> {code}
> Failed tests:
> testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful
> testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server
> testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful
> testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server"
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1683:
--------------------------------
Affects Version/s: 5.0.0
> btadmin tests on windows failed with "Could not start the server"
> -----------------------------------------------------------------
>
> Key: JBTM-1683
> URL: https://issues.jboss.org/browse/JBTM-1683
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie
> Affects Versions: 5.0.0
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.4
>
>
> http://172.17.131.2/job/blacktie-windows2008-taconic/272
> {code}
> Failed tests:
> testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful
> testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server
> testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful
> testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months