Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-1792

blacktie-stompconnect cannot be deployed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 5.0.0.M4
    • None
    • BlackTie
    • None

      http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/117/consoleText

      [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@redhat.com zfeng@redhat.com mmusgrov@redhat.com tom.jenkinson@redhat.com mlittle@redhat.com
Finished: FAILURE

            [JBTM-1792] blacktie-stompconnect cannot be deployed

            Tom Jenkinson added a comment -

            gtrikler@redhat.com, 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-taconic/316/ 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!

            Tom Jenkinson added a comment - gtrikler@redhat.com , 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-taconic/316/ 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!

            Gytis Trikleris (Inactive) added a comment - - edited

            Deleted

            Gytis Trikleris (Inactive) added a comment - - edited Deleted

            Tom Jenkinson added a comment -

            JAVA_OPTS was set in the job config, I have removed the memory settings from it as there wasn't a comment to say they were required. This should allow the server to start correctly.

            Tom Jenkinson added a comment - JAVA_OPTS was set in the job config, I have removed the memory settings from it as there wasn't a comment to say they were required. This should allow the server to start correctly.

            Tom Jenkinson added a comment -

            Check if JAVA_OPTS is set in the environment in the job config. It looks to be catted together with some incompatible value

            Tom Jenkinson added a comment - Check if JAVA_OPTS is set in the environment in the job config. It looks to be catted together with some incompatible value

            Zheng Feng added a comment -

            Hi Tom,

            JAVA_OPTS already set in environment; overriding default settings with values: -Xms2303m -Xmx2303m -XX:MaxPermSize=1024m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Xmx256m -XX:MaxPermSize=256m
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /home/hudson/workspace/narayana-dualstack/blacktie/jboss-as/

  JAVA: /usr/local/jdk1.7.0_17/bin/java

  JAVA_OPTS:  -server -XX:+UseCompressedOops -Xms2303m -Xmx2303m -XX:MaxPermSize=1024m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Xmx256m -XX:MaxPermSize=256m -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE

=========================================================================

Error occurred during initialization of VM
Incompatible minimum and maximum heap sizes specified

            It looks like jboss-as doest not start.

            Zheng Feng added a comment - Hi Tom, JAVA_OPTS already set in environment; overriding default settings with values: -Xms2303m -Xmx2303m -XX:MaxPermSize=1024m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Xmx256m -XX:MaxPermSize=256m ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/hudson/workspace/narayana-dualstack/blacktie/jboss-as/ JAVA: /usr/local/jdk1.7.0_17/bin/java JAVA_OPTS: -server -XX:+UseCompressedOops -Xms2303m -Xmx2303m -XX:MaxPermSize=1024m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Xmx256m -XX:MaxPermSize=256m -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE ========================================================================= Error occurred during initialization of VM Incompatible minimum and maximum heap sizes specified It looks like jboss-as doest not start.

              thjenkin@redhat.com Tom Jenkinson
              gtrikler@redhat.com Gytis Trikleris (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: