This sounds to me like the infamous NT service logout bug in the 1.3 JVM
and 1.x HotSpot JVMs. Can you check out this Bug report at Sun and see
if it fits the bill?:
http://developer.java.sun.com/developer/bugParade/bugs/4323062.html
Scott Stirling
Allaire
On 19 Dec 2000 22:52:20 -0600, BugRat Mail System wrote:
> Bug report #628 has just been filed.
>
> You can view the report at the following URL:
>
> <http://znutar.cortexity.com/BugRatViewer/ShowReport/628>
>
> REPORT #628 Details.
>
> Project: Tomcat
> Category: Bug Report
> SubCategory: New Bug Report
> Class: swbug
> State: received
> Priority: high
> Severity: serious
> Confidence: public
> Environment:
> Release: 3.2 and 3.2.1
> JVM Release: Sun Jvm 1.3
> Operating System: Whistler
> OS Release: Beta1
> Platform: Intel
>
> Synopsis:
> Will not run unless logged in as adminstrator
>
> Description:
> For some reason Tomcat will not run as a nt service unless I'm logged in as
>administrator, this occurs on both 3.2 and 3.2.1. I just installed 3.2.1 and tried it
>using the default configuration with the excpetion of changing wrapper.properties so
>it would run as a service.
>
> After installing when I'm logged in as administrator everything is fine, but if I'm
>not logged in the service stops. Also, no files are created leaving me to believe
>it's a permissions problem, but that's obviously on a guess. I tried changing the
>service so it logs in as administrator but that didn't work either, so that may not
>be the problem.
