[jbossts-issues] [JBoss JIRA] (JBTM-1957) XTS crash recovery tests fail on IBM JDK
[
https://issues.jboss.org/browse/JBTM-1957?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1957:
-------------------------------------
Hi Ondra,
I think we should raise an Arquillian issue rather than the workaround, is that possible?
It should be quite straight forward to create a simple Arquillian test that just starts
the server to replicate this.
"Server is already running" can be quite a common issue, to start masking that
would not be perfect. Even though your wasStarted check does eliminate some possibilities,
I would have to defer to Paul on whether it is too much of a catchall solution. Also, how
come you externalised the "jboss-as" variable. I agree its nicer in a variable
but it makes the diff more involved.
Tom
XTS crash recovery tests fail on IBM JDK
----------------------------------------
Key: JBTM-1957
URL: https://issues.jboss.org/browse/JBTM-1957
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.17.10
Reporter: Ondřej Chaloupka
Assignee: Ondřej Chaloupka
Priority: Minor
The XTS crash recovery tests fail on IBM JDK. This seem to be a problem of Arquillian
settings.
What I do:
- switch to IBM JDK (JAVA_HOME + PATH)
- export JBOSS_HOME=/home/ochaloup/jboss/jboss-eap-*
- cd XTS/localjunit/crash-recovery-tests
- mvn test -Pxts.integration.tests.profile -Parq
-Dtest=com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit
What I get - tests fail with error:
The server is already running! Managed containers do not support connecting to running
server instances due to the possible harmful effect of connecting to the wrong server.
Please stop server before running or change to another type of container.
--
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