[JBoss JIRA] (JBTM-1824) Unexpected jdk1.7.0_03
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-1824:
-------------------------------------
Summary: Unexpected jdk1.7.0_03
Key: JBTM-1824
URL: https://issues.jboss.org/browse/JBTM-1824
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: BlackTie
Reporter: Gytis Trikleris
Assignee: Amos Feng
Priority: Minor
Fix For: 5.0.0.M4
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
{code}
BUILD SUCCESSFUL
Total time: 4 seconds
"Started server"
Calling "C:\hudson\workspace\narayana-windows2008-taconic\blacktie\jboss-as\bin\standalone.conf.bat"
\Java\jdk1.7.0_03' was unexpected at this time.
C:\hudson\workspace\narayana-windows2008-taconic\blacktie\jboss-as\bin>Calling .\tools\maven\bin\mvn.bat -gs tools\maven\conf\settings.xml -Dbpa=vc9x32 clean install "-Djbossas.ip.addr=WIN-5GKPEREVUOO"
{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, 11 months
[JBoss JIRA] (JBTM-1792) blacktie-stompconnect cannot be deployed
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1792?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris edited comment on JBTM-1792 at 7/4/13 11:16 AM:
----------------------------------------------------------------
Deleted
was (Author: gytis):
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
> blacktie-stompconnect cannot be deployed
> ----------------------------------------
>
> Key: JBTM-1792
> URL: https://issues.jboss.org/browse/JBTM-1792
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Gytis Trikleris
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/117/con...
> {code}
> [ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.3.Final:deploy (default) on project blacktie-stompconnect: Could not execute goal deploy on /home/hudson/workspace/narayana-dualstack/blacktie/stompconnect-1.0/target/blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar. Reason: Error could not execute operation '{
> [ERROR] "address" => [],
> [ERROR] "operation" => "read-attribute",
> [ERROR] "name" => "launch-type"
> [ERROR] }'. java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.3.Final:deploy (default) on project blacktie-stompconnect: Could not execute goal deploy on /home/hudson/workspace/narayana-dualstack/blacktie/stompconnect-1.0/target/blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar. Reason: Error could not execute operation '{
> "address" => [],
> "operation" => "read-attribute",
> "name" => "launch-type"
> }'.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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:601)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Could not execute goal deploy on /home/hudson/workspace/narayana-dualstack/blacktie/stompconnect-1.0/target/blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar. Reason: Error could not execute operation '{
> "address" => [],
> "operation" => "read-attribute",
> "name" => "launch-type"
> }'.
> at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:155)
> at org.jboss.as.plugin.deployment.AbstractAppDeployment.doExecute(AbstractAppDeployment.java:69)
> at org.jboss.as.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:111)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.lang.IllegalStateException: Error could not execute operation '{
> "address" => [],
> "operation" => "read-attribute",
> "name" => "launch-type"
> }'.
> at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:186)
> at org.jboss.as.plugin.common.AbstractServerConnection.getClient(AbstractServerConnection.java:132)
> at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:109)
> at org.jboss.as.plugin.deployment.AbstractDeployment.validate(AbstractDeployment.java:167)
> at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:133)
> ... 23 more
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:181)
> ... 27 more
> Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out
> at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:156)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:111)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:94)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 29 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :blacktie-stompconnect
> UID PID PPID C STIME TTY TIME CMD
> hudson 6674 25496 0 18:38 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 7393 6674 0 18:39 ? 00:00:00 ps -f
> hudson 25494 29253 0 18:02 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 25496 25494 0 18:02 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 29208 29205 0 Apr26 ? 00:38:02 sshd: hudson@notty
> hudson 29246 29208 0 Apr26 ? 00:00:00 bash -c cd '/home/hudson' && java -jar slave.jar
> hudson 29253 29246 0 Apr26 ? 01:49:14 java -jar slave.jar
> testsuite: no process killed
> server: no process killed
> client: no process killed
> cs: no process killed
> UID PID PPID C STIME TTY TIME CMD
> hudson 6674 25496 0 18:38 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 7404 6674 0 18:39 ? 00:00:00 ps -f
> hudson 25494 29253 0 18:02 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 25496 25494 0 18:02 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 29208 29205 0 Apr26 ? 00:38:02 sshd: hudson@notty
> hudson 29246 29208 0 Apr26 ? 00:00:00 bash -c cd '/home/hudson' && java -jar slave.jar
> hudson 29253 29246 0 Apr26 ? 01:49:14 java -jar slave.jar
> Some tests failed: http://172.17.131.2/job/narayana-dualstack/117/
> BlackTie build failed
> Build step 'Execute shell' marked build as failure
> Archiving artifacts
> Email was triggered for: Failure
> Sending email for trigger: Failure
> Sending email to: gtrikler(a)redhat.com zfeng(a)redhat.com mmusgrov(a)redhat.com tom.jenkinson(a)redhat.com mlittle(a)redhat.com
> Finished: FAILURE
> {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, 11 months
[JBoss JIRA] (JBTM-1747) CNFE when invoking a plain Web service with standalone-xts.xml config
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1747?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1747:
----------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/jbosstm/jboss-as/pull/15
> CNFE when invoking a plain Web service with standalone-xts.xml config
> ---------------------------------------------------------------------
>
> Key: JBTM-1747
> URL: https://issues.jboss.org/browse/JBTM-1747
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M4
>
> Original Estimate: 2 days
> Time Spent: 1 day, 1 hour
> Remaining Estimate: 0 minutes
>
> I've not had chance to reproduce this, but this is what I think I did:
> 1. Start Wildfly with the standalone-xts.xml configuration
> 2. Deploy a plain (non-XTS) web service to the server
> 3. Invoke the web service from inside this server, ensuring that org.jboss.xts is not in the dependencies. Which it shouldn't be if you are just invoking a plain WS.
> 4. Observe the CNFE on one of the TXBridge interceptors (I don't remember which).
> I think the problem is that XTS is adding the handler chain for doing default context propagation to all web services, rather than just those that have the XTS dependency.
--
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, 11 months
[JBoss JIRA] (JBTM-1747) CNFE when invoking a plain Web service with standalone-xts.xml config
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1747?focusedWorklogId=12429442&page=... ]
Gytis Trikleris logged work on JBTM-1747:
-----------------------------------------
Author: Gytis Trikleris
Created on: 04/Jul/13 10:41 AM
Start Date: 04/Jul/13 10:40 AM
Worklog Time Spent: 4 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 1 day, 3 hours)
Time Spent: 1 day, 1 hour (was: 5 hours)
Worklog Id: (was: 12429442)
> CNFE when invoking a plain Web service with standalone-xts.xml config
> ---------------------------------------------------------------------
>
> Key: JBTM-1747
> URL: https://issues.jboss.org/browse/JBTM-1747
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M4
>
> Original Estimate: 2 days
> Time Spent: 1 day, 1 hour
> Remaining Estimate: 0 minutes
>
> I've not had chance to reproduce this, but this is what I think I did:
> 1. Start Wildfly with the standalone-xts.xml configuration
> 2. Deploy a plain (non-XTS) web service to the server
> 3. Invoke the web service from inside this server, ensuring that org.jboss.xts is not in the dependencies. Which it shouldn't be if you are just invoking a plain WS.
> 4. Observe the CNFE on one of the TXBridge interceptors (I don't remember which).
> I think the problem is that XTS is adding the handler chain for doing default context propagation to all web services, rather than just those that have the XTS dependency.
--
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, 11 months
[JBoss JIRA] (JBTM-1809) At trace logging to facilitate discovery of the transaction hierarchy
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1809?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1809:
-----------------------------------
Sufficient logging for the txvis tool added. If additional lines are required please reopen this JIRA to get them included.
> At trace logging to facilitate discovery of the transaction hierarchy
> ---------------------------------------------------------------------
>
> Key: JBTM-1809
> URL: https://issues.jboss.org/browse/JBTM-1809
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 5.0.0.M3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Optional
> Fix For: 5.0.0.M4
>
>
> In a distributed JTS transaction there is insufficient information in the logs to facilitate the construction of the transaction hierarchy.
> For example when a transaction propagates between 3 servers the logs on server 3 do not indicate which of the two other servers has the parent transaction. This feature is required by the [https://community.jboss.org/wiki/TransactionMonitoringAndVisualization] tool.
> A possible solution is to print out the TM node identifier and the CORBA request id in the CORBA Client and Server Request Interceptors (in methods send_request and receive_request_service_contexts respectively).
--
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, 11 months
[JBoss JIRA] (JBTM-1611) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09, 10, 12 with jacorb and HornetQ object store enabled
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1611?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1611:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
The HQ store is not designed for use with an external recovery manager. So the fix I applied was to disable the remote recovery manager when running crash recovery tests with the hornetq store.
> Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09,10,12 with jacorb and HornetQ object store enabled
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1611
> URL: https://issues.jboss.org/browse/JBTM-1611
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 4.17.3
> Reporter: Ondřej Chaloupka
> Assignee: Michael Musgrove
> Fix For: 5.0.0.M4, 4.17.5
>
> Attachments: 0001-JBTM-1611-Make-recovery-passes-configurable.patch
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> During testing EAP 6.1.0.ER3 I'm hitting problem on QA tests of narayana project for branch 4.17 when running qa tests with jacorb and hornetq object store (happening for NIO and AIO).
> Tests which are failing:
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09
> - CrashRecovery09_Test01
> - CrashRecovery09_Test03
> - CrashRecovery09_Test05
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery10
> - CrashRecovery10_Test01
> - CrashRecovery10_Test03
> - CrashRecovery10_Test05
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12
> - CrashRecovery12_Test03
> - CrashRecovery12_Test06
> Detailed log could be found in job:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-61-jbossts-qa-te...
> I was trying to get more info on the test CrashRecovery09 but I can say just that the value honlder has value 0 instead of 1 on org.jboss.jbossts.qa.CrashRecovery09Clients.Client01a (line 84).
--
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, 11 months
[JBoss JIRA] (JBTM-1747) CNFE when invoking a plain Web service with standalone-xts.xml config
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1747?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1747:
--------------------------------
Comment: was deleted
(was: Conversation with Gytis on a potential solution:
pfrobinson: whilst you are at it, can you have a quick check to see if you can add modules to the classloader in that phase too?
[12:06pm] gytist: you mean dependencies like org.jboss.xts?
[12:10pm] pfrobinson: yeah
[12:10pm] pfrobinson: I want to scan for the use of @Transactional and then add the org.jboss.jts depenedency to the deployment
[12:10pm] gytist: I think it is, some of the subsystems automatically add dependencies
[12:11pm] pfrobinson: yeah, that was my thoughts too
[12:11pm] pfrobinson: for example, if persistence.xml is present, you add the jpa deps
[12:11pm] gytist: I saw it when I was researching my issue on Monday
[12:11pm] gytist: need to find it again
[12:12pm] gytist: grep for this class WSDependenciesProcessor
[12:12pm] gytist: that's what you need
[12:12pm] pfrobinson: great, thanks)
> CNFE when invoking a plain Web service with standalone-xts.xml config
> ---------------------------------------------------------------------
>
> Key: JBTM-1747
> URL: https://issues.jboss.org/browse/JBTM-1747
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M4
>
> Original Estimate: 2 days
> Time Spent: 5 hours
> Remaining Estimate: 1 day, 3 hours
>
> I've not had chance to reproduce this, but this is what I think I did:
> 1. Start Wildfly with the standalone-xts.xml configuration
> 2. Deploy a plain (non-XTS) web service to the server
> 3. Invoke the web service from inside this server, ensuring that org.jboss.xts is not in the dependencies. Which it shouldn't be if you are just invoking a plain WS.
> 4. Observe the CNFE on one of the TXBridge interceptors (I don't remember which).
> I think the problem is that XTS is adding the handler chain for doing default context propagation to all web services, rather than just those that have the XTS dependency.
--
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, 11 months
[JBoss JIRA] (JBTM-1792) blacktie-stompconnect cannot be deployed
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1792?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1792:
-------------------------------------
[~gytis], this is a different error, if you look in the console on 316 you can see the following:
BUILD SUCCESSFUL
Total time: 4 seconds
"Started server"
Calling "C:\hudson\workspace\narayana-windows2008-taconic\blacktie\jboss-as\bin\standalone.conf.bat"
\Java\jdk1.7.0_03' was unexpected at this time.
C:\hudson\workspace\narayana-windows2008-taconic\blacktie\jboss-as\bin>Calling .\tools\maven\bin\mvn.bat -gs tools\maven\conf\settings.xml -Dbpa=vc9x32 clean install "-Djbossas.ip.addr=WIN-5GKPEREVUOO"
In particular "\Java\jdk1.7.0_03' was unexpected at this time."
It is because there is something dodgy with the JAVA_HOME being used on taconic, please can you:
1. delete your comment above (so as not to cause confusion)
2. Raise a new jira with these details
3. change the link on http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon... to the new jira
The error does look really similar I grant you but it is definitely caused by for a different reason, this issue will now be marked as resolved - thanks!
> blacktie-stompconnect cannot be deployed
> ----------------------------------------
>
> Key: JBTM-1792
> URL: https://issues.jboss.org/browse/JBTM-1792
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/117/con...
> {code}
> [ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.3.Final:deploy (default) on project blacktie-stompconnect: Could not execute goal deploy on /home/hudson/workspace/narayana-dualstack/blacktie/stompconnect-1.0/target/blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar. Reason: Error could not execute operation '{
> [ERROR] "address" => [],
> [ERROR] "operation" => "read-attribute",
> [ERROR] "name" => "launch-type"
> [ERROR] }'. java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.3.Final:deploy (default) on project blacktie-stompconnect: Could not execute goal deploy on /home/hudson/workspace/narayana-dualstack/blacktie/stompconnect-1.0/target/blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar. Reason: Error could not execute operation '{
> "address" => [],
> "operation" => "read-attribute",
> "name" => "launch-type"
> }'.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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:601)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Could not execute goal deploy on /home/hudson/workspace/narayana-dualstack/blacktie/stompconnect-1.0/target/blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar. Reason: Error could not execute operation '{
> "address" => [],
> "operation" => "read-attribute",
> "name" => "launch-type"
> }'.
> at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:155)
> at org.jboss.as.plugin.deployment.AbstractAppDeployment.doExecute(AbstractAppDeployment.java:69)
> at org.jboss.as.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:111)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.lang.IllegalStateException: Error could not execute operation '{
> "address" => [],
> "operation" => "read-attribute",
> "name" => "launch-type"
> }'.
> at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:186)
> at org.jboss.as.plugin.common.AbstractServerConnection.getClient(AbstractServerConnection.java:132)
> at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:109)
> at org.jboss.as.plugin.deployment.AbstractDeployment.validate(AbstractDeployment.java:167)
> at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:133)
> ... 23 more
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:181)
> ... 27 more
> Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out
> at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:156)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:111)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:94)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 29 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :blacktie-stompconnect
> UID PID PPID C STIME TTY TIME CMD
> hudson 6674 25496 0 18:38 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 7393 6674 0 18:39 ? 00:00:00 ps -f
> hudson 25494 29253 0 18:02 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 25496 25494 0 18:02 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 29208 29205 0 Apr26 ? 00:38:02 sshd: hudson@notty
> hudson 29246 29208 0 Apr26 ? 00:00:00 bash -c cd '/home/hudson' && java -jar slave.jar
> hudson 29253 29246 0 Apr26 ? 01:49:14 java -jar slave.jar
> testsuite: no process killed
> server: no process killed
> client: no process killed
> cs: no process killed
> UID PID PPID C STIME TTY TIME CMD
> hudson 6674 25496 0 18:38 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 7404 6674 0 18:39 ? 00:00:00 ps -f
> hudson 25494 29253 0 18:02 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 25496 25494 0 18:02 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 29208 29205 0 Apr26 ? 00:38:02 sshd: hudson@notty
> hudson 29246 29208 0 Apr26 ? 00:00:00 bash -c cd '/home/hudson' && java -jar slave.jar
> hudson 29253 29246 0 Apr26 ? 01:49:14 java -jar slave.jar
> Some tests failed: http://172.17.131.2/job/narayana-dualstack/117/
> BlackTie build failed
> Build step 'Execute shell' marked build as failure
> Archiving artifacts
> Email was triggered for: Failure
> Sending email for trigger: Failure
> Sending email to: gtrikler(a)redhat.com zfeng(a)redhat.com mmusgrov(a)redhat.com tom.jenkinson(a)redhat.com mlittle(a)redhat.com
> Finished: FAILURE
> {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, 11 months