|
From: Jeremy Fujimoto-J. <Fuj...@ah...> - 2004-06-07 22:04:42
|
I have discovered that when I start the JavaServiceWrapper and it's pointing to the 1.4.2_04 JDK (e.g. wrapper.java.command=C:/j2sdk1.4.2_04/bin/java) it fails to load the wrapper.dll library. I get the following test in the log: STATUS | wrapper | 2004/06/07 14:23:13 | --> Wrapper Started as Service STATUS | wrapper | 2004/06/07 14:23:13 | Launching a JVM... INFO | jvm 1 | 2004/06/07 14:23:15 | WARNING - Unable to load the Wrapper's native library 'wrapper.dll'. INFO | jvm 1 | 2004/06/07 14:23:15 | The file is located on the path at the following location but INFO | jvm 1 | 2004/06/07 14:23:15 | could not be loaded: INFO | jvm 1 | 2004/06/07 14:23:15 | C:\Tomcat\VAP\bin\..\common\lib\wrapper.dll INFO | jvm 1 | 2004/06/07 14:23:15 | Please verify that the file is readable by the current user INFO | jvm 1 | 2004/06/07 14:23:15 | and that the file has not been corrupted in any way. INFO | jvm 1 | 2004/06/07 14:23:15 | System signals will not be handled correctly. INFO | jvm 1 | 2004/06/07 14:23:15 | INFO | jvm 1 | 2004/06/07 14:23:15 | Wrapper (Version 3.1.0) http://wrapper.tanukisoftware.org However, when I use the 1.3.1_07 version of the JDK this problem does not occur. I am using the JavaServiceWrapper to run Tomcat 4.0.6 on Windows. I have tried a couple of different Tomcat installs (different PCs and even different WebApps). I can reproduce the behavior using both 3.0.5 and 3.1.0 of the JavaServiceWrapper. (Both the problem when using 1.4.2_04 and not having a problem with 1.3.1_07 can be reproduced on multiple computers.) Is this a known conflict? I haven't been able to find any message in the mailing list that seemed to directly apply. Is there anything I can do to get it to work? Is there a version of the 1.4 JDK with which this problem does not occur? Thanks, -Jeremy |