You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Eldin Okanovic (JIRA)" <ji...@apache.org> on 2016/07/02 09:20:10 UTC

[jira] [Created] (DAEMON-351) Context class loader of stopping thread is null

Eldin Okanovic created DAEMON-351:
-------------------------------------

             Summary: Context class loader of stopping thread is null
                 Key: DAEMON-351
                 URL: https://issues.apache.org/jira/browse/DAEMON-351
             Project: Commons Daemon
          Issue Type: Bug
          Components: Procrun
    Affects Versions: 1.0.15
         Environment: Windows 10 x64, Java 1.8.x.
            Reporter: Eldin Okanovic
            Priority: Minor


I don't know who is responsible for setting context class loader for current thread when starting and stopping service/app, but it's not set (is null) when stopping service.

I am using jvm mode and main method in both cases (when starting and stopping).
Example output in main method:

//output is sun.misc.Launcher$AppClassLoader@c387f44 when starting service
//output is null when stoping service
System.out.println(Thread.currentThread().getContextClassLoader());

This causes a problem when i need to load classes from app defined classpath in stopping process.

So, i was forced to manually get classloader instance when starting service, and set the same classloader instance when stoping a service.

//starting:
classLoader = classLoader = Thread.currentThread().getContextClassLoader();

//stoping:
Thread.currentThread().setContextClassLoader(classLoader);




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)