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

Re: [Wrapper-user] SERVICE_CONTROL_INTERROGATE - last message before wrapper dies

[Krishna K. <kko...@wo...>]

Just wanted to update the group regarding this problem.  It turned out 
that we were specifying memory arguments to the JVM in the wrapper's 
config. file erroneously.

The JVM argument parameters were provided twice:

wrapper.java.additional.4=-Xms256m
wrapper.java.additional.5=-Xmx800M


# Initial Java Heap Size (in MB)
wrapper.java.initmemory=25

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=100

The result is that the command line that wrapper process generated 
looked like this:

java -Xms256m -Xmx800M -Xms25m -Xmx100m

The second set of memory arguments were not enough for our process to 
run and the service would abend due to insufficient memory and the 
OutOfMemory error line would also not show up in the logs.


Leif Mortenson wrote:

> Krishna Kottamasu wrote:
>
>> Thanks for your prompt response.   Upgrading this customer to 
>> 3.1.1/3.1.2 could take some time.  I can try setting 
>> wrapper.debug=false in the config. file and see how it goes.  From 
>> your message, this is what I understood:
>
>
> Ok, I assumed you had enabled debug output when you started 
> encountering problems.
> Is there a reason why you have debug output enabled by default?  Debug 
> output builds
> up pretty large log files in a hurry.  It looks like you have it 
> limited to 10, 10MB files
> though so you should be Ok as far as disk-space.
>
>> If more than one thread in our application tries to write something 
>> to the standard out (which the wrapper traps and outputs to the 
>> wrapper's log file) at the same time, that could be crashing the 
>> wrapper process.  Is my understanding correct?
>
>
> I want to reclarify this.   It is only a problem with multithreading 
> in the C code of the
> Wrapper.exe process.   There is NOT a problem when console log output 
> coming
> from the Java program itself.   Logging from multi threaded Java apps 
> is perfectly
> safe.
>
> If the User presss CTRL-C,  second thread from the OS is called into 
> the Wrapper
> process.   If my debug log output from this second thread attempts to 
> log at the same
> instant as a log message from the Wrapper's main event loop then there 
> was a chance
> of memory corruption.   With debug output disabled, this would pretty 
> much never
> happen.
>
>> I've also answered your questions right underneath them in the 
>> original message.
>
>
> Thanks,
> Leif
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM. 
> Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] Tomcat starts and shuts down in the same few second

[Andreas K. <and...@gm...>]

Hello everybody

I'm a new user of wrapper. Currently I observed a strange behavior
using wrapper 3.1.1 with tomcat 5.0.28.

If I start tomcat with catalina.sh everything works fine.

But when I start Tomcat with wrapper in console mode, Tomcat starts up
and shuts down in the same moment. I set the logging to debug. For me
there is no sign of an error or exception shown.

This is the critical part of the log:

jvm 1    | Oct 8, 2004 2:22:14 PM org.apache.jk.server.JkMain start
jvm 1    | INFO: Jk running ID=0 time=6/655
config=/usr/local/tomcat5/conf/jk2.properties
jvm 1    | Oct 8, 2004 2:22:14 PM org.apache.catalina.startup.Catalina start
jvm 1    | INFO: Server startup in 31411 ms
jvm 1    | WrapperStartStopApp: start main method completed
wrapperp | send a packet PING : ping
jvm 1    | Received a packet PING : ping
jvm 1    | Send a packet PING : ok
jvm 1    | All non-daemon threads have stopped.  Exiting.
jvm 1    | WrapperManager.stop(0) called by thread: Wrapper-Connection
jvm 1    | Send a packet STOP : 0
wrapperp | read a packet PING : ok
wrapper  | Got ping response from JVM
wrapperp | read a packet STOP : 0
wrapper  | JVM requested a shutdown. (0)
wrapper  | wrapperStopProcess(0) called.
wrapper  | Sending stop signal to JVM
wrapperp | send a packet STOP : NULL
jvm 1    | Thread, Wrapper-Connection, handling the shutdown process.
jvm 1    | calling listener.stop()
jvm 1    | WrapperStartStopApp: stop(0)
jvm 1    | WrapperStartStopApp: invoking stop main method
jvm 1    | Oct 8, 2004 2:22:16 PM org.apache.catalina.core.StandardService stop
jvm 1    | INFO: Stopping service Tomcat-Standalone

Has somebody an idea what the reason could be for this strange behavior?

Thanks a lot for your comments.

Andreas


-- 
Concentrator:  http://www.datacomm.ch/andreas.kapp/

[Wrapper-user] Tomcat5 starts and is shuts down afterwards

[Andreas K. <and...@gm...>]

Hallo everybody

I'm a new user of wrapper. Currently I observed a strange behavior
using wrapper with tomcat 5.0.28.

If I start tomcat with catalina.sh everything works fine.

But when I start Tomcat with wrapper in console mode, Tomcat starts up
and shuts down in the same moment. I set the logging to debug. For me
there is no sign of an error or exception shown.

This is the critical part of the log:

jvm 1    | Oct 8, 2004 2:22:14 PM org.apache.jk.server.JkMain start
jvm 1    | INFO: Jk running ID=0 time=6/655
config=/usr/local/tomcat5/conf/jk2.properties
jvm 1    | Oct 8, 2004 2:22:14 PM org.apache.catalina.startup.Catalina start
jvm 1    | INFO: Server startup in 31411 ms
jvm 1    | WrapperStartStopApp: start main method completed
wrapperp | send a packet PING : ping
jvm 1    | Received a packet PING : ping
jvm 1    | Send a packet PING : ok
jvm 1    | All non-daemon threads have stopped.  Exiting.
jvm 1    | WrapperManager.stop(0) called by thread: Wrapper-Connection
jvm 1    | Send a packet STOP : 0
wrapperp | read a packet PING : ok
wrapper  | Got ping response from JVM
wrapperp | read a packet STOP : 0
wrapper  | JVM requested a shutdown. (0)
wrapper  | wrapperStopProcess(0) called.
wrapper  | Sending stop signal to JVM
wrapperp | send a packet STOP : NULL
jvm 1    | Thread, Wrapper-Connection, handling the shutdown process.
jvm 1    | calling listener.stop()
jvm 1    | WrapperStartStopApp: stop(0)
jvm 1    | WrapperStartStopApp: invoking stop main method
jvm 1    | Oct 8, 2004 2:22:16 PM org.apache.catalina.core.StandardService stop
jvm 1    | INFO: Stopping service Tomcat-Standalone

Has somebody an idea what the reason could be for this strange behavior?

Thanks a lot for your comments.

Andreas

--
Concentrator:  http://www.datacomm.ch/andreas.kapp/

