[
https://issues.redhat.com/browse/WFLY-14199?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFLY-14199:
-----------------------------------------
Thanks, [~jamezp]. This kind of thing seems like an argument for WFCORE-436. Although in
general it seems like the basic WF design should allow for stop to be called in any case
where some start was called on some type that has a start/stop kind of method pair. It
might not be called when application deployment fails during boot, but when the server was
reloaded any MSC services that had been started during that failed deployment attempt
should have been stopped, allowing cleanup work to happen. And DeploymentUnitPhaseService
itself will call undeploy() on any successfully executed DUPs if a subsequent one in its
phase fails.
Individual MSC services that fail during their own start() method may not be doing cleanup
though.
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)