I'd rather leave that one for somebody who has experience with Tomcat on a Win32 production server...
Chris -----Original Message----- From: Michael Duffy [mailto:[EMAIL PROTECTED] Sent: 02 October 2003 16:21 To: Tomcat Users List Subject: RE: One More Piece Of Info RE:JSTL Failure Under Tomcat 4.0.6 Hi Chris, Thank you for pointing that out. (I'd forgotten about it.) I see that I'm set up to log in as the System account, but the checkbox that says "Allow service to interact with local desktop" was unchecked. Hmmmm - could that have kept Tomcat from looking inside those JARs? I have two other JSTL apps that deployed and ran fine under that arrangement, but I'll try it with this one and see if that explains it. When I deploy on a test/prod server, should I ask the admin to set up the Tomcat service to log in as System with desktop access? Or is it better to set up a separate account? Please advise. Thanks - MOD Thanks for contributing to --- Walker Chris <[EMAIL PROTECTED]> wrote: > Hi Michael, > > This is a Winows thing, rather than a Tomcat thing. > Control > Panel->Services->Apache Tomcat 4.1->Startup will > show you the NT account the > service uses to start. By default services use the > System account, which > IIRC, can't access any network resources such as > mapped drives. It may also > be unable to access local files if they have > restrictive permissions. > > When you run Tomcat as a command it will run under > your login account. > > Chris > > -----Original Message----- > From: Michael Duffy [mailto:[EMAIL PROTECTED] > Sent: 02 October 2003 16:02 > To: Tomcat Users List > Subject: RE: One More Piece Of Info RE:JSTL Failure > Under Tomcat 4.0.6 > > > > Hi Chris, > > Hmmm, good question. There's no argument in the > tomcat.exe that calls for a username OR password. > > I'm admin on my own machine. The question is: what > about the deployment machine? If it's installed > under > the admin account, wouldn't it use the System admin > username and password? > > How would that affect looking inside the JARs for > the > TLD file? > > I'm not saying you're wrong. I have NO idea why the > service would fail and the command line succeed. > I'm > just trying to understand what's really happening > here > so I can correct it. Thanks - MOD > > > > --- Walker Chris <[EMAIL PROTECTED]> wrote: > > Michael, > > > > What account does the service run under? The > > default for most services is > > the System account, which may be having problems > > accessing some resource > > that your application needs. > > > > Chris > > > > -----Original Message----- > > From: Michael Duffy [mailto:[EMAIL PROTECTED] > > Sent: 02 October 2003 15:34 > > To: Tomcat Users List > > Subject: RE: One More Piece Of Info RE:JSTL > Failure > > Under Tomcat 4.0.6 > > > > > > > > Yoav, you're a genius. It came right up when I > > stopped the service and ran it from the command > > window. > > > > I'm NOT crazy. ;) Thank you! > > > > Now, the question is that when I deploy this it's > > going to be Tomcat 4.0.6 running as a service and > > connected to IIS on a Windows XP server. What did > I > > do wrong when I deployed Tomcat as a service that > > should be corrected now? > > > > My sincerest thanks. I've been at my wits end, > and > > haven't been thinking as clearly as I should. I'm > > glad that you were. - MOD > > > > > > --- "Shapira, Yoav" <[EMAIL PROTECTED]> wrote: > > > > > > Howdy, > > > > > > >Yes, I run Tomcat as a Windows service. I > asked > > > for > > > >both stdout.log and stderr.log when I set up > the > > > >service. Here's the script. - MOD > > > > > > Hmm, let's try to take another variable out of > the > > > equation. I'm sure > > > your script is fine, but can you run tomcat > > normally > > > from the command > > > line, not as a service, and not using your > script. > > > > > Use catalina.bat run > > > so that the console window stays open. > > > > > > Yoav Shapira > > > > > > > > > > > > This e-mail, including any attachments, is a > > > confidential business communication, and may > > contain > > > information that is confidential, proprietary > > and/or > > > privileged. This e-mail is intended only for > the > > > individual(s) to whom it is addressed, and may > not > > > be saved, copied, printed, disclosed or used by > > > anyone else. If you are not the(an) intended > > > recipient, please immediately delete this e-mail > > > from your computer system and notify the sender. > > > > Thank you. > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > For additional commands, e-mail: > > > [EMAIL PROTECTED] > > > > > > > > > __________________________________ > > Do you Yahoo!? > > The New Yahoo! Shopping - with improved product > > search > > http://shopping.yahoo.com > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > __________________________________ > Do you Yahoo!? > The New Yahoo! Shopping - with improved product > search > http://shopping.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