Re: [Wrapper-user] Programatically start a service from java

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

Daniel,
    The Wrapper does not provide a direct way to start or stop an 
external service directly
from within a Java application.   It does however allow you to define 
dependencies on other
services to make sure that they are started before your java application 
is started.  There are
some gotchas on system shutdown however, so be sure to read over the 
following docs:
http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-dependency-n.html

    One way for you to start and stop other services would be for you to 
write a simple
method in your application to do so.   You should be able to use the 
Runtime.exec methods
to run a command directly like "net start foobar" or "net stop 
foobar".   Have not tried
this myself, but I don't see why it shouldn't work for you.

Cheers,
Leif

Daniel Bress wrote:

>Does the service wrapper provide a means to programmatically start/stop
>a service from within a java application?
>
>Thanks,
>Dan
>  
>

Re: [Wrapper-user] Console hiding & java.lang.Process suggestion

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

Rich,
It looks like you have given this some thought, so sorry if I am missing
your
point. The wrapper.ntservice.hide-console and wrapper.ntservice.console
properties are used to control how the native Wrapper process creates or
hides
its own Console window. This is all outside of the scope of the Java process
so the methods that you pointed out are unfortunately not applicable to the
problem.

The native Wrapper process launches and then controls a single Java process.
The console is needed by several functions within the Wrapper process. It is
possible to pipe Java output from to the Wrapper process even if a console
window has not been registered.

There are problems with some system signals as well as the ability to
display
a Swing GUI with some Java versions however if a console has not been
registered.

Cheers,
Leif

Rich Townsend wrote:

> To Wrapper Devs,
>
> In the documentation for the property "wrapper.ntservice.hide_console"
> it says:
> "In order to capture the console output of a Java application the
> Wrapper must create a console for the JVM to use."
> , and:
> "In order to be able to display the Java GUI with older JVMs, the
> console can not be hidden by default."
>
> Can it not employ a Java-based solution and use the Runtime and
> Process classes in the java.lang package?
> I do not know whether you have considered this already, but their docs
> say that they have both existed since JDK1.0, for benefit of older code.
> You can start processes using the Runtime object to spawn Process
> objects.
> For a Java app you then specify "javaw xyz" as the process : this does
> not use a console at all, but being created with the Process object,
> it will still have InputStream/OutputStream objects that you can link to.
>
> Then setup stream copying threads to capture the process output
> invisibly and direct it where you want, to an AWT/Swing console, other
> program, log file or even real console.
> If the app requires input from its System.in stream then you would
> need some sort of console for the user to type into to pass onto the
> process, otherwise, it need not be displayed (probably not for a
> background service?).
> The Process object can spawn and operate in its own thread so that
> when it ends/quits/exits (use "waitfor()") it can notify an attached
> listener in your main wrapper program.
> Note that the Process streams are inverted because you are
> communicating inwards (for example, getOutputStream() returns what the
> Process considers to be its System.in).
>
> The disadvantage is that each new JVM process requires its own block
> of memory to run in (do not know how much JDK1.5 sharing saves, though).
>
> Also, so that the integration methods still work across the process
> boundary, you would need to make sure that you have a small helper
> class on the other side that you call as the process.
> OS API -> JNI -> WrapperMain -> WrapperHelperProcessApp -> User's App
> So then the WrapperStartStopApp "start()"/"stop()" methods can be
> activated by using some escape sequences or mini-protocol passed
> through the Process streams that is handled by your helper on the
> other side to manipulate the user's wrapped JAR/class.
> Requires at most 2 JVMs, as if more Java-wrapped services are needed
> then a loop in the wrapper helper can thread them in parallel and
> try-catch each on exception/error (including setting the security
> manager to catch inner System.exit() calls).
>
> Neat program anyway,
> See Ya,
> Rich Townsend.

Re: [Wrapper-user] Does the wrapper work with Tomcat 5.0.28?

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

Gil,
    Thanks for following up on this.  I am going to add a note to the 
Tomcat integration example
about this.  Could you confirm that the only change you made was to change:
wrapper.java.additional.1=-Djava.endorsed.dirs=../bin:../common/endorsed
to:
wrapper.java.additional.1=-Djava.endorsed.dirs=../common/endorsed

Thanks,
Leif

Gil Adam wrote:

> I found the problem with this.  In case it's helpful to anyone else, 
> the solution is to remove the %CATALINA_HOME%\bin from the 
> java.endorsed.dirs system property.
>
> -Gil
>
> At 06:22 PM 10/6/2004, you wrote:
>
>
>> Does anyone know if the Wrapper is compatible with Tomcat 5.0.28. I 
>> was using it with Tomcat 5.0.18 with no trouble, then I put in Tomcat 
>> 5.0.28 (which starts up using the same options just fine using the 
>> tomcat startup.bat script) and I get the following error:
>>
>>
>> --> Wrapper Started as Service
>> Launching a JVM...
>> Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org
>>
>> Bootstrap: Class loader creation threw exception
>> java.lang.ExceptionInInitializerError
>>         at 
>> org.apache.catalina.startup.ClassLoaderFactory.<clinit>(ClassLoaderFactory.java:63) 
>>
>>         at 
>> org.apache.catalina.startup.Bootstrap.initClassLoaders(Bootstrap.java:103) 
>>
>>         at 
>> org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:196)
>>         at 
>> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:402)
>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>         at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
>>
>>         at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
>>
>>         at java.lang.reflect.Method.invoke(Method.java:324)
>>         at 
>> org.tanukisoftware.wrapper.WrapperStartStopApp.run(WrapperStartStopApp.java:154) 
>>
>>         at java.lang.Thread.run(Thread.java:534)
>> Caused by: org.apache.commons.logging.LogConfigurationException: 
>> org.apache.commons.logging.LogConfigurationException: 
>> java.lang.NullPointerException (Caused by 
>> java.lang.NullPointerException) (Caused by 
>> org.apache.commons.logging.LogConfigurationException: 
>> java.lang.NullPointerException (Caused by 
>> java.lang.NullPointerException))
>>         at 
>> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543) 
>>
>>         at 
>> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) 
>>
>>         at 
>> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) 
>>
>>         at 
>> org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
>>         at 
>> org.apache.tomcat.util.compat.JdkCompat.<clinit>(JdkCompat.java:55)
>>         ... 10 more
>> Caused by: org.apache.commons.logging.LogConfigurationException: 
>> java.lang.NullPointerException (Caused by 
>> java.lang.NullPointerException)
>>         at 
>> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397) 
>>
>>         at 
>> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) 
>>
>>         ... 14 more
>> Caused by: java.lang.NullPointerException
>>         at 
>> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:374) 
>>
>>         ... 15 more
>> <-- Wrapper Stopped
>>
>>
>> Does anyone know what I'm doing to cause this?
>>
>> Thank you very much, all.
>>
>> -Gil
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
>> Use IT products in your business? Tell us what you think of them. 
>> Give us
>> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find 
>> out more
>> http://productguide.itmanagersjournal.com/guidepromo.tmpl
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>
> ---------------------------------------------------------------------
> Gil Adam
> ga...@in...
> Extension: 430
> Instant Messenger: AnswerGil
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out 
> more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

