[JBoss JIRA] (JBTM-1136) XTS Crash Recovery fail: Could not start container
by Amos Feng (JIRA)
Amos Feng created JBTM-1136:
-------------------------------
Summary: XTS Crash Recovery fail: Could not start container
Key: JBTM-1136
URL: https://issues.jboss.org/browse/JBTM-1136
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Amos Feng
Assignee: Tom Jenkinson
http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java6/193
http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java6/194
http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java7/137
It looks like booting jboss-as with the following error and xtstests.war can not be deployed. the arquillian thinks the container does not start.
{code}
02:51:57,012 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 50) JBAS014612: Operation ("add") failed - address: ([("subsystem" => "osgi")]): org.jboss.msc.service.DuplicateServiceException: Service jbosgi.integration.PersistentBundlesHandler is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:955) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.osgi.service.PersistentBundlesIntegration.addService(PersistentBundlesIntegration.java:76) [jboss-as-osgi-service-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.osgi.parser.OSGiSubsystemAdd$2.execute(OSGiSubsystemAdd.java:130) [jboss-as-osgi-service-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.osgi.parser.OSGiSubsystemAdd$1.execute(OSGiSubsystemAdd.java:103) [jboss-as-osgi-service-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:311) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_03]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_03]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
{code}
--
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-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