[JBoss JIRA] (JBTM-2145) Blacktie subsystem configuration build fails
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-2145?page=com.atlassian.jira.plugin.... ]
Amos Feng resolved JBTM-2145.
-----------------------------
Resolution: Duplicate Issue
> Blacktie subsystem configuration build fails
> --------------------------------------------
>
> Key: JBTM-2145
> URL: https://issues.jboss.org/browse/JBTM-2145
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Application Server Integration, BlackTie
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Priority: Blocker
> Fix For: 5.0.2
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/113
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Building WildFly: Blacktie Subsystem Build 5.0.2.Final-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ wildfly-blacktie-build ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @ wildfly-blacktie-build ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) @ wildfly-blacktie-build ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp (get-build-timestamp) @ wildfly-blacktie-build ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ wildfly-blacktie-build ---
> [INFO]
> [INFO] --- jacoco-maven-plugin:0.6.3.201306030806:prepare-agent (pre-unit-test) @ wildfly-blacktie-build ---
> [INFO] Skipping JaCoCo for project with packaging type 'pom'
> [INFO] surefireArgLine set to
> [INFO]
> [INFO] --- maven-antrun-plugin:1.7:run (build-blacktie-modular-config) @ wildfly-blacktie-build ---
> [INFO] Executing tasks
> main:
> modules-minimalistic:
> [echo] Initializing module -> org.wildfly.extension.blacktie
> [mkdir] Created dir: /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-blacktie/build/target/wildfly-blacktie-build-5.0.2.Final-SNAPSHOT/modules/system/layers/base/org/wildfly/extension/blacktie/main
> [copy] Copying 1 file to /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-blacktie/build/target/wildfly-blacktie-build-5.0.2.Final-SNAPSHOT/modules/system/layers/base/org/wildfly/extension/blacktie/main
> [copy] Copying 1 file to /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-blacktie/build/target/wildfly-blacktie-build-5.0.2.Final-SNAPSHOT/modules/system/layers/base/org/wildfly/extension/blacktie/main
> [INFO] Executed tasks
> [INFO]
> [INFO] --- maven-antrun-plugin:1.7:run (generate-blacktie-config) @ wildfly-blacktie-build ---
> [INFO] Executing tasks
> main:
> generate-configs:
> [mkdir] Created dir: /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-blacktie/build/target/wildfly-blacktie-build-5.0.2.Final-SNAPSHOT/docs/examples/configs
> [echo] Merging standalone configuration/standalone/template.xml and /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-blacktie/build/src/main/resources/configuration/examples/subsystems-blacktie.xml into /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-blacktie/build/target/wildfly-blacktie-build-5.0.2.Final-SNAPSHOT/docs/examples/configs/standalone-blacktie.xml, using StandaloneMain
> [java] java.lang.IllegalStateException: Could not find '[subsystem=../../../../../../jboss-as/build/src/main/resources/configuration/subsystems/threads.xml, supplement=null]' under the base directory '/home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-blacktie/build/src/main/resources'
> [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:194)
> [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:771)
> [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:221)
> [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:135)
> [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:108)
> [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> [java] at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
> [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(Method.java:601)
> [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
> [java] at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68)
> [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> [java] at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
> [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(Method.java:601)
> [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
> [java] at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:398)
> [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> [java] at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
> [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(Method.java:601)
> [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
> [java] at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68)
> [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> [java] at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
> [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(Method.java:601)
> [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
> [java] at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:398)
> [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> [java] at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
> [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(Method.java:601)
> [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
> [java] at org.apache.tools.ant.Target.execute(Target.java:390)
> [java] at org.apache.tools.ant.Target.performTasks(Target.java:411)
> [java] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
> [java] at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
> [java] at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
> [java] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
> [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> [java] at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
> [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(Method.java:601)
> [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
> [java] at org.apache.tools.ant.Target.execute(Target.java:390)
> [java] at org.apache.tools.ant.Target.performTasks(Target.java:411)
> [java] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
> [java] at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
> [java] at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:327)
> [java] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
> [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> [java] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> [java] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> [java] at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> [java] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> [java] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> [java] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> [java] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(Method.java:601)
> [java] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [java] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [java] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [java] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [java] Caused by: java.lang.IllegalStateException: Could not find '[subsystem=../../../../../../jboss-as/build/src/main/resources/configuration/subsystems/threads.xml, supplement=null]' under the base directory '/home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-blacktie/build/src/main/resources'
> [java] at org.jboss.as.config.assembly.ConfigurationAssembler.populateTemplate(ConfigurationAssembler.java:109)
> [java] at org.jboss.as.config.assembly.ConfigurationAssembler.assemble(ConfigurationAssembler.java:64)
> [java] at org.jboss.as.config.assembly.StandaloneMain.main(StandaloneMain.java:53)
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(Method.java:601)
> [java] at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:217)
> [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:152)
> [java] ... 76 more
> [java] Java Result: -1
> all:
> [INFO] Executed tasks
> [INFO]
> [INFO] --- byteman-rulecheck-maven-plugin:2.1.3:rulecheck (rulecheck) @ wildfly-blacktie-build ---
> [INFO]
> [INFO] --- jacoco-maven-plugin:0.6.3.201306030806:report (post-unit-test) @ wildfly-blacktie-build ---
> [INFO] Skipping JaCoCo for project with packaging type 'pom'
> [INFO]
> [INFO] --- jacoco-maven-plugin:0.6.3.201306030806:check (check) @ wildfly-blacktie-build ---
> [INFO] Skipping JaCoCo for project with packaging type 'pom'
> [INFO]
> [INFO] >>> maven-source-plugin:2.2.1:jar (attach-sources) @ wildfly-blacktie-build >>>
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @ wildfly-blacktie-build ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) @ wildfly-blacktie-build ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp (get-build-timestamp) @ wildfly-blacktie-build ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ wildfly-blacktie-build ---
> [INFO]
> [INFO] --- jacoco-maven-plugin:0.6.3.201306030806:prepare-agent (pre-unit-test) @ wildfly-blacktie-build ---
> [INFO] Skipping JaCoCo for project with packaging type 'pom'
> [INFO] surefireArgLine set to
> [INFO]
> [INFO] <<< maven-source-plugin:2.2.1:jar (attach-sources) @ wildfly-blacktie-build <<<
> [INFO]
> [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @ wildfly-blacktie-build ---
> [INFO]
> [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources) @ wildfly-blacktie-build ---
> [INFO]
> [INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ wildfly-blacktie-build ---
> [INFO] Reading assembly descriptor: src/main/assembly/zip.xml
> [INFO] Building zip: /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-blacktie/build/target/wildfly-blacktie-build-5.0.2.Final-SNAPSHOT-bin.zip
> [INFO]
> [INFO] --- maven-install-plugin:2.4:install (default-install) @ wildfly-blacktie-build ---
> [INFO] Installing /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-blacktie/build/pom.xml to /home/hudson/.m2/repository/org/jboss/narayana/blacktie/wildfly-blacktie-build/5.0.2.Final-SNAPSHOT/wildfly-blacktie-build-5.0.2.Final-SNAPSHOT.pom
> [INFO] Installing /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-blacktie/build/target/wildfly-blacktie-build-5.0.2.Final-SNAPSHOT-bin.zip to /home/hudson/.m2/repository/org/jboss/narayana/blacktie/wildfly-blacktie-build/5.0.2.Final-SNAPSHOT/wildfly-blacktie-build-5.0.2.Final-SNAPSHOT-bin.zip
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WildFly: Blacktie Subsystem Parent ................ SUCCESS [2.417s]
> [INFO] WildFly: Blacktie Subsystem ....................... SUCCESS [8.332s]
> [INFO] WildFly: Blacktie Subsystem Build ................. SUCCESS [1.941s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 13.141s
> [INFO] Finished at: Fri Apr 04 23:23:50 BST 2014
> [INFO] Final Memory: 56M/253M
> [INFO] ------------------------------------------------------------------------
> Archive: /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-blacktie/build/target/wildfly-blacktie-build-5.0.2.Final-SNAPSHOT-bin.zip
> creating: /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-8.0.1.Final-SNAPSHOT/modules/system/layers/base/org/wildfly/extension/blacktie/
> creating: /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-8.0.1.Final-SNAPSHOT/modules/system/layers/base/org/wildfly/extension/blacktie/main/
> extracting: /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-8.0.1.Final-SNAPSHOT/modules/system/layers/base/org/wildfly/extension/blacktie/main/wildfly-blacktie-5.0.2.Final-SNAPSHOT.jar
> inflating: /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-8.0.1.Final-SNAPSHOT/modules/system/layers/base/org/wildfly/extension/blacktie/main/module.xml
> Buildfile: /home/hudson/workspace/narayana-codeCoverage/blacktie/scripts/hudson/initializeJBoss.xml
> initializeJBoss:
> BUILD FAILED
> /home/hudson/workspace/narayana-codeCoverage/blacktie/scripts/hudson/initializeJBoss.xml:5: Warning: Could not find file /home/hudson/workspace/narayana-codeCoverage/blacktie/wildfly-8.0.1.Final-SNAPSHOT/docs/examples/configs/standalone-blacktie.xml to copy.
> {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
10 years, 8 months
[JBoss JIRA] (JBTM-2147) Transactions are leaked when XAResource misbehaves
by Koen Janssens (JIRA)
Koen Janssens created JBTM-2147:
-----------------------------------
Summary: Transactions are leaked when XAResource misbehaves
Key: JBTM-2147
URL: https://issues.jboss.org/browse/JBTM-2147
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JTS
Affects Versions: 4.17.7
Environment: jboss EAP 6.1.1
Reporter: Koen Janssens
Assignee: Tom Jenkinson
We have noticed that arjuna leaks transactions when something 'unexpected' happens during tx aborting. The transaction stays in 'aborting' state while it does notify TxLIsteners that the tx has ended.
This can be reproduced as follows:
* A TX is started and both a DB (last)resource and horntq (XA) resource get enlisted. The tx takes a long time and times out.
* Arjuna reaper thread notices the time out and starts a worker thread to cancel the TX.
* Before the worker thread can 'abort' the hornetq XA resource, the arjuna worker thread is interruped (txReaperCancelWaitPeriod expires) by arjuna
* Since the worker thread is interruped, the hornetq XA resource throws an 'HornetQInterruptedException'
* This unexpected exception causes arjuna to notify registered javax/transaction/Synchronization's (and return DB connection to the pool), without ending the Tx.
>From then on, jboss logs are full of:
Trying to start a new transaction when old is not complete: Old: < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff40bab98c:1f71a485:5335ece7:3625a31, node_name=1, branch_uid=0:ffff40bab98c:1f71a485:5335ece7:3625bbc, subordinatenodename=null, eis_name=java:/XAOracleDS >, New < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff40bab98c:1f71a485:5335ece7:3641efc, node_name=1, branch_uid=0:ffff40bab98c:1f71a485:5335ece7:36420a1, subordinatenodename=null, eis_name=java:/XAOracleDS >, Flags 0
Although the root cause is a misbehaving hornetq resource, I think arjuna should be a bit more resilient.
More background in https://access.redhat.com/support/cases/01061583/
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-2146) wsat-jta-multi_hop quickstart doesn't work
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2146?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris resolved JBTM-2146.
-----------------------------------
Fix Version/s: (was: 5.0.2)
(was: 4.17.19)
Resolution: Rejected
> wsat-jta-multi_hop quickstart doesn't work
> ------------------------------------------
>
> Key: JBTM-2146
> URL: https://issues.jboss.org/browse/JBTM-2146
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Demonstrator, TxBridge, XTS
> Environment: Windows 8.1
> Java 7
> Same for jboss-eap-6.1/jboss-eap-6.2/jboss-eap-6.3
> Reporter: Antonin Danek
> Assignee: Gytis Trikleris
>
> When running the wsat-jta-multi_hop quick start, the test fails:
> (despite standalone-xts.xml is provided exactly how the instructions say + 127.0.0.1:9990 is accessible using the browser)
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest
> IV 06, 2014 2:10:16 DOP. org.jboss.arquillian.container.impl.MapObject populate
> WARNING: Configuration contain properties not supported by the backing object org.jboss.as.arquillian
> .container.remote.RemoteContainerConfiguration
> Unused property entries: {serverConfig=standalone-xts.xml}
> Supported property names: [managementPort, username, managementAddress, managementProtocol, password]
> ....
> WARN: Cannot undeploy: test.war
> org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: j
> ava.lang.RuntimeException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting:
> //127.0.0.1:9990. The connection failed
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.undeploy(ServerDe
> ploymentHelper.java:109)
> at org.jboss.as.arquillian.container.ArchiveDeployer.undeploy(ArchiveDeployer.java:55)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.undeploy(CommonDeployableConta
> iner.java:152)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
> ainerDeployController.java:205)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
> ainerDeployController.java:185)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOper
> ation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(Co
> ntainerDeployController.java:184)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploym
> entContext(ContainerDeploymentContextHandler.java:78)
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-2146) wsat-jta-multi_hop quickstart doesn't work
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2146?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris closed JBTM-2146.
---------------------------------
> wsat-jta-multi_hop quickstart doesn't work
> ------------------------------------------
>
> Key: JBTM-2146
> URL: https://issues.jboss.org/browse/JBTM-2146
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Demonstrator, TxBridge, XTS
> Environment: Windows 8.1
> Java 7
> Same for jboss-eap-6.1/jboss-eap-6.2/jboss-eap-6.3
> Reporter: Antonin Danek
> Assignee: Gytis Trikleris
>
> When running the wsat-jta-multi_hop quick start, the test fails:
> (despite standalone-xts.xml is provided exactly how the instructions say + 127.0.0.1:9990 is accessible using the browser)
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest
> IV 06, 2014 2:10:16 DOP. org.jboss.arquillian.container.impl.MapObject populate
> WARNING: Configuration contain properties not supported by the backing object org.jboss.as.arquillian
> .container.remote.RemoteContainerConfiguration
> Unused property entries: {serverConfig=standalone-xts.xml}
> Supported property names: [managementPort, username, managementAddress, managementProtocol, password]
> ....
> WARN: Cannot undeploy: test.war
> org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: j
> ava.lang.RuntimeException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting:
> //127.0.0.1:9990. The connection failed
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.undeploy(ServerDe
> ploymentHelper.java:109)
> at org.jboss.as.arquillian.container.ArchiveDeployer.undeploy(ArchiveDeployer.java:55)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.undeploy(CommonDeployableConta
> iner.java:152)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
> ainerDeployController.java:205)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
> ainerDeployController.java:185)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOper
> ation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(Co
> ntainerDeployController.java:184)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploym
> entContext(ContainerDeploymentContextHandler.java:78)
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-2146) wsat-jta-multi_hop quickstart doesn't work
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2146?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris reopened JBTM-2146:
-----------------------------------
> wsat-jta-multi_hop quickstart doesn't work
> ------------------------------------------
>
> Key: JBTM-2146
> URL: https://issues.jboss.org/browse/JBTM-2146
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Demonstrator, TxBridge, XTS
> Environment: Windows 8.1
> Java 7
> Same for jboss-eap-6.1/jboss-eap-6.2/jboss-eap-6.3
> Reporter: Antonin Danek
> Assignee: Gytis Trikleris
> Fix For: 4.17.19, 5.0.2
>
>
> When running the wsat-jta-multi_hop quick start, the test fails:
> (despite standalone-xts.xml is provided exactly how the instructions say + 127.0.0.1:9990 is accessible using the browser)
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest
> IV 06, 2014 2:10:16 DOP. org.jboss.arquillian.container.impl.MapObject populate
> WARNING: Configuration contain properties not supported by the backing object org.jboss.as.arquillian
> .container.remote.RemoteContainerConfiguration
> Unused property entries: {serverConfig=standalone-xts.xml}
> Supported property names: [managementPort, username, managementAddress, managementProtocol, password]
> ....
> WARN: Cannot undeploy: test.war
> org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: j
> ava.lang.RuntimeException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting:
> //127.0.0.1:9990. The connection failed
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.undeploy(ServerDe
> ploymentHelper.java:109)
> at org.jboss.as.arquillian.container.ArchiveDeployer.undeploy(ArchiveDeployer.java:55)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.undeploy(CommonDeployableConta
> iner.java:152)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
> ainerDeployController.java:205)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
> ainerDeployController.java:185)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOper
> ation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(Co
> ntainerDeployController.java:184)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploym
> entContext(ContainerDeploymentContextHandler.java:78)
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-2146) wsat-jta-multi_hop quickstart doesn't work
by Antonin Danek (JIRA)
[ https://issues.jboss.org/browse/JBTM-2146?page=com.atlassian.jira.plugin.... ]
Antonin Danek resolved JBTM-2146.
---------------------------------
Resolution: Done
> wsat-jta-multi_hop quickstart doesn't work
> ------------------------------------------
>
> Key: JBTM-2146
> URL: https://issues.jboss.org/browse/JBTM-2146
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Demonstrator, TxBridge, XTS
> Environment: Windows 8.1
> Java 7
> Same for jboss-eap-6.1/jboss-eap-6.2/jboss-eap-6.3
> Reporter: Antonin Danek
> Assignee: Gytis Trikleris
> Fix For: 4.17.19, 5.0.2
>
>
> When running the wsat-jta-multi_hop quick start, the test fails:
> (despite standalone-xts.xml is provided exactly how the instructions say + 127.0.0.1:9990 is accessible using the browser)
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest
> IV 06, 2014 2:10:16 DOP. org.jboss.arquillian.container.impl.MapObject populate
> WARNING: Configuration contain properties not supported by the backing object org.jboss.as.arquillian
> .container.remote.RemoteContainerConfiguration
> Unused property entries: {serverConfig=standalone-xts.xml}
> Supported property names: [managementPort, username, managementAddress, managementProtocol, password]
> ....
> WARN: Cannot undeploy: test.war
> org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: j
> ava.lang.RuntimeException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting:
> //127.0.0.1:9990. The connection failed
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.undeploy(ServerDe
> ploymentHelper.java:109)
> at org.jboss.as.arquillian.container.ArchiveDeployer.undeploy(ArchiveDeployer.java:55)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.undeploy(CommonDeployableConta
> iner.java:152)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
> ainerDeployController.java:205)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
> ainerDeployController.java:185)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOper
> ation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(Co
> ntainerDeployController.java:184)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploym
> entContext(ContainerDeploymentContextHandler.java:78)
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-2146) wsat-jta-multi_hop quickstart doesn't work
by Antonin Danek (JIRA)
[ https://issues.jboss.org/browse/JBTM-2146?page=com.atlassian.jira.plugin.... ]
Antonin Danek commented on JBTM-2146:
-------------------------------------
I've used wildfly-8.0.1.Final-SNAPSHOT and 5.0.2.Final-SNAPSHOT Quickstarts now and it work just fine.
My bad, sorry. I've been trying some jboss-eap quickstarts before and I didn't realize I have to run these on wildfly, not just jboss eap.
> wsat-jta-multi_hop quickstart doesn't work
> ------------------------------------------
>
> Key: JBTM-2146
> URL: https://issues.jboss.org/browse/JBTM-2146
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Demonstrator, TxBridge, XTS
> Environment: Windows 8.1
> Java 7
> Same for jboss-eap-6.1/jboss-eap-6.2/jboss-eap-6.3
> Reporter: Antonin Danek
> Assignee: Gytis Trikleris
> Fix For: 4.17.19, 5.0.2
>
>
> When running the wsat-jta-multi_hop quick start, the test fails:
> (despite standalone-xts.xml is provided exactly how the instructions say + 127.0.0.1:9990 is accessible using the browser)
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest
> IV 06, 2014 2:10:16 DOP. org.jboss.arquillian.container.impl.MapObject populate
> WARNING: Configuration contain properties not supported by the backing object org.jboss.as.arquillian
> .container.remote.RemoteContainerConfiguration
> Unused property entries: {serverConfig=standalone-xts.xml}
> Supported property names: [managementPort, username, managementAddress, managementProtocol, password]
> ....
> WARN: Cannot undeploy: test.war
> org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: j
> ava.lang.RuntimeException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting:
> //127.0.0.1:9990. The connection failed
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.undeploy(ServerDe
> ploymentHelper.java:109)
> at org.jboss.as.arquillian.container.ArchiveDeployer.undeploy(ArchiveDeployer.java:55)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.undeploy(CommonDeployableConta
> iner.java:152)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
> ainerDeployController.java:205)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
> ainerDeployController.java:185)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOper
> ation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(Co
> ntainerDeployController.java:184)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploym
> entContext(ContainerDeploymentContextHandler.java:78)
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-2146) wsat-jta-multi_hop quickstart doesn't work
by Antonin Danek (JIRA)
[ https://issues.jboss.org/browse/JBTM-2146?page=com.atlassian.jira.plugin.... ]
Antonin Danek edited comment on JBTM-2146 at 4/7/14 12:37 PM:
--------------------------------------------------------------
I've used wildfly-8.0.1.Final-SNAPSHOT and 5.0.2.Final-SNAPSHOT Quickstarts now and it works just fine.
My bad, sorry. I've been trying some jboss-eap quickstarts before and I didn't realize I have to run these on wildfly, not just jboss eap.
was (Author: antonindanek):
I've used wildfly-8.0.1.Final-SNAPSHOT and 5.0.2.Final-SNAPSHOT Quickstarts now and it work just fine.
My bad, sorry. I've been trying some jboss-eap quickstarts before and I didn't realize I have to run these on wildfly, not just jboss eap.
> wsat-jta-multi_hop quickstart doesn't work
> ------------------------------------------
>
> Key: JBTM-2146
> URL: https://issues.jboss.org/browse/JBTM-2146
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Demonstrator, TxBridge, XTS
> Environment: Windows 8.1
> Java 7
> Same for jboss-eap-6.1/jboss-eap-6.2/jboss-eap-6.3
> Reporter: Antonin Danek
> Assignee: Gytis Trikleris
> Fix For: 4.17.19, 5.0.2
>
>
> When running the wsat-jta-multi_hop quick start, the test fails:
> (despite standalone-xts.xml is provided exactly how the instructions say + 127.0.0.1:9990 is accessible using the browser)
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest
> IV 06, 2014 2:10:16 DOP. org.jboss.arquillian.container.impl.MapObject populate
> WARNING: Configuration contain properties not supported by the backing object org.jboss.as.arquillian
> .container.remote.RemoteContainerConfiguration
> Unused property entries: {serverConfig=standalone-xts.xml}
> Supported property names: [managementPort, username, managementAddress, managementProtocol, password]
> ....
> WARN: Cannot undeploy: test.war
> org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: j
> ava.lang.RuntimeException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting:
> //127.0.0.1:9990. The connection failed
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.undeploy(ServerDe
> ploymentHelper.java:109)
> at org.jboss.as.arquillian.container.ArchiveDeployer.undeploy(ArchiveDeployer.java:55)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.undeploy(CommonDeployableConta
> iner.java:152)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
> ainerDeployController.java:205)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
> ainerDeployController.java:185)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOper
> ation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(Co
> ntainerDeployController.java:184)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploym
> entContext(ContainerDeploymentContextHandler.java:78)
--
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
10 years, 8 months