[Wrapper-user] Console hiding & java.lang.Process suggestion

[Rich T. <arm...@ho...>]

To Wrapper Devs,

In the documentation for the property "wrapper.ntservice.hide_console" it 
says:
"In order to capture the console output of a Java application the Wrapper 
must create a console for the JVM to use."
, and:
"In order to be able to display the Java GUI with older JVMs, the console 
can not be hidden by default."

Can it not employ a Java-based solution and use the Runtime and Process 
classes in the java.lang package?
I do not know whether you have considered this already, but their docs say 
that they have both existed since JDK1.0, for benefit of older code.
You can start processes using the Runtime object to spawn Process objects.
For a Java app you then specify "javaw xyz" as the process : this does not 
use a console at all, but being created with the Process object, it will 
still have InputStream/OutputStream objects that you can link to.

Then setup stream copying threads to capture the process output invisibly 
and direct it where you want, to an AWT/Swing console, other program, log 
file or even real console.
If the app requires input from its System.in stream then you would need some 
sort of console for the user to type into to pass onto the process, 
otherwise, it need not be displayed (probably not for a background 
service?).
The Process object can spawn and operate in its own thread so that when it 
ends/quits/exits (use "waitfor()") it can notify an attached listener in 
your main wrapper program.
Note that the Process streams are inverted because you are communicating 
inwards (for example, getOutputStream() returns what the Process considers 
to be its System.in).

The disadvantage is that each new JVM process requires its own block of 
memory to run in (do not know how much JDK1.5 sharing saves, though).

Also, so that the integration methods still work across the process 
boundary, you would need to make sure that you have a small helper class on 
the other side that you call as the process.
OS API -> JNI -> WrapperMain -> WrapperHelperProcessApp -> User's App
So then the WrapperStartStopApp "start()"/"stop()" methods can be activated 
by using some escape sequences or mini-protocol passed through the Process 
streams that is handled by your helper on the other side to manipulate the 
user's wrapped JAR/class.
Requires at most 2 JVMs, as if more Java-wrapped services are needed then a 
loop in the wrapper helper can thread them in parallel and try-catch each on 
exception/error (including setting the security manager to catch inner 
System.exit() calls).

Neat program anyway,
See Ya,
Rich Townsend.

_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/

[Wrapper-user] Programatically start a service from java

[Daniel B. <db...@te...>]

Does the service wrapper provide a means to programmatically start/stop
a service from within a java application?

Thanks,
Dan

-----Original Message-----
From: Gil Adam [mailto:gi...@gi...]=20
Sent: Wednesday, October 06, 2004 9:52 PM
To: wra...@li...
Subject: Re: [Wrapper-user] Does the wrapper work with Tomcat 5.0.28?

I found the problem with this.  In case it's helpful to anyone else, the

solution is to remove the %CATALINA_HOME%\bin from the
java.endorsed.dirs=20
system property.

-Gil

At 06:22 PM 10/6/2004, you wrote:


>Does anyone know if the Wrapper is compatible with Tomcat 5.0.28. I was

>using it with Tomcat 5.0.18 with no trouble, then I put in Tomcat
5.0.28=20
>(which starts up using the same options just fine using the tomcat=20
>startup.bat script) and I get the following error:
>
>
>--> Wrapper Started as Service
>Launching a JVM...
>Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org
>
>Bootstrap: Class loader creation threw exception
>java.lang.ExceptionInInitializerError
>         at=20
>
org.apache.catalina.startup.ClassLoaderFactory.<clinit>(ClassLoaderFacto
ry.java:63)
>         at=20
>
org.apache.catalina.startup.Bootstrap.initClassLoaders(Bootstrap.java:10
3)
>         at
org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:196)
>         at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:402)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at=20
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
>         at=20
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:324)
>         at=20
>
org.tanukisoftware.wrapper.WrapperStartStopApp.run(WrapperStartStopApp.j
ava:154)
>         at java.lang.Thread.run(Thread.java:534)
>Caused by: org.apache.commons.logging.LogConfigurationException:=20
>org.apache.commons.logging.LogConfigurationException:=20
>java.lang.NullPointerException (Caused by
java.lang.NullPointerException)=20
>(Caused by org.apache.commons.logging.LogConfigurationException:=20
>java.lang.NullPointerException (Caused by
java.lang.NullPointerException))
>         at=20
>
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImp
l.java:543)
>         at=20
>
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImp
l.java:235)
>         at=20
>
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImp
l.java:209)
>         at
org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
>         at=20
> org.apache.tomcat.util.compat.JdkCompat.<clinit>(JdkCompat.java:55)
>         ... 10 more
>Caused by: org.apache.commons.logging.LogConfigurationException:=20
>java.lang.NullPointerException (Caused by
java.lang.NullPointerException)
>         at=20
>
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFact
oryImpl.java:397)
>         at=20
>
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImp
l.java:529)
>         ... 14 more
>Caused by: java.lang.NullPointerException
>         at=20
>
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFact
oryImpl.java:374)
>         ... 15 more
><-- Wrapper Stopped
>
>
>Does anyone know what I'm doing to cause this?
>
>Thank you very much, all.
>
>-Gil
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IT Product Guide on
ITManagersJournal
>Use IT products in your business? Tell us what you think of them. Give
us
>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
more
>http://productguide.itmanagersjournal.com/guidepromo.tmpl
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

---------------------------------------------------------------------
Gil Adam
ga...@in...
Extension: 430
Instant Messenger: AnswerGil=20



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give
us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Does the wrapper work with Tomcat 5.0.28?

[Gil A. <gi...@gi...>]

I found the problem with this.  In case it's helpful to anyone else, the 
solution is to remove the %CATALINA_HOME%\bin from the java.endorsed.dirs 
system property.

-Gil

At 06:22 PM 10/6/2004, you wrote:


