[JBoss JIRA] (JBTM-1619) HeuristicTest (and some others) hang
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1619?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1619:
--------------------------------
Assignee: Gytis Trikleris (was: Tom Jenkinson)
> HeuristicTest (and some others) hang
> ------------------------------------
>
> Key: JBTM-1619
> URL: https://issues.jboss.org/browse/JBTM-1619
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 4.17.3, 5.0.0.M2
> Reporter: jaikiran pai
> Assignee: Gytis Trikleris
>
> Running the com.hp.mwtests.ts.jts.local.heuristics.HeuristicTest (and some other tests in that module) hang on my system. All of them hang at the point where the POA is being destroyed. Here's the jstack output of the hanging tests:
> {code}
> 2013-04-05 18:53:53
> Full thread dump Java HotSpot(TM) Server VM (20.1-b02 mixed mode):
> "Attach Listener" daemon prio=10 tid=0x6e503c00 nid=0x55dc waiting on condition [0x00000000]
> java.lang.Thread.State: RUNNABLE
> "POADestructor" prio=10 tid=0x6dd6f800 nid=0x559c in Object.wait() [0x6d7fe000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x9f0c0558> (a org.jacorb.poa.RequestController)
> at java.lang.Object.wait(Object.java:485)
> at org.jacorb.poa.RequestController.waitForShutdown(Unknown Source)
> - locked <0x9f0c0558> (a org.jacorb.poa.RequestController)
> at org.jacorb.poa.POA$1.run(Unknown Source)
> "Transaction Reaper Worker 0" daemon prio=10 tid=0x6dd13800 nid=0x5599 in Object.wait() [0x6dbfe000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x9e18c450> (a java.util.LinkedList)
> at java.lang.Object.wait(Object.java:485)
> at com.arjuna.ats.arjuna.coordinator.TransactionReaper.waitForCancellations(TransactionReaper.java:321)
> - locked <0x9e18c450> (a java.util.LinkedList)
> at com.arjuna.ats.internal.arjuna.coordinator.ReaperWorkerThread.run(ReaperWorkerThread.java:65)
> "Transaction Reaper" daemon prio=10 tid=0x6dd5d000 nid=0x5598 in Object.wait() [0x6de5c000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x9e184ae0> (a com.arjuna.ats.arjuna.coordinator.TransactionReaper)
> at com.arjuna.ats.internal.arjuna.coordinator.ReaperThread.run(ReaperThread.java:90)
> - locked <0x9e184ae0> (a com.arjuna.ats.arjuna.coordinator.TransactionReaper)
> "Listener:55978" daemon prio=10 tid=0x6dd2ac00 nid=0x5597 runnable [0x6dead000]
> java.lang.Thread.State: RUNNABLE
> at java.net.PlainSocketImpl.socketAccept(Native Method)
> at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
> - locked <0x9f0c0140> (a java.net.SocksSocketImpl)
> at java.net.ServerSocket.implAccept(ServerSocket.java:462)
> at java.net.ServerSocket.accept(ServerSocket.java:430)
> at com.arjuna.ats.internal.arjuna.recovery.Listener.run(Listener.java:122)
> "ClientMessageReceptor0" daemon prio=10 tid=0x6dd22400 nid=0x5596 in Object.wait() [0x6defe000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x9f0c02d0> (a java.lang.Object)
> at java.lang.Object.wait(Object.java:485)
> at org.jacorb.orb.giop.GIOPConnection.waitUntilConnected(Unknown Source)
> - locked <0x9f0c02d0> (a java.lang.Object)
> at org.jacorb.orb.giop.GIOPConnection.getMessage(Unknown Source)
> at org.jacorb.orb.giop.GIOPConnection.receiveMessages(Unknown Source)
> at org.jacorb.orb.giop.MessageReceptor.doWork(Unknown Source)
> at org.jacorb.util.threadpool.ConsumerTie.run(Unknown Source)
> at java.lang.Thread.run(Thread.java:662)
> "ServerSocketListener" daemon prio=10 tid=0x6df7e000 nid=0x5594 runnable [0x6e196000]
> java.lang.Thread.State: RUNNABLE
> at java.net.PlainSocketImpl.socketAccept(Native Method)
> at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
> - locked <0x9f0c0400> (a java.net.SocksSocketImpl)
> at java.net.ServerSocket.implAccept(ServerSocket.java:462)
> at java.net.ServerSocket.accept(ServerSocket.java:430)
> at org.jacorb.orb.iiop.IIOPListener$Acceptor.run(Unknown Source)
> "RequestController-1" daemon prio=10 tid=0x6dd2c800 nid=0x5593 in Object.wait() [0x6e1fc000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x9f0c0600> (a java.lang.Object)
> at java.lang.Object.wait(Object.java:485)
> at org.jacorb.poa.RequestController.waitForQueue(Unknown Source)
> - locked <0x9f0c0600> (a java.lang.Object)
> at org.jacorb.poa.RequestController.run(Unknown Source)
> "Low Memory Detector" daemon prio=10 tid=0xb67bcc00 nid=0x5591 runnable [0x00000000]
> java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread1" daemon prio=10 tid=0xb67bb000 nid=0x5590 waiting on condition [0x00000000]
> java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread0" daemon prio=10 tid=0xb67b9000 nid=0x558f waiting on condition [0x00000000]
> java.lang.Thread.State: RUNNABLE
> "Signal Dispatcher" daemon prio=10 tid=0xb67b7800 nid=0x558e runnable [0x00000000]
> java.lang.Thread.State: RUNNABLE
> "Finalizer" daemon prio=10 tid=0xb67a9400 nid=0x558d in Object.wait() [0x6f165000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x9f0f5fb8> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
> - locked <0x9f0f5fb8> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
> at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
> "Reference Handler" daemon prio=10 tid=0xb67a7c00 nid=0x558c in Object.wait() [0x6e8b1000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x9f0f6088> (a java.lang.ref.Reference$Lock)
> at java.lang.Object.wait(Object.java:485)
> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
> - locked <0x9f0f6088> (a java.lang.ref.Reference$Lock)
> "main" prio=10 tid=0xb6705400 nid=0x5586 in Object.wait() [0xb68af000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x9e2d8010> (a org.jacorb.poa.POA$1)
> at java.lang.Thread.join(Thread.java:1186)
> - locked <0x9e2d8010> (a org.jacorb.poa.POA$1)
> at java.lang.Thread.join(Thread.java:1239)
> at org.jacorb.poa.POA.destroy(Unknown Source)
> 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)
> - locked <0x9f1098f0> (a com.arjuna.orbportability.RootOA)
> at com.hp.mwtests.ts.jts.local.heuristics.HeuristicTest.test(HeuristicTest.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:78)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70)
> "VM Thread" prio=10 tid=0xb67a4000 nid=0x558b runnable
> "GC task thread#0 (ParallelGC)" prio=10 tid=0xb670c800 nid=0x5587 runnable
> "GC task thread#1 (ParallelGC)" prio=10 tid=0xb670e000 nid=0x5588 runnable
> "GC task thread#2 (ParallelGC)" prio=10 tid=0xb670f800 nid=0x5589 runnable
> "GC task thread#3 (ParallelGC)" prio=10 tid=0xb6710c00 nid=0x558a runnable
> "VM Periodic Task Thread" prio=10 tid=0xb67be800 nid=0x5592 waiting on condition
> JNI global references: 1330
> {code}
> My environment is Ubuntu 11.x, Java version:
> {code}
> java version "1.6.0_26"
> Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode)
> {code}
> mvn version:
> {code}
> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 19:21:28+0530)
> {code}
> This happens on master as well as 4.17 branch.
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1626) Service jboss.binding.undefined not found in AdvertiseUnadvertiseTest
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1626?page=com.atlassian.jira.plugin.... ]
Amos Feng updated JBTM-1626:
----------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/blacktie/pull/38
> Service jboss.binding.undefined not found in AdvertiseUnadvertiseTest
> ---------------------------------------------------------------------
>
> Key: JBTM-1626
> URL: https://issues.jboss.org/browse/JBTM-1626
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Priority: Critical
> Fix For: 5.0.0.M3
>
>
> http://172.17.131.2/job/blacktie-linux64/1469
> {noformat}
> Running AdvertiseUnadvertiseTest
> 2013-04-10 07:43:10,924 [main] INFO (org.xnio :73 ) - XNIO Version 3.1.0.Beta9
> 2013-04-10 07:43:10,946 [main] INFO (xnio.nio :51 ) - XNIO NIO Implementation Version 3.1.0.Beta9
> 2013-04-10 07:43:11,013 [main] INFO (jboss.remoting :70 ) - JBoss Remoting version 3.2.15.GA
> [0m07:43:12,415 INFO [org.jboss.as.repository] (management-handler-thread - 5) JBAS014900: Content added at location /home/hudson/workspace/blacktie-linux64/jboss-as/standalone/data/content/03/0b85cbbfba334c502c74b16edf96ec3b7c581d/content
> [0m[0m07:43:12,417 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war")
> [0m[33m07:43:13,135 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice.
> [0m[33m07:43:13,346 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016012: Deployment deployment "test.war" contains CDI annotations but beans.xml was not found.
> [0m[0m07:43:13,482 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'BlacktieStompAdministrationService' with 'hornetq-ra' resource adapter
> [0m[0m07:43:13,487 INFO [org.jboss.as.undertow] (MSC service thread 1-1) JBAS018210: Register web context: /test
> [0m[0m07:43:13,523 INFO [org.hornetq.ra] (default-threads - 1) HQ151000: awaiting topic/queue creation queue/BTR_BTStompAdmin
> [0m[0m07:43:13,638 INFO [org.jboss.as.server] (management-handler-thread - 5) JBAS018559: Deployed "test.war" (runtime-name : "test.war")
> [0m[31m07:43:14,344 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 7) JBAS014612: Operation ("read-attribute") failed - address: ({
> "socket-binding-group" => "standard-sockets",
> "socket-binding" => "undefined"
> }): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.binding.undefined not found
> at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:625) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:1081) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.server.services.net.BindingMetricHandlers$AbstractBindingMetricsHandler$1.execute(BindingMetricHandlers.java:66) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:439) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:321) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:228) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:223) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:193) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:114) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
> [0m[0m07:43:14,419 INFO [org.jboss.as.undertow] (MSC service thread 1-3) JBAS018224: Unregister web context: /test
> [0m[0m07:43:14,446 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 56ms
> [0m[0m07:43:14,539 INFO [org.jboss.as.repository] (management-handler-thread - 8) JBAS014901: Content removed from location /home/hudson/workspace/blacktie-linux64/jboss-as/standalone/data/content/03/0b85cbbfba334c502c74b16edf96ec3b7c581d/content
> [0m[0m07:43:14,539 INFO [org.jboss.as.server] (management-handler-thread - 8) JBAS018558: Undeployed "test.war" (runtime-name: "test.war")
> [0mTests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.814 sec <<< FAILURE!
> Results :
> Tests in error:
> AdvertiseUnadvertiseTest: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "JBAS014749: Operation handler failed: Service service jboss.binding.undefined not found"
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> {noformat}
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1626) Service jboss.binding.undefined not found in AdvertiseUnadvertiseTest
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1626?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1626:
---------------------------------
version mismatch jboss-as-arquillian-container-remote
> Service jboss.binding.undefined not found in AdvertiseUnadvertiseTest
> ---------------------------------------------------------------------
>
> Key: JBTM-1626
> URL: https://issues.jboss.org/browse/JBTM-1626
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Priority: Critical
> Fix For: 5.0.0.M3
>
>
> http://172.17.131.2/job/blacktie-linux64/1469
> {noformat}
> Running AdvertiseUnadvertiseTest
> 2013-04-10 07:43:10,924 [main] INFO (org.xnio :73 ) - XNIO Version 3.1.0.Beta9
> 2013-04-10 07:43:10,946 [main] INFO (xnio.nio :51 ) - XNIO NIO Implementation Version 3.1.0.Beta9
> 2013-04-10 07:43:11,013 [main] INFO (jboss.remoting :70 ) - JBoss Remoting version 3.2.15.GA
> [0m07:43:12,415 INFO [org.jboss.as.repository] (management-handler-thread - 5) JBAS014900: Content added at location /home/hudson/workspace/blacktie-linux64/jboss-as/standalone/data/content/03/0b85cbbfba334c502c74b16edf96ec3b7c581d/content
> [0m[0m07:43:12,417 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war")
> [0m[33m07:43:13,135 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice.
> [0m[33m07:43:13,346 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016012: Deployment deployment "test.war" contains CDI annotations but beans.xml was not found.
> [0m[0m07:43:13,482 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'BlacktieStompAdministrationService' with 'hornetq-ra' resource adapter
> [0m[0m07:43:13,487 INFO [org.jboss.as.undertow] (MSC service thread 1-1) JBAS018210: Register web context: /test
> [0m[0m07:43:13,523 INFO [org.hornetq.ra] (default-threads - 1) HQ151000: awaiting topic/queue creation queue/BTR_BTStompAdmin
> [0m[0m07:43:13,638 INFO [org.jboss.as.server] (management-handler-thread - 5) JBAS018559: Deployed "test.war" (runtime-name : "test.war")
> [0m[31m07:43:14,344 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 7) JBAS014612: Operation ("read-attribute") failed - address: ({
> "socket-binding-group" => "standard-sockets",
> "socket-binding" => "undefined"
> }): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.binding.undefined not found
> at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:625) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:1081) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.server.services.net.BindingMetricHandlers$AbstractBindingMetricsHandler$1.execute(BindingMetricHandlers.java:66) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:439) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:321) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:228) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:223) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:193) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:114) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
> [0m[0m07:43:14,419 INFO [org.jboss.as.undertow] (MSC service thread 1-3) JBAS018224: Unregister web context: /test
> [0m[0m07:43:14,446 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 56ms
> [0m[0m07:43:14,539 INFO [org.jboss.as.repository] (management-handler-thread - 8) JBAS014901: Content removed from location /home/hudson/workspace/blacktie-linux64/jboss-as/standalone/data/content/03/0b85cbbfba334c502c74b16edf96ec3b7c581d/content
> [0m[0m07:43:14,539 INFO [org.jboss.as.server] (management-handler-thread - 8) JBAS018558: Undeployed "test.war" (runtime-name: "test.war")
> [0mTests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.814 sec <<< FAILURE!
> Results :
> Tests in error:
> AdvertiseUnadvertiseTest: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "JBAS014749: Operation handler failed: Service service jboss.binding.undefined not found"
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> {noformat}
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1522) "no XTS application recovery module found" during XTS Recovery Tests
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1522?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1522:
---------------------------------
Done
> "no XTS application recovery module found" during XTS Recovery Tests
> --------------------------------------------------------------------
>
> Key: JBTM-1522
> URL: https://issues.jboss.org/browse/JBTM-1522
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Paul Robinson
> Assignee: Amos Feng
> Priority: Critical
> Fix For: 5.0.0.M3
>
> Attachments: 2013-04-01_jbtm-1522_outputs.zip, com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit-output.txt, com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-2.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-output-2.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-output.txt, com.arjuna.qa.junit.TestBACrashDuringCommit.txt, com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit-output.txt, com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit.txt
>
>
> See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/211/artifact/XTS/...
> Notice the following log is displayed repeatedly until the test gives up waiting for recovery:
> {code}
> WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046032: no XTS application recovery module found to help reactivate recovered WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0
> {code}
> This error comes from org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple#recoverParticipants(). In particular:
> {code}
> if (!found) {
> // we failed to find a helper to convert a participant record so log a warning
> // but leave it in the table for next time
> RecoveryLogger.i18NLogger.warn_participant_at_XTSATRecoveryModule_4(participantRecoveryRecord.getId());
> }
> {code}
> It looks like the code is unable to restore the participant from the log due to restoreParticipant(XTSATRecoveryModule module) returning false. There is ParticipantRecoveryRecord in the log as you can see it dumped to the console in the above log. Maybe there is a problem with that log, or maybe we are missing another log entry?
> This problem is intermittent, so it's unlikely that you will see this happen when you attach a debugger. However, we could attach a debugger to see what happens in the normal case and also to inspect the log to see if anything is missing in the failing case. But I have a cunning plan...
> h4.Cunning Plan
> We need to get a copy of the failing log, before recovery is attempted. We should then be able to use that log to reproduce the issue on our own machines. Steps to take:
> # Update BaseCrashTest to copy the contents of the tx-object-store to a unique folder location (So we can retrieve it later for a failed run). Make sure you create the folder structure under target/surefire-reports so that CI archives it off. Do the copy between controller.kill and controller.start. This way we get the log before the recovery manager has had chance to tamper with it.
> # Update the "narayana-JBTM-1522" job in CI to use your branch, containing the change above.
> # Configure the job to run @hourly until it fails with this problem.
> # Take a copy of the tx-object-store from the failing test and then put it in place on your AS8 build.
> # Boot the AS and confirm that the issue is reproduced.
> # You can now keep putting the tx-object-store back in place every time you need to reproduce the issue.
> # Attach a debugger to find out what the problem is.
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1522) "no XTS application recovery module found" during XTS Recovery Tests
by SBS JIRA Integration (JIRA)
[ https://issues.jboss.org/browse/JBTM-1522?page=com.atlassian.jira.plugin.... ]
SBS JIRA Integration updated JBTM-1522:
---------------------------------------
Forum Reference: https://community.jboss.org/message/807912#807912
> "no XTS application recovery module found" during XTS Recovery Tests
> --------------------------------------------------------------------
>
> Key: JBTM-1522
> URL: https://issues.jboss.org/browse/JBTM-1522
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Paul Robinson
> Assignee: Amos Feng
> Priority: Critical
> Fix For: 5.0.0.M3
>
> Attachments: 2013-04-01_jbtm-1522_outputs.zip, com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit-output.txt, com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-2.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-output-2.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-output.txt, com.arjuna.qa.junit.TestBACrashDuringCommit.txt, com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit-output.txt, com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit.txt
>
>
> See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/211/artifact/XTS/...
> Notice the following log is displayed repeatedly until the test gives up waiting for recovery:
> {code}
> WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046032: no XTS application recovery module found to help reactivate recovered WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0
> {code}
> This error comes from org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple#recoverParticipants(). In particular:
> {code}
> if (!found) {
> // we failed to find a helper to convert a participant record so log a warning
> // but leave it in the table for next time
> RecoveryLogger.i18NLogger.warn_participant_at_XTSATRecoveryModule_4(participantRecoveryRecord.getId());
> }
> {code}
> It looks like the code is unable to restore the participant from the log due to restoreParticipant(XTSATRecoveryModule module) returning false. There is ParticipantRecoveryRecord in the log as you can see it dumped to the console in the above log. Maybe there is a problem with that log, or maybe we are missing another log entry?
> This problem is intermittent, so it's unlikely that you will see this happen when you attach a debugger. However, we could attach a debugger to see what happens in the normal case and also to inspect the log to see if anything is missing in the failing case. But I have a cunning plan...
> h4.Cunning Plan
> We need to get a copy of the failing log, before recovery is attempted. We should then be able to use that log to reproduce the issue on our own machines. Steps to take:
> # Update BaseCrashTest to copy the contents of the tx-object-store to a unique folder location (So we can retrieve it later for a failed run). Make sure you create the folder structure under target/surefire-reports so that CI archives it off. Do the copy between controller.kill and controller.start. This way we get the log before the recovery manager has had chance to tamper with it.
> # Update the "narayana-JBTM-1522" job in CI to use your branch, containing the change above.
> # Configure the job to run @hourly until it fails with this problem.
> # Take a copy of the tx-object-store from the failing test and then put it in place on your AS8 build.
> # Boot the AS and confirm that the issue is reproduced.
> # You can now keep putting the tx-object-store back in place every time you need to reproduce the issue.
> # Attach a debugger to find out what the problem is.
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1407?focusedWorklogId=12429003&page=... ]
Gytis Trikleris logged work on JBTM-1407:
-----------------------------------------
Author: Gytis Trikleris
Created on: 11/Apr/13 9:30 AM
Start Date: 11/Apr/13 9:30 AM
Worklog Time Spent: 9 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 2 days, 3 hours, 30 minutes)
Time Spent: 3 days, 6 hours, 30 minutes (was: 3 days, 6 hours, 21 minutes)
Worklog Id: (was: 12429003)
> Have a build option that builds JTS only against JacORB or IDLJ, but not both.
> ------------------------------------------------------------------------------
>
> Key: JBTM-1407
> URL: https://issues.jboss.org/browse/JBTM-1407
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System, JTS
> Affects Versions: 4.17.3
> Reporter: Mark Little
> Assignee: Gytis Trikleris
> Priority: Critical
> Fix For: 5.0.0.M3
>
> Time Spent: 3 days, 6 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> This boils down to supporting two new profiles:
> ./build.sh -P jts-jacorb
> ./build.sh -P jts-idlj
--
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
11 years, 5 months