My Tomcat service (since 7.0.8) would die with "Commons Daemon procrun stdout initializedError occurred during initialization of VM Unable to load native library" when I tried to start it. I finally traced got fed up with starting it from the command line and traced it down to this option that is used by the installer (according to service-install.log) in the //IS call:
--Jvm "C:\Programme\Java\jre6\bin\server\jvm.dll" If instead --Jvm is set to auto all works well. Why? The DLL exists, is readable/executable by all and I am doing this under an account with admin privileges (on XP) anyhow. While we are on this topic I have a few more questions: 1) If --StartPath is omitted Tomcat attempts to start in the local directory, which of course fails; this is very puzzling, as one would expect it to start under the install directory by default (and yes --Install was supplied) 2) Where is it safe to use env. vars so as to shorten the invocation a bit? According to the windows services HOWTO apparently only in the --Jvm option. Is it so? 3) Since you target Java 5 and above maybe you could start using the star syntax in the classpath to shorten things a bit further 4) Is there still a dependency on tools.jar, e.g., for servlets? Thanks, -- O.L. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