>Does anyone know if the Wrapper is compatible with Tomcat 5.0.28. I was 
>using it with Tomcat 5.0.18 with no trouble, then I put in Tomcat 5.0.28 
>(which starts up using the same options just fine using the tomcat 
>startup.bat script) and I get the following error:
>
>
>--> Wrapper Started as Service
>Launching a JVM...
>Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org
>
>Bootstrap: Class loader creation threw exception
>java.lang.ExceptionInInitializerError
>         at 
> org.apache.catalina.startup.ClassLoaderFactory.<clinit>(ClassLoaderFactory.java:63)
>         at 
> org.apache.catalina.startup.Bootstrap.initClassLoaders(Bootstrap.java:103)
>         at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:196)
>         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:402)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:324)
>         at 
> org.tanukisoftware.wrapper.WrapperStartStopApp.run(WrapperStartStopApp.java:154)
>         at java.lang.Thread.run(Thread.java:534)
>Caused by: org.apache.commons.logging.LogConfigurationException: 
>org.apache.commons.logging.LogConfigurationException: 
>java.lang.NullPointerException (Caused by java.lang.NullPointerException) 
>(Caused by org.apache.commons.logging.LogConfigurationException: 
>java.lang.NullPointerException (Caused by java.lang.NullPointerException))
>         at 
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
>         at 
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
>         at 
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
>         at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
>         at 
> org.apache.tomcat.util.compat.JdkCompat.<clinit>(JdkCompat.java:55)
>         ... 10 more
>Caused by: org.apache.commons.logging.LogConfigurationException: 
>java.lang.NullPointerException (Caused by java.lang.NullPointerException)
>         at 
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397)
>         at 
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
>         ... 14 more
>Caused by: java.lang.NullPointerException
>         at 
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:374)
>         ... 15 more
><-- Wrapper Stopped
>
>
>Does anyone know what I'm doing to cause this?
>
>Thank you very much, all.
>
>-Gil
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
>Use IT products in your business? Tell us what you think of them. Give us
>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
>http://productguide.itmanagersjournal.com/guidepromo.tmpl
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

---------------------------------------------------------------------
Gil Adam
ga...@in...
Extension: 430
Instant Messenger: AnswerGil 

[Wrapper-user] Does the wrapper work with Tomcat 5.0.28?

[Gil A. <gi...@gi...>]

Does anyone know if the Wrapper is compatible with Tomcat 5.0.28. I was 
using it with Tomcat 5.0.18 with no trouble, then I put in Tomcat 5.0.28 
(which starts up using the same options just fine using the tomcat 
startup.bat script) and I get the following error:


--> Wrapper Started as Service
Launching a JVM...
Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org

Bootstrap: Class loader creation threw exception
java.lang.ExceptionInInitializerError
         at 
org.apache.catalina.startup.ClassLoaderFactory.<clinit>(ClassLoaderFactory.java:63)
         at 
org.apache.catalina.startup.Bootstrap.initClassLoaders(Bootstrap.java:103)
         at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:196)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:402)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at 
org.tanukisoftware.wrapper.WrapperStartStopApp.run(WrapperStartStopApp.java:154)
         at java.lang.Thread.run(Thread.java:534)
Caused by: org.apache.commons.logging.LogConfigurationException: 
org.apache.commons.logging.LogConfigurationException: 
java.lang.NullPointerException (Caused by java.lang.NullPointerException) 
(Caused by org.apache.commons.logging.LogConfigurationException: 
java.lang.NullPointerException (Caused by java.lang.NullPointerException))
         at 
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
         at 
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
         at 
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
         at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
         at org.apache.tomcat.util.compat.JdkCompat.<clinit>(JdkCompat.java:55)
         ... 10 more
Caused by: org.apache.commons.logging.LogConfigurationException: 
java.lang.NullPointerException (Caused by java.lang.NullPointerException)
         at 
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397)
         at 
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
         ... 14 more
Caused by: java.lang.NullPointerException
         at 
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:374)
         ... 15 more
<-- Wrapper Stopped


Does anyone know what I'm doing to cause this?

Thank you very much, all.

-Gil 

Re: [Wrapper-user] Disable auto-restart of JVM ...

[Michael 'b. S. <msc...@gi...>]

Hey Leif,

thanks for the quick answer. I'm impressed.

On Wed, 6 Oct 2004, Leif Mortenson wrote:

>wrapper.max_failed_invocations=1
>wrapper.successful_invocation_time=2147483647
err, uhm, yes

>Please explain what you are wanting to do.  A new property may be in order.
I just want to disable "automagic" restarting of a (maybe) killed JVM.
At the moment I dont know when such an "unexpected" event may occur, 
except when the JVM gets killed.

I just want to make sure that the thing doesnt get restarted, cause in my 
setup there are a few dependencies between services and if one particular 
service dies, some others needs to be restarted too.

Hm, I wonder if thats possible too?
Restarting another service through a trigger?

Greetings,
Michael

PS:
wrapper.on_failure.default=SHUTDOWN
just an idea ;)

-- 
 I am root. If you see me laughing, you better have a backup.

Re: [Wrapper-user] Disable auto-restart of JVM ...

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

Michael,
    It is currently not possible to completely disable the restart 
feature.  But you can get pretty
close.   By setting the following two properties, you limit the failed 
restart count to 1.  The
second property is to make sure that this counter does not get reset for 
a very long time, in
this case a little over 68 years.  That should be long enough.

wrapper.max_failed_invocations=1
wrapper.successful_invocation_time=2147483647

    The only problem with this solution may be that you will get the 
following message when
the JVM terminates abnormally:

wrapper  | JVM exited unexpectedly.
wrapper  | There were 1 failed launches in a row, each lasting less than 
2147483647 seconds.  Giving up.
wrapper  |   There may be a configuration problem: please check the logs.
wrapper  | <-- Wrapper Stopped

    A round number might be a little better for users to see:

wrapper.max_failed_invocations=1
wrapper.successful_invocation_time=2000000000

    Please explain what you are wanting to do.  A new property may be in 
order.

Cheers,
Leif


Michael 'buk' Scherer wrote:

>... when the JVM dies unexpectedly.
>Is that possible and if so, how?
>
>Thanks in advance,
>Michael
>
>  
>

[Wrapper-user] Disable auto-restart of JVM ...

