Re: [Wrapper-user] Wrapper start problems on Linux

[Lars S. <Lar...@if...>]

Hi Leif

Thanks for the reply, it seems like I had a mistake in my wrapper.conf, 
so the wrapper.debug=TRUE helped a lot.
Now that I can see the command that is used I was wondering why:
wrapper.java.command=java
in my wrapper.conf results in a command like:
"c:\windows\system32\java.exe
My problem is that my application now works when I enter the correct 
path to java.exe as wrapper.java.command, but since the location can be 
different from system to system I would like to avoid to hard code it, 
is there away to get the correct path without hard coding it in the 
wrapper.conf?
Thanks

Lars

On 17-12-2010 09:51, Leif Mortenson wrote:
> Lars,
> Could you please set the wrapper.debug=TRUE property and then post
> your wrapper.log and wrapper.conf as attachments?  I am not sure what
> would be causing the errors you mentioned, but I should be able to see
> from the logs.
>
> The message about the "public static" is that the WrapperSimpleApp
> requires that the main class you specify is a public class, and that
> it defines a public static main method.   If either of those is not
> true then you will not be able to access it.
>
> Cheers,
> Leif
>
> On Thu, Dec 16, 2010 at 10:54 PM, Lars Schnoor<Lar...@if...>  wrote:
>> Hi again
>>
>> I am again trying the mentioned scenario, but with the parameters as:
>> wrapper.java.mainclass=special.start.class
>> wrapper.app.parameter.1=-"parameter to special start class"
>> wrapper.app.parameter.2=myStartClass
>>
>> where myStartClass implements WrapperListener.
>> This works fine on Linux (Red Hat Enterprise Linux 5.5 64-bit with Java
>> 1.6.0 Update 22 64-bit).
>> On Windows 7 (64-bit with Java 1.6.0 Update 21 32-bit) it does not work,
>> I get a lot of error messages in the log file about a timeout in waiting
>> for a signal from the JVM.
>> Any help would be greatly appreciated.
>>
>> When I try Integration method #1 I get an exception about that the
>> WrapperSimpleApp can not access a member with modifiers "public static"
>> in the special.start.class.
>> Thanks
>>
>> Lars
>>
>> On 06-11-2009 16:40, Leif Mortenson wrote:
>>> Lars,
>>> If the WrapperManager is not initialized, then the Wrapper will kill
>>> the JVM by default after 30 seconds or so.  Have you disabled any of
>>> the default timeouts?  If so, all of the freeze detection code will
>>> not be working.
>>>
>>> Have you tried using Integration method #1?  It lets you do codeless
>>> integration.  If your special.start.class is designed to run as a
>>> normal standalone Java main class then following will work:
>>>
>>> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
>>> wrapper.app.parameter.1=special.start.class
>>> wrapper.app.parameter.2=-"parameter to special start class"
>>> wrapper.app.parameter.3=myStartClass
>>>
>>> See the following documentation for more details:
>>> http://wrapper.tanukisoftware.org/doc/english/integrate-simple-win.html
>>>
>>> Cheers,
>>> Leif
>>>
>>> On Fri, Nov 6, 2009 at 11:37 PM, Lars Schnoor<Lar...@if...>    wrote:
>>>> Hi Leif
>>>> Thanks for the quick reply. I changed the wrapper parameters like you
>>>> suggested and now it works.
>>>> The special.start.class does not implement WrapperListener or initialize the
>>>> WrapperManager, but it works anyway.
>>>> I did not make the special.start.class myself, so I can't make implement the
>>>> WrapperListener.
>>>>
>>>> Lars
>>>>
>>>> Leif Mortenson wrote:
>>>>
>>>> Lars,
>>>> All versions of the Wrapper actually expect that you correctly break
>>>> the parameters into individual parameters.  On Windows they are all
>>>> reconstructed into a single line so it works, but on UNIX, the command
>>>> is broken up into the individual components and passed to the system
>>>> as an array.
>>>>
>>>> You need to do the following and it will work on all platforms:
>>>>
>>>> wrapper.java.mainclass=special.start.class
>>>> wrapper.app.parameter.1=-"parameter to special start class"
>>>> wrapper.app.parameter.1=myStartClass
>>>>
>>>> The class you specify for the wrapper.java.mainclass must implement
>>>> the WrapperListener and initialize the WrapperManager class directly
>>>> or indirectly.  You are using what we call Integration Method #3.
>>>> Please read over the following page and let me know if you have any
>>>> additional questions.
>>>> http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html
>>>>
>>>> Cheers,
>>>> Leif
>>>>
>>>>
>>>> On Fri, Nov 6, 2009 at 10:18 PM, Lars Schnoor<Lar...@if...>    wrote:
>>>>
>>>>
>>>> Hi
>>>> I have a Java application that is started in a special way. I have a main
>>>> class in my application that implements the WrapperListener interface.
>>>> from the command prompt I can start my application with:
>>>> java -cp myApplication.jar special.start.class -"parameter to special start
>>>> class" myStartClass
>>>> I can start my application by the above line on both Windows and Linux.
>>>>
>>>> On Windows I put the following line in my wrapper.conf:
>>>> wrapper.java.mainclass=special.start.class -"parameter to special start
>>>> class" myStartClass
>>>> And it works fine.
>>>>
>>>> On Linux (Red Hat Enterprise Linux 5 64-bit) I tried the same, putting the
>>>> same line in the wrapper.conf:
>>>> wrapper.java.mainclass=special.start.class -"parameter to special start
>>>> class" myStartClass
>>>> Here it does not work, I get an ClassNotFoundException for the class:
>>>> special.start.class -"parameter to special start class" myStartClass
>>>> For me it seems as if the wrapper on Linux sees special.start.class
>>>> -"parameter to special start class" myStartClass as one class, where the
>>>> wrapper on Windows starts the special.start.class with -"parameter to
>>>> special start class" myStartClass as parameters.
>>>> I tried putting:
>>>> wrapper.java.mainclass=special.start.class
>>>> wrapper.app.parameter.1=-"parameter to special start class" myStartClass
>>>> in the wrapper.conf and with this the wrapper starts, but since the
>>>> special.start.class does not implement the WrapperListener interface, the
>>>> wrapper shuts down after five tries.
>>>> Any idea how I can get it to work on Linux, I am using version 3.2.3 of the
>>>> wrapper?
>>>> Thanks in advance!
>>>>
>>>> Lars
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user