Ivanov [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 12, 2005 10:02 PM
To: Benson Margulies; tomcat-user@jakarta.apache.org
Subject: Re: java.library.path when running as a service
My PATH variable already includes $CATALINA_HOME\common\lib, and it
definitely has worked in the past. Wouldn't
10:02 PM
To: Benson Margulies; tomcat-user@jakarta.apache.org
Subject: Re: java.library.path when running as a service
My PATH variable already includes $CATALINA_HOME\common\lib, and it
definitely has worked in the past. Wouldn't this also affect Tomcat
launched from the command line? My
@jakarta.apache.org
Subject: Re: java.library.path when running as a service
Thank you for the reply. I was not aware, is the PATH variable
different for each service? How can it be set? This would likely be
the cause of my problem if it's true.
On 7/13/05, Benson Margulies [EMAIL PROTECTED] wrote
]
Sent: Tuesday, July 12, 2005 10:02 PM
To: Benson Margulies; tomcat-user@jakarta.apache.org
Subject: Re: java.library.path when running as a service
My PATH variable already includes $CATALINA_HOME\common\lib, and it
definitely has worked in the past. Wouldn't this also affect Tomcat
Due to a bug in the JRE/JVM, your dependent DLLs have to either be in
PATH or in the directory containing java.exe. My personal favorite
solution to this is to use the delay loader hook to get around it.
-Original Message-
From: Michael Ivanov [mailto:[EMAIL PROTECTED]
Sent: Tuesday,
My PATH variable already includes $CATALINA_HOME\common\lib, and it
definitely has worked in the past. Wouldn't this also affect Tomcat
launched from the command line? My problem only occurs when Tomcat is
a service. Also, can you elaborate on what the delay loader hook is?
Thank you.
On