[Michael 'b. S. <msc...@gi...>]

... when the JVM dies unexpectedly.
Is that possible and if so, how?

Thanks in advance,
Michael

-- 
 I am root. If you see me laughing, you better have a backup.

Re: [Wrapper-user] Timeout on heavy server startup

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

Ori,
Version 3.1.0 fixed a problem where the first ping timeout was effectively
hard coded to 30 seconds even though you set the wrapper.ping.timeout
property
to a larger value. From your output, I think this might be what you are
running
into.

Could you try using 3.1.0 and let me know how it works. If it is still
failing,
then I would need you to set the wrapper.debug=true property and post the
resulting wrapper.log file so I can tell you exactly how to resolve it.

Cheers,
Leif

Ori Argov wrote:

> Hi Lief,
>
> I'm using version 3.0.2 of the wrapper and it generally runs great.
>
> I'm using the JSW to start a heavy weblogic server which takes quite a
> while to start.
>
> I've implemented the necessary interface to control the startup of the
> NT service and
>
> Ask for waitHints as the server goes up. (Sometime it even maxes out
> on the windows timeout for service startup, but I've seen Oracle do
> that as well, so I guess this cannot be helped by the wrapper which
> uses the NT Service Manager like every other service).
>
> The issue I'm seeing is that rarely (not a specific machine or OS) the
> wrapper decides to timeout the server for no apparent reason.
>
> The startup timeout is set to 1200 seconds, and the ping timeout to
> 600 (yes, I know it's bad - but we are using the wrapper mainly for
> its service wrapping capabilities and not for JVM hanging detections)
> but the server timeouts after about 2 minutes.
>
> The waitHint is 15 seconds each time.
>
> Cpu.timeout is 10 sec.
>
> The error is this:
>
> ERROR | wrapper | 2004/09/26 09:08:48 | Startup failed: Timed out
> waiting for signal from JVM.
>
> ERROR | wrapper | 2004/09/26 09:08:48 | Java Virtual Machine did not
> exit on request, terminated
>
> STATUS | wrapper | 2004/09/26 09:08:54 | Launching a JVM...
>
> I have looked at the code and saw 2 places where this error is being
> issued: (in wrapper.c)
>
> Line 1592: this looks like in a JVM launch state, so we passed that
> already.
>
> Line 1638: this looks like the right one since we are in startup state.
>
> What is suspicious for me is that the same variable
> wrapperData->jStateTimeout is used to keep track of all timeout events.
>
> This field is being updated both on pings and waitHints. I know that
> it is always incremented from time(NULL) but could
>
> It be that the ping (which is smaller) overrides the startup waitHint
> on this variable and causes a timeout?
>
> I have not analyzed the code completely so forgive me if I've just
> said something silly.
>
> Any ideas on how to pinpoint this problem? Which prints should I add
> that will help me analyze the error next time I see it?
>
> Thanks,
>
> Ori
>

Re: [Wrapper-user] 100% CPU Usage Issue with File Logging On and Console Off

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

Gil,
    I did some testing with a JVM that basically just thrashes output to 
the console, and the
Wrapper process does indeed appear to be the bottleneck in this case.   
This is caused by
the way the Wrapper is currently logging the output to its log file.   
It is only an issue when
there is such very large quantities of console output.  I'll take a look 
at improving this
performance for the next release.   3.1.2 is currently going through the 
final release cycle.
So it will have to wait for the following version.

Cheers,
Leif


Gil Adam wrote:

> I've been trying to test the wrapper 3.1.1 to run Tomcat 5 as a 
> Windows NT Service.  Our application produces a lot of output to 
> STDOUT and when I run it under the Java Service Wrapper with logging 
> to a file turned on, the wrapper.exe takes up 100% CPU for a while 
> just to process the STDOUT output while the JVM java.exe takes up 
> nothing.
>
> I've tried checking to make sure that console logging is off by 
> setting the following:
>
> wrapper.ntservices.interactive=false
> wrapper.syslog.loglevel=NONE
> wrapper.console.format=
> wrapper.console.loglevel=NONE
>
> I currently have wrapper.logfile.loglevel=INFO
>
> Does anyone have any experience with this?  Other than this one thing, 
> the wrapper is working fantastically.
>
> -Gil

Re: [Wrapper-user] send email notification when JVM and/or wrapper goes down

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

Patrick,
Other users have asked for this as well and it is already on my list for 
a near-future release.
I went ahead and added a feature request for it as well.
https://sourceforge.net/tracker/index.php?func=detail&aid=1041150&group_id=39428&atid=425190

There is also an outstanding feature request to be able to execute 
arbitrary commands
in response to the same list of events:
https://sourceforge.net/tracker/index.php?func=detail&aid=837037&group_id=39428&atid=425190

Cheers,
Leif

Patrick Wyss wrote:

>i'm looking for a way to get an email notification when the JVM goes down
>(or can not be invoked) or doesn't receive any CPU for a certain time or
>anything else happens.
>
>is it maybe possible to hook in a commandline-command that is executed on
>certain events?
>or maybe an easy way to hook in a class which is called?
>
>or maybe there is an easy way to have a second logfile only getting the
>STATUS messages (which somehow could be piped to mail or something, if i
>would not have to work on windows servers ;-))
>
>thanks
>patrick
>  
>

Re: [Wrapper-user] Configuring log4j with a wrapper service

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

Alan,
    From what you posted, I don't see a problem with how your 
configuration.  But it is not
possible to tell without seeing your full wrapper.conf file and the 
debug output from the
startup of your application.

    Add the wrapper.debug=true property and look closely at the full 
java command that
the Wrapper generates and see if anything stands out.   If you don't see 
the problem, then
post that output back to this list and I'll take a look at it.

Cheers,
Leif

Alan Stewart wrote:

>
> I previously ran a command-line java app by specifying
>
> java -Dlog4j.configuration=log4j.daemon.properties -cp <class path 
> entries> <main class> ,  which worked fine.
>
> I've now configured the app to run as a service and have specified
>
> wrapper.java.additional.1=-Dlog4j.configuration=D:/Java/zurich/log4j.daemon.properties 
> in the wrapper.conf file, but log4j is not initializing correctly and 
> I get the following the wrapper.log:
>
> INFO   | jvm 1    | 2004/10/06 09:55:26 | Wrapper (Version 3.1.1) 
> http://wrapper.tanukisoftware.org
> INFO   | jvm 1    | 2004/10/06 09:55:26 |
> INFO   | jvm 1    | 2004/10/06 09:55:26 | log4j:WARN No appenders 
> could be found for logger (au.com.zurich.integration.MQMessageDaemon).
> INFO   | jvm 1    | 2004/10/06 09:55:26 | log4j:WARN Please initialize 
> the log4j system properly.
> STATUS | wrapper  | 2004/10/06 09:55:28 | <-- Wrapper Stopped
>
> I've tried putting the full path to the log4.daemon.properties file in 
> the configuration line above, but it till doesn't work.
>
> What am I doing wrong?
>
> Thanks
> Alan

[Wrapper-user] Configuring log4j with a wrapper service

[Alan S. <ala...@zu...>]

I previously ran a command-line java app by specifying 

