[OPENDJ-981] Stopping embedded OpenDJ does not stop all owned threads Created: 10/Jun/13  Updated: 08/Nov/19  Resolved: 12/Mar/16

Status: Done
Project: OpenDJ
Component/s: core server
Affects Version/s: 2.5.0-Xpress1, 2.4.6
Fix Version/s: Not applicable

Type: Bug Priority: Major
Reporter: Jean-Noël Rouvignac Assignee: Matthew Swift
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
duplicates OPENDJ-389 Embedded server leaks threads and thr... Dev backlog
Dev Assignee: Matthew Swift
QA Assignee: Christophe Sovant


Bug reported on the OpenDJ mailing list:

2013/6/8 Peter Varga <pvarga@opentext.com>


We are using OpenDJ embedded in servlet.
We use org.opends.server.util.EmbeddedUtils.startServer() to start the server, and org.opends.server.util.EmbeddedUtils.stopServer() to stop it.

After stopping it, the thread “Monitor Provider State Updater” is still running. Looking at the OpenDJ source code, it is evidently an OpenDJ thread – see MonitorProvider.java

It looks like the MonitorProvider class should register itself as a ServerShutdownListener.
Then in the implementation of processServerShutdown(), it should call SCHEDULER.shutdownNow().

Comment by Matthew Swift [ 06/Jan/16 ]

Re-opening for re-evaluation.

Comment by Matthew Swift [ 07/Nov/19 ]

Moved to closed state because the fixVersion has already been released.

Generated at Thu Jan 21 23:40:55 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.