wrapper-user — User issues for Wrapper. (Support questions, etc.)

Re: [Wrapper-user] Win64 support

[Hursev <hu...@si...>]

Ok,

 

The only real problem is that these is no API call that initialize service's
security.

This can be fixed with this code:

 

(in src\c\wrapper_win.c)

 

Add 

static BOOL bInitSecurity = FALSE;

void InitSecurity()

{

                HRESULT hr;

                if (!bInitSecurity)

                {

                               hr = CoInitialize(NULL);

                               hr = CoInitializeSecurity(NULL, -1, NULL,
NULL, 

                                               RPC_C_AUTHN_LEVEL_PKT, 

                                               RPC_C_IMP_LEVEL_IMPERSONATE,

                                               NULL,

                                               EOAC_NONE,

                                               NULL);

                               bInitSecurity = TRUE;

                }

}

 

And then add call to InitSecurity() in the begin of wrapperExecute(). For
example after "wrapperData->exitCode = 0;"

 

Compile with 'Struct member alignment'='default'. In project that I
downloaded this option was /Zp1 (1 byte).

 

This should fix problems. I tested (and I am it using on) Win2003 x64
SP1/SP2.

 

Note: 

1.       Parameters that I pass to CoInitializeSecurity are not best. If you
want you can choose better.

2.       There should be better place for call to InitSecurity(). You need
it only once.

 

 

 

From: wra...@li...
[mailto:wra...@li...] On Behalf Of David Hayes
Sent: Monday, March 26, 2007 4:46 PM
To: wra...@li...
Subject: Re: [Wrapper-user] Win64 support

 

The user list is the best place. Leif can build it in, but also other Win64
users who may be desperate for a fix can get it too then.

 

David

 

  _____  

From: wra...@li...
[mailto:wra...@li...] On Behalf Of Hursev
Sent: 26 March 2007 14:26
To: wra...@li...
Cc: Hu...@si...
Subject: [Wrapper-user] Win64 support

 

Hi,

 

I think I found the 64bit windows support problem. Where should I send the
information?

 

Hursev

 

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.18/733 - Release Date: 25/03/2007
11:07

 

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.18/733 - Release Date: 25/03/2007
11:07

Re: [Wrapper-user] Win64 support

[David H. <da...@sm...>]

The user list is the best place. Leif can build it in, but also other Win64
users who may be desperate for a fix can get it too then.

 

David

 

   _____  

From: wra...@li...
[mailto:wra...@li...] On Behalf Of Hursev
Sent: 26 March 2007 14:26
To: wra...@li...
Cc: Hu...@si...
Subject: [Wrapper-user] Win64 support

 

Hi,

 

I think I found the 64bit windows support problem. Where should I send the
information?

 

Hursev


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.18/733 - Release Date: 25/03/2007
11:07



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.18/733 - Release Date: 25/03/2007
11:07
 

[Wrapper-user] Win64 support

[Hursev <hu...@si...>]

Hi,

 

I think I found the 64bit windows support problem. Where should I send the
information?

 

Hursev

Re: [Wrapper-user] WrapperSimpleApp change to send SNMP traps...

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

Corey,
This is a feature that is currently under development.  Unfortunately, 
the way you
are doing it is not reliable.  It is the simple way to do it.  But will 
only allow reports
 to be sent for successful restarts of the JVM.

In order to make sure that mails are send for all failure modes, the 
events must be
mailed from the wrapper.exe process (developed in C).

If you want to do something in Java, you can tell after a restart has 
happened by
looking at the JVM Id from the WrapperManager on startup.  If it is 
greater than
1 then you know that a restart has just occurred.

Cheers,
Leif

Corey Ellis wrote:
> Hi,
>
> We have started to use the Java Service Wrapper (great app!!), and we 
> are required to send traps when upon graceful startup, graceful 
> shutdown, and when the wrapper detects a problem with the application 
> and restarts ( i.e. kill -9 of the process).
>
> We have integrated code into the WrapperSimpleApp class to send traps 
> in the start and stop methods.  This is working for the first two 
> requirements graceful startup/shutdown, but I need to know where to 
> hook in, in order to be able to send a trap when the wrapper attempts 
> a restart for any reason ( i.e. Exception, process dies, etc.).  I 
> thought that the controlEvent method would be the right place, but I 
> am not sure it is.
>
> If someone can point me to the right place (class, method) in order to 
> generate an SNMP trap upon application failure this will be great.  
> What we really want is as follows:
>
> 1.  Once the wrapper has attempted to restart the application the 
> configured amount of times, then send an alarm.  This way we will only 
> send an alarm if the wrapper fails to restart the application.
>
> Thanks
> Corey

[Wrapper-user] WrapperSimpleApp change to send SNMP traps...

[Corey E. <cor...@gm...>]

Hi,

We have started to use the Java Service Wrapper (great app!!), and we are
required to send traps when upon graceful startup, graceful shutdown, and
when the wrapper detects a problem with the application and restarts (i.e.
kill -9 of the process).

We have integrated code into the WrapperSimpleApp class to send traps in the
start and stop methods.  This is working for the first two requirements
graceful startup/shutdown, but I need to know where to hook in, in order to
be able to send a trap when the wrapper attempts a restart for any reason (
i.e. Exception, process dies, etc.).  I thought that the controlEvent method
would be the right place, but I am not sure it is.

If someone can point me to the right place (class, method) in order to
generate an SNMP trap upon application failure this will be great.  What we
really want is as follows:

1.  Once the wrapper has attempted to restart the application the configured
amount of times, then send an alarm.  This way we will only send an alarm if
the wrapper fails to restart the application.

Thanks
Corey

Re: [Wrapper-user] Windows page file increasing

[Todd W. <to...@sc...>]

Hi Leif,

Thanks so much for you willingness to help.  We're using method #2, and
are not calling any of the WrapperManager API calls.  I have no doubt
that we could still be doing something wrong, but thanks for helping to
troubleshoot.

The page file seems to increase as much as about 10 MB every few
minutes, so it can become a pretty big problem.

I can certainly describe to you how to reproduce the issue.  It's a bit
involved, so, if it's okay, I'll email you off the list about it.

Thanks much,

Todd


On Wed, 21 Mar 2007 10:18:46 +0900, "Leif Mortenson"
<le...@ta...> said:
> Todd,
>     Does your application make use of any of the WrapperManager API 
> calls?  Or are
> you simply using Method #1 or #2 to wrap your application?
> 
>     I ask because a memory leak in the WrapperManager.listServices() 
> method was
> recently reported.  It has been fixed for the upcoming 3.2.4 release.  
> That leak was in
> the native library and showed up as a leak in the java process but I had 
> not verified that
> there was not also a leak in the OS.
> 
>     I have not noticed any such leak in the past, but that doesn't mean 
> it is not there.
> How significant is the leak you are seeing?   How is its growth releated 
> to the Wrapper's
> lifecycle?  Basically you have told me there is a leak in the Wrapper, I 
> am looking for
> how I can reproduce your tests and see this myself.
> 
> Cheers,
> Leif
> 
> Todd Wilson wrote:
> > Hi,
> >
> > We've had a terrible time tracking down what was a bizarre type of
> > memory leak where, when running on Windows, the java.exe process would
> > not increase dramatically in size, but the page file used by the OS
> > would.  I finally narrowed the issue down to Java Service Wrapper.  If I
> > run our application without using Java Service Wrapper, everything works
> > great.  When I start it up with Java Service Wrapper, however, and start
> > using it as it's normally used, the page file size starts to increase
> > significantly.  I've tried upgrading to the latest version of Java
> > Service Wrapper, but, unfortunately, it didn't help.  There's probably
> > something simply I'm missing.  Has anyone else encountered this?  Thanks
> > in advance for any help you might be able to offer.
> >
> > Kind regards,
> >
> > Todd Wilson
> >   
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Restart request causes 5 rapid retries and death

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

Ben,
This is not a failure mode that I have seen before. At the point you are
getting the error message, the Wrapper has succeeded in launching the JVM,
the WrapperManager class in the JVM has initialized and opened a connection
back to the Wrapper process, sending its access key. The Wrapper then
responds by sending a START packed to the, JVM telling it it is time to
start
its application.
The sending of this START packet is failing for some reason. This would be
the first packet that the Wrapper attempts to send to JVM. Reviewing the
source, there is only 1 possible error at this point in the lifecycle.
That is a
failure at the socket level sending the packet. If you could reproduce this
with the wrapper.debug=true property set, I would be able to tell what the
exact failure is.

What does your system look like when this starts happening? Are you
under high load, low on resources or memory? This could happen if the
JVM process was crashing at exactly that moment. I am only guessing at
this point and will need more information.

Cheers,
Leif

