[
https://issues.apache.org/jira/browse/DAEMON-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851867#action_12851867
]
Mladen Turk commented on DAEMON-100:
------------------------------------
You patch will not solve this issue. Procrun doesn't use Daemon java code.
The problem is that procrun unlike java.exe uses different thread for launching
jvm.
> Thread.currentThread().getContextClassLoader() == null when the program is
> runned by Prunsrv
> --------------------------------------------------------------------------------------------
>
> Key: DAEMON-100
> URL: https://issues.apache.org/jira/browse/DAEMON-100
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
> Environment: Win XP, jre1.5.0_11, -Djava.security.policy=<path to a
> file with following content>:
> grant {
> permission java.security.AllPermission "", "";
> permission com.sun.rmi.rmid.ExecPermission "<<ALL FILES>>";
> permission com.sun.rmi.rmid.ExecOptionPermission "*";
> };
> Reporter: Anton Vodonosov
> Attachments: DaemonLoader.patch
>
>
> Thread.currentThread().getContextClassLoader() == null when the program is
> runned by Prunsrv, but when we run the same system using java.exe,
> Thread.currentThread().getContextClassLoader() is not null.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
