Encourage named threads for easier debugging

wocommunity · Apr 25, 2016 · 3f81ea6 · 3f81ea6
1 parent f04e5d2
commit 3f81ea6
Showing 1 changed file with 6 additions and 3 deletions.
diff --git a/Frameworks/Core/ERExtensions/Sources/er/extensions/appserver/ERXShutdownHook.java b/Frameworks/Core/ERExtensions/Sources/er/extensions/appserver/ERXShutdownHook.java
@@ -53,7 +53,7 @@ public abstract class ERXShutdownHook extends Thread {
 
 	public static void initERXShutdownHook() {
 		System.out.println( "WILL ADD SHUTDOWNHOOK" );
-		Runtime.getRuntime().addShutdownHook( new Thread() {
+		Runtime.getRuntime().addShutdownHook( new Thread( "shutdown_complete_message_writer" ) {
 			@Override
 			public void run() {
 				try {
@@ -90,7 +90,8 @@ public static void useMe() {
 	}
 
 	/**
-	 * Construct a new nameless shutdown hook and register it.
+	 * Construct a new nameless shutdown hook and register it. It is recommended to use named hooks wherever
+	 * possible for easier debugging.
 	 */
 	public ERXShutdownHook() {
 		Runtime.getRuntime().addShutdownHook( this );
@@ -102,8 +103,10 @@ public ERXShutdownHook() {
 	 * @param hookName hook name
 	 */
 	public ERXShutdownHook( String hookName ) {
-		this();
+		super( hookName );
 		name = hookName;
+		Runtime.getRuntime().addShutdownHook( this );
+		ALL_HOOKS.add( this );
 	}
 
 	@Override