-
Type:
Bug
-
Status: Dev backlog
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2.6.0
-
Fix Version/s: None
-
Component/s: core server
-
Labels:
-
Support Ticket IDs:
If the server is used in a J2EE environment (e.g. OpenAM) then we need to be aware of leaking threads and thread locals, since these will prevent hot redeployment. In particular, all APIs which need to use additional threads should expose a means control the thread life-cycle, e.g. by using a ThreadFactory, Executor, etc.
In the server there are a couple of potential leaks:
- thread local org.opends.server.backends.jeb.ID2Entry.EntryCoder
- Idle time limit thread
- Monitor provider state updater
- is duplicated by
-
OPENDJ-981 Stopping embedded OpenDJ does not stop all owned threads
-
- Done
-
- is related to
-
OPENDJ-3191 Revisit how we are doing DN and AttributeDescription caching in the SDK
-
- Dev backlog
-
-
OPENDJ-2927 Ensure that there are no memory/thread leaks in the SDK when used in a J2EE environment
-
- Dev backlog
-