[
https://issues.jboss.org/browse/JBTM-1134?page=com.atlassian.jira.plugin....
]
Ivo Studensky commented on JBTM-1134:
-------------------------------------
Paul,
I cannot see
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java6/189 ,
but you said that you had an issue between the last test of InboundCrashRecoveryTests and
the first test of OutboundCrashRecoveryTests which seems to be related to waiting between
tearDown() and setUp() methods. If the last test of InboundCrashRecoveryTests passes then
IMHO it cannot be related to kill() method.
To your points:
{quote}
Do you not mean, the server has started to shutdown, when it gets back from this method?
{quote}
The server should be already down at that moment as it is killed from within the
transaction which should end before getting back from web container, am I right?
{quote}
It sounds like from this statement that you think we should add a delay to make sure the
server is definitely down?
{quote}
I have not met such issue, so I am not sure, but I would try it. It could be an Arquillian
bug that it does not wait for full server shutdown. It is weird anyway.
TXBridge test failure: OutboundCrashRecoveryTests: The server is
already running!
---------------------------------------------------------------------------------
Key: JBTM-1134
URL:
https://issues.jboss.org/browse/JBTM-1134
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.0.0.M1
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 4.16.4, 5.0.0.M2
See:
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java6/189
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira