Re: [Wrapper-user] wrapper service going down with thefollowingexceptions

[Leif M. <lei...@ta...>]

Salman,
You are running wrapper-windows-x86-32.exe, that is then launching a
64-bit version of Java.   The JVM loads the
org.tanukisoftware.wrapper.WrapperManager class which in turn attempts
to load the wrapper-windows-x86-64.dll

The problem you are having is that the copy of Java you are running is 64-bit.

Cheers,
Leif

On Sat, Feb 21, 2009 at 2:59 AM, JAN Salman
<Sal...@al...> wrote:
> Hi Leif,
> As I understand that it is the wrapper-windows-x86-32.exe that should
> load to wrapper-windows-x86-32.dll before even the JVM is invoked.
>
> The error we are getting is that the wrapper-windows-x86-32.exe is not
> loading wrapper-windows-x86-32.dll (instead looking for
> wrapper-windows-x86-64.exe).  I do not understand why that error/warning
> message would be related to JVM being a 32bit version.
>
> Many be that, I am not understanding the sequence as to what call what.
>
> I understand wrapper-windows-x86-32.exe---call-->
> wrapper-windows-x86-32.dll---calls---> wrapper.jar
> (JVM)---invokes-->Java code/class
>
> Can u explain?
>
> Thanks
> Salman
>
>
> -----Original Message-----
> From: Leif Mortenson [mailto:lei...@ta...]
> Sent: Friday, February 20, 2009 11:31 AM
> To: JAN Salman
> Cc: wra...@li...; SUNKAVELLI Sai; BASNYAT
> Dharmendra
> Subject: Re: [Wrapper-user] wrapper service going down with
> thefollowingexceptions
>
> Salman,
> Yes, you are using a 32-bit version of the Wrapper, but you are using
> that to launch a 64-bit version of Java.   That part is fine, but a
> 64-bit wrapper.dll is required to work with the 64-bit version of
> Java.
> The Java version is displayed here from your log:
> ---
> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager Debug:
> Running a 64-bit JVM.
> ...
> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager Debug: Java
> Version   : 1.5.0_16-b02 Java HotSpot(TM) 64-Bit Server VM
> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager Debug: Java
> VM Vendor : Sun Microsystems Inc.
> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager Debug: OS
> Name        : Windows 2003
> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager Debug: OS
> Arch        : amd64
> ---
>
> Unless you need the 64-bit JVM, please try installing a 32-bit version
> of Java.  That should fix your problem.
>
> Cheers,
> Leif
>
> On Sat, Feb 21, 2009 at 1:10 AM, JAN Salman
> <Sal...@al...> wrote:
>> Hi Leif,
>> The Windows Service executable path is :
>>
>> "C:\Program Files
>> (x86)\wrapper-delta-pack-3.3.1\bin\wrapper-windows-x86-32.exe" -s
>> "C:\Program Files (x86)\wrapper-delta-pack-3.3.1\conf\wrapper.conf"
>>
>> You can see that we are using wrapper-windows-x86-32.exe
>>
>> -----Original Message-----
>> From: JAN Salman
>> Sent: Friday, February 20, 2009 11:07 AM
>> To: 'Leif Mortenson'; wra...@li...
>> Cc: SUNKAVELLI Sai; BASNYAT Dharmendra
>> Subject: RE: [Wrapper-user] wrapper service going down with
>> thefollowingexceptions
>>
>> Hi Leif,
>> The issue appears to be that we are using the attached Wrapper Windows
>> Service package (which is a 32 bit version).
>>
>> The Windows 2003 Server we have is a 64-bit OS and setup in
>> compatibility mode. Meaning u can also run 32-bit apps on it.
>>
>> The issue is why the wrapper-windows-x86-32.dll is not loading
>> wrapper-windows-x86-32.dll , and instead asking for
>> wrapper-windows-x86-64.dll?
>>
>> Thanks
>> Salman
>>
>>
>> -----Original Message-----
>> From: Leif Mortenson [mailto:lei...@ta...]
>> Sent: Thursday, February 19, 2009 9:15 PM
>> To: wra...@li...
>> Cc: JAN Salman
>> Subject: Re: [Wrapper-user] wrapper service going down with
>> thefollowingexceptions
>>
>> Sai,
>> As the log output states, the problem is that your wrapper.dll file is
>> not being located correctly:
>>
>> ---
>> INFO   | jvm 1    | 2009/02/17 19:11:28 | 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/02/17 19:11:28 | WrapperManager Debug:
>> Unable to load native library: wrapper.dll  Cause: no wrapper in
>> java.library.path
>> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager:
>> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager: WARNING -
>> Unable to load the Wrapper's native library because none of the
>> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager:
>> following files:
>> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager:
>> wrapper-windows-x86-64.dll
>> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager:
>> wrapper.dll
>> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager:
>> could be located on the following java.library.path:
>> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager:
>> C:\Program Files\wrapper-delta-pack-3.3.1\lib
>> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager:
>> C:\Program Files\wrapper-delta-pack-3.3.1\lib\windows-x86-32
>> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager:
>> Please see the documentation for the wrapper.java.library.path
>> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager:
>> configuration property.
>> INFO   | jvm 1    | 2009/02/17 19:11:28 | WrapperManager:
>> System signals will not be handled correctly.
>> ---
>>
>> Your java library path is currently:
>> -Djava.library.path="C:/Program
>> Files/wrapper-delta-pack-3.3.1/lib;C:/Program
>> Files/wrapper-delta-pack-3.3.1/lib/windows-x86-32"
>>
>> Can you confirm that a wrapper.dll or wrapper-windows-x86-64.dll
>> exists in that directory.  I just noticed in your log file that you
>> are running the community edition.  We do not include 64-bit windows
>> versions in the community edition at this time.   To get this working,
>> you will need to either use a 32-bit JVM or upgrade to a Standard
>> edition server license.
>>
>> Sorry I had not noticed that in your first email.  The malformed
>> library path looked like the problem.
>>
>> Please let me know if you have any questions.
>>
>> Sincerely,
>> Leif Mortenson,
>> Tanuki Software, Ltd.
>>
>>
>> On Fri, Feb 20, 2009 at 4:43 AM, Sunkavelli, Sai M (Sai)** CTR **
>> <sai...@al...> wrote:
>>>
>>> Hi Leif,
>>>
>>> I changed the path and removed the additional '\' in the path as you
>>> suggested below and still we have the problem. Here is the log file
>> with
>>> the error, could you please let us know why this is happening.
>>>
>>> Thanks
>>> -Sai
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Leif Mortenson [mailto:lei...@ta...]
>>> Sent: Saturday, February 14, 2009 10:44 AM
>>> To: wra...@li...
>>> Cc: Jan, Salman (Salman)
>>> Subject: Re: [Wrapper-user] wrapper service going down with
>>> thefollowingexceptions
>>>
>>> Sai,
>>> The problem is that the Wrapper's native DLL is not being located
>>> correctly.  Without that, the wrapper loses the ability to protect
> the
>>> Java process from system logout events.   This message should have
>>> been visible in your logs even without enabling debug output:
>>>
>>> ---
>>> INFO   | jvm 1    | 2009/02/12 15:10:11 | WrapperManager:
>>> INFO   | jvm 1    | 2009/02/12 15:10:11 | WrapperManager: WARNING -
>>> Unable to load the Wrapper's native library because none of the
>>> INFO   | jvm 1    | 2009/02/12 15:10:11 | WrapperManager:
>>> following files:
>>> INFO   | jvm 1    | 2009/02/12 15:10:11 | WrapperManager:
>>> wrapper-windows-x86-64.dll
>>> INFO   | jvm 1    | 2009/02/12 15:10:11 | WrapperManager:
>>> wrapper.dll
>>> INFO   | jvm 1    | 2009/02/12 15:10:11 | WrapperManager:
>>> could be located on the following java.library.path:
>>> INFO   | jvm 1    | 2009/02/12 15:10:11 | WrapperManager:
>>> C:\Program Files\wrapper-delta-pack-3.3.1\lib
>>> INFO   | jvm 1    | 2009/02/12 15:10:11 | WrapperManager:
>>> Please see the documentation for the wrapper.java.library.path
>>> INFO   | jvm 1    | 2009/02/12 15:10:11 | WrapperManager:
>>> configuration property.
>>> INFO   | jvm 1    | 2009/02/12 15:10:11 | WrapperManager:
>>> System signals will not be handled correctly.
>>> INFO   | jvm 1    | 2009/02/12 15:10:11 | WrapperManager:
>>> ---
>>>
>>> The generated library path is currently set to:
>>> -Djava.library.path="C:/Program Files/wrapper-delta-pack-3.3.1\/lib"
>>>
>>> My guess is that the extra slash before the lib is what is causing
>>> your problems.   Try removing that by correcting the following in
> your
>>> wrapper.conf:
>>> wrapper.java.library.path.1=C:/Program
>>> Files/wrapper-delta-pack-3.3.1\/lib
>>> Change to:
>>> wrapper.java.library.path.1=C:/Program
>>> Files/wrapper-delta-pack-3.3.1/lib
>>>
>>> Let me know how this works for you.
>>>
>>> Cheers,
>>> Leif
>>>
>>>
>>>
>>> On Sat, Feb 14, 2009 at 8:47 AM, Sunkavelli, Sai M (Sai)** CTR **
>>> <sai...@al...> wrote:
>>>> Hi Leif,
>>>>
>>>> Here are the log and conf files. Please let us know why this User
>>>> logged out error is occurring.
>>>>
>>>> Thanks
>>>> -Sai
>>>>
>>>> -----Original Message-----
>>>> From: Leif Mortenson [mailto:lei...@ta...]
>>>> Sent: Wednesday, February 11, 2009 10:54 PM
>>>> To: wra...@li...
>>>> Cc: Jan, Salman (Salman)
>>>> Subject: Re: [Wrapper-user] wrapper service going down with the
>>>> followingexceptions
>>>>
>>>> Salman,
>>>> I am not able to tell exactly what is happening from what was sent.
>>>> Could you please set the wrapper.debug=true property, delete any
>>>> existing wrapper.log file, then reproduce this.  Send me the
>> resulting
>>>
>>>> wrapper.log and wrapper.conf files in entirety as attachments.  I
>>>> should then be able to tell you what is happening.
>>>>
>>>> Cheers,
>>>> Leif
>>>>
>>>> On Thu, Feb 12, 2009 at 8:09 AM, Sunkavelli, Sai M (Sai)** CTR **
>>>> <sai...@al...> wrote:
>>>>> Hi
>>>>>
>>>>> Please help with the following exception in the wrapper log and my
>>>>> java program is terminating after this error.
>>>>>
>>>>>
>>>>> INFO   | wrapper  | 2009/02/11 16:43:13 | User logged out.
> Ignored.
>>>>> INFO   | wrapper  | 2009/02/11 16:43:13 | User logged out.
> Ignored.
>>>>> STATUS | wrapper  | 2009/02/11 16:43:16 | <-- Wrapper Stopped
>>>>>
>>>>> Thanks and regards
>>>>> Sai Manohar Sunkavelli.