[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:
-------------------------------------
Check if JAVA_OPTS is set in the environment in the job config. It looks to be catted together with some incompatible value
> 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
12 years, 9 months
[JBoss JIRA] (JBTM-1792) blacktie-stompconnect cannot be deployed
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1792?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1792:
---------------------------------
Hi Tom,
{noformat}
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
{noformat}
It looks like jboss-as doest not start.
> 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
12 years, 9 months
[JBoss JIRA] (JBTM-1795) Use tests jar for common module test classes instead of using build-helper plugin
by Paul Gier (JIRA)
Paul Gier created JBTM-1795:
-------------------------------
Summary: Use tests jar for common module test classes instead of using build-helper plugin
Key: JBTM-1795
URL: https://issues.jboss.org/browse/JBTM-1795
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Build System
Reporter: Paul Gier
Assignee: Paul Gier
The build-helper-maven-plugin is currently used in several places to add test classes from the common module to the classpath. A better way to do this is to package up the common test classes in a jar, and then add the jar as a test dependency to the module(s) where they are needed.
--
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
12 years, 9 months
[JBoss JIRA] (JBTM-1364) Migrate "REST-AT to JTA" bridge into REST-TX component
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1364?focusedWorklogId=12429412&page=... ]
Gytis Trikleris logged work on JBTM-1364:
-----------------------------------------
Author: Gytis Trikleris
Created on: 24/Jun/13 12:39 PM
Start Date: 24/Jun/13 12:39 PM
Worklog Time Spent: 1 day
Issue Time Tracking
-------------------
Remaining Estimate: 1 day (was: 2 days)
Time Spent: 4 days (was: 3 days)
Worklog Id: (was: 12429412)
> Migrate "REST-AT to JTA" bridge into REST-TX component
> ------------------------------------------------------
>
> Key: JBTM-1364
> URL: https://issues.jboss.org/browse/JBTM-1364
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Demonstrator, REST, TxBridge
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Labels: assign
> Fix For: 5.0.0.M4
>
> Original Estimate: 1 week
> Time Spent: 4 days
> Remaining Estimate: 1 day
>
> The task is to the work Gytis did on his internship and migrate it into the REST-TX project.
> Tasks:
> 1. Review the current solution looking for:
> 1.1 Major issues that prevent an initial release
> 1.2 Test coverage
> 2. Make any required changes
> 3. Merge into the REST-TX project
> 4. Migrate the quickstarts accross
> 5. Create a blog post
> 5.1 Consider what the end user will need to do to use this technology. We may want to wait until REST-AT and this Bridge are shipped with a Narayana build of AS7. Otherwise the steps to get this working could be rather lengthy.
--
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
12 years, 9 months
[JBoss JIRA] (JBTM-1778) JBossTS qa testsuite fails on HP-UX
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1778?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1778:
-----------------------------------
Comment: was deleted
(was: There is already a config option to extend the test timeout period. Please could you try that option first. The testgroup config files are in the directory qa/testdefs. Edit the following files:
jbossts-qa-currenttests01-testdefs.xml
jbossts-qa-jtatests01-testdefs.xml
jbossts-qa-otsserver-testdefs.xml
jbossts-qa-otsserver-timeout-testdefs.xml
look for the <default_timeout value="xxx"/> entry and double the timeout value.)
> JBossTS qa testsuite fails on HP-UX
> -----------------------------------
>
> Key: JBTM-1778
> URL: https://issues.jboss.org/browse/JBTM-1778
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.6.1.CP13
> Reporter: Ondřej Chaloupka
> Assignee: Michael Musgrove
> Attachments: jstack-3091
>
>
> Hi Michael,
> as part of the EAP5.2.0 certification tests running on HP-UX 11v3 machines.
> I've hit problems with several testcases in the ts testsuite.
> We are testing on machines under this tag: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/hpux11v3/
> As I think that you know the testsuite the most I'm assigning this issue to you. If I've mistaken, please, reassign it.
> Those are:
> - jbossts-qa-currenttests01 number 20 stays stuck forever. It stays on current.resume call. I'm adding the jstack output, that I've got from the call, as attachment here.
> - jbossts-qa-jtatests01 number 005 fails with error message:
> java.lang.Exception: Test failed! JTATests01_Test005 got 1 fewer task passes than expected
> - jbossts-qa-otsserver number 010, 011, 012 and 017 fail with the error
> got 1 fewer task passes than expected
> I've tried to get some closer knowledge about the problem but I wasn't able much.
> Others tests from testsuite pass fine without error. Just their run time is longer in comparison with testsuite running on RHEL.
> We are running tests on jdk6 and jdk7 on 32bits and 64bits. These particular results belong to jdk6 and 32b.
> The jenkins run could be found at:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap5-jbossts-testsui...
> Would you have some suggestion about this?
--
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
12 years, 9 months
[JBoss JIRA] (JBTM-1778) JBossTS qa testsuite fails on HP-UX
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1778?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-1778:
----------------------------------------
There is already a config option to extend the test timeout period. Please could you try that option first. The testgroup config files are in the directory qa/testdefs. Edit the following files:
jbossts-qa-currenttests01-testdefs.xml
jbossts-qa-jtatests01-testdefs.xml
jbossts-qa-otsserver-testdefs.xml
jbossts-qa-otsserver-timeout-testdefs.xml
look for the <default_timeout value="xxx"/> entry and double the timeout value.
> JBossTS qa testsuite fails on HP-UX
> -----------------------------------
>
> Key: JBTM-1778
> URL: https://issues.jboss.org/browse/JBTM-1778
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.6.1.CP13
> Reporter: Ondřej Chaloupka
> Assignee: Michael Musgrove
> Attachments: jstack-3091
>
>
> Hi Michael,
> as part of the EAP5.2.0 certification tests running on HP-UX 11v3 machines.
> I've hit problems with several testcases in the ts testsuite.
> We are testing on machines under this tag: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/hpux11v3/
> As I think that you know the testsuite the most I'm assigning this issue to you. If I've mistaken, please, reassign it.
> Those are:
> - jbossts-qa-currenttests01 number 20 stays stuck forever. It stays on current.resume call. I'm adding the jstack output, that I've got from the call, as attachment here.
> - jbossts-qa-jtatests01 number 005 fails with error message:
> java.lang.Exception: Test failed! JTATests01_Test005 got 1 fewer task passes than expected
> - jbossts-qa-otsserver number 010, 011, 012 and 017 fail with the error
> got 1 fewer task passes than expected
> I've tried to get some closer knowledge about the problem but I wasn't able much.
> Others tests from testsuite pass fine without error. Just their run time is longer in comparison with testsuite running on RHEL.
> We are running tests on jdk6 and jdk7 on 32bits and 64bits. These particular results belong to jdk6 and 32b.
> The jenkins run could be found at:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap5-jbossts-testsui...
> Would you have some suggestion about this?
--
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
12 years, 9 months
[JBoss JIRA] (JBTM-1778) JBossTS qa testsuite fails on HP-UX
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1778?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1778:
-------------------------------------
Hi Ondra,
Can you try increasing the timeout for the tests that are failing?:
e.g.: for jbossts-qa-otsserver, you can modify <default_timeout value="960"/> in https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_6_1_GA_C...
Tom
> JBossTS qa testsuite fails on HP-UX
> -----------------------------------
>
> Key: JBTM-1778
> URL: https://issues.jboss.org/browse/JBTM-1778
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.6.1.CP13
> Reporter: Ondřej Chaloupka
> Assignee: Michael Musgrove
> Attachments: jstack-3091
>
>
> Hi Michael,
> as part of the EAP5.2.0 certification tests running on HP-UX 11v3 machines.
> I've hit problems with several testcases in the ts testsuite.
> We are testing on machines under this tag: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/hpux11v3/
> As I think that you know the testsuite the most I'm assigning this issue to you. If I've mistaken, please, reassign it.
> Those are:
> - jbossts-qa-currenttests01 number 20 stays stuck forever. It stays on current.resume call. I'm adding the jstack output, that I've got from the call, as attachment here.
> - jbossts-qa-jtatests01 number 005 fails with error message:
> java.lang.Exception: Test failed! JTATests01_Test005 got 1 fewer task passes than expected
> - jbossts-qa-otsserver number 010, 011, 012 and 017 fail with the error
> got 1 fewer task passes than expected
> I've tried to get some closer knowledge about the problem but I wasn't able much.
> Others tests from testsuite pass fine without error. Just their run time is longer in comparison with testsuite running on RHEL.
> We are running tests on jdk6 and jdk7 on 32bits and 64bits. These particular results belong to jdk6 and 32b.
> The jenkins run could be found at:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap5-jbossts-testsui...
> Would you have some suggestion about this?
--
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
12 years, 9 months
[JBoss JIRA] (JBTM-1794) Unknown host: lancel
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-1794:
-------------------------------------
Summary: Unknown host: lancel
Key: JBTM-1794
URL: https://issues.jboss.org/browse/JBTM-1794
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Environment: lancel
Reporter: Gytis Trikleris
Assignee: Tom Jenkinson
http://172.17.131.2/job/jbossts-EAP61-jdbcobjectstore/DB_TYPE=mysql,jdk=j...
{code}
Jun 21, 2013 6:29:31 PM com.sun.corba.se.impl.orb.ORBImpl getLocalHostName
WARNING: "IOP00710208: (INTERNAL) Unable to determine local hostname from InetAddress.getLocalHost().getHostName()"
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 208 completed: No
at com.sun.corba.se.impl.logging.ORBUtilSystemException.getLocalHostFailed(ORBUtilSystemException.java:3871)
at com.sun.corba.se.impl.logging.ORBUtilSystemException.getLocalHostFailed(ORBUtilSystemException.java:3889)
at com.sun.corba.se.impl.orb.ORBImpl.getLocalHostName(ORBImpl.java:1726)
at com.sun.corba.se.impl.orb.ORBImpl.set_parameters(ORBImpl.java:523)
at org.omg.CORBA.ORB.init(ORB.java:337)
at com.arjuna.orbportability.internal.orbspecific.orb.implementations.ORBBase.init(ORBBase.java:77)
at com.arjuna.orbportability.orb.core.ORB.init(ORB.java:90)
at com.arjuna.orbportability.ORB.initORB(ORB.java:186)
at com.hp.mwtests.ts.jta.jts.basic.UtilsUnitTest.setUp(UtilsUnitTest.java:96)
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:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
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)
Caused by: java.net.UnknownHostException: lancel: lancel
at java.net.InetAddress.getLocalHost(InetAddress.java:1360)
at com.sun.corba.se.impl.orb.ORBImpl.getLocalHostName(ORBImpl.java:1724)
... 36 more
{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
12 years, 9 months