java -Dlog4j.configuration=log4j.daemon.properties -cp <class path 
entries> <main class> ,  which worked fine.

I've now configured the app to run as a service and have specified 

wrapper.java.additional.1=-Dlog4j.configuration=D:/Java/zurich/log4j.daemon.properties 
in the wrapper.conf file, but log4j is not initializing correctly and I 
get the following the wrapper.log:

INFO   | jvm 1    | 2004/10/06 09:55:26 | Wrapper (Version 3.1.1) 
http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2004/10/06 09:55:26 | 
INFO   | jvm 1    | 2004/10/06 09:55:26 | log4j:WARN No appenders could be 
found for logger (au.com.zurich.integration.MQMessageDaemon).
INFO   | jvm 1    | 2004/10/06 09:55:26 | log4j:WARN Please initialize the 
log4j system properly.
STATUS | wrapper  | 2004/10/06 09:55:28 | <-- Wrapper Stopped

I've tried putting the full path to the log4.daemon.properties file in the 
configuration line above, but it till doesn't work.

What am I doing wrong?

Thanks
Alan


----
This email is intended for the named recipient only. It may contain information which is confidential, commercially sensitive, or copyright. If you are not the intended recipient you must not reproduce or distribute any part of the email, disclose its contents, or take any action in reliance. If you have received this email in error, please contact the sender and delete the message. It is your responsibility to scan this email and any attachments for viruses and other defects.
To the extent permitted by law, Zurich and its associates will not be liable for any loss or damage arising in any way from this communication including any file attachments. We may monitor email you send to us, either as a reply to this email or any email you send to us, to confirm our systems are protected and for compliance with company policies. Although we take reasonable precautions to protect the confidentiality of our email systems, we do not warrant the confidentiality or security of email or attachments we receive.

RE: [Wrapper-user] Win2k access denied on service start

[Ori A. <oa...@me...>]

Hi Leif,
One more thing about this issue:
I added the logon as service account to the conf file and the service
registers just fine.
Then I get the error you predicted when failing to have the user rights for
logon as service:

System error 1069 has occurred.
The service did not start due to a logon failure.

However, the specified user is registered with this right on the policies of
the local machine (As you instructed via control panel, actually it was
there before, I did not have to make any changes).

Only when I re-enter the password manually again in the "Log On" tab of the
service's properties window does the service start successfully.

Any idea how to make the password work without having to enter it manually?

Thanks,

Ori

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Ori Argov
Sent: Sunday, September 12, 2004 6:43 PM
To: 'wra...@li...'
Subject: RE: [Wrapper-user] Win2k access denied on service start

I think this is the cause by the way:
http://www.winnetmag.com/articles/index.cfm?articleid=39534

Ori

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Leif
Mortenson
Sent: Sunday, September 12, 2004 4:27 PM
To: wra...@li...
Subject: Re: [Wrapper-user] Win2k access denied on service start

Ori,
As it said in that first thread, this is usually a problem with the account
settings being incorrect. Are you getting the error when you try to install
the service? Or when you try to start it?
You are going to need to set the "Logon as Service" right for the user you
are trying to run as. This is not possible in Home editions of Windows.
Read over the following page:
http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-account.html

Cheers,
Leif

Ori Argov wrote:

> Hi,
>
> I'm also seeing the problem described here: (access denied when
> starting as NT service)
>
>
https://sourceforge.net/mailarchive/forum.php?thread_id=4186150&forum_id=119
48
>
<https://sourceforge.net/mailarchive/forum.php?thread_id=4186150&forum_id=11
948>
>
> https://sourceforge.net/mailarchive/message.php?msg_id=6261140
>
> My versions are as follows:
>
> Wrapper: 3.0.2
>
> OS: Win2k SP4
>
> JRE: 1.4.1_05
>
> Thanks,
>
> Ori
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________




-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

RE: [Wrapper-user] Timed out waiting for a signal from the JVM.

[Victor K. <Vic...@se...>]

> It may be that without that thread, your main method was 
> completing and the JVM was exiting before the Wrapper had
> a chance to time out?
I have my own non-daemon thread and the application was still
running, but swing was initialisng the awt event thread.

> At any rate, you will want to correct your properties.
Done, many thanks.


Regards,

Vic
--
Victor Kirk
Analyst
Serco Integrated Transport
Tel: +44 (0)1642 636894
Fax: +44 (0)1642 636701
--



> -----Original Message-----
> From: Leif Mortenson [mailto:le...@ta...]
> Sent: 30 September 2004 11:21
> To: wra...@li...
> Subject: Re: [Wrapper-user] Timed out waiting for a signal 
> from the JVM.
> 
> 
> Victor,
> 
> >This worked for me.  I also got it working the way it was
> >before.  I noticed one of my classes still refered to a 
> >debug utility which uses swing, I removed that and it
> >worked!  Maybe the awt event handler clashed with that for
> >the wrapper.
> >  
> >
> Strange, I am not sure why the Swing code would have made any 
> difference.
> 
> If Swing is initialized then it starts up a non-daemon thread 
> to handle 
> events.
> It may be that without that thread, your main method was 
> completing and 
> the JVM
> was exiting before the Wrapper had a chance to time out?
> 
> At any rate, you will want to correct your properties.
> 
> >Thanks for the help, it's certainly apperciated.
> >  
> >
> You are welcome.
> 
> Cheers,
> Leif
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on 
> ITManagersJournal
> Use IT products in your business? Tell us what you think of 
> them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to 
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 
  This message, including attachments, is intended only for the use by the
person(s) to whom it is addressed. It may contain information which is
privileged and confidential. Copying or use by anybody else is not
authorised. If you are not the intended recipient, please contact the sender
as soon as possible. The views expressed in this communication may not
necessarily be the views held by Serco Integrated Transport.

Re: [Wrapper-user] Timed out waiting for a signal from the JVM.

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

Victor,

>This worked for me.  I also got it working the way it was
>before.  I noticed one of my classes still refered to a 
>debug utility which uses swing, I removed that and it
>worked!  Maybe the awt event handler clashed with that for
>the wrapper.
>  
>
Strange, I am not sure why the Swing code would have made any difference.

If Swing is initialized then it starts up a non-daemon thread to handle 
events.
It may be that without that thread, your main method was completing and 
the JVM
was exiting before the Wrapper had a chance to time out?

At any rate, you will want to correct your properties.

>Thanks for the help, it's certainly apperciated.
>  
>
You are welcome.

Cheers,
Leif

Re: [Wrapper-user] Timed out waiting for a signal from the JVM.

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

Victor,
    Ok this failure mode has been removed for the 3.1.2 release.  If a 