Ben Cox wrote:
>> Hi all,
>>
>> I've been using Wrapper version 3.2.3 to manage my service on a
>> Windows 2003 Server machine. Everything is working rather well,
>> except occasionally when requesting a restart from within the app
>> (and sometimes just during a "normal" restart after an error). What
>> will happen is that the wrapper will attempt to start my app and then
>> give up and terminate the JVM within _one_ second!
>>
>> At least, that's how it looks from the timestamps on the log output
>> (below)... am I missing (or misinterpreting) a config file setting?
>>
>> Thanks,
>>
>> Ben
>>
>>
>> STATUS | wrapper | 2007/03/20 15:48:27 | JVM requested a restart.
>>
>> STATUS | wrapper | 2007/03/20 15:48:34 | Launching a JVM...
>>
>> INFO | jvm 17 | 2007/03/20 15:48:34 | Wrapper (Version 3.2.3)
>> http://wrapper.tanukisoftware.org
>>
>> INFO | jvm 17 | 2007/03/20 15:48:34 | Copyright 1999-2006 Tanuki
>> Software, Inc. All Rights Reserved.
>>
>> INFO | jvm 17 | 2007/03/20 15:48:34 |
>>
>> ERROR | wrapper | 2007/03/20 15:48:34 | Unable to send the start
>> command to the JVM.
>>
>> ERROR | wrapper | 2007/03/20 15:48:34 | JVM did not exit on request,
>> terminated
>>
>> STATUS | wrapper | 2007/03/20 15:48:39 | Launching a JVM...
>>
>> INFO | jvm 18 | 2007/03/20 15:48:40 | Wrapper (Version 3.2.3)
>> http://wrapper.tanukisoftware.org
>>
>> INFO | jvm 18 | 2007/03/20 15:48:40 | Copyright 1999-2006 Tanuki
>> Software, Inc. All Rights Reserved.
>>
>> INFO | jvm 18 | 2007/03/20 15:48:40 |
>>
>> ERROR | wrapper | 2007/03/20 15:48:40 | Unable to send the start
>> command to the JVM.
>>
>> ERROR | wrapper | 2007/03/20 15:48:40 | JVM did not exit on request,
>> terminated
>>
>> STATUS | wrapper | 2007/03/20 15:48:45 | Launching a JVM...
>>
>> INFO | jvm 19 | 2007/03/20 15:48:45 | Wrapper (Version 3.2.3)
>> http://wrapper.tanukisoftware.org
>>
>> INFO | jvm 19 | 2007/03/20 15:48:45 | Copyright 1999-2006 Tanuki
>> Software, Inc. All Rights Reserved.
>>
>> INFO | jvm 19 | 2007/03/20 15:48:45 |
>>
>> ERROR | wrapper | 2007/03/20 15:48:45 | Unable to send the start
>> command to the JVM.
>>
>> ERROR | wrapper | 2007/03/20 15:48:46 | JVM did not exit on request,
>> terminated
>>
>> STATUS | wrapper | 2007/03/20 15:48:51 | Launching a JVM...
>>
>> INFO | jvm 20 | 2007/03/20 15:48:51 | Wrapper (Version 3.2.3)
>> http://wrapper.tanukisoftware.org
>>
>> INFO | jvm 20 | 2007/03/20 15:48:51 | Copyright 1999-2006 Tanuki
>> Software, Inc. All Rights Reserved.
>>
>> INFO | jvm 20 | 2007/03/20 15:48:51 |
>>
>> ERROR | wrapper | 2007/03/20 15:48:51 | Unable to send the start
>> command to the JVM.
>>
>> ERROR | wrapper | 2007/03/20 15:48:51 | JVM did not exit on request,
>> terminated
>>
>> STATUS | wrapper | 2007/03/20 15:48:56 | Launching a JVM...
>>
>> INFO | jvm 21 | 2007/03/20 15:48:57 | Wrapper (Version 3.2.3)
>> http://wrapper.tanukisoftware.org
>>
>> INFO | jvm 21 | 2007/03/20 15:48:57 | Copyright 1999-2006 Tanuki
>> Software, Inc. All Rights Reserved.
>>
>> INFO | jvm 21 | 2007/03/20 15:48:57 |
>>
>> ERROR | wrapper | 2007/03/20 15:48:57 | Unable to send the start
>> command to the JVM.
>>
>> ERROR | wrapper | 2007/03/20 15:48:57 | JVM did not exit on request,
>> terminated
>>
>> FATAL | wrapper | 2007/03/20 15:48:57 | There were 5 failed launches
>> in a row, each lasting less than 300 seconds. Giving up.
>>
>> FATAL | wrapper | 2007/03/20 15:48:57 | There may be a configuration
>> problem: please check the logs.
>>
>> STATUS | wrapper | 2007/03/20 15:48:58 | <-- Wrapper Stopped

Re: [Wrapper-user] Windows page file increasing

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

Todd,
    Does your application make use of any of the WrapperManager API 
calls?  Or are
you simply using Method #1 or #2 to wrap your application?

    I ask because a memory leak in the WrapperManager.listServices() 
method was
recently reported.  It has been fixed for the upcoming 3.2.4 release.  
That leak was in
the native library and showed up as a leak in the java process but I had 
not verified that
there was not also a leak in the OS.

    I have not noticed any such leak in the past, but that doesn't mean 
it is not there.
How significant is the leak you are seeing?   How is its growth releated 
to the Wrapper's
lifecycle?  Basically you have told me there is a leak in the Wrapper, I 
am looking for
how I can reproduce your tests and see this myself.

Cheers,
Leif

Todd Wilson wrote:
> Hi,
>
> We've had a terrible time tracking down what was a bizarre type of
> memory leak where, when running on Windows, the java.exe process would
> not increase dramatically in size, but the page file used by the OS
> would.  I finally narrowed the issue down to Java Service Wrapper.  If I
> run our application without using Java Service Wrapper, everything works
> great.  When I start it up with Java Service Wrapper, however, and start
> using it as it's normally used, the page file size starts to increase
> significantly.  I've tried upgrading to the latest version of Java
> Service Wrapper, but, unfortunately, it didn't help.  There's probably
> something simply I'm missing.  Has anyone else encountered this?  Thanks
> in advance for any help you might be able to offer.
>
> Kind regards,
>
> Todd Wilson
>   

[Wrapper-user] Windows page file increasing

[Todd W. <to...@sc...>]

Hi,

We've had a terrible time tracking down what was a bizarre type of
memory leak where, when running on Windows, the java.exe process would
not increase dramatically in size, but the page file used by the OS
would.  I finally narrowed the issue down to Java Service Wrapper.  If I
run our application without using Java Service Wrapper, everything works
great.  When I start it up with Java Service Wrapper, however, and start
using it as it's normally used, the page file size starts to increase
significantly.  I've tried upgrading to the latest version of Java
Service Wrapper, but, unfortunately, it didn't help.  There's probably
something simply I'm missing.  Has anyone else encountered this?  Thanks
in advance for any help you might be able to offer.

Kind regards,

Todd Wilson

Re: [Wrapper-user] Converting Java Application into Windows Service ?

[Almond K. <sha...@ho...>]

Thanks Leif for such a detailed reply.

The first step I did was to follow point 4 suggested by you. I started a non-daemon thread from my main method then my service was not stopped automatically until I stopped it.

Most of the steps you told me were about clean up and I was able to do them simply.

I have confusion about point 3. Please let me tell you about some context. I am going to use embedded Tom Cat in my application and I need it to install my program as Windows Service. 

So what I did initially was this.
http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html

I created my application class "MyApp" with two methods StartTomCat()  and StopTomCat() and I instantiated an object of my application in Main class (given by you as example). 

The log is as follows:

STATUS | wrapper  | 2007/03/19 12:06:56 | CP30 Service installed.
STATUS | wrapper  | 2007/03/19 12:06:59 | Starting the CP30 Service service...
STATUS | wrapper  | 2007/03/19 12:06:59 | --> Wrapper Started as Service
STATUS | wrapper  | 2007/03/19 12:06:59 | Launching a JVM...
INFO   | jvm 1    | 2007/03/19 12:06:59 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2007/03/19 12:06:59 |   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
INFO   | jvm 1    | 2007/03/19 12:06:59 | 
INFO   | wrapper  | 2007/03/19 12:07:04 | Waiting to start...
INFO   | jvm 1    | 2007/03/19 12:07:00 | 
INFO   | jvm 1    | 2007/03/19 12:07:00 |     Constructor is called!
INFO   | jvm 1    | 2007/03/19 12:07:00 |     Application is started!
INFO   | jvm 1    | 2007/03/19 12:07:06 | InThread !InThread !InThread !InThread 
INFO   | jvm 1    | 2007/03/19 12:07:47 |     Application is stopped!
INFO   | jvm 1    | 2007/03/19 12:07:47 | InThread !InThread !
INFO   | jvm 1    | 2007/03/19 12:07:48 | InThread !InThread 
STATUS | wrapper  | 2007/03/19 12:07:48 | <-- Wrapper Stopped

In conf file , I defined 

wrapper.java.mainclass=com.myappl.vcp.service.Main

but I did not define any thing for wrapper.app.parameter.1

I did not use WrapperSimpleApp instead I used class implementing  WrapperListener and was able to achieve the expected results. Now source code for WrapperSimpleApp is not given so I do not know if I am missing some things in my WrapperListener class. I want Start() and Stop() methods of myself so I want to go with Integration method 3.

