Bug 6702 - win 2k services not working
Summary: win 2k services not working
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 3
Classification: Unclassified
Component: Unknown (show other bugs)
Version: Unknown
Hardware: PC All
: P3 critical with 1 vote (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-27 03:44 UTC by gaobin
Modified: 2006-03-12 15:33 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gaobin 2002-02-27 03:44:18 UTC
When we tried to use "jk_nt_service.exe -i jakarta 
<TOMCAT_HOME>/conf/wrapper.properties" to add the service inside the service 
lists of the windows2k system, it can work; while furtherly use the 
command "net start jakarta" , this service cannot be started, and the error 
message is like "the service did not report an error action"(you can type the 
command NET HELPMSG 3534 to get the message)

I guessed the "jakarta" service maybe didn't actually add into the service 
list. As you know, under the dos command environment, if we type the 
command "net start", will get the entire services listed, which already added 
into the windows system. But the Jakarta is never on the list.

But the "tomcat.bat start" is fine under the same case, so where is the 
problem?
Comment 1 gaobin 2002-02-27 05:25:02 UTC
When we tried to use "jk_nt_service.exe -i jakarta 
<TOMCAT_HOME>/conf/wrapper.properties" to add the service inside the service 
lists of the windows2k system, it can work; while furtherly use the 
command "net start jakarta" , this service cannot be started, and the error 
message is like "the service did not report an error action"(you can type the 
command NET HELPMSG 3534 to get the message)

I guessed the "jakarta" service maybe didn't actually add into the service 
list. As you know, under the dos command environment, if we type the 
command "net start", will get the entire services listed, which already added 
into the windows system. But the Jakarta is never on the list.

But the "tomcat.bat start" is fine under the same case, so where is the 
problem? 
Comment 2 David Schreibman 2002-03-04 23:41:41 UTC
This works fine for us here ...

Did you at least edit the default wrapper.properties to point to your tomcat and
java homes?
Comment 3 Paul T Smith 2002-03-30 22:06:48 UTC
I am running the same system. Win2K with SP2 applied. The 3.3.1 release 
candidate worked fine but when I moved up to the final version I experienced 
the same issues. The service is added to the list and can be seen in the MMC 
Services snapin however when you try to start the service you get the 
standard "Service failed to start error message". Tomcat starts up fine using 
the startup.bat file.
Comment 4 Larry Isaacs 2002-04-01 14:44:17 UTC
The updated conf\wrapper.properties file in Tomcat 3.3.1 has a problem in that
wrapper.jvm.options should be non-blank or the $(wrapper.jvm.options) should
be removed from wrapper.cmd_line.  See if that fixes your problem.
Comment 5 Bridgit Horvatin 2002-04-15 14:56:32 UTC
I am having the same issue and have the same configuration, Win2000, SP2.  I 
have edited wrapper.properties to point to both Java Home and Tomcat Home and 
removed the wrapper.jvm.options from the cmd_line.  When the service attempting 
to start the message is returned.  Jakarta service could not be started.  The 
service did not report an error. 
Comment 6 Paul T Smith 2002-04-19 08:34:41 UTC
Try adding the -Xrs option as the parameters for the wrapper.jvm.options. I 
found this worked rather than removing the option altogether. This incidentally 
is required to stop the service from terminating unexpectedly when the user 
logs off.
Comment 7 Juergen Friedrich 2002-04-23 06:39:48 UTC
I have same problems like you. System is Win2000 Server, SP2. I ve done every hint on this problem, 
nothing works. What can I do else? Thanks for reply
Comment 8 David Schreibman 2002-04-25 23:05:33 UTC
I really don't think there's an actual bug here.

This works fine, but you have to be careful about escaping backslashes '\' (or 
just using forward slashes).  The other gotcha is dealing with spaces within the 
paths (part of this vulnerability was fixed in 3.3.1) but since people are 
expected to edit wrapper.properties there's always a chance for such errors.
Comment 9 Subra Mallampalli 2002-06-24 23:30:58 UTC
Check the jvm.stderr file in the logs directory. It might have some error logs. 
It turned out, for me, that the parser.jar file was missing, and so, SAX 
support was missing. I found it in crimson.jar which was missing in the default 
classpath in wrapper.properties
Comment 10 william.barker 2006-03-12 23:33:44 UTC
Per #8 I'm assuming that this is no longer an issue.

In any case, jk_nt_service is deprecated in favor of procrun from commons-
daemon.