-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
When a deployment that contains it's own logging configuration is undeployed the LogContext used for the deployment is not completely cleared. A GC cycle will end up doing this, but there is potential for issues, mainly on Windows, if a file handler is used during a redeploy. The file could be in-use by the old context.
During undeploy we should probably get the LogContextConfiguration and remove all the loggers, handlers, formatters and error managers.
Note that the only place I've seen this be an actual issue is in the test suite on Windows when a file handler is used and after the test is complete there is an attempt to delete the file.
- is blocked by
-
WFCORE-3951 Upgrade jboss-logmanager from 2.1.2.Final to 2.1.3.Final
- Resolved
-
WFCORE-3954 Upgrade jboss-logmanager from 2.1.3.Final to 2.1.4.Final
- Resolved
- is related to
-
LOGMGR-128 Create the ability to close or destroy a LogContext
- Resolved
-
WFCORE-5894 The test UndertowService is missing required permissions
- Closed