[
https://issues.redhat.com/browse/WFLY-14199?page=com.atlassian.jira.plugi...
]
James Perkins commented on WFLY-14199:
--------------------------------------
It looks like the issue is the test. Since there is an attempt to deploy a broken
deployment the undeploy does not correctly happen leaving the {{ResteasyProviderFactory}}
in an invalid state because the server is not destroyed. I'm not sure if there is a
way in the {{RestEasyDeployment}} to invoke {{stop()}} on a failed deployment, but that
would be the solution. It is a little concerning one deployments bean manager can end up
associated with another deployment. I'll file a RESTEasy issue for that. However the
WildFly fix is to fix the test which I will submit a PR for.
OnOffOpenTracingTestCase leaves the server in a bad state
---------------------------------------------------------
Key: WFLY-14199
URL:
https://issues.redhat.com/browse/WFLY-14199
Project: WildFly
Issue Type: Bug
Components: MP OpenTracing, Test Suite
Affects Versions: 22.0.0.Alpha1
Reporter: Emmanuel Hugonnet
Assignee: Emmanuel Hugonnet
Priority: Major
{color:#333333}OnOffOpenTracingTestCase{color} will leave the server in such a state that
SimpleRestClientTestCase will fail. Removing and adding the opentracing subsystem to check
that it doesn't work once removedĀ shoudl be reevaluated.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)