You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Dan Armbrust (JIRA)" <ji...@apache.org> on 2008/07/11 15:24:31 UTC
[jira] Created: (DAEMON-110) tomcat service can't be launched on
some systems with jre 1.6
tomcat service can't be launched on some systems with jre 1.6
-------------------------------------------------------------
Key: DAEMON-110
URL: https://issues.apache.org/jira/browse/DAEMON-110
Project: Commons Daemon
Issue Type: Bug
Environment: Windows environments where no instance of msvcr71.dll is on the system path.
Reporter: Dan Armbrust
On some windows systems, the tomcat service launcher will not start - instead, reporting the following errors:
[2008-04-07 10:48:33] [info] Procrun (2.0.3.0) started
[2008-04-07 10:48:33] [info] Running Service...
[2008-04-07 10:48:33] [info] Starting service...
[2008-04-07 10:48:33] [174 javajni.c] [error] The specified module could not
be found.
[2008-04-07 10:48:33] [986 prunsrv.c] [error] Failed creating java C:\Program
Files\Java\jre1.6.0_05\bin\client\jvm.dll
[2008-04-07 10:48:33] [1260 prunsrv.c] [error] ServiceStart returned 1
[2008-04-07 10:48:33] [info] Run service finished.
[2008-04-07 10:48:33] [info] Procrun finished.
This is due to a Sun bug which Sun refuses to fix:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6509291
So, the problem has to be worked around somewhere else. The tomcat developers feel that the issue should be fixed here, in commons-daemon.
There is a nice summary of what needs to be done here:
https://issues.apache.org/bugzilla/show_bug.cgi?id=41538#c26
And plenty more information in that thread on tomcat.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAEMON-110) tomcat service can't be launched on
some systems with jre 1.6
Posted by "Mladen Turk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DAEMON-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612879#action_12612879 ]
Mladen Turk commented on DAEMON-110:
------------------------------------
You can always add %JAVA_HOME%\jre\bin to the system PATH variable.
The solution that would allow procrun to set that dynamically will work only with Windows XP SP1+
by using SetDllDirectory, and that is the only way to do it without respawning the process.
Since this function is not present on earlier windows versions, the solution to the problem
will never cover the full set of supported OS's (WIN2k+)
> tomcat service can't be launched on some systems with jre 1.6
> -------------------------------------------------------------
>
> Key: DAEMON-110
> URL: https://issues.apache.org/jira/browse/DAEMON-110
> Project: Commons Daemon
> Issue Type: Bug
> Environment: Windows environments where no instance of msvcr71.dll is on the system path.
> Reporter: Dan Armbrust
>
> On some windows systems, the tomcat service launcher will not start - instead, reporting the following errors:
> [2008-04-07 10:48:33] [info] Procrun (2.0.3.0) started
> [2008-04-07 10:48:33] [info] Running Service...
> [2008-04-07 10:48:33] [info] Starting service...
> [2008-04-07 10:48:33] [174 javajni.c] [error] The specified module could not
> be found.
> [2008-04-07 10:48:33] [986 prunsrv.c] [error] Failed creating java C:\Program
> Files\Java\jre1.6.0_05\bin\client\jvm.dll
> [2008-04-07 10:48:33] [1260 prunsrv.c] [error] ServiceStart returned 1
> [2008-04-07 10:48:33] [info] Run service finished.
> [2008-04-07 10:48:33] [info] Procrun finished.
> This is due to a Sun bug which Sun refuses to fix:
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6509291
> So, the problem has to be worked around somewhere else. The tomcat developers feel that the issue should be fixed here, in commons-daemon.
> There is a nice summary of what needs to be done here:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=41538#c26
> And plenty more information in that thread on tomcat.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DAEMON-110) tomcat service can't be launched on
some systems with jre 1.6
Posted by "Mladen Turk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DAEMON-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mladen Turk resolved DAEMON-110.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.0.1
Fixed with the 1.0.2 but it require the OS to support SetDllLibrary path in the kernel meaning XP and later
> tomcat service can't be launched on some systems with jre 1.6
> -------------------------------------------------------------
>
> Key: DAEMON-110
> URL: https://issues.apache.org/jira/browse/DAEMON-110
> Project: Commons Daemon
> Issue Type: Bug
> Environment: Windows environments where no instance of msvcr71.dll is on the system path.
> Reporter: Dan Armbrust
> Assignee: Mladen Turk
> Fix For: 1.0.1
>
>
> On some windows systems, the tomcat service launcher will not start - instead, reporting the following errors:
> [2008-04-07 10:48:33] [info] Procrun (2.0.3.0) started
> [2008-04-07 10:48:33] [info] Running Service...
> [2008-04-07 10:48:33] [info] Starting service...
> [2008-04-07 10:48:33] [174 javajni.c] [error] The specified module could not
> be found.
> [2008-04-07 10:48:33] [986 prunsrv.c] [error] Failed creating java C:\Program
> Files\Java\jre1.6.0_05\bin\client\jvm.dll
> [2008-04-07 10:48:33] [1260 prunsrv.c] [error] ServiceStart returned 1
> [2008-04-07 10:48:33] [info] Run service finished.
> [2008-04-07 10:48:33] [info] Procrun finished.
> This is due to a Sun bug which Sun refuses to fix:
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6509291
> So, the problem has to be worked around somewhere else. The tomcat developers feel that the issue should be fixed here, in commons-daemon.
> There is a nice summary of what needs to be done here:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=41538#c26
> And plenty more information in that thread on tomcat.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DAEMON-110) tomcat service can't be launched on
some systems with jre 1.6
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DAEMON-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebb updated DAEMON-110:
------------------------
Fix Version/s: (was: 1.0.1)
1.0.2
> tomcat service can't be launched on some systems with jre 1.6
> -------------------------------------------------------------
>
> Key: DAEMON-110
> URL: https://issues.apache.org/jira/browse/DAEMON-110
> Project: Commons Daemon
> Issue Type: Bug
> Environment: Windows environments where no instance of msvcr71.dll is on the system path.
> Reporter: Dan Armbrust
> Assignee: Mladen Turk
> Fix For: 1.0.2
>
>
> On some windows systems, the tomcat service launcher will not start - instead, reporting the following errors:
> [2008-04-07 10:48:33] [info] Procrun (2.0.3.0) started
> [2008-04-07 10:48:33] [info] Running Service...
> [2008-04-07 10:48:33] [info] Starting service...
> [2008-04-07 10:48:33] [174 javajni.c] [error] The specified module could not
> be found.
> [2008-04-07 10:48:33] [986 prunsrv.c] [error] Failed creating java C:\Program
> Files\Java\jre1.6.0_05\bin\client\jvm.dll
> [2008-04-07 10:48:33] [1260 prunsrv.c] [error] ServiceStart returned 1
> [2008-04-07 10:48:33] [info] Run service finished.
> [2008-04-07 10:48:33] [info] Procrun finished.
> This is due to a Sun bug which Sun refuses to fix:
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6509291
> So, the problem has to be worked around somewhere else. The tomcat developers feel that the issue should be fixed here, in commons-daemon.
> There is a nice summary of what needs to be done here:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=41538#c26
> And plenty more information in that thread on tomcat.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.