[JBoss JIRA] (JBTM-1622) StackOverflowError when loading org.jboss.ws.common:main module
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1622?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1622:
-------------------------------------
Seems to only fail on 32bit machines: jaime & tenafly. Succeeds on 64 bit beacon and hoboken.
jaime is running JDK 1.7.0_09, where as hoboken runs jdk1.7.0_17. I tried running the test many times (~5) on hoboken with JDK 1.7.0_09, but I couldn't get it to fail.
> StackOverflowError when loading org.jboss.ws.common:main module
> ---------------------------------------------------------------
>
> Key: JBTM-1622
> URL: https://issues.jboss.org/browse/JBTM-1622
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M3
>
>
> See: http://172.17.131.2/job/narayana/229
> {noformat}
> Tests in error:
> testRollback(org.jboss.as.test.xts.simple.wsat.client.WSATTestCase): Receiver[com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.][com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.(..)
> testCommit(org.jboss.as.test.xts.simple.wsat.client.WSATTestCase): Receiver[com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.][com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.(..)
> testCannotComplete(org.jboss.as.test.xts.simple.wsba.coordinatorcompletion.client.WSBACoordinatorCompletionTestCase): Unexpected exception, expected<com.arjuna.wst.TransactionRolledBackException> but was<java.lang.Exception>
> testCancel(org.jboss.as.test.xts.simple.wsba.coordinatorcompletion.client.WSBACoordinatorCompletionTestCase): Receiver[com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.][com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.(..)
> testSuccess(org.jboss.as.test.xts.simple.wsba.coordinatorcompletion.client.WSBACoordinatorCompletionTestCase): Receiver[com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.][com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.(..)
> testCancel(org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase): Receiver[com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.][com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.(..)
> testSuccess(org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase): Receiver[com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.][com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.(..)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (JBTM-1622) StackOverflowError when loading org.jboss.ws.common:main module
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1622?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1622:
-------------------------------------
Also happens for non-WS tests. Here it happened in the JAX-RS AS integration tests:
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/230/artifact/jbos...
> StackOverflowError when loading org.jboss.ws.common:main module
> ---------------------------------------------------------------
>
> Key: JBTM-1622
> URL: https://issues.jboss.org/browse/JBTM-1622
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M3
>
>
> See: http://172.17.131.2/job/narayana/229
> {noformat}
> Tests in error:
> testRollback(org.jboss.as.test.xts.simple.wsat.client.WSATTestCase): Receiver[com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.][com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.(..)
> testCommit(org.jboss.as.test.xts.simple.wsat.client.WSATTestCase): Receiver[com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.][com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.(..)
> testCannotComplete(org.jboss.as.test.xts.simple.wsba.coordinatorcompletion.client.WSBACoordinatorCompletionTestCase): Unexpected exception, expected<com.arjuna.wst.TransactionRolledBackException> but was<java.lang.Exception>
> testCancel(org.jboss.as.test.xts.simple.wsba.coordinatorcompletion.client.WSBACoordinatorCompletionTestCase): Receiver[com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.][com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.(..)
> testSuccess(org.jboss.as.test.xts.simple.wsba.coordinatorcompletion.client.WSBACoordinatorCompletionTestCase): Receiver[com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.][com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.(..)
> testCancel(org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase): Receiver[com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.][com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.(..)
> testSuccess(org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase): Receiver[com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.][com.arjuna.webservices.util.InvalidEnumerationException: ARJUNA042002: Invalid fault type enumeration: No namespace on "html" element. You must send a SOAP request.(..)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (JBTM-1625) Retain the commit id of the app server being used for testing
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-1625:
-----------------------------------
Summary: Retain the commit id of the app server being used for testing
Key: JBTM-1625
URL: https://issues.jboss.org/browse/JBTM-1625
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Build System
Reporter: Tom Jenkinson
Assignee: Gytis Trikleris
Priority: Critical
Fix For: 5.0.0.M3
When we rebase jboss-as we should log the commit of the rebased master branch.
If you just add the command:
echo This is the JBoss-AS commit
git rev-parse upstream/master
That will be enough as the build log will have:
This is the JBoss-AS commit
d56a7873e277017e56fcbfc74f814e0d2703f503
For example.
This is important when we have problems introduced in the AS so we can help to identify when the problem is first observed more defined way than a timestamp (which is timezoned against a failure in Newcastle and a GitHub timestamp (whenever they are)).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (JBTM-1460) TXBridge test hangs when Arquillian starts the container
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1460?page=com.atlassian.jira.plugin.... ]
Mark Little updated JBTM-1460:
------------------------------
Component/s: Testing
TxBridge
> TXBridge test hangs when Arquillian starts the container
> --------------------------------------------------------
>
> Key: JBTM-1460
> URL: https://issues.jboss.org/browse/JBTM-1460
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, TxBridge
> Environment: AS7 master as of 2013-02-05
> Arquillian core: 1.0.0.Final
> Arquillian osgi: 1.0.2.Final
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.Final
>
> Attachments: client.log, server.log
>
>
> See: 172.17.131.2/job/btny-pulls-narayana/345/ where the job has hung for about 16hrs.
> From looking at the stack trace in client.log (attached):
> {code}
> at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:107)
> at org.jboss.jbossts.txbridge.tests.inbound.junit.InboundBasicTests.setUp(InboundBasicTests.java:75)
> {code}
> The hang is happening on this line:
> {code}
> controller.start(CONTAINER);
> {code}
> Which is starting the container 'jboss', which is described in the arquillian.xml as:
> {code}
> <container qualifier="jboss" default="true" mode="manual">
> <configuration>
> <property name="javaVmArguments">${server.jvm.args}</property>
> <property name="serverConfig">standalone-xts.xml</property>
> <property name="managementAddress">${node.address}</property>
> </configuration>
> </container>
> {code}
> From looking at server.log (attached) it looks like the server has started and deployed the deployments:
> First of two deployments:
> {code}
> 18:36:32,013 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "txbridge-inbound-tests-service.war" (runtime-name : "txbridge-inbound-tests-service.war")
> {code}
> Second of two deployments:
> {code}
> 18:36:32,975 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "txbridge-inbound-tests-client.war" (runtime-name : "txbridge-inbound-tests-client.war")
> {code}
> Notice that the output above is that last line of output on the server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months