So my understanding is that once I implement the interface WrapperListner then I have to make sure that I call startTomCat() from start() of it and StopTomCat() from stop() method of it and the interface will take care every thing itself. Basically my whole logic is floating around this code http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html . Even my application class does not have main method because it has only two methods StartTomCat() and STopTomCat() .

Please let me know if there is a flaw in my understanding.

Thanks,

Almond


Leif Mortenson <le...@ta...> wrote: Almond,
    You need to read the documentation again :-)
http://wrapper.tanukisoftware.org/doc/english/integrate.html

    Most likely method #1 will work for you:
http://wrapper.tanukisoftware.org/doc/english/integrate-simple-win.html

   There were a few problems with what you said below:
1) You should start with a clean directory and copy the required Wrapper 
files into your
application rather than the other way around.  There are some things 
that you will not
need such as the wrappertest.jar file.

2) You should create your wrapper.conf file based on the template file:
WRAPPER_HOME/src/conf/wrapper.conf.in rather than using
WRAPPER_HOME/conf/wrapper.conf.

3) As specified in the documentation and in the wrapper.conf file,
the wrapper.java.mainclass property is used to specify the main class
passed to the JVM.  In most cases however, this is not your application's
main class.  The Wrapper has some code which must be initialized in the
JVM first.  This is covered clearly in the above documentation.  Try this:
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp

Your main method is then specified as the first parameter to the above main
class.
wrapper.app.parameter.1=

4) From the output that you sent however, it looks like your main class
starts, prints a startup message, a shutdown message and then exits.
Even if you do all of the above correctly, your application will still quit
immediately because your main method does not appear to be designed
to stay running.   Running your class standalone in Java would have the
same effect.

The Wrapper works correctly in cases like this.  But from your post, it
sounds like you are expecting that the JVM stay running.  Your application
needs to start at least one non-daemon thread within the JVM that does not
terminate.   When all such threads have terminated, the JVM things the
application has completed and the JVM will exit.

5) When you are still trying to get things working, I suggest running the
application in a console window using TestWrapper.bat rather than running
as a service.  It is easier to see what is happening.  Once that is all 
working,
THEN, you should try it as a service.

6) Not required, but I suggest copying your bat files out of the
WRAPPER_HOME/src/bin and then naming them after your application.

Let me know if you have more questions...After checking out the docs of
course.

Cheers,
Leif
   

