[
https://issues.jboss.org/browse/JBTM-1262?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1262:
-------------------------------------
I don't know why the KillProcessor is not detecting the change, but it is likely due
to a change in jboss-cli.sh that means the command we invoke is invalid.
Backporting JBTM-1241 should work around this issue, whilst making the tests more stable
and easier to maintain.
JBossAS7ServerKillProcessor doesn't detect when server killed
-------------------------------------------------------------
Key: JBTM-1262
URL:
https://issues.jboss.org/browse/JBTM-1262
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.5
See:
http://172.17.131.2/job/jbossts-branch416-EAP601-java7/170/artifact/XTS/s...
In particular:
{code}
08:30:11,018 INFO [stdout] (TaskWorker-1) rule.debug{kill JVM at commit} : !!!killing
JVM!!!
Sep 20, 2012 8:30:14 AM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Sep 20, 2012 8:30:40 AM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Sep 20, 2012 8:31:06 AM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
{code}
This shows that the server was killed by Byteman, but the KillProcessor still thinks it
is alive.
--
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