|
From: Leif M. <lei...@ta...> - 2009-03-04 00:07:58
|
Rob, When the WrapperManager class in the JVM is initialized, it attempts to load the wrapper.dll using two names. The first is a platform specific name that works when running the Wrapper using delta-pack naming. The second is the regular wrapper.dll file. You can see that in the following debug log outpu. The first is not found and the second is: INFO | jvm 1 | 2009/03/04 09:02:40 | WrapperManager Debug: Load native library. One or more attempts may fail if platform specific libraries do not exist. This is NORMAL and is only a problem if they all fail. INFO | jvm 1 | 2009/03/04 09:02:40 | WrapperManager Debug: Unable to load native library: wrapper-windows-x86-64.dll Cause: no wrapper-windows-x86-64 in java.library.path INFO | jvm 1 | 2009/03/04 09:02:40 | WrapperManager Debug: Loaded native library: wrapper.dll As you noticed, the base name of both of these, "wrapper", can be configured using the wrapper.native_library=wrapper property: http://wrapper.tanukisoftware.org/doc/english/prop-native-library.html If you specify it as wrapper.native_library=wrapper-windows-x86-32-3.3.2-st then the WrapperManager will attempt to load the native library using the names: wrapper-windows-x86-32-3.3.2-st-windows-x86-64.dll and wrapper-windows-x86-32-3.3.2-st.dll. But yes, it will work. Cheers, Leif On Wed, Mar 4, 2009 at 5:09 AM, Leland, Robert <rob...@io...> wrote: > I have packaged wrapper into a maven distribution, excluding the license of > course. > In doing so I renamed the wrapper.dll, along with the wrapper.jar. > In the wrapper.conf I see a place to change the name of the wrapper.jar. > > My question is this: > If the wrapper.dll is renamed to wrapper-windows-x86-32-3.3.2-st.dll and > installed in the lib directory, will the wrapper.exe be able to find the > dll? Will there be any problems from this ? > > When I installed wrapper.exe using this configuration there were no > complaints. > > -Rob |