[
https://issues.redhat.com/browse/JBTM-3231?page=com.atlassian.jira.plugin...
]
Michael Musgrove commented on JBTM-3231:
----------------------------------------
Note that the resolution for this issue was to run each test in its own test suite. This
hypothesis is that this fix works because the root cause of the problem is that
org.jboss.arquillian.container.test.api.ContainerController#kill functionality is not
doing what I expect and sometimes does not release all of the container resources. Since
the above resolution seems to fix the problem I do not plan to investigate any further for
now.
Also note that two different failure modes were observed:
# org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not stop
container
# javax.ws.rs.ProcessingException: RESTEASY004655: Unable to invoke request:
org.apache.http.NoHttpResponseException: 127.0.0.1:8080 failed to respond
The plan is to enable trace logging on LRA CI jobs so that we have something to help debug
the problem if it is ever seen again.
LRA recovery test fails after restart on JDK11
----------------------------------------------
Key: JBTM-3231
URL:
https://issues.redhat.com/browse/JBTM-3231
Project: JBoss Transaction Manager
Issue Type: Bug
Components: LRA, Testing
Affects Versions: 5.10.1.Final
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Priority: Major
Fix For: 5.10.3.Final
CI testing:
LRACoordinatorTestCase=testRecovery2 fails to restart the container after crashing via
byteman on JDK11. Seems to be intermittent on Amsterdam CI and more consistent on Upshift,
for example:
http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/552/
https://ci-master-jenkins-csb-narayana.cloud.paas.psi.redhat.com/job/nara...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)