Almond Khan wrote:
> All, I downloaded the source code and made my simple example with help 
> of code given on site(jar file is attached). That is very simple 
> example. My start method and stop method simply print message and then 
> exit.
>
> 1- I created jar file
> 2- I put jar file in lib with wrapper.jar and wrappertest.jar
> 3-  I added classpath in conf file
>            wrapper.java.classpath.3=../lib/myexample.jar
> 4-  I modified Main class in conf file and pointed it to my example
>            wrapper.java.mainclass=org.tanukisoftware.wrapper.example.Main
>
> But when I am running , my service starts and stops(I assume). How did 
> I figure it out ??
>
> C:\wrapper-delta\wrapper-delta-pack-3.2.3\bin>InstallTestWrapper-NT.bat
> wrapper  | Test Wrapper Sample Application installed.
>
> C:\wrapper-delta\wrapper-delta-pack-3.2.3\bin>StartTestWrapper-NT.bat
> wrapper  | Starting the Test Wrapper Sample Application service...
> wrapper  | Test Wrapper Sample Application started.
>
> C:\wrapper-delta\wrapper-delta-pack-3.2.3\bin>StopTestWrapper-NT.bat
> wrapper  | The Test Wrapper Sample Application service was not running.
>
> C:\wrapper-delta\wrapper-delta-pack-3.2.3\bin>UninstallTestWrapper-NT.bat
> wrapper  | Test Wrapper Sample Application removed.
>  
> So service was started but it stopped itself. I tried to start service 
> from windows service controller, it showed it was started but when I 
> refreshed service controller, it was not running.
>
> I looked at log and it also says the same thing.(Application is 
> started and Application is stopped are my custom messages)
>
> STATUS | wrapper  | 2007/03/16 12:53:08 | Test Wrapper Sample 
> Application installed.
> STATUS | wrapper  | 2007/03/16 12:53:12 | Starting the Test Wrapper 
> Sample Application service...
> STATUS | wrapper  | 2007/03/16 12:53:12 | --> Wrapper Started as Service
> STATUS | wrapper  | 2007/03/16 12:53:12 | Launching a JVM...
> INFO   | jvm 1    | 2007/03/16 12:53:12 | Wrapper (Version 3.2.3) 
> http://wrapper.tanukisoftware.org
> INFO   | jvm 1    | 2007/03/16 12:53:12 |   Copyright 1999-2006 Tanuki 
> Software, Inc.  All Rights Reserved.
> INFO   | jvm 1    | 2007/03/16 12:53:12 |
> INFO   | jvm 1    | 2007/03/16 12:53:13 |
> INFO   | jvm 1    | 2007/03/16 12:53:13 |     Application is started!
> INFO   | jvm 1    | 2007/03/16 12:53:14 |
> INFO   | jvm 1    | 2007/03/16 12:53:14 |     Application is stopped!
> STATUS | wrapper  | 2007/03/16 12:53:14 | Test Wrapper Sample 
> Application started.
> STATUS | wrapper  | 2007/03/16 12:53:15 | <-- Wrapper Stopped
>
>
>
> I wonder why stop() method is getting called and why service is 
> stopping itself.
>
> Any help would be really appreciated. Please find an attached jar file 
> and conf for my code
>
> Thanks,
>
> Khan
>
> */Chuck Williams /* wrote:
>
>     Wrapper is great to run your app as either a windows service or
>     linux daemon.� To try something quickly, read the Quick Start on
>     the project home page at
>     http://wrapper.tanukisoftware.org/doc/english/introduction.html
>
>     Chuck
>
>     Almond Khan wrote on 03/14/2007 01:47 PM:
>>     Hi,
>>
>>     I googled for converting java application and ended with this
>>     project.
>>
>>     We have embedded tomcat in our application and we use console to
>>     start/stop it.
>>
>>     Now we are moving forward and we want to run applictaion as
>>     Windows service and I am wondering how can I convert my .class
>>     into Windows service.
>>
>>     "So question is that how can I convert .class file into windows
>>     service"
>>
>>     Any help is appreciated
>>
>>     Thanks,
>>
>>     Noman
>


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user




 

Re: [Wrapper-user] Converting Java Application into Windows Service ?

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

Almond,
    You need to read the documentation again :-)
http://wrapper.tanukisoftware.org/doc/english/integrate.html

    Most likely method #1 will work for you:
http://wrapper.tanukisoftware.org/doc/english/integrate-simple-win.html

   There were a few problems with what you said below:
1) You should start with a clean directory and copy the required Wrapper 
files into your
application rather than the other way around.  There are some things 
that you will not
need such as the wrappertest.jar file.

2) You should create your wrapper.conf file based on the template file:
WRAPPER_HOME/src/conf/wrapper.conf.in rather than using
WRAPPER_HOME/conf/wrapper.conf.

3) As specified in the documentation and in the wrapper.conf file,
the wrapper.java.mainclass property is used to specify the main class
passed to the JVM.  In most cases however, this is not your application's
main class.  The Wrapper has some code which must be initialized in the
JVM first.  This is covered clearly in the above documentation.  Try this:
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp

Your main method is then specified as the first parameter to the above main
class.
wrapper.app.parameter.1=<YourMainClass>

4) From the output that you sent however, it looks like your main class
starts, prints a startup message, a shutdown message and then exits.
Even if you do all of the above correctly, your application will still quit
immediately because your main method does not appear to be designed
to stay running.   Running your class standalone in Java would have the
same effect.

The Wrapper works correctly in cases like this.  But from your post, it
sounds like you are expecting that the JVM stay running.  Your application
needs to start at least one non-daemon thread within the JVM that does not
terminate.   When all such threads have terminated, the JVM things the
application has completed and the JVM will exit.

5) When you are still trying to get things working, I suggest running the
application in a console window using TestWrapper.bat rather than running
as a service.  It is easier to see what is happening.  Once that is all 
working,
THEN, you should try it as a service.

6) Not required, but I suggest copying your bat files out of the
WRAPPER_HOME/src/bin and then naming them after your application.

Let me know if you have more questions...After checking out the docs of
course.

Cheers,
Leif
   

Almond Khan wrote:
> All, I downloaded the source code and made my simple example with help 
> of code given on site(jar file is attached). That is very simple 
> example. My start method and stop method simply print message and then 
> exit.
>
> 1- I created jar file
> 2- I put jar file in lib with wrapper.jar and wrappertest.jar
> 3-  I added classpath in conf file
>            wrapper.java.classpath.3=../lib/myexample.jar
> 4-  I modified Main class in conf file and pointed it to my example
>            wrapper.java.mainclass=org.tanukisoftware.wrapper.example.Main
>
> But when I am running , my service starts and stops(I assume). How did 
> I figure it out ??
>
> C:\wrapper-delta\wrapper-delta-pack-3.2.3\bin>InstallTestWrapper-NT.bat
> wrapper  | Test Wrapper Sample Application installed.
>
> C:\wrapper-delta\wrapper-delta-pack-3.2.3\bin>StartTestWrapper-NT.bat
> wrapper  | Starting the Test Wrapper Sample Application service...
> wrapper  | Test Wrapper Sample Application started.
>
> C:\wrapper-delta\wrapper-delta-pack-3.2.3\bin>StopTestWrapper-NT.bat
> wrapper  | The Test Wrapper Sample Application service was not running.
>
> C:\wrapper-delta\wrapper-delta-pack-3.2.3\bin>UninstallTestWrapper-NT.bat
> wrapper  | Test Wrapper Sample Application removed.
>  
> So service was started but it stopped itself. I tried to start service 
> from windows service controller, it showed it was started but when I 
> refreshed service controller, it was not running.
>
> I looked at log and it also says the same thing.(Application is 
> started and Application is stopped are my custom messages)
>
> STATUS | wrapper  | 2007/03/16 12:53:08 | Test Wrapper Sample 
> Application installed.
> STATUS | wrapper  | 2007/03/16 12:53:12 | Starting the Test Wrapper 
> Sample Application service...
> STATUS | wrapper  | 2007/03/16 12:53:12 | --> Wrapper Started as Service
> STATUS | wrapper  | 2007/03/16 12:53:12 | Launching a JVM...
> INFO   | jvm 1    | 2007/03/16 12:53:12 | Wrapper (Version 3.2.3) 
> http://wrapper.tanukisoftware.org
> INFO   | jvm 1    | 2007/03/16 12:53:12 |   Copyright 1999-2006 Tanuki 
> Software, Inc.  All Rights Reserved.
> INFO   | jvm 1    | 2007/03/16 12:53:12 |
> INFO   | jvm 1    | 2007/03/16 12:53:13 |
> INFO   | jvm 1    | 2007/03/16 12:53:13 |     Application is started!
> INFO   | jvm 1    | 2007/03/16 12:53:14 |
> INFO   | jvm 1    | 2007/03/16 12:53:14 |     Application is stopped!
> STATUS | wrapper  | 2007/03/16 12:53:14 | Test Wrapper Sample 
> Application started.
> STATUS | wrapper  | 2007/03/16 12:53:15 | <-- Wrapper Stopped
>
>
>
> I wonder why stop() method is getting called and why service is 
> stopping itself.
>
> Any help would be really appreciated. Please find an attached jar file 
> and conf for my code
>
> Thanks,
>
> Khan
>
> */Chuck Williams <ch...@ma...>/* wrote:
>
>     Wrapper is great to run your app as either a windows service or
>     linux daemon.� To try something quickly, read the Quick Start on
>     the project home page at
>     http://wrapper.tanukisoftware.org/doc/english/introduction.html
>
>     Chuck
>
>     Almond Khan wrote on 03/14/2007 01:47 PM:
>>     Hi,
>>
>>     I googled for converting java application and ended with this
>>     project.
>>
>>     We have embedded tomcat in our application and we use console to
>>     start/stop it.
>>
>>     Now we are moving forward and we want to run applictaion as
>>     Windows service and I am wondering how can I convert my .class
>>     into Windows service.
>>
>>     "So question is that how can I convert .class file into windows
>>     service"
>>
>>     Any help is appreciated
>>
>>     Thanks,
>>
>>     Noman
>

Re: [Wrapper-user] Mac OS X + Intel processor problem

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

Albert,
Sorry what do you mean by a "64-bit Window"? I'm not a big Mac user...

The problem you are seeing is because a 64-bit libwrapper.jnilib file is not
available. If you are running a 64-bit JVM it will require a 64-bit 
libwrapper.jnilib
file. It shouldn't matter how the JVM is launched.

Cheers,
Leif

Thong La wrote:
> Hello Leif,
>
> Regarding this issue, do you think that we will run into the same 
> thing when trying to use Wrapper in a 64-bit Window? Also, what will 
> be the impact of this error message? (as wrapper still run after 
> generating this error message).
>
> Thanks,
> Albert
>
> -------------------------------------------------------------------------
> From: "Albert La" <laq...@ho...>
> Reply-To: wra...@li...
> To: <wra...@li...>
> Subject: [Wrapper-user] Mac OS X + Intel processor problem
>
>
> I posted this on the user forum, and now move it to the mailing list 
> as Leif's advice. Basically, we're looking for a solution for the 
> wrapper to work with both 32-bit Mac, and 64-bit Mac.
>
> Thanks,
>
> ------------------------------------------
> We got the following warning in wrapper log when trying to run it on 
> an eMac ( Mac OS X 10.4.7 / Intel 64 bit processor).
>
> "WARNING - Unable to load the Wrapper's native library 
> 'libwrapper.jnilib'.
> The file is located on the path at the following location but could 
> not be loaded:
> /Applications/../lib/libwrapper.jnilib Please verify that the file is 
> readable by the current user and that the file has not been corrupted 
> in any way. One common cause of this problem is running a 32-bit 
> version of the Wrapper with a 64-bit version of Java, or vica versa. 
> This is a 32-bit JVM. System signals will not be handled correctly. "
> Any idea how to fix it?
> Thanks in advance.
> Albert
> ------------------------------------------
> RE: Mac OS X + Intel processor problem
> By: Leif Mortenson (mortenson) - 2007-03-13 20:29
> Albert,
> This is because you are running a 64-bit JVM with the 32-bit version 
> of the Wrapper. The wrapper process itself is standalone and thus it 
> is possible to run on your 64-bit OS. But the the native library MUST 
> match the JVM and needs to be a 64-bit library.
>
> Unfortunately, I do not have access to a 64-bit OSX system to do the 
> build myself. You can build from source, but may have to tweek the 
> Makefile to get it to work. I would be happy to help you with any 
> required modifications if you move the discussion to the wrapper-user 
> mailing list. Another user may have already done this work, so that is 
> a better place to ask.
>
> Cheers,
> Leif
>
>
>
>
> << prj_adm.png >>
> << donate.png >>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to 
> share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
> _________________________________________________________________
> Play Flexicon: the crossword game that feeds your brain. PLAY now for 
> FREE.? 
> http://zone.msn.com/en/flexicon/default.htm?icid=flexicon_hmtagline
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

Re: [Wrapper-user] Mac OS X + Intel processor problem

[Thong L. <laq...@ho...>]

Hello Leif,

Regarding this issue, do you think that we will run into the same thing when 
trying to use Wrapper in a 64-bit Window? Also, what will be the impact of 
this error message? (as wrapper still run after generating this error 
message).

Thanks,
Albert

-------------------------------------------------------------------------
From: "Albert La" <laq...@ho...>
Reply-To: wra...@li...
To: <wra...@li...>
Subject: [Wrapper-user] Mac OS X + Intel processor problem


I posted this on the user forum, and now move it to the mailing list as 
Leif's advice. Basically, we're looking for a solution for the wrapper to 
work with both 32-bit Mac, and 64-bit Mac.

Thanks,

------------------------------------------
We got the following warning in wrapper log when trying to run it on an eMac 
( Mac OS X 10.4.7 / Intel 64 bit processor).

"WARNING - Unable to load the Wrapper's native library 'libwrapper.jnilib'.
The file is located on the path at the following location but could not be 
loaded:
/Applications/../lib/libwrapper.jnilib Please verify that the file is 
readable by the current user and that the file has not been corrupted in any 
way. One common cause of this problem is running a 32-bit version of the 
Wrapper with a 64-bit version of Java, or vica versa. This is a 32-bit JVM. 
System signals will not be handled correctly. "
  Any idea how to fix it?
Thanks in advance.
Albert
------------------------------------------
RE: Mac OS X + Intel processor problem
By: Leif Mortenson (mortenson) - 2007-03-13 20:29
Albert,
This is because you are running a 64-bit JVM with the 32-bit version of the 
Wrapper. The wrapper process itself is standalone and thus it is possible to 
run on your 64-bit OS. But the the native library MUST match the JVM and 
needs to be a 64-bit library.

Unfortunately, I do not have access to a 64-bit OSX system to do the build 
myself. You can build from source, but may have to tweek the Makefile to get 
it to work. I would be happy to help you with any required modifications if 
you move the discussion to the wrapper-user mailing list. Another user may 
have already done this work, so that is a better place to ask.

Cheers,
Leif




<< prj_adm.png >>
<< donate.png >>


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV


_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

_________________________________________________________________
Play Flexicon: the crossword game that feeds your brain. PLAY now for FREE.  
  http://zone.msn.com/en/flexicon/default.htm?icid=flexicon_hmtagline

Re: [Wrapper-user] Converting Java Application into Windows Service ?

[Chuck W. <ch...@ma...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Wrapper is great to run your app as either a windows service or linux
daemon.  To try something quickly, read the Quick Start on the project
home page at
<a class="moz-txt-link-freetext" href="http://wrapper.tanukisoftware.org/doc/english/introduction.html">http://wrapper.tanukisoftware.org/doc/english/introduction.html</a><br>
<br>
Chuck<br>
<br>
Almond Khan wrote on 03/14/2007 01:47 PM:
<blockquote cite="mid...@we..."
 type="cite"><font face="Verdana, Arial" size="2">Hi,<br>
  <br>
I googled for converting java application and ended with this project.<br>
  <br>
We have embedded tomcat in our application and we use console to
start/stop it.<br>
  <br>
Now we are moving forward and we want to run applictaion as Windows
service and I am wondering how can I convert my .class into Windows
service.<br>
  <br>
"So question is that how can I convert .class file into windows service"<br>
  <br>
Any help is appreciated <br>
  <br>
Thanks,<br>
  <br>
Noman</font><br>
  <br>
  <p> </p>
  <pre wrap="">
<hr size="4" width="90%">
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT &amp; business topics through brief surveys-and earn cash
<a class="moz-txt-link-freetext" href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&amp;p=sourceforge&amp;CID=DEVDEV</a></pre>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Wrapper-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Wra...@li...">Wra...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/wrapper-user">https://lists.sourceforge.net/lists/listinfo/wrapper-user</a>
  </pre>
</blockquote>
<br>
</body>
</html>

[Wrapper-user] Converting Java Application into Windows Service ?

[Almond K. <sha...@ho...>]

Hi,

I googled for converting java application and ended with this project.

We have embedded tomcat in our application and we use console to start/stop it.
 
Now we are moving forward and we want to run applictaion as Windows service and I am wondering how can I convert my .class into Windows service.
 
"So question is that how can I convert .class file into windows service"
 
Any help is appreciated 

Thanks,

Noman


 

[Wrapper-user] 64-bit Windows?

[Chuck W. <ch...@ma...>]

Hi All,

I don't see a binary distribution for 64-bit Windows.  Is this expected
to work if for example I build the wrapper native code in that
environment, or is there a known problem with it?

I'm in the process of testing my app in a number of 64-bit environments
and just hit this issue.

Chuck

Re: [Wrapper-user] Building on OpenBSD + AMD64 prob

[Peter T. <pet...@ya...>]

--- Leif Mortenson <le...@ta...> wrote:
> up under VMware.  But 'll be honest about my current todo list...It
> is  going to take me a little while.

Thanks much for the honesty.  Make sure its OBSD amd64 (not i386)

>     What does your Makefile look like?  Are you sure that the -fPIC 
> option was
> added at a point that it will be used by both builds?

Got me but I think so ... I have attempted to move -fPIC all over the
place to no availe :) see:

https://www.nan-elmoth.net/Makefile-OpenBSD-x86-64

Re: [Wrapper-user] JVM restart with ping-timeout

[madis <ma...@ja...>]

Deleting class files and recompiling the original source did the trick.

Thanks for pointers.

Leif Mortenson wrote:
> Madis,
>     The Wrapper sends PING packets to the JVM at an interval defined by the
> wrapper.ping.interval property, every 5 seconds by default.  The JVM side of
> Normally, the JVM immediately responds by sending a PING back to the
> Wrapper process.
>     A timeout occurs when ever more than the wrapper.ping.timeout has 
> expired
> without the Wrapper process receiving a PING packet from the JVM.
>
> A) This is not a problem that I have ever had reported in the past.
> B) Reviewing the source, I do not see any way at all that this could be 
> happening
> with the unmodified source.   Immediately after the "Received a 
> packet..." message
> is logged by the handleSocket() method, it proceeds to call the 
> sendCommand()
> method where a "Send a packet..." message should be logged.  That is not 
> happening.
>
>     I would love to help further, but it is not really possible for me 
> to try to debug
> modified versions of the Wrapper.   I have given you clues as to where 
> the problem
> likely is, but you are going to need to go in and debug what is happening.
>
>     Cheers,
>     Leif
>
> madis wrote:
>   
>> I compile the service wrapper java source with my own project. Kinda 
>> got that way because when I installed the service on XP sp2,  I could 
>> not get it started. Everything was OK after I did a little restart but 
>> I poked around a little before that (not much, just the properties and 
>> dll resolving).
>>
>> Tryd with original source from version 3.2.3:
>>
>> Still doing 50% from full cycle:
>> ....................
>> INFO   | jvm 1    | 2007/03/14 16:18:13 | Received a packet PING : ping
>> DEBUG  | wrapperp | 2007/03/14 16:18:17 | send a packet PING : ping
>> INFO   | jvm 1    | 2007/03/14 16:18:17 | Received a packet PING : ping
>> DEBUG  | wrapperp | 2007/03/14 16:18:21 | send a packet PING : ping
>> INFO   | jvm 1    | 2007/03/14 16:18:21 | Received a packet PING : ping
>> DEBUG  | wrapperp | 2007/03/14 16:18:25 | send a packet PING : ping
>> ....................
>>
>> If the ping cycle is incomplete why does it take so many trys before 
>> VM shuts down?
>>
>> Leif Mortenson wrote:
>>     
>>> Madis,
>>>     Looking at your logs, the JVM is receiving pings from the Wrapper 
>>> process
>>> correctly, but it does not appear to be sending the ping reply back to 
>>> the Wrapper.
>>>
>>>     This is what a single ping cycle should look like:
>>> ---
>>> DEBUG  | wrapperp | send a packet PING : ping
>>> INFO   | jvm 1    | Received a packet PING : ping
>>> INFO   | jvm 1    | Send a packet PING : ping
>>> DEBUG  | wrapperp | read a packet PING : ping
>>> ---
>>>
>>>     But from your logs, you are only seeing the first two lines:
>>> ---
>>> DEBUG  | wrapperp | 2007/03/14 14:13:22 | send a packet PING : ping
>>> INFO   | jvm 1    | 2007/03/14 14:13:22 | Received a packet PING : ping
>>> DEBUG  | wrapperp | 2007/03/14 14:13:26 | send a packet PING : ping
>>> INFO   | jvm 1    | 2007/03/14 14:13:26 | Received a packet PING : ping
>>> ---
>>>
>>>     Reviewing the source, I can not think of any reason why this would 
>>> happen
>>> repeatedly.  There are event callbacks, but if the thread was getting 
>>> stuck there
>>> somehow, you would not see the second fourth line.
>>>
>>>     Are you using an unmodified version of the wrapper jar?  I ask 
>>> because of
>>> the lines like the following in the log:
>>> ---
>>> INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PROPERTIES : 
>>> (Property Values)
>>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_ARCH->x86
>>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_BITS->32
>>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java 
>>> props:set.WRAPPER_FILE_SEPARATOR->\
>>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_OS->windows
>>> ---
>>>     From their timing in the log, they are being printed before your 
>>> application has
>>> been started and must be being displayed from within the internal
>>> WrapperManager.readProperties method.  That is not output that was in 
>>> the original
>>> source.
>>>
>>> Cheers,
>>> Leif
>>>
>>>
>>> madis wrote:
>>>   
>>>       
>>>> Hi
>>>>
>>>> Altough the system is practically idle I often get VM restarts beacuse 
>>>> the ping request times out. I have set the timeout for 4 minutes with
>>>> wrapper.ping.timeout=240
>>>> wrapper.ping.interval=5
>>>>
>>>> Does anybody know how to fix this problem without disabling VM restarts?
>>>>
>>>> Madis
>>>>
>>>>
>>>> Here is the logfile for an example restart:
>>>>   
>>>>     
>>>>         
>>> <snip>
>>>
>>>
>>> -------------------------------------------------------------------------
>>> Take Surveys. Earn Cash. Influence the Future of IT
>>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>>> opinions on IT & business topics through brief surveys-and earn cash
>>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>   
>>>       
>> ------------------------------------------------------------------------
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>   
>>     
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

Re: [Wrapper-user] JVM restart with ping-timeout

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

Madis,
    The Wrapper sends PING packets to the JVM at an interval defined by the
wrapper.ping.interval property, every 5 seconds by default.  The JVM side of
Normally, the JVM immediately responds by sending a PING back to the
Wrapper process.
    A timeout occurs when ever more than the wrapper.ping.timeout has 
expired
without the Wrapper process receiving a PING packet from the JVM.

A) This is not a problem that I have ever had reported in the past.
B) Reviewing the source, I do not see any way at all that this could be 
happening
with the unmodified source.   Immediately after the "Received a 
packet..." message
is logged by the handleSocket() method, it proceeds to call the 
sendCommand()
method where a "Send a packet..." message should be logged.  That is not 
happening.

    I would love to help further, but it is not really possible for me 
to try to debug
modified versions of the Wrapper.   I have given you clues as to where 
the problem
likely is, but you are going to need to go in and debug what is happening.

    Cheers,
    Leif

madis wrote:
> I compile the service wrapper java source with my own project. Kinda 
> got that way because when I installed the service on XP sp2,  I could 
> not get it started. Everything was OK after I did a little restart but 
> I poked around a little before that (not much, just the properties and 
> dll resolving).
>
> Tryd with original source from version 3.2.3:
>
> Still doing 50% from full cycle:
> ....................
> INFO   | jvm 1    | 2007/03/14 16:18:13 | Received a packet PING : ping
> DEBUG  | wrapperp | 2007/03/14 16:18:17 | send a packet PING : ping
> INFO   | jvm 1    | 2007/03/14 16:18:17 | Received a packet PING : ping
> DEBUG  | wrapperp | 2007/03/14 16:18:21 | send a packet PING : ping
> INFO   | jvm 1    | 2007/03/14 16:18:21 | Received a packet PING : ping
> DEBUG  | wrapperp | 2007/03/14 16:18:25 | send a packet PING : ping
> ....................
>
> If the ping cycle is incomplete why does it take so many trys before 
> VM shuts down?
>
> Leif Mortenson wrote:
>> Madis,
>>     Looking at your logs, the JVM is receiving pings from the Wrapper 
>> process
>> correctly, but it does not appear to be sending the ping reply back to 
>> the Wrapper.
>>
>>     This is what a single ping cycle should look like:
>> ---
>> DEBUG  | wrapperp | send a packet PING : ping
>> INFO   | jvm 1    | Received a packet PING : ping
>> INFO   | jvm 1    | Send a packet PING : ping
>> DEBUG  | wrapperp | read a packet PING : ping
>> ---
>>
>>     But from your logs, you are only seeing the first two lines:
>> ---
>> DEBUG  | wrapperp | 2007/03/14 14:13:22 | send a packet PING : ping
>> INFO   | jvm 1    | 2007/03/14 14:13:22 | Received a packet PING : ping
>> DEBUG  | wrapperp | 2007/03/14 14:13:26 | send a packet PING : ping
>> INFO   | jvm 1    | 2007/03/14 14:13:26 | Received a packet PING : ping
>> ---
>>
>>     Reviewing the source, I can not think of any reason why this would 
>> happen
>> repeatedly.  There are event callbacks, but if the thread was getting 
>> stuck there
>> somehow, you would not see the second fourth line.
>>
>>     Are you using an unmodified version of the wrapper jar?  I ask 
>> because of
>> the lines like the following in the log:
>> ---
>> INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PROPERTIES : 
>> (Property Values)
>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_ARCH->x86
>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_BITS->32
>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java 
>> props:set.WRAPPER_FILE_SEPARATOR->\
>> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_OS->windows
>> ---
>>     From their timing in the log, they are being printed before your 
>> application has
>> been started and must be being displayed from within the internal
>> WrapperManager.readProperties method.  That is not output that was in 
>> the original
>> source.
>>
>> Cheers,
>> Leif
>>
>>
>> madis wrote:
>>   
>>> Hi
>>>
>>> Altough the system is practically idle I often get VM restarts beacuse 
>>> the ping request times out. I have set the timeout for 4 minutes with
>>> wrapper.ping.timeout=240
>>> wrapper.ping.interval=5
>>>
>>> Does anybody know how to fix this problem without disabling VM restarts?
>>>
>>> Madis
>>>
>>>
>>> Here is the logfile for an example restart:
>>>   
>>>     
>> <snip>
>>
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>   
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

Re: [Wrapper-user] JVM restart with ping-timeout

[madis <ma...@ja...>]

I compile the service wrapper java source with my own project. Kinda got 
that way because when I installed the service on XP sp2,  I could not 
get it started. Everything was OK after I did a little restart but I 
poked around a little before that (not much, just the properties and dll 
resolving).

Tryd with original source from version 3.2.3:

Still doing 50% from full cycle:
....................
INFO   | jvm 1    | 2007/03/14 16:18:13 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 16:18:17 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 16:18:17 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 16:18:21 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 16:18:21 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 16:18:25 | send a packet PING : ping
....................

If the ping cycle is incomplete why does it take so many trys before VM 
shuts down?

Leif Mortenson wrote:
> Madis,
>     Looking at your logs, the JVM is receiving pings from the Wrapper 
> process
> correctly, but it does not appear to be sending the ping reply back to 
> the Wrapper.
>
>     This is what a single ping cycle should look like:
> ---
> DEBUG  | wrapperp | send a packet PING : ping
> INFO   | jvm 1    | Received a packet PING : ping
> INFO   | jvm 1    | Send a packet PING : ping
> DEBUG  | wrapperp | read a packet PING : ping
> ---
>
>     But from your logs, you are only seeing the first two lines:
> ---
> DEBUG  | wrapperp | 2007/03/14 14:13:22 | send a packet PING : ping
> INFO   | jvm 1    | 2007/03/14 14:13:22 | Received a packet PING : ping
> DEBUG  | wrapperp | 2007/03/14 14:13:26 | send a packet PING : ping
> INFO   | jvm 1    | 2007/03/14 14:13:26 | Received a packet PING : ping
> ---
>
>     Reviewing the source, I can not think of any reason why this would 
> happen
> repeatedly.  There are event callbacks, but if the thread was getting 
> stuck there
> somehow, you would not see the second fourth line.
>
>     Are you using an unmodified version of the wrapper jar?  I ask 
> because of
> the lines like the following in the log:
> ---
> INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PROPERTIES : 
> (Property Values)
> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_ARCH->x86
> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_BITS->32
> INFO   | jvm 1    | 2007/03/14 14:13:17 | java 
> props:set.WRAPPER_FILE_SEPARATOR->\
> INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_OS->windows
> ---
>     From their timing in the log, they are being printed before your 
> application has
> been started and must be being displayed from within the internal
> WrapperManager.readProperties method.  That is not output that was in 
> the original
> source.
>
> Cheers,
> Leif
>
>
> madis wrote:
>   
>> Hi
>>
>> Altough the system is practically idle I often get VM restarts beacuse 
>> the ping request times out. I have set the timeout for 4 minutes with
>> wrapper.ping.timeout=240
>> wrapper.ping.interval=5
>>
>> Does anybody know how to fix this problem without disabling VM restarts?
>>
>> Madis
>>
>>
>> Here is the logfile for an example restart:
>>   
>>     
> <snip>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

Re: [Wrapper-user] JVM restart with ping-timeout

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

Madis,
    Looking at your logs, the JVM is receiving pings from the Wrapper 
process
correctly, but it does not appear to be sending the ping reply back to 
the Wrapper.

    This is what a single ping cycle should look like:
---
DEBUG  | wrapperp | send a packet PING : ping
INFO   | jvm 1    | Received a packet PING : ping
INFO   | jvm 1    | Send a packet PING : ping
DEBUG  | wrapperp | read a packet PING : ping
---

    But from your logs, you are only seeing the first two lines:
---
DEBUG  | wrapperp | 2007/03/14 14:13:22 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 14:13:22 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 14:13:26 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 14:13:26 | Received a packet PING : ping
---

    Reviewing the source, I can not think of any reason why this would 
happen
repeatedly.  There are event callbacks, but if the thread was getting 
stuck there
somehow, you would not see the second fourth line.

    Are you using an unmodified version of the wrapper jar?  I ask 
because of
the lines like the following in the log:
---
INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PROPERTIES : 
(Property Values)
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_ARCH->x86
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_BITS->32
INFO   | jvm 1    | 2007/03/14 14:13:17 | java 
props:set.WRAPPER_FILE_SEPARATOR->\
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_OS->windows
---
    From their timing in the log, they are being printed before your 
application has
been started and must be being displayed from within the internal
WrapperManager.readProperties method.  That is not output that was in 
the original
source.

Cheers,
Leif


madis wrote:
> Hi
>
> Altough the system is practically idle I often get VM restarts beacuse 
> the ping request times out. I have set the timeout for 4 minutes with
> wrapper.ping.timeout=240
> wrapper.ping.interval=5
>
> Does anybody know how to fix this problem without disabling VM restarts?
>
> Madis
>
>
> Here is the logfile for an example restart:
>   
<snip>

Re: [Wrapper-user] Can't make old wrapper daemon go away

[Mark L. <ma...@le...>]

Leif,

Many, many thanks. No problem with all the e-mails, as they had a happy 
ending. :) Thanks for running this down and correcting it. I ran your 
new script and it works perfectly. Now it all makes sense. The only 
change I made when it stopped working was that I put my app one level 
deeper in the file system so that the path was increased by a few 
characters. It seemed so inconsequential to me that it didn't even occur 
to me when I racked my brain trying to figure out what was different 
when it stopped working. Good illustration of the basic rule of 
troubleshooting: assume that no change is inconsequential, and record 
even the smallest ones. Thanks again.

-Mark

Leif Mortenson wrote:
> Sorry for all the mails
>
> Mark,
>    I figured it out.  ps on OSX has a -w argument which tells ps to 
> use 132 columns.
> If you do it twice then it uses as many columns as necessary.  It 
> seems to work the
> same whether it is being run directly from a shell or from within a 
> subprocess.
>
>    Anyway.  I have attached the fixed shell script with the following 
> fix:
> ---
>                case "$DIST_OS" in
>                    'macosx')
>                        pidtest=`$PSEXE -ww -p $pid -o command | grep 
> "$WRAPPER_CMD" | tail -1`
>                        ;;
>                    *)
>                        pidtest=`$PSEXE -p $pid -o args | grep 
> "$WRAPPER_CMD" | tail -1`
>                        ;;
>                esac
> ---
>
>    Please let me know how it works for you.
>
> Cheers,
> Leif
>
> Leif Mortenson wrote:
>> Mark,
>>     Hi again.  The following change will make this problem less 
>> likely, but it will still be
>> encountered for narrow parent shells, or for long paths.  Make this 
>> change in the
>> getpid function of the script.
>> ---
>>                 case "$DIST_OS" in
>>                     'macosx')
>>                         pidtest=`$PSEXE -p $pid -o command | grep 
>> "$WRAPPER_CMD" | tail -1`
>>                         ;;
>>                     *)
>>                         pidtest=`$PSEXE -p $pid -o args | grep 
>> "$WRAPPER_CMD" | tail -1`
>>                         ;;
>>                 esac
>> ---
>>
>>     Still working on a better solution.
>>
>> Cheers,
>> Leif
>>
>> Leif Mortenson wrote:
>>  
>>> Mark,
>>> I played around with this some more today trying to figure out what 
>>> the problem
>>> could possibly be.  The very first time I tried this today, I saw 
>>> the same thing you
>>> did,  BUT  when I tried to repeat it, I was unable to.  Every other 
>>> attempt results
>>> in the script working perfectly.  Are you seeing this intermittently 
>>> or does it happen
>>> every time?
>>>
>>> Mark Leone wrote:
>>>      
>>>> I downloaded the script two different times from the URL you 
>>>> provided. I even tried reverting back to the script in the 3.2.3 
>>>> distribution, just to see what happens. Although I get the stale 
>>>> pid error with both versions of the script, the distribution 
>>>> version throws some other error messages relating to a keyword 
>>>> error, I believe; so I'm satisfied that I'm actually executing the 
>>>> new version of the script.
>>>>           
>>> Ok.  That does indeed sound like you are running the correct thing.
>>>
>>> We are not seeing the same results, but I am attempting to 
>>> understand why.
>>> Could you edit your script and make following modifications in the 
>>> getpid()
>>> function:
>>> ---
>>>                 case "$DIST_OS" in
>>>                     'macosx')
>>>                         echo "pidtest='$PSEXE -p $pid | grep 
>>> \"$WRAPPER_CMD\" | tail -1'"
>>>                         pidtest=`$PSEXE -p $pid | grep 
>>> "$WRAPPER_CMD" | tail -1`
>>>                         ;;
>>>                     *)
>>>                         pidtest=`$PSEXE -p $pid -o args | grep 
>>> "$WRAPPER_CMD" | tail -1`
>>>                         ;;
>>>                 esac
>>>                 echo "pidtest=[$pidtest]"
>>> ---
>>> The changes are to add the two echo statements.  Be careful of the 
>>> regular single
>>> quotes in the first echo.
>>>
>>> On my system, when I check the status, I get the following:
>>> ---
>>> myhost:~/dev/sourceforge/wrapper/test myuser$ ./action status
>>> pidtest='/bin/ps -p 2631 | grep 
>>> "/Users/myuser/dev/sourceforge/wrapper/test/../bin/wrapper" | tail -1'
>>> pidtest=[ 2631 p2 S+ 0:00.15 
>>> /Users/myuser/dev/sourceforge/wrapper/test/../bin/wrapper  
>>> /Users/myuser/dev/sourceforge/wrappe]
>>> Action Test Case is running (2631).
>>> ---
>>>
>>> AHHHH  I figured it out as I wrote this.   See that the second 
>>> pidtest value output is
>>> clipped at the end?  That is because the output is coming from the 
>>> piped output of the
>>> ps command.   For some reason, OSX is truncating the output lines to 
>>> the width of
>>> the parent shell even though that process is running in the background.
>>>
>>> If the shell width is wide, then this will work correctly.  If 
>>> however, the shell with is
>>> narrow enough that the wrapper process name is not fully listed then 
>>> the grep will
>>> fail.   See this example:
>>> ---
>>> myhost:~/dev/sourceforge/wrapper/test myuser$ ./action status
>>> pidtest='/bin/ps -p 2631 | grep 
>>> "/Users/myuser/dev/sourceforge/wrapper/test/../bin/wrapper" | tail -1'
>>> pidtest=[]
>>> Removed stale pid file: 
>>> /Users/myuser/dev/sourceforge/wrapper/test/./action.pid
>>> Action Test Case is not running.
>>> ---
>>>
>>> In the above case, ps returns the following:
>>> ---
>>>   PID  TT  STAT      TIME COMMAND
>>>  2631  p2  R+     0:00.35 /Users/myuser/dev/sourceforge/wrapper/t
>>> ---
>>> So the grep is failing.
>>>
>>> Anyone have any ideas on how to resolve this?  I will look into it 
>>> as well...
>>>
>>> Cheers,
>>> Leif
>>>       
>>
>>
>> ------------------------------------------------------------------------- 
>>
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to 
>> share your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV 
>>
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>   
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

[Wrapper-user] Compilation in HP-UX IA64

[Diego R. <dru...@be...>]

Hi, I'm trying to compile the sources in a HP-UX IA64 and I'm getting
the following error:

Wrapper Build System
--------------------
Buildfile: build.xml

init:
OS=3D'HP-UX'

update-info:
Copying 1 file to
/home/cce/wrapper/wrapper_3.1.1_src/src/java/org/tanukisoftware/wrapper
Copying 1 file to /home/cce/wrapper/wrapper_3.1.1_src/src/c

compile-java:
Compiling 1 source file to
/home/cce/wrapper/wrapper_3.1.1_src/build/classes

compile-c-unix:
if test ! -d .deps; then mkdir .deps; fi
gcc -O3 -Wall --pedantic -DHPUX -D_XOPEN_SOURCE_EXTENDED wrapper.c
wrapperinfo.c wrappereventloop.c wrapper_unix.c property.c logger.c -lm
-o ../../bin/wrapper
wrapper.c: In function 'wrapperProtocolOpen':
wrapper.c:558: warning: dereferencing type-punned pointer will break
strict-aliasing rules
logger.c:230: warning: missing braces around initializer
logger.c:230: warning: (near initialization for
'log_printfMutex.m_short')
ld: Unsatisfied symbol "rk_globfree" in file /var/tmp//cc025oOs.o
ld: Unsatisfied symbol "rk_glob" in file /var/tmp//cc025oOs.o
2 errors.
collect2: ld returned 1 exit status
gmake: *** [wrapper] Error 1

BUILD FAILED
/home/cce/wrapper/wrapper_3.1.1_src/build.xml:316: exec returned: 2


Any Ideas?=20

Diego.
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

[Wrapper-user] JVM restart with ping-timeout

[madis <ma...@ja...>]

Hi

Altough the system is practically idle I often get VM restarts beacuse 
the ping request times out. I have set the timeout for 4 minutes with
wrapper.ping.timeout=240
wrapper.ping.interval=5

Does anybody know how to fix this problem without disabling VM restarts?

Madis


Here is the logfile for an example restart:

STATUS | wrapper  | 2007/03/14 14:13:17 | Starting the Jawilla Test service...
STATUS | wrapper  | 2007/03/14 14:13:17 | --> Wrapper Started as Service
DEBUG  | wrapper  | 2007/03/14 14:13:17 | Using tick timer.
DEBUG  | wrapperp | 2007/03/14 14:13:17 | server listening on port 32000.
STATUS | wrapper  | 2007/03/14 14:13:17 | Launching a JVM...
DEBUG  | wrapper  | 2007/03/14 14:13:17 | command: 
"H:\WINDOWS\system32\javaw.exe" -Djava.library.path="../lib" -classpath 
"../lib/jawilla-wrapper.jar;../lib/comm.jar" 
-Dwrapper.key="dNieTuNL6egp5T7P" -Dwrapper.port=32000 
-Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 
-Dwrapper.debug="TRUE" -Dwrapper.pid=4772 -Dwrapper.version="3.2.3" 
-Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" 
-Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 com.jawilla.wrapper.Main
DEBUG  | wrapper  | 2007/03/14 14:13:17 | JVM started (PID=508)
INFO   | jvm 1    | 2007/03/14 14:13:17 | Initializing...
INFO   | jvm 1    | 2007/03/14 14:13:17 | WrapperManager class initialized by thread: main  Using classloader: 
sun.misc.Launcher$AppClassLoader@d9f9c3
INFO   | jvm 1    | 2007/03/14 14:13:17 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2007/03/14 14:13:17 |   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
INFO   | jvm 1    | 2007/03/14 14:13:17 |
INFO   | jvm 1    | 2007/03/14 14:13:17 | Wrapper Manager: JVM #1
INFO   | jvm 1    | 2007/03/14 14:13:17 | Running a 32-bit JVM.
INFO   | jvm 1    | 2007/03/14 14:13:17 | Wrapper Manager: Registering shutdown hook
INFO   | jvm 1    | 2007/03/14 14:13:17 | Wrapper Manager: Using wrapper
INFO   | jvm 1    | 2007/03/14 14:13:17 | Java Version   : 1.6.0-b105 Java HotSpot(TM) Client VM
INFO   | jvm 1    | 2007/03/14 14:13:17 | Java VM Vendor : Sun Microsystems Inc.
INFO   | jvm 1    | 2007/03/14 14:13:17 |
INFO   | jvm 1    | 2007/03/14 14:13:17 | Control event monitor thread started.
INFO   | jvm 1    | 2007/03/14 14:13:17 | WrapperManager.start(com.jawilla.wrapper.Main@201f9, args[]) called by thread: main
INFO   | jvm 1    | 2007/03/14 14:13:17 | Startup runner thread started.
INFO   | jvm 1    | 2007/03/14 14:13:17 | Communications runner thread started.
INFO   | jvm 1    | 2007/03/14 14:13:17 | Open socket to wrapper...Wrapper-Connection
INFO   | jvm 1    | 2007/03/14 14:13:17 | Opened Socket from 31000 to 32000
INFO   | jvm 1    | 2007/03/14 14:13:17 | Send a packet KEY : dNieTuNL6egp5T7P
INFO   | jvm 1    | 2007/03/14 14:13:17 | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000])
DEBUG  | wrapperp | 2007/03/14 14:13:17 | accepted a socket from 127.0.0.1 on port 31000
DEBUG  | wrapperp | 2007/03/14 14:13:17 | read a packet KEY : dNieTuNL6egp5T7P
DEBUG  | wrapper  | 2007/03/14 14:13:17 | Got key from JVM: dNieTuNL6egp5T7P
DEBUG  | wrapperp | 2007/03/14 14:13:17 | send a packet LOW_LOG_LEVEL : 1
DEBUG  | wrapperp | 2007/03/14 14:13:17 | send a packet PING_TIMEOUT : 240
DEBUG  | wrapperp | 2007/03/14 14:13:17 | send a packet PROPERTIES : (Property Values)
DEBUG  | wrapper  | 2007/03/14 14:13:17 | Start Application.
DEBUG  | wrapperp | 2007/03/14 14:13:17 | send a packet START : start
INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet LOW_LOG_LEVEL : 1
INFO   | jvm 1    | 2007/03/14 14:13:17 | Wrapper Manager: LowLogLevel from Wrapper is 1
INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PING_TIMEOUT : 240
INFO   | jvm 1    | 2007/03/14 14:13:17 | PingTimeout from Wrapper is 240000
INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PROPERTIES : (Property Values)
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_ARCH->x86
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_BITS->32
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_FILE_SEPARATOR->\
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_OS->windows
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_PATH_SEPARATOR->;
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.console.format->PM
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.console.loglevel->ERROR
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.console.title->Jawilla Test Manager
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.java.classpath.1->../lib/jawilla-wrapper.jar
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.java.classpath.2->../lib/comm.jar
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.java.command->javaw
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.java.library.path.1->../lib
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.java.mainclass->com.jawilla.wrapper.Main
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.logfile->../logs/wrapper.log
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.logfile.format->LPTM
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.logfile.loglevel->DEBUG
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.logfile.maxfiles->0
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.logfile.maxsize->100k
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ntservice.dependency.1->
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ntservice.description->Your add here.
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ntservice.displayname->Jawilla Test
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ntservice.interactive->true
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ntservice.name->jawillatest
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ntservice.starttype->AUTO_START
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ping.interval->5
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.ping.timeout->240
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:wrapper.syslog.loglevel->ERROR
INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet START : start
INFO   | jvm 1    | 2007/03/14 14:13:17 | calling WrapperListener.start()
INFO   | jvm 1    | 2007/03/14 14:13:17 | Waiting for WrapperListener.start runner thread to complete.
INFO   | jvm 1    | 2007/03/14 14:13:17 | WrapperListener.start runner thread started.
INFO   | jvm 1    | 2007/03/14 14:13:17 | start()
INFO   | jvm 1    | 2007/03/14 14:13:17 | user.dir=h:\work\e-police\serviceWrapper\bin
INFO   | jvm 1    | 2007/03/14 14:13:17 | WrapperListener.start runner thread stopped.
INFO   | jvm 1    | 2007/03/14 14:13:17 | returned from WrapperListener.start()
INFO   | jvm 1    | 2007/03/14 14:13:17 | Send a packet STARTED :
DEBUG  | wrapperp | 2007/03/14 14:13:17 | read a packet STARTED :
DEBUG  | wrapper  | 2007/03/14 14:13:17 | JVM signalled that it was started.
INFO   | jvm 1    | 2007/03/14 14:13:17 | Startup runner thread stopped.
STATUS | wrapper  | 2007/03/14 14:13:19 | Jawilla Test started.
DEBUG  | wrapperp | 2007/03/14 14:13:22 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 14:13:22 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 14:13:26 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 14:13:26 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 14:13:31 | send a packet PING : ping
..............................................................................................................
DEBUG  | wrapperp | 2007/03/14 14:17:44 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 14:17:44 | Received a packet PING : ping
ERROR  | wrapper  | 2007/03/14 14:17:47 | JVM appears hung: Timed out waiting for signal from JVM.
ERROR  | wrapper  | 2007/03/14 14:17:47 | JVM did not exit on request, terminated
DEBUG  | wrapperp | 2007/03/14 14:17:47 | server listening on port 32001.
DEBUG  | wrapper  | 2007/03/14 14:17:47 | JVM was only running for 245 seconds leading to a failed restart count of 1.
DEBUG  | wrapper  | 2007/03/14 14:17:47 | Waiting 5 seconds before launching another JVM.
STATUS | wrapper  | 2007/03/14 14:17:52 | Launching a JVM...

Re: [Wrapper-user] Building on OpenBSD + AMD64 prob

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

Peter,
    I am not currently able to try this out myself.  I can try to get an 
OpenBSD system set
up under VMware.  But 'll be honest about my current todo list...It is 
going to take me a
little while.

    Looking out your output, in addition to the warnings, the thing that 
as actually causing
the build to fail is the following:
/usr/bin/ld: wrapperjni_unix.o: relocation R_X86_64_32 can not be used
when making a shared object; recompile with -fPIC

    It looks like your "wrapper" process is being built correctly.  It 
is the "libwrapper.so"
file that is failing.

    What does your Makefile look like?  Are you sure that the -fPIC 
option was
added at a point that it will be used by both builds?

Cheers,
Leif


Peter Thoenen wrote:
> Alright so been digging throught the archives and src to get this to
> compile on OBSD (mainly mod'ing the hell out of the FreeBSD makefile
> and some other items like s/FREEBSD/OPENBSD).  The problem I am hitting
> now and google isn't helping I think is AMD64 specific .. ideas? (see
> below):
>
> 07-03-09 15:20:23 /usr/local/src/wrapper_3.2.3_src # ./build64.sh 
>
> Wrapper Build System
> --------------------
> Buildfile: build.xml
>
> init:msg:
> **********************************************************************
> About to build a 64-bit version of the Java Service Wrapper 3.2.3.
> The OS Name is "OpenBSD", resolved from "OpenBSD".
> The Architecture is "x86", resolved from "amd64".
> The distribution name will be: wrapper-OpenBSD-x86-64-3.2.3
> **********************************************************************
>
> update-info:
> Copying 1 file to
> /usr/local/src/wrapper_3.2.3_src/src/java/org/tanukisoftware/wrapper
> Copying 1 file to /usr/local/src/wrapper_3.2.3_src/src/c
>
> compile-java-warn:
> **********************************************************************
> WARNING
> The jar is being built for Java version 1.4.  This will not be
> compatible with older JVMs.
> **********************************************************************
>
> compile-java:
> Compiling 1 source file to
> /usr/local/src/wrapper_3.2.3_src/build/classes
> ClassArgument.name=org.tanukisoftware.wrapper.WrapperManager
>
> compile-c-unix:
> if test ! -d .deps; then mkdir .deps; fi
> gcc -Wall -pedantic -DOPENBSD -DPIC wrapper.c wrapperinfo.c
> wrappereventloop.c wrapper_unix.c property.c logger.c -lm -lcompat
> -pthread -o ../../bin/wrapper
> /tmp//ccF22459.o(.text+0xc54): In function `wrapperProtocolFunction':
> : warning: strcpy() is almost always misused, please use strlcpy()
> /tmp//ccF22459.o(.text+0x29): In function
> `wrapperAddDefaultProperties':
> : warning: sprintf() is often misused, please use snprintf()
> gcc -Wall -pedantic -DOPENBSD -DPIC -I/usr/local/jdk-1.5.0/include
> -I/usr/local/jdk-1.5.0/include/openbsd    -c -o wrapperinfo.o
> wrapperinfo.c
> gcc -Wall -pedantic -DOPENBSD -DPIC -shared wrapperjni_unix.o
> wrapperinfo.o wrapperjni.o -o ../../lib/libwrapper.so
> /usr/bin/ld: wrapperjni_unix.o: relocation R_X86_64_32 can not be used
> when making a shared object; recompile with -fPIC
> wrapperjni_unix.o: could not read symbols: Bad value
> collect2: ld returned 1 exit status
> gmake: *** [libwrapper.so] Error 1
>
> BUILD FAILED
> /usr/local/src/wrapper_3.2.3_src/build.xml:580: exec returned: 2
>
> Total time: 7 seconds
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>