java additional property
does not start with a - character then it is skipped and a warning is 
displayed in the log.
If a future user makes this mistake in 3.1.2, it should now be 
immediately obvious how to
resolve it.

Cheers,
Leif

Leif Mortenson wrote:

> Victor,
>    I see the problem now.   If you look closely t the command 
> generated by the Wrapper, you
> will that your main class is showing up before the classpath or 
> anything.   I was not paying
> close enough attention to the right things.
>
> Change:
> wrapper.java.additional.1=uk.co.mooed.calllogger.Logger
> wrapper.java.additional.2=call-logger.properties
>
> To:
> wrapper.app.parameter.1=uk.co.mooed.calllogger.Logger
> wrapper.app.parameter.2=call-logger.properties
>
> The way Java was being launched, your Logger class was the direct main 
> class, and
> everything else was being passed to your main method as arguments.   I 
> will try to think
> of a way that the Wrapper could have caught this for a future 
> version.  May just be
> as simple as making sure that the wrapper.java.additional.n properties 
> always start
> with a "-" character.
>
> Cheers,
> Leif

RE: [Wrapper-user] Timed out waiting for a signal from the JVM.

[Victor K. <Vic...@se...>]

Leif,

This worked for me.  I also got it working the way it was
before.  I noticed one of my classes still refered to a 
debug utility which uses swing, I removed that and it
worked!  Maybe the awt event handler clashed with that for
the wrapper.

Thanks for the help, it's certainly apperciated.

Regards,

Vic
--
Victor Kirk
Analyst
Serco Integrated Transport
Tel: +44 (0)1642 636894
Fax: +44 (0)1642 636701
--



> -----Original Message-----
> From: Leif Mortenson [mailto:le...@ta...]
> Sent: 30 September 2004 10:54
> To: wra...@li...
> Subject: Re: [Wrapper-user] Timed out waiting for a signal 
> from the JVM.
> 
> 
> Victor,
>     I see the problem now.   If you look closely t the 
> command generated 
> by the Wrapper, you
> will that your main class is showing up before the classpath or 
> anything.   I was not paying
> close enough attention to the right things.
> 
> Change:
> wrapper.java.additional.1=uk.co.mooed.calllogger.Logger
> wrapper.java.additional.2=call-logger.properties
> 
> To:
> wrapper.app.parameter.1=uk.co.mooed.calllogger.Logger
> wrapper.app.parameter.2=call-logger.properties
> 
> The way Java was being launched, your Logger class was the 
> direct main 
> class, and
> everything else was being passed to your main method as 
> arguments.   I 
> will try to think
> of a way that the Wrapper could have caught this for a future 
> version.  
> May just be
> as simple as making sure that the wrapper.java.additional.n 
> properties 
> always start
> with a "-" character.
> 
> Cheers,
> Leif
> 
> 
> Victor Kirk wrote:
> 
> >Thanks for the quick reply :-)
> >
> >  
> >
> >>    I do not see the Java side startup banner which shows that the 
> >>WrapperManager class is being correctly initialized.   In every case
> >>I have seen to date, this was caused by the user setting the main
> >>class directly to their application's main class.   
> >>    
> >>
> >My config definitaly uses WrapperSimpleApp.
> >
> >  
> >
> >>When this happens, the app will start normally, but the Java side
> >>of the Wrapper does not get initialized correctly and you get a
> >>timeout.
> >>    
> >>
> >
> >Are there any conditions that my app must obey which qould otherwise
> >prevent WrapperSimpleApp from replying to the ping? Would it be worth
> >making my app reply to the pings and use my main class as the
> >mainclass?
> >
> >  
> >
> >>could you please add the wrapper.debug=TRUE
> >>    
> >>
> >Heres my new config
> >
> >wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
> >wrapper.java.classpath.1=wrapper.jar
> >wrapper.java.classpath.2=call-logger.jar
> >wrapper.java.command=java.exe
> >wrapper.java.library.path.1=.
> >wrapper.java.additional.1=uk.co.mooed.calllogger.Logger
> >wrapper.java.additional.2=call-logger.properties
> >wrapper.ntservice.displayname=FROG Call Logger
> >wrapper.ntservice.name=FROGCallLogger
> >wrapper.ntservice.description=Logs calls
> >wrapper.ntservice.starttype=AUTO_START
> >wrapper.ntservice.interactive=false
> >wrapper.debug=TRUE
> >
> >
> >and heres the new output:
> >
> >wrapper  | --> Wrapper Started as Console
> >wrapper  | Using system timer.
> >wrapperp | server listening on port 32000.
> >wrapper  | Launching a JVM...
> >wrapper  | command: "c:\products\j2sdk\bin\java.exe"
> >uk.co.mooed.calllogger.Logger ca
> >ll-logger.properties -Djava.library.path="." -classpath
> >"wrapper.jar;call-logger.jar"
> > -Dwrapper.key="QZqr731c447p4Jlx" -Dwrapper.port=32000
> >-Dwrapper.debug="TRUE" -Dwrapp
> >er.use_system_time="TRUE" -Dwrapper.version="3.1.1"
> >-Dwrapper.native_library="wrapper
> >" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1
> >org.tanukisoftware.wrapper.WrapperSimp
> >leApp
> >wrapper  | JVM started (PID=3928)
> >jvm 1    | localhost: Logging in localhost:23 (attempt 1)
> >jvm 1    | localhost: Logged in
> >jvm 1    | localhost: Connecting to localhost:4001 (attempt 1)
> >jvm 1    | localhost: Connected
> >jvm 1    | localhost: Logging started
> >wrapper  | Startup failed: Timed out waiting for a signal 
> from the JVM.
> >wrapper  | JVM did not exit on request, terminated
> >wrapper  | JVM was only running for 29 seconds leading to a 
> failed restart
> >count of 1
> >.
> >wrapper  | Waiting 5 seconds before launching another JVM.
> >wrapper  | Launching a JVM...
> >...
> >  
> >
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on 
> ITManagersJournal
> Use IT products in your business? Tell us what you think of 
> them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to 
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 
  This message, including attachments, is intended only for the use by the
person(s) to whom it is addressed. It may contain information which is
privileged and confidential. Copying or use by anybody else is not
authorised. If you are not the intended recipient, please contact the sender
as soon as possible. The views expressed in this communication may not
necessarily be the views held by Serco Integrated Transport.

Re: [Wrapper-user] Timed out waiting for a signal from the JVM.

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

Victor,
    I see the problem now.   If you look closely t the command generated 
by the Wrapper, you
will that your main class is showing up before the classpath or 
anything.   I was not paying
close enough attention to the right things.

