thanks Mike .. that's pretty much what I'm using. What's the best way to determine why a service starts but does not finish initializing? This is the early initialization that's failing.
----- Original Message ----- From: "Manning, Mike" <[EMAIL PROTECTED]> To: "'Turbine Users List'" <[EMAIL PROTECTED]> Sent: Thursday, January 31, 2002 5:04 PM Subject: RE: Scheduler service not initializing > Using a 2.2b1 jar circa december-ish, I've got jobs working on Tomcat 4.0.1 > as an NT Service. > > -Mike > > -----Original Message----- > From: Dave Hollar [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 31, 2002 4:45 PM > To: [EMAIL PROTECTED] > Subject: Scheduler service not initializing > > > I've just moved my app to our deployment platform - nt 4.0 - which has > tomcat > installed as a service. Almost everything works as expected except the > scheduler service never finishes initializing and therefore our jobs never > run. In the logs I see the start but not the finish for the initialization. > > The biggest difference between the dev and deployment environments is that > tomcat is a service on the deployment platform. Could this be the problem? > Are there any other thoughts as to what the problem could be? > > Thanks- > Dave > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
