[JBoss JIRA] (JBTM-1252) Remove XTS/interop
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1252:
-----------------------------------
Summary: Remove XTS/interop
Key: JBTM-1252
URL: https://issues.jboss.org/browse/JBTM-1252
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.17.0, 5.0.0.M2
Tests now Arquillian-ified under XTS/localjunit
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBTM-1253) narayana-ipv6-dualstack: qa/tests/build does not exist.
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1253:
-----------------------------------
Summary: narayana-ipv6-dualstack: qa/tests/build does not exist.
Key: JBTM-1253
URL: https://issues.jboss.org/browse/JBTM-1253
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Testing
Reporter: Paul Robinson
Assignee: Michael Musgrove
Fix For: 4.17.0, 5.0.0.M2
See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana-ipv6-dualstack/69...
In particular:
{code}
QA Test Suite orb=idlj
will download JDBC drivers
Buildfile: /home/hudson/workspace/narayana-ipv6-dualstack/qa/run-tests.xml
junit-jts-testsuite:
[echo] Running junit test group currenttests01 from basedir=/home/hudson/workspace/narayana-ipv6-dualstack/qa
BUILD FAILED
/home/hudson/workspace/narayana-ipv6-dualstack/qa/run-tests.xml:116: The following error occurred while executing this line:
/home/hudson/workspace/narayana-ipv6-dualstack/qa/run-tests.xml:345: /home/hudson/workspace/narayana-ipv6-dualstack/qa/tests/build does not exist.
Total time: 0 seconds
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBTM-1262) JBossAS7ServerKillProcessor doesn't detect when server killed
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1262:
-----------------------------------
Summary: JBossAS7ServerKillProcessor doesn't detect when server killed
Key: JBTM-1262
URL: https://issues.jboss.org/browse/JBTM-1262
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.5
See: http://172.17.131.2/job/jbossts-branch416-EAP601-java7/170/artifact/XTS/s...
In particular:
{code}
08:30:11,018 INFO [stdout] (TaskWorker-1) rule.debug{kill JVM at commit} : !!!killing JVM!!!
Sep 20, 2012 8:30:14 AM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Sep 20, 2012 8:30:40 AM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Sep 20, 2012 8:31:06 AM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
{code}
This shows that the server was killed by Byteman, but the KillProcessor still thinks it is alive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBTM-1263) Port all xts crash recovery fixes from narayana 5.x branch
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1263:
-----------------------------------
Summary: Port all xts crash recovery fixes from narayana 5.x branch
Key: JBTM-1263
URL: https://issues.jboss.org/browse/JBTM-1263
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: XTS
Affects Versions: 4.16.4
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.5
We could port them as individual commits, to improve auditability. However, I would estimate there to be ~20+ commits. This would be time consuming and error prone.
The safest thing to do would be to copy the entire 'XTS/localjunit/crash-recovery-tests' from the narayana 5 branch over the top of 'XTS/sar/crash-recovery-tests' as they are both Arquillian based and only differ in the fact that the Narayana 5 branch version has all the fixes applied.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBTM-1205) Intermittent txbridge failure
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-1205:
-----------------------------------
Summary: Intermittent txbridge failure
Key: JBTM-1205
URL: https://issues.jboss.org/browse/JBTM-1205
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: TxBridge
Reporter: Tom Jenkinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
http://172.17.131.2/job/narayana-java6/1252/
[INFO] Surefire report directory: /home/hudson/workspace/narayana-java6/txbridge/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.jbossts.txbridge.tests.inbound.junit.InboundBasicTests
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.252 sec
Running org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 142.832 sec
Running org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 73.828 sec
Running org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundCrashRecoveryTests
Tests run: 4, Failures: 0, Errors: 2, Skipped: 1, Time elapsed: 60.231 sec <<< FAILURE!
Results :
Tests in error:
testCrashTwoLogs(org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundCrashRecoveryTests): The server is already running! Managed containers does not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container.(..)
testCrashTwoLogs(org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundCrashRecoveryTests): Deployment with name txbridge-outbound-tests-client could not be undeployed. Container jboss must be still running.
Tests run: 17, Failures: 0, Errors: 2, Skipped: 1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6:05.578s
[INFO] Finished at: Wed Jul 18 10:42:38 BST 2012
[INFO] Final Memory: 22M/205M
[INFO] ------------------------------------------------------------------------
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBTM-1197) large tx timeouts are bugged
by Jonathan Halliday (JIRA)
Jonathan Halliday created JBTM-1197:
---------------------------------------
Summary: large tx timeouts are bugged
Key: JBTM-1197
URL: https://issues.jboss.org/browse/JBTM-1197
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transaction Core
Affects Versions: 4.16.4
Reporter: Jonathan Halliday
Assignee: Tom Jenkinson
When CoordinatorEnvironmentBean.defaultTimeout approaches Integer.MAX_VALUE, the calculation in ReaperElement.<ctor> wraps, resulting in an immediate tx timeout
_absoluteTimeoutMills = (timeout * 1000) + System.currentTimeMillis();
should be
_absoluteTimeoutMills = (timeout * 1000L) + System.currentTimeMillis();
in order to avoid -ve i.e. times in the past when timeout is large.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months