Change:
wrapper.java.additional.1=uk.co.mooed.calllogger.Logger
wrapper.java.additional.2=call-logger.properties

To:
wrapper.app.parameter.1=uk.co.mooed.calllogger.Logger
wrapper.app.parameter.2=call-logger.properties

The way Java was being launched, your Logger class was the direct main 
class, and
everything else was being passed to your main method as arguments.   I 
will try to think
of a way that the Wrapper could have caught this for a future version.  
May just be
as simple as making sure that the wrapper.java.additional.n properties 
always start
with a "-" character.

Cheers,
Leif


Victor Kirk wrote:

>Thanks for the quick reply :-)
>
>  
>
>>    I do not see the Java side startup banner which shows that the 
>>WrapperManager class is being correctly initialized.   In every case
>>I have seen to date, this was caused by the user setting the main
>>class directly to their application's main class.   
>>    
>>
>My config definitaly uses WrapperSimpleApp.
>
>  
>
>>When this happens, the app will start normally, but the Java side
>>of the Wrapper does not get initialized correctly and you get a
>>timeout.
>>    
>>
>
>Are there any conditions that my app must obey which qould otherwise
>prevent WrapperSimpleApp from replying to the ping? Would it be worth
>making my app reply to the pings and use my main class as the
>mainclass?
>
>  
>
>>could you please add the wrapper.debug=TRUE
>>    
>>
>Heres my new config
>
>wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
>wrapper.java.classpath.1=wrapper.jar
>wrapper.java.classpath.2=call-logger.jar
>wrapper.java.command=java.exe
>wrapper.java.library.path.1=.
>wrapper.java.additional.1=uk.co.mooed.calllogger.Logger
>wrapper.java.additional.2=call-logger.properties
>wrapper.ntservice.displayname=FROG Call Logger
>wrapper.ntservice.name=FROGCallLogger
>wrapper.ntservice.description=Logs calls
>wrapper.ntservice.starttype=AUTO_START
>wrapper.ntservice.interactive=false
>wrapper.debug=TRUE
>
>
>and heres the new output:
>
>wrapper  | --> Wrapper Started as Console
>wrapper  | Using system timer.
>wrapperp | server listening on port 32000.
>wrapper  | Launching a JVM...
>wrapper  | command: "c:\products\j2sdk\bin\java.exe"
>uk.co.mooed.calllogger.Logger ca
>ll-logger.properties -Djava.library.path="." -classpath
>"wrapper.jar;call-logger.jar"
> -Dwrapper.key="QZqr731c447p4Jlx" -Dwrapper.port=32000
>-Dwrapper.debug="TRUE" -Dwrapp
>er.use_system_time="TRUE" -Dwrapper.version="3.1.1"
>-Dwrapper.native_library="wrapper
>" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1
>org.tanukisoftware.wrapper.WrapperSimp
>leApp
>wrapper  | JVM started (PID=3928)
>jvm 1    | localhost: Logging in localhost:23 (attempt 1)
>jvm 1    | localhost: Logged in
>jvm 1    | localhost: Connecting to localhost:4001 (attempt 1)
>jvm 1    | localhost: Connected
>jvm 1    | localhost: Logging started
>wrapper  | Startup failed: Timed out waiting for a signal from the JVM.
>wrapper  | JVM did not exit on request, terminated
>wrapper  | JVM was only running for 29 seconds leading to a failed restart
>count of 1
>.
>wrapper  | Waiting 5 seconds before launching another JVM.
>wrapper  | Launching a JVM...
>...
>  
>

RE: [Wrapper-user] Timed out waiting for a signal from the JVM.

[Victor K. <Vic...@se...>]

Thanks for the quick reply :-)

>     I do not see the Java side startup banner which shows that the 
> WrapperManager class is being correctly initialized.   In every case
> I have seen to date, this was caused by the user setting the main
> class directly to their application's main class.   
My config definitaly uses WrapperSimpleApp.

> When this happens, the app will start normally, but the Java side
> of the Wrapper does not get initialized correctly and you get a
> timeout.

Are there any conditions that my app must obey which qould otherwise
prevent WrapperSimpleApp from replying to the ping? Would it be worth
making my app reply to the pings and use my main class as the
mainclass?

> could you please add the wrapper.debug=TRUE
Heres my new config

wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.java.classpath.1=wrapper.jar
wrapper.java.classpath.2=call-logger.jar
wrapper.java.command=java.exe
wrapper.java.library.path.1=.
wrapper.java.additional.1=uk.co.mooed.calllogger.Logger
wrapper.java.additional.2=call-logger.properties
wrapper.ntservice.displayname=FROG Call Logger
wrapper.ntservice.name=FROGCallLogger
wrapper.ntservice.description=Logs calls
wrapper.ntservice.starttype=AUTO_START
wrapper.ntservice.interactive=false
wrapper.debug=TRUE


and heres the new output:

wrapper  | --> Wrapper Started as Console
wrapper  | Using system timer.
wrapperp | server listening on port 32000.
wrapper  | Launching a JVM...
wrapper  | command: "c:\products\j2sdk\bin\java.exe"
uk.co.mooed.calllogger.Logger ca
ll-logger.properties -Djava.library.path="." -classpath
"wrapper.jar;call-logger.jar"
 -Dwrapper.key="QZqr731c447p4Jlx" -Dwrapper.port=32000
-Dwrapper.debug="TRUE" -Dwrapp
er.use_system_time="TRUE" -Dwrapper.version="3.1.1"
-Dwrapper.native_library="wrapper
" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1
org.tanukisoftware.wrapper.WrapperSimp
leApp
wrapper  | JVM started (PID=3928)
jvm 1    | localhost: Logging in localhost:23 (attempt 1)
jvm 1    | localhost: Logged in
jvm 1    | localhost: Connecting to localhost:4001 (attempt 1)
jvm 1    | localhost: Connected
jvm 1    | localhost: Logging started
wrapper  | Startup failed: Timed out waiting for a signal from the JVM.
wrapper  | JVM did not exit on request, terminated
wrapper  | JVM was only running for 29 seconds leading to a failed restart
count of 1
.
wrapper  | Waiting 5 seconds before launching another JVM.
wrapper  | Launching a JVM...
...


Regards,

Vic
--
Victor Kirk
Analyst
Serco Integrated Transport
Tel: +44 (0)1642 636894
Fax: +44 (0)1642 636701
--
  This message, including attachments, is intended only for the use by the
person(s) to whom it is addressed. It may contain information which is
privileged and confidential. Copying or use by anybody else is not
authorised. If you are not the intended recipient, please contact the sender
as soon as possible. The views expressed in this communication may not
necessarily be the views held by Serco Integrated Transport.