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

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

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

Victor,
    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.   
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.
    I added some code to version 3.1.0 which should make this mistake 
more obvious to
the user.   What version of the Wrapper are you running.

    That said, I am confused at this point looking at your configuration 
file.  It looks like
it should be working correctly.   I notice that you named it 
service.conf.  Is it possible
that another wrapper.conf file also exists?

    In any rate, could you please add the wrapper.debug=TRUE property to 
your
configuration file and repost with the resulting log output.   I am 
curious as to exactly
what is going on.

    One minor detail in your configuration.  It would work fine on 
Windows, but fail on
Unix if you ever tried to port your application:
This:
wrapper.java.additional.1=uk.co.mooed.calllogger.Logger 
call-logger.properties

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

Cheers,
Leif

Victor Kirk wrote:

>I'm having problems running my app as a service.  The application
>opens up a few sockets an logs data to file(s), nothing complicated
>to go wrong some I'm assuming it is a config proplem. If anyone
>can suggest anything I'd be grateful.
>
>
>The output below implies my application was started correctly
>but the wrapper thought it was frozen.  My application works
>fine when executed without the wrapper.
>
>$wrapper -c service.conf
>wrapper  | --> Wrapper Started as Console
>wrapper  | Launching a JVM...
>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.
>x5
>
>
>Heres my service.conf
>
>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
>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
>
>
>And here is my main
>
>    public static void main(String[] args) {
>        logger=new Logger();
>        logger.start();
>    }
>        
>Thanks for reading this,
>
>Vic
>  
>

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

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

I'm having problems running my app as a service.  The application
opens up a few sockets an logs data to file(s), nothing complicated
to go wrong some I'm assuming it is a config proplem. If anyone
can suggest anything I'd be grateful.


The output below implies my application was started correctly
but the wrapper thought it was frozen.  My application works
fine when executed without the wrapper.

$wrapper -c service.conf
wrapper  | --> Wrapper Started as Console
wrapper  | Launching a JVM...
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.
x5


Heres my service.conf

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
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


And here is my main

    public static void main(String[] args) {
        logger=new Logger();
        logger.start();
    }
        
Thanks for reading this,

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.

RE: [Wrapper-user] send email notification when JVM and/or wrappe r goes down

[Stuijt, J. <JS...@gt...>]

You could make your own watchdog-thread inside the JVM you want to know
about. This watchdog should tell another JVM on a regular basis: "I am still
alive!" If this is not done for some time, the other JVM could then send you
an email or do whatever. Both JVM's could even watch each other.

Have fun.

Met vriendelijke groet,
Johan Stuijt
Application Engineer
MES Expert Center
Doorkiesnummer: 075 612 79 34
 
GTI Industrie Noordwest bv
	Industrial Automation

	Houthavenkade 44  1506 PD Zaandam
	Postbus 1377  1500 AJ Zaandam
	tel.: 075 612 76 00   fax: 075 612 30 60
	www.gti-group.com/ia



-----Oorspronkelijk bericht-----
Van: Patrick Wyss [mailto:pat...@en...] 
Verzonden: woensdag 29 september 2004 17:18
Aan: wra...@li...
Onderwerp: [Wrapper-user] send email notification when JVM and/or wrapper
goes down

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



-------------------------------------------------------
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
================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en 
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht 
onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en 
de afzender direct te informeren door het bericht te retourneren. 
================================================
The information contained in this message may be confidential 
and is intended to be exclusively for the addressee. Should you 
receive this message unintentionally, please do not use the contents 
herein and notify the sender immediately by return e-mail.
================================================

RE: [Wrapper-user] How to get a thread dump in a JVM freeze incid ent?

[Stuijt, J. <JS...@gt...>]

You could have a look at JMX:
- in your app you start a JMX registry and a http service
- from a browser you can then connect to the http service and
  call a method from that is in the WrapperListener class.
  If you make available the method "threadDump()" then you can request
  A threaddump from your application.
  This will (of course) only work if your JVM is still "alive".

Google: "mx4j"

Good luck!

Met vriendelijke groet,
Johan Stuijt
Application Engineer
MES Expert Center
Doorkiesnummer: 075 612 79 34
 
GTI Industrie Noordwest bv
	Industrial Automation

	Houthavenkade 44  1506 PD Zaandam
	Postbus 1377  1500 AJ Zaandam
	tel.: 075 612 76 00   fax: 075 612 30 60
	www.gti-group.com/ia



-----Oorspronkelijk bericht-----
Van: Balaji KM [mailto:bal...@gm...] 
Verzonden: dinsdag 21 september 2004 11:43
Aan: wra...@li...
Onderwerp: [Wrapper-user] How to get a thread dump in a JVM freeze incident?

Dear All,

	I'm using java service wrapper 3.1.0 in my application which runs on
IBM JRE 1.3.0. When the application freezes, we are tring to get
thread dump using wrapperlistener's "D" command. We couldn't succeed
in getting a thread dump;no response from the wrapper service. We
observed that service was in hung state. Even in case of a freeze
incident, how should I configure the wrapper service to get a thread
dump.

I have listed my app configurations as follows:

wrapper.java.command=C:/IBM/Java13/jre/bin/java 
wrapper.java.mainclass=com.elind.service.fixgateway.common.FixMarketDataMain
Process
wrapper.max_failed_invocations=1 
wrapper.ping.timeout=0
wrapper.java.classpath.1=C:/Test/lib/wrapper.jar
wrapper.java.classpath.2=C:/Test/lib/FixGateway.jar
wrapper.java.classpath.3=C:/Test/lib/jgl3.1.0.jar
wrapper.java.classpath.4=C:/Test/lib/xerces.jar
wrapper.java.classpath.5=C:/Test/lib/xmlparserv2.jar
wrapper.java.library.path.1=C:/Test/lib
wrapper.console.format=PM
wrapper.console.loglevel=INFO
wrapper.logfile=../logs/wrapper.log
wrapper.logfile.format=LPTM
wrapper.logfile.loglevel=INFO
wrapper.logfile.maxsize=0
wrapper.logfile.maxfiles=0
wrapper.syslog.loglevel=NONE
wrapper.ntservice.name=FixTradingPartner
wrapper.ntservice.displayname=FixTradingPartner
wrapper.ntservice.description=FixTradingPartner
wrapper.ntservice.dependency.1=
wrapper.ntservice.starttype=AUTO_START
wrapper.ntservice.interactive=false
wrapper.ntservice.console=false
wrapper.working.dir=C:/Test/batch

Awaiting for you valuable suggestions.

Thanks in advance,

Warm Regards,
Balaji K M.


-------------------------------------------------------
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. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en 
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht 
onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en 
de afzender direct te informeren door het bericht te retourneren. 
================================================
The information contained in this message may be confidential 
and is intended to be exclusively for the addressee. Should you 
receive this message unintentionally, please do not use the contents 
herein and notify the sender immediately by return e-mail.
================================================

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

[Patrick W. <pat...@en...>]

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] java.lang.NoClassDefFoundError

[Lindsay S. <lgs...@bi...>]

That's it, all working .. Thanks very very much.

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Leif
Mortenson
Sent: Tuesday, 28 September 2004 1:54 PM
To: wra...@li...
Subject: Re: [Wrapper-user] java.lang.NoClassDefFoundError


Lindsay,
    Looking at your original classpath, it looks like your dcm.DipperDCM

is a raw class file
that is not included in a JAR.   It is being  found because you have the

"." directory included
on your classpath.

    Try adding that to the classpath in your wrapper.conf file:
wrapper.java.classpath.1=lib/wrapper.jar
wrapper.java.classpath.2=lib/comm.jar
wrapper.java.classpath.3=lib/log4j-1.2.8.jar
wrapper.java.classpath.4=lib/mysql-connector-java-3.0.14-production-bin.
jar
wrapper.java.classpath.5=.

    As an aside, you can also do this: wrapper.java.classpath.1=.
wrapper.java.classpath.2=lib/*.jar

Cheers,
Leif

Lindsay Steele wrote:

> I am getting a little frustrated with trying to get an application to
> run.  
>  
> My application happily runs with the following batch file:
>  
> java -cp
>
".;lib/comm.jar;lib/log4j-1.2.8.jar;lib/mysql-connector-java-3.0.14-prod
uction-bin.jar;lib/wrapper.jar" 
> dcm.DipperDCM 
>  
> When I run it with the wrapper I get the following.  This seems be
> what is always stopping it from running.
>  
> java.lang.NoClassDefFoundError: dcm/DipperDCM
>  
> my Wrapper properties are below.
>  
> It seems to find the conf file,  and logs to the correct place but
> cannot find the java class files to start the app.
>  
> root
> +---conf
> +---dcm
> +---lib
> L---log
>  
> The batch files and wrapper exe are in the root directory - dcm
> contains the class files and conf contains the conf files.
>  
>  I have searched the archives, FAQ's .. and read and read docs.  I
> have also tried many things, including.
>  
>  * Setting the full path to the java executable - tried many
> variations on this.
> * Setting a working directory - same result
> * Running the app in different modes - method 1 - and then I wrote 
> a wrapper class and tried to use method 3 - everything falls down when

> it will not find the class to start things.
> * Changing all sorts of settings in the conf file.
>  
> I am using Windows XP for development,  wrapper 3.11 and Sun's JDK 
> 1.4.2
>  
> Any ideas .. I am a loss.
>  
>  Thanks,
>  
>            Lindsay
>  
> #********************************************************************
> # Wrapper Properties
> #********************************************************************
> # Java Application wrapper.java.command=C:\j2sdk1.4.2\bin\java
>  
> # Java Main class.  This class must implement the WrapperListener
> interface
> #  or guarantee that the WrapperManager class is initialized.  Helper
> #  classes are provided to do this for you.  See the Integration
section
> #  of the documentation for details.
> #wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
> wrapper.java.mainclass=dcm.DipperDCM
>  
> # Java Classpath (include wrapper.jar)  Add class path elements as #  
> needed starting from 1 wrapper.java.classpath.1=lib/wrapper.jar
> wrapper.java.classpath.2=lib/comm.jar
> wrapper.java.classpath.3=lib/log4j-1.2.8.jar
>
wrapper.java.classpath.4=lib/mysql-connector-java-3.0.14-production-bin.
jar
>  
> wrapper.debug=true
>  
> wrapper.working.dir=\temp\run-win\
>  
> # Java Library Path (location of Wrapper.DLL or libwrapper.so) 
> wrapper.java.library.path.1=lib
>  
> # Java Additional Parameters
> #wrapper.java.additional.1=
>  
> # Initial Java Heap Size (in MB)
> #wrapper.java.initmemory=3
>  
> # Maximum Java Heap Size (in MB)
> #wrapper.java.maxmemory=64
>  
> # Application parameters.  Add parameters as needed starting from 1 
> wrapper.app.parameter.1=
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  




-------------------------------------------------------
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. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Daylight Savings Time and use_system_time=FALSE

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

Jeffrey,
    I am unclear on the nature of the "event" that you have scheduled?   
Is this a part
of your Java application?

    The Wrapper itself does not do anything with the system clock or 
control how the
JVM process sees the system clock.   No matter what the value of the 
use_system_time
property is, the JVM should see the system time exactly as if it was 
running standalone.

    The use_system_time property is used to control how the Wrapper 
process itself
handles timing internally.   By setting it to false, it uses internal 
"ticks" which is not as
accurate as the system time, but is much more resilient to high system 
loads and changes
in system time.   Neither method is directly visible to the Java 
application.  The tick
method simply makes the Wrapper much more stable under load and makes it 
very
unlikely that a JVM will be restarted due to such loads.

If you want to see what time the Wrapper thinks it is as you change the 
time.  Set the
wrapper.debug=true  property and then watch the wrapper.log file across 
the system
time change.

Cheers,
Leif

Jeffrey R. Ostrowski wrote:

>I"m using v.3.1.1.  I've set use_system_time=FALSE in 
>my .conf file.  When I change my computer settings between 
>EDT and EST (and vice versa), there is no apparent change 
>when my event runs.  For example, if I have an event 
>scheduled for 2:58PM and the clock changes from 3:57PM EDT 
>to 2:57PM EST on my machine, the event is not triggered at 
>the new time of 2:58PM.
>
>Is there a parameter that I'm missing???
>  
>

Re: [Wrapper-user] java.lang.NoClassDefFoundError

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

Lindsay,
    Looking at your original classpath, it looks like your dcm.DipperDCM 
is a raw class file
that is not included in a JAR.   It is being  found because you have the 
"." directory included
on your classpath.

    Try adding that to the classpath in your wrapper.conf file:
wrapper.java.classpath.1=lib/wrapper.jar
wrapper.java.classpath.2=lib/comm.jar
wrapper.java.classpath.3=lib/log4j-1.2.8.jar
wrapper.java.classpath.4=lib/mysql-connector-java-3.0.14-production-bin.jar
wrapper.java.classpath.5=.

    As an aside, you can also do this:
wrapper.java.classpath.1=.
wrapper.java.classpath.2=lib/*.jar

Cheers,
Leif

Lindsay Steele wrote:

> I am getting a little frustrated with trying to get an application to 
> run.  
>  
> My application happily runs with the following batch file:
>  
> java -cp 
> ".;lib/comm.jar;lib/log4j-1.2.8.jar;lib/mysql-connector-java-3.0.14-production-bin.jar;lib/wrapper.jar" 
> dcm.DipperDCM 
>  
> When I run it with the wrapper I get the following.  This seems be 
> what is always stopping it from running.
>  
> java.lang.NoClassDefFoundError: dcm/DipperDCM
>  
> my Wrapper properties are below.
>  
> It seems to find the conf file,  and logs to the correct place but 
> cannot find the java class files to start the app.
>  
> root
> ├───conf
> ├───dcm
> ├───lib
> └───log
>  
> The batch files and wrapper exe are in the root directory - dcm 
> contains the class files and conf contains the conf files.
>  
>  I have searched the archives, FAQ's .. and read and read docs.  I 
> have also tried many things, including.
>  
>  * Setting the full path to the java executable - tried many 
> variations on this.
> * Setting a working directory - same result
> * Running the app in different modes - method 1 - and then I wrote 
> a wrapper class and tried to use method 3 - everything falls down when 
> it will not find the class to start things.
> * Changing all sorts of settings in the conf file.
>  
> I am using Windows XP for development,  wrapper 3.11 and Sun's JDK 1.4.2 
>  
> Any ideas .. I am a loss.
>  
>  Thanks,
>  
>            Lindsay
>  
> #********************************************************************
> # Wrapper Properties
> #********************************************************************
> # Java Application
> wrapper.java.command=C:\j2sdk1.4.2\bin\java
>  
> # Java Main class.  This class must implement the WrapperListener 
> interface
> #  or guarantee that the WrapperManager class is initialized.  Helper
> #  classes are provided to do this for you.  See the Integration section
> #  of the documentation for details.
> #wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
> wrapper.java.mainclass=dcm.DipperDCM
>  
> # Java Classpath (include wrapper.jar)  Add class path elements as
> #  needed starting from 1
> wrapper.java.classpath.1=lib/wrapper.jar
> wrapper.java.classpath.2=lib/comm.jar
> wrapper.java.classpath.3=lib/log4j-1.2.8.jar
> wrapper.java.classpath.4=lib/mysql-connector-java-3.0.14-production-bin.jar
>  
> wrapper.debug=true
>  
> wrapper.working.dir=\temp\run-win\
>  
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=lib
>  
> # Java Additional Parameters
> #wrapper.java.additional.1=
>  
> # Initial Java Heap Size (in MB)
> #wrapper.java.initmemory=3
>  
> # Maximum Java Heap Size (in MB)
> #wrapper.java.maxmemory=64
>  
> # Application parameters.  Add parameters as needed starting from 1
> wrapper.app.parameter.1=
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  

Re: [Wrapper-user] java.lang.NoClassDefFoundError

[Paul C. <cas...@au...>]

DQoNCg0KDQpIaSBMaW5kc2F5LA0KDQpHb2luZyBieSB0aGUgcGFja2FnZSBuYW1lcyBvZiB5b3Vy
IGphciBmaWxlcyBpbiB0aGUgY2xhc3NwYXRoLCBJJ20gZ3Vlc3NpbmcNCnRoYXQgdGhlIGRjbSBw
YWNrYWdlIChjb250YWluaW5nIHRoZSBkY20uRGlwcGVyRENNIGNsYXNzKSBpcyBpbiB0aGUgY3Vy
cmVudA0KZGlyZWN0b3J5IHdoZW4gdGhlIGJhdGNoIGZpbGUgcnVucy4gIElmIHRoaXMgaXMgY29y
cmVjdCwgaGF2ZSB5b3UgYWRkZWQNCnRoYXQgZGlyZWN0b3J5IHRvIHRoZSB3cmFwcGVyIGNvbmYg
ZmlsZT8NCg0KUmVnYXJkcywNCg0KUGF1bCBDYXNhbm92YQ0KDQoNCg0KICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgDQogICAgICAgICAgICAgIkxpbmRzYXkgU3RlZWxlIiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICANCiAgICAgICAgICAgICA8bHN0ZWVsZUBpaW5ldC5uZSAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KICAgICAgICAgICAg
IHQuYXU+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgVG8gDQogICAgICAgICAgICAgU2VudCBieTogICAgICAgICAgICAgICAgICA8d3JhcHBlci11
c2VyQGxpc3RzLnNvdXJjZWZvcmdlLm5ldCANCiAgICAgICAgICAgICB3cmFwcGVyLXVzZXItYWRt
aSAgICAgICAgID4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KICAgICAgICAg
ICAgIG5AbGlzdHMuc291cmNlZm9yICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgY2MgDQogICAgICAgICAgICAgZ2UubmV0ICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBTdWJqZWN0IA0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgW1dyYXBwZXItdXNlcl0gICAgICAgICAg
ICAgICAgICAgICAgDQogICAgICAgICAgICAgMjgvMDkvMjAwNCAxMjozNCAgICAgICAgICBqYXZh
LmxhbmcuTm9DbGFzc0RlZkZvdW5kRXJyb3IgICAgICANCiAgICAgICAgICAgICBQTSAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCiAgICAgICAgICAgICBQbGVhc2Ug
cmVzcG9uZCB0byAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0K
ICAgICAgICAgICAgICAgd3JhcHBlci11c2VyICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IA0KDQoNCg0KDQpJIGFtIGdldHRpbmcgYSBsaXR0bGUgZnJ1c3RyYXRlZCB3aXRoIHRyeWluZyB0
byBnZXQgYW4gYXBwbGljYXRpb24gdG8gcnVuLg0KDQpNeSBhcHBsaWNhdGlvbiBoYXBwaWx5IHJ1
bnMgd2l0aCB0aGUgZm9sbG93aW5nIGJhdGNoIGZpbGU6DQoNCmphdmEgLWNwDQoiLjtsaWIvY29t
bS5qYXI7bGliL2xvZzRqLTEuMi44LmphcjtsaWIvbXlzcWwtY29ubmVjdG9yLWphdmEtMy4wLjE0
LXByb2R1Y3Rpb24tYmluLmphcjtsaWIvd3JhcHBlci5qYXIiDQogZGNtLkRpcHBlckRDTQ0KDQpX
aGVuIEkgcnVuIGl0IHdpdGggdGhlIHdyYXBwZXIgSSBnZXQgdGhlIGZvbGxvd2luZy4gIFRoaXMg
c2VlbXMgYmUgd2hhdCBpcw0KYWx3YXlzIHN0b3BwaW5nIGl0IGZyb20gcnVubmluZy4NCg0KamF2
YS5sYW5nLk5vQ2xhc3NEZWZGb3VuZEVycm9yOiBkY20vRGlwcGVyRENNDQoNCm15IFdyYXBwZXIg
cHJvcGVydGllcyBhcmUgYmVsb3cuDQoNCkl0IHNlZW1zIHRvIGZpbmQgdGhlIGNvbmYgZmlsZSwg
IGFuZCBsb2dzIHRvIHRoZSBjb3JyZWN0IHBsYWNlIGJ1dCBjYW5ub3QNCmZpbmQgdGhlIGphdmEg
Y2xhc3MgZmlsZXMgdG8gc3RhcnQgdGhlIGFwcC4NCg0Kcm9vdA0KhoCAgGNvbmYNCoaAgIBkY20N
CoaAgIBsaWINCoSAgIBsb2cNCg0KVGhlIGJhdGNoIGZpbGVzIGFuZCB3cmFwcGVyIGV4ZSBhcmUg
aW4gdGhlIHJvb3QgZGlyZWN0b3J5IC0gZGNtIGNvbnRhaW5zDQp0aGUgY2xhc3MgZmlsZXMgYW5k
IGNvbmYgY29udGFpbnMgdGhlIGNvbmYgZmlsZXMuDQoNCiBJIGhhdmUgc2VhcmNoZWQgdGhlIGFy
Y2hpdmVzLCBGQVEncyAuLiBhbmQgcmVhZCBhbmQgcmVhZCBkb2NzLiAgSSBoYXZlDQphbHNvIHRy
aWVkIG1hbnkgdGhpbmdzLCBpbmNsdWRpbmcuDQoNCiAqIFNldHRpbmcgdGhlIGZ1bGwgcGF0aCB0
byB0aGUgamF2YSBleGVjdXRhYmxlIC0gdHJpZWQgbWFueSB2YXJpYXRpb25zIG9uDQp0aGlzLg0K
KiBTZXR0aW5nIGEgd29ya2luZyBkaXJlY3RvcnkgLSBzYW1lIHJlc3VsdA0KKiBSdW5uaW5nIHRo
ZSBhcHAgaW4gZGlmZmVyZW50IG1vZGVzIC0gbWV0aG9kIDEgLSBhbmQgdGhlbiBJIHdyb3RlIGEN
CndyYXBwZXIgY2xhc3MgYW5kIHRyaWVkIHRvIHVzZSBtZXRob2QgMyAtIGV2ZXJ5dGhpbmcgZmFs
bHMgZG93biB3aGVuIGl0DQp3aWxsIG5vdCBmaW5kIHRoZSBjbGFzcyB0byBzdGFydCB0aGluZ3Mu
DQoqIENoYW5naW5nIGFsbCBzb3J0cyBvZiBzZXR0aW5ncyBpbiB0aGUgY29uZiBmaWxlLg0KDQpJ
IGFtIHVzaW5nIFdpbmRvd3MgWFAgZm9yIGRldmVsb3BtZW50LCAgd3JhcHBlciAzLjExIGFuZCBT
dW4ncyBKREsgMS40LjINCg0KQW55IGlkZWFzIC4uIEkgYW0gYSBsb3NzLg0KDQogVGhhbmtzLA0K
DQogICAgICAgICAgIExpbmRzYXkNCg0KIyoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqDQojIFdyYXBwZXIgUHJvcGVydGll
cw0KIyoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqDQojIEphdmEgQXBwbGljYXRpb24NCndyYXBwZXIuamF2YS5jb21tYW5k
PUM6XGoyc2RrMS40LjJcYmluXGphdmENCg0KIyBKYXZhIE1haW4gY2xhc3MuICBUaGlzIGNsYXNz
IG11c3QgaW1wbGVtZW50IHRoZSBXcmFwcGVyTGlzdGVuZXIgaW50ZXJmYWNlDQojICBvciBndWFy
YW50ZWUgdGhhdCB0aGUgV3JhcHBlck1hbmFnZXIgY2xhc3MgaXMgaW5pdGlhbGl6ZWQuICBIZWxw
ZXINCiMgIGNsYXNzZXMgYXJlIHByb3ZpZGVkIHRvIGRvIHRoaXMgZm9yIHlvdS4gIFNlZSB0aGUg
SW50ZWdyYXRpb24gc2VjdGlvbg0KIyAgb2YgdGhlIGRvY3VtZW50YXRpb24gZm9yIGRldGFpbHMu
DQojd3JhcHBlci5qYXZhLm1haW5jbGFzcz1vcmcudGFudWtpc29mdHdhcmUud3JhcHBlci5XcmFw
cGVyU2ltcGxlQXBwDQp3cmFwcGVyLmphdmEubWFpbmNsYXNzPWRjbS5EaXBwZXJEQ00NCg0KIyBK
YXZhIENsYXNzcGF0aCAoaW5jbHVkZSB3cmFwcGVyLmphcikgIEFkZCBjbGFzcyBwYXRoIGVsZW1l
bnRzIGFzDQojICBuZWVkZWQgc3RhcnRpbmcgZnJvbSAxDQp3cmFwcGVyLmphdmEuY2xhc3NwYXRo
LjE9bGliL3dyYXBwZXIuamFyDQp3cmFwcGVyLmphdmEuY2xhc3NwYXRoLjI9bGliL2NvbW0uamFy
DQp3cmFwcGVyLmphdmEuY2xhc3NwYXRoLjM9bGliL2xvZzRqLTEuMi44Lmphcg0Kd3JhcHBlci5q
YXZhLmNsYXNzcGF0aC40PWxpYi9teXNxbC1jb25uZWN0b3ItamF2YS0zLjAuMTQtcHJvZHVjdGlv
bi1iaW4uamFyDQoNCndyYXBwZXIuZGVidWc9dHJ1ZQ0KDQp3cmFwcGVyLndvcmtpbmcuZGlyPVx0
ZW1wXHJ1bi13aW5cDQoNCiMgSmF2YSBMaWJyYXJ5IFBhdGggKGxvY2F0aW9uIG9mIFdyYXBwZXIu
RExMIG9yIGxpYndyYXBwZXIuc28pDQp3cmFwcGVyLmphdmEubGlicmFyeS5wYXRoLjE9bGliDQoN
CiMgSmF2YSBBZGRpdGlvbmFsIFBhcmFtZXRlcnMNCiN3cmFwcGVyLmphdmEuYWRkaXRpb25hbC4x
PQ0KDQojIEluaXRpYWwgSmF2YSBIZWFwIFNpemUgKGluIE1CKQ0KI3dyYXBwZXIuamF2YS5pbml0
bWVtb3J5PTMNCg0KIyBNYXhpbXVtIEphdmEgSGVhcCBTaXplIChpbiBNQikNCiN3cmFwcGVyLmph
dmEubWF4bWVtb3J5PTY0DQoNCiMgQXBwbGljYXRpb24gcGFyYW1ldGVycy4gIEFkZCBwYXJhbWV0
ZXJzIGFzIG5lZWRlZCBzdGFydGluZyBmcm9tIDENCndyYXBwZXIuYXBwLnBhcmFtZXRlci4xPQ0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg==

[Wrapper-user] java.lang.NoClassDefFoundError

[Lindsay S. <ls...@ii...>]

I am getting a little frustrated with trying to get an application to
run.   
 
My application happily runs with the following batch file:
 
java -cp
".;lib/comm.jar;lib/log4j-1.2.8.jar;lib/mysql-connector-java-3.0.14-prod
uction-bin.jar;lib/wrapper.jar" dcm.DipperDCM 
 
When I run it with the wrapper I get the following.  This seems be what
is always stopping it from running.
 
java.lang.NoClassDefFoundError: dcm/DipperDCM
 
my Wrapper properties are below.
 
It seems to find the conf file,  and logs to the correct place but
cannot find the java class files to start the app.
 
root
+---conf
+---dcm
+---lib
L---log
 
The batch files and wrapper exe are in the root directory - dcm contains
the class files and conf contains the conf files.
 
 I have searched the archives, FAQ's .. and read and read docs.  I have
also tried many things, including.
 
 * Setting the full path to the java executable - tried many variations
on this.
* Setting a working directory - same result
* Running the app in different modes - method 1 - and then I wrote a
wrapper class and tried to use method 3 - everything falls down when it
will not find the class to start things.
* Changing all sorts of settings in the conf file.
 
I am using Windows XP for development,  wrapper 3.11 and Sun's JDK 1.4.2

 
Any ideas .. I am a loss.
 
 Thanks,
 
           Lindsay
 
#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=C:\j2sdk1.4.2\bin\java
 
# Java Main class.  This class must implement the WrapperListener
interface
#  or guarantee that the WrapperManager class is initialized.  Helper
#  classes are provided to do this for you.  See the Integration section
#  of the documentation for details.
#wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.java.mainclass=dcm.DipperDCM
 
# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=lib/wrapper.jar
wrapper.java.classpath.2=lib/comm.jar
wrapper.java.classpath.3=lib/log4j-1.2.8.jar
wrapper.java.classpath.4=lib/mysql-connector-java-3.0.14-production-bin.
jar
 
wrapper.debug=true
 
wrapper.working.dir=\temp\run-win\
 
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=lib
 
# Java Additional Parameters
#wrapper.java.additional.1=
 
# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3
 
# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=64
 
# Application parameters.  Add parameters as needed starting from 1
wrapper.app.parameter.1=

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

[Wrapper-user] Daylight Savings Time and use_system_time=FALSE

[Jeffrey R. O. <af...@wa...>]

I"m using v.3.1.1.  I've set use_system_time=FALSE in 
my .conf file.  When I change my computer settings between 
EDT and EST (and vice versa), there is no apparent change 
when my event runs.  For example, if I have an event 
scheduled for 2:58PM and the clock changes from 3:57PM EDT 
to 2:57PM EST on my machine, the event is not triggered at 
the new time of 2:58PM.

Is there a parameter that I'm missing???

[Wrapper-user] Timeout on heavy server startup

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

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 

 

 

 



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

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

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

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


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

Re: [Wrapper-user] wrapper.log

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

Teikei,
Currently, the Wrapper captures all output from the JVM process.   This 
includes output from
the JVM ouput via System.out or System.err.  But it also includes low 
level output from the
JVM itself like crash output, and thread dumps.  The later can not be 
captured by java based
logging tools.

All of the above output from the JVM is logged by the Wrapper at a log 
level of INFO.   It
is not currently possible to filter System.out and System.err at 
different log levels.

If you need to have finer control of the Java output, then I suggest 
using a logging tool inside
the JVM.   That is what I do and then still sent it to standard out.  
This lets me have fine
control over Java logging, while still being able to have all log output 
in the wrapper.log file.

Cheers,
Leif


v103 wrote:

>I have one simple question.
>
>Do every standard outputs, standard error outputs from JVM get picked by JSW
>and written down to wrapper.log(as default setting).  Controlling
>wrapper.logfile.loglevel property has any effect on controlling these
>outputs?
>
>thanks
>
>Taikei Matsushita
>  
>

[Wrapper-user] wrapper.log

[v103 <v1...@za...>]

I have one simple question.

Do every standard outputs, standard error outputs from JVM get picked by JSW
and written down to wrapper.log(as default setting).  Controlling
wrapper.logfile.loglevel property has any effect on controlling these
outputs?

thanks

Taikei Matsushita

Re: [Wrapper-user] JVM process exited with a code of -1073741571

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

Vadim,
    Also, if it is fairly easy for you to reproduce this problem, I 
would appreciate it if you could
try out this new candidate for the 3.1.2 release.   When the JVM 
crashes, it should now display
an error message with the exception name even if debug output is disabled.

http://wrapper.tanukisoftware.org/tmp/3.1.2-e/wrapper_win32_3.1.2-e.zip

Cheers,
Leif

Leif Mortenson wrote:

> Vadim,
>    Doing some research, I figured out that the function call I am 
> making to get the process exit
> code is capable of returning the value of an uncaught exception that 
> killed the process.   I will
> modify the Wrapper for the 3.1.2 release to display more useful 
> information in this case.
>
>    In your case, the exception being thrown was 
> STATUS_STACK_OVERFLOW.   This is
> a low level error in the JVM implementation and not a Java level stack 
> overflow.  Try looking
> through the Sun bug database, or trying a newer JVM version.  It may 
> have been fixed.
> This was the kind of thing that the Wrapper was originally built for. :-)
>
> Cheers,
> Leif
>
> Vadim Punski wrote:
>
>> Hi!
>> I've found a lot of posts started with " JVM process exited with a 
>> code", but no one with such a strange exit code.
>> This could be reproduced by clicking 10-20 times on some button of 
>> the application in the browser.
>> During button pressing the system not overloaded at all.
>> The same thing works perfect during simple jvm execution w/o java 
>> wrapper.
>> All timings and timeouts were extended up to 3-4 minutes, and pinging 
>> works perfect.
>> wrapper.conf configuration added after log messages.
>>
>> Any ideas ?!
>>
>> Best Regards,
>>    Vadim
>>
>> DEBUG  | wrapper  | 2004/09/22 18:22:40 | JVM process exited with a 
>> code of -1073741571, setting the wrapper exit code to -1073741571.
>> ERROR  | wrapper  | 2004/09/22 18:22:40 | JVM exited unexpectedly.
>

Re: [Wrapper-user] JVM process exited with a code of -1073741571

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

Vadim,
    Doing some research, I figured out that the function call I am 
making to get the process exit
code is capable of returning the value of an uncaught exception that 
killed the process.   I will
modify the Wrapper for the 3.1.2 release to display more useful 
information in this case.

    In your case, the exception being thrown was 
STATUS_STACK_OVERFLOW.   This is
a low level error in the JVM implementation and not a Java level stack 
overflow.  Try looking
through the Sun bug database, or trying a newer JVM version.  It may 
have been fixed.
This was the kind of thing that the Wrapper was originally built for. :-)

Cheers,
Leif

Vadim Punski wrote:

> Hi!
> I've found a lot of posts started with " JVM process exited with a 
> code", but no one with such a strange exit code.
> This could be reproduced by clicking 10-20 times on some button of the 
> application in the browser.
> During button pressing the system not overloaded at all.
> The same thing works perfect during simple jvm execution w/o java 
> wrapper.
> All timings and timeouts were extended up to 3-4 minutes, and pinging 
> works perfect.
> wrapper.conf configuration added after log messages.
>
> Any ideas ?!
>
> Best Regards,
>    Vadim
>
> DEBUG  | wrapper  | 2004/09/22 18:22:40 | JVM process exited with a 
> code of -1073741571, setting the wrapper exit code to -1073741571.
> ERROR  | wrapper  | 2004/09/22 18:22:40 | JVM exited unexpectedly.

Re: [Wrapper-user] How to get a thread dump in a JVM freeze incident?

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

Balaji,
    I was unclear about what you mean by the "D" command.   The 
WrapperListener does
not provide such a function.   The Wrapper does include a 
WrapperActionServer class
which lets you connect the the JVM using Telnet and do things like 
request thread dumps
or restarts.   This class is not enabled by default, you have to write a 
few lines of code to
enable it.  See the javadocs.
    Not that the action server will also not work if the JVM is truly hung.

    How the Wrapper handles freezes, depends on what you mean my an 
"application freeze".
If it is the entire JVM which freezes then the Wrapper will 
automatically restart the JVM.  If
this happens, it is not possible to get a thread dump because the JVM is 
usually too far gone
at that point.

    If your application is frozen, but the JVM is still functioning 
correctly then the Wrapper
will not usually be able to detect this.  This is because the Wrapper's 
core threads are still
functioning correctly.

    To get a thread dump in the second case, a system administrator will 
need to request it
manually and then restart the JVM.   You can do this manually for any 
JVM by pressing
CTRL-BREAK on windows or passing the 'dump' command to the wrapper shell 
script
on UNIX.    It is also possible to use the above WrapperActionServer.
   
    If it is possible for your application to detect that it is no 
longer functioning correctly,
then you can add the following code.   It will request a thread dump and 
then restart
the JVM.

WrapperManager.requestThreadDump();
WrapperManager.restart();

Cheers,
Leif

Balaji KM wrote:

>Dear All,
>
>	I'm using java service wrapper 3.1.0 in my application which runs on
>IBM JRE 1.3.0. When the application freezes, we are tring to get
>thread dump using wrapperlistener's "D" command. We couldn't succeed
>in getting a thread dump;no response from the wrapper service. We
>observed that service was in hung state. Even in case of a freeze
>incident, how should I configure the wrapper service to get a thread
>dump.
>
>I have listed my app configurations as follows:
>
>wrapper.java.command=C:/IBM/Java13/jre/bin/java 
>wrapper.java.mainclass=com.elind.service.fixgateway.common.FixMarketDataMainProcess
>wrapper.max_failed_invocations=1 
>wrapper.ping.timeout=0
>wrapper.java.classpath.1=C:/Test/lib/wrapper.jar
>wrapper.java.classpath.2=C:/Test/lib/FixGateway.jar
>wrapper.java.classpath.3=C:/Test/lib/jgl3.1.0.jar
>wrapper.java.classpath.4=C:/Test/lib/xerces.jar
>wrapper.java.classpath.5=C:/Test/lib/xmlparserv2.jar
>wrapper.java.library.path.1=C:/Test/lib
>wrapper.console.format=PM
>wrapper.console.loglevel=INFO
>wrapper.logfile=../logs/wrapper.log
>wrapper.logfile.format=LPTM
>wrapper.logfile.loglevel=INFO
>wrapper.logfile.maxsize=0
>wrapper.logfile.maxfiles=0
>wrapper.syslog.loglevel=NONE
>wrapper.ntservice.name=FixTradingPartner
>wrapper.ntservice.displayname=FixTradingPartner
>wrapper.ntservice.description=FixTradingPartner
>wrapper.ntservice.dependency.1=
>wrapper.ntservice.starttype=AUTO_START
>wrapper.ntservice.interactive=false
>wrapper.ntservice.console=false
>wrapper.working.dir=C:/Test/batch
>
>Awaiting for you valuable suggestions.
>
>Thanks in advance,
>
>Warm Regards,
>Balaji K M.
>  
>

[Wrapper-user] JVM process exited with a code of -1073741571

[Vadim P. <va...@2t...>]

Hi!
I've found a lot of posts started with " JVM process exited with a 
code", but no one with such a strange exit code.
This could be reproduced by clicking 10-20 times on some button of the 
application in the browser.
During button pressing the system not overloaded at all.
The same thing works perfect during simple jvm execution w/o java wrapper.
All timings and timeouts were extended up to 3-4 minutes, and pinging 
works perfect.
wrapper.conf configuration added after log messages.

Any ideas ?!

Best Regards,
    Vadim

DEBUG  | wrapper  | 2004/09/22 18:22:40 | JVM process exited with a code 
of -1073741571, setting the wrapper exit code to -1073741571.
ERROR  | wrapper  | 2004/09/22 18:22:40 | JVM exited unexpectedly.
DEBUG  | wrapper  | 2004/09/22 18:22:41 | Waiting 5 seconds before 
launching another JVM.
STATUS | wrapper  | 2004/09/22 18:22:45 | Launching a JVM...
DEBUG  | wrapper  | 2004/09/22 18:22:45 | command: 
"c:\j2sdk1.4.2_02\bin\java" -server -XX:NewSize=400m -XX:PermSize=40m 
-Xms512m -Xmx512m -Xloggc:C:\jboss-3.2.2\server\default\log\GC.log 
-Dprogram.name=Wrapper -Xms512m -Xmx512m 
-Djava.library.path="C:/jboss-3.2.2/lib;;C:/Eldat Common Path;" 
-classpath 
"C:/jboss-3.2.2/lib/wrapper.jar;C:/j2sdk1.4.2_02/lib/tools.jar;C:/jboss-3.2.2/bin/run.jar" 
-Dwrapper.key="rZuk3O5PJPe7hdQ1" -Dwrapper.port=32000 
-Dwrapper.debug="TRUE" -Dwrapper.use_system_time="TRUE" 
-Dwrapper.version="3.1.1" -Dwrapper.native_library="wrapper" 
-Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="50" -Dwrapper.jvmid=2 
org.tanukisoftware.wrapper.WrapperSimpleApp org.jboss.Main -c default
DEBUG  | wrapper  | 2004/09/22 18:22:45 | JVM started (PID=16856)
INFO   | jvm 2    | 2004/09/22 18:22:48 | WrapperManager class 
initialized by thread: main  Using classloader: 
sun.misc.Launcher$AppClassLoader@1ff5ea7
INFO   | jvm 2    | 2004/09/22 18:22:48 | Wrapper Manager: JVM #2
INFO   | jvm 2    | 2004/09/22 18:22:48 | Wrapper Manager: Registering 
shutdown hook
INFO   | jvm 2    | 2004/09/22 18:22:48 | Wrapper Manager: Using wrapper
INFO   | jvm 2    | 2004/09/22 18:22:48 | Loaded native library: wrapper.dll
INFO   | jvm 2    | 2004/09/22 18:22:48 | Calling native initialization 
method.
INFO   | jvm 2    | 2004/09/22 18:22:48 | Initializing WrapperManager 
native library.
INFO   | jvm 2    | 2004/09/22 18:22:48 | Java Executable: 
c:\j2sdk1.4.2_02\bin\java.exe
INFO   | jvm 2    | 2004/09/22 18:22:48 | Windows version: 5.0.2195
INFO   | jvm 2    | 2004/09/22 18:22:48 | Java Version   : 1.4.2_02-b03 
Java HotSpot(TM) Server VM
INFO   | jvm 2    | 2004/09/22 18:22:48 | Java VM Vendor : Sun 
Microsystems Inc.
INFO   | jvm 2    | 2004/09/22 18:22:48 |
INFO   | jvm 2    | 2004/09/22 18:22:48 | Wrapper (Version 3.1.1) 
http://wrapper.tanukisoftware.org
INFO   | jvm 2    | 2004/09/22 18:22:48 |
INFO   | jvm 2    | 2004/09/22 18:22:48 | 
WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@1fae3c6, 
args["-c", "default"]) called by thread: main
INFO   | jvm 2    | 2004/09/22 18:22:48 | Open socket to wrapper...
INFO   | jvm 2    | 2004/09/22 18:22:48 | Opened Socket
INFO   | jvm 2    | 2004/09/22 18:22:48 | Send a packet KEY : 
rZuk3O5PJPe7hdQ1
INFO   | jvm 2    | 2004/09/22 18:22:48 | 
handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=1143])
DEBUG  | wrapperp | 2004/09/22 18:22:48 | accepted a socket from 
127.0.0.1 on port 1143
DEBUG  | wrapperp | 2004/09/22 18:22:48 | read a packet KEY : 
rZuk3O5PJPe7hdQ1
DEBUG  | wrapper  | 2004/09/22 18:22:48 | Got key from JVM: rZuk3O5PJPe7hdQ1
DEBUG  | wrapperp | 2004/09/22 18:22:48 | send a packet LOW_LOG_LEVEL : 1
DEBUG  | wrapperp | 2004/09/22 18:22:48 | send a packet PING_TIMEOUT : 300
DEBUG  | wrapper  | 2004/09/22 18:22:48 | Start Application.
DEBUG  | wrapperp | 2004/09/22 18:22:48 | send a packet START : start
INFO   | jvm 2    | 2004/09/22 18:22:48 | Received a packet 
LOW_LOG_LEVEL : 1
INFO   | jvm 2    | 2004/09/22 18:22:48 | Wrapper Manager: LowLogLevel 
from Wrapper is 1
INFO   | jvm 2    | 2004/09/22 18:22:48 | Received a packet PING_TIMEOUT 
: 300
INFO   | jvm 2    | 2004/09/22 18:22:48 | Wrapper Manager: PingTimeout 
from Wrapper is 300000
INFO   | jvm 2    | 2004/09/22 18:22:48 | Received a packet START : start
INFO   | jvm 2    | 2004/09/22 18:22:48 | calling listener.start()
INFO   | jvm 2    | 2004/09/22 18:22:48 | WrapperSimpleApp: start(args)
INFO   | jvm 2    | 2004/09/22 18:22:48 | WrapperSimpleApp: invoking 
main method
INFO   | jvm 2    | 2004/09/22 18:22:48 | WrapperSimpleApp: main method 
completed
INFO   | jvm 2    | 2004/09/22 18:22:48 | WrapperSimpleApp: start(args) 
end.  Main Completed=true, exitCode=null
INFO   | jvm 2    | 2004/09/22 18:22:48 | returned from listener.start()
INFO   | jvm 2    | 2004/09/22 18:22:48 | Send a packet STARTED :
DEBUG  | wrapperp | 2004/09/22 18:22:48 | read a packet STARTED :
DEBUG  | wrapper  | 2004/09/22 18:22:48 | JVM signalled that it was started.
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,343 INFO  [Server] 
Starting JBoss (MX MicroKernel)...
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Release ID: JBoss [WonderLand] 3.2.2 (build: CVSTag=JBoss_3_2_2 
date=200310182216)
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Home Dir: C:\jboss-3.2.2
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Home URL: file:/C:/jboss-3.2.2/
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Library URL: file:/C:/jboss-3.2.2/lib/
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Patch URL: null
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Server Name: default
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Server Home Dir: C:\jboss-3.2.2\server\default
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Server Home URL: file:/C:/jboss-3.2.2/server/default/
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Server Data Dir: C:\jboss-3.2.2\server\default\data
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Server Temp Dir: C:\jboss-3.2.2\server\default\tmp
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Server Config URL: file:/C:/jboss-3.2.2/server/default/conf/
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Server Library URL: file:/C:/jboss-3.2.2/server/default/lib/
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,359 INFO  [Server] 
Root Deployemnt Filename: jboss-service.xml
INFO   | jvm 2    | 2004/09/22 18:22:49 | 18:22:49,375 INFO  [Server] 
Starting General Purpose Architecture (GPA)...
INFO   | jvm 2    | 2004/09/22 18:22:50 | 18:22:50,625 INFO  
[ServerInfo] Java version: 1.4.2_02,Sun Microsystems Inc.
INFO   | jvm 2    | 2004/09/22 18:22:50 | 18:22:50,625 INFO  
[ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.4.2_02-b03,Sun 
Microsystems Inc.
INFO   | jvm 2    | 2004/09/22 18:22:50 | 18:22:50,625 INFO  
[ServerInfo] OS-System: Windows 2000 5.0,x86

.... Jboss loading, deployment  .... etc...
***************************************************
wrapper.conf :

###
#
###

#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=c:/j2sdk1.4.2_02/bin/java

# Java Main class.  This class must implement the WrapperListener interface
#  or guarantee that the WrapperManager class is initialized.  Helper
#  classes are provided to do this for you.  See the Integration section
#  of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=C:/jboss-3.2.2/lib/wrapper.jar
wrapper.java.classpath.2=C:/j2sdk1.4.2_02/lib/tools.jar
wrapper.java.classpath.3=C:/jboss-3.2.2/bin/run.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=C:/jboss-3.2.2/lib;
wrapper.java.library.path.2=C:/Eldat Common Path;

# Java Additional Parameters
wrapper.java.additional.1=-server
wrapper.java.additional.2=-XX:NewSize=400m
wrapper.java.additional.3=-XX:PermSize=40m
wrapper.java.additional.4=-Xms512m
wrapper.java.additional.5=-Xmx512m
wrapper.java.additional.6=-Xloggc:C:\jboss-3.2.2\server\default\log\GC.log
wrapper.java.additional.7=-Dprogram.name=Wrapper
#wrapper.java.additional.6=-Xdebug
#wrapper.java.additional.7=-Xnoagent
#wrapper.java.additional.8=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8787
#wrapper.java.additional.9=-Djava.compiler=NONE
#wrapper.java.additional.10=-XX:+PrintGCTimeStamps
#wrapper.java.additional.11=-verbosegc
#wrapper.java.additional.12=-XX:+PrintGCDetails
#wrapper.java.additional.13=-XX:+PrintHeapAtGC

wrapper.debug=true
wrapper.startup.timeout=60
wrapper.shutdown.timeout=60
wrapper.jvm_exit.timeout=60
wrapper.ping.timeout=300
wrapper.ping.interval=240   
wrapper.cpu.timeout=50

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

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

# Application parameters.  Add parameters as needed starting from 1
wrapper.app.parameter.1=org.jboss.Main
wrapper.app.parameter.2=-c
wrapper.app.parameter.3=default

#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console.  (See docs for formats)
wrapper.console.format=PM

# Log Level for console output.  (See docs for log levels)
wrapper.console.loglevel=DEBUG

# Log file to use for wrapper output logging.
wrapper.logfile=../server/default/log/wrapper.log

# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=LPTM

# Log Level for log file output.  (See docs for log levels)
wrapper.logfile.loglevel=DEBUG

# Maximum size that the log file will be allowed to grow to before
#  the log is rolled. Size is specified in bytes.  The default value
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
#  'm' (mb) suffix.  For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=10m

# Maximum number of rolled log files which will be allowed before old
#  files are deleted.  The default value of 0 implies no limit.
wrapper.logfile.maxfiles=10

# Log Level for sys/event log output.  (See docs for log levels)
wrapper.syslog.loglevel=NONE

#********************************************************************
# Wrapper NT Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
#  using this configuration file has been installed as a service.
#  Please uninstall the service before modifying this section.  The
#  service can then be reinstalled.

# Name of the service
wrapper.ntservice.name=JBoss322

# Display name of the service
wrapper.ntservice.displayname=JBoss Application Server Service

# Description of the service
wrapper.ntservice.description=JBoss Application Server Service

# Service dependencies.  Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=MySQL

# Mode in which the service is installed.  AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START

# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false

Re: [Wrapper-user] Why does the wrapper fork a JVM process?

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

Daniel,
Long long ago, version 1.x of the Wrapper used to do just what you are 
talking about.
It created a JVM using the JNI interface by linking with the jvm.dll.
There were a number of problems with this approach.

1) The wrapper became a bit tied to the version of Java.

2) It was not possible to run Java exactly as you could with a 
standalone JVM.

3) The biggest issue is the ability of the Wrapper to recover and 
restart a JVM that
crashes or hangs. When they were in the same process, if the JVM died, 
so did the
Wrapper. It was simply a way to launch the JVM as a service, but did not 
provide
any of the stability features of the current Wrapper. As far as I know, 
all other
competing Java launching tools use the single process method.

Let me know if you have any more questions.

Cheers,
Leif

Daniel Bress wrote:

> I noticed that when I run the wrapper I get two processes 
> (wrapper.exe, and java.exe), I know the wrapper.exe is the wrapper, 
> and java.exe is the JVM. Isn’t it possible to invoke the JVM 
> programmatically so that it starts as a thread, and thusly the 
> java.exe process is never created?
>
> I am curious as to why the wrapper uses the approach it does.
>
> Dan
>
> ------------------------------------------------------------------------
>
> *From:* Balaji k. Madhavan [mailto:Ba...@el...]
> *Sent:* Tuesday, September 21, 2004 4:44 AM
> *To:* wra...@li...
> *Subject:* [Wrapper-user] How to get a thread dump in a JVM freeze 
> incident?
>
> Dear All,
>
> I'm using java service wrapper 3.1.0 in my application which runs on 
> IBM JRE 1.3.0. When the application freezes, we are tring to get 
> thread dump using wrapperlistener's "D" command. We couldn't succeed 
> in getting a thread dump;no response from the wrapper service. We 
> observed that service was in hung state. Even in case of a freeze 
> incident, how should I configure the wrapper service to get a thread dump.
>
> I have listed my app configurations as follows:
>
> wrapper.java.command=C:/IBM/Java13/jre/bin/java
> wrapper.java.mainclass=com.elind.service.fixgateway.common.FixMarketDataMainProcess 
>
> wrapper.max_failed_invocations=1
> wrapper.ping.timeout=0
> wrapper.java.classpath.1=C:/Test/lib/wrapper.jar
> wrapper.java.classpath.2=C:/Test/lib/FixGateway.jar
> wrapper.java.classpath.3=C:/Test/lib/jgl3.1.0.jar
> wrapper.java.classpath.4=C:/Test/lib/xerces.jar
> wrapper.java.classpath.5=C:/Test/lib/xmlparserv2.jar
> wrapper.java.library.path.1=C:/Test/lib
> wrapper.console.format=PM
> wrapper.console.loglevel=INFO
> wrapper.logfile=../logs/wrapper.log
> wrapper.logfile.format=LPTM
> wrapper.logfile.loglevel=INFO
> wrapper.logfile.maxsize=0
> wrapper.logfile.maxfiles=0
> wrapper.syslog.loglevel=NONE
> wrapper.ntservice.name=FixTradingPartner
> wrapper.ntservice.displayname=FixTradingPartner
> wrapper.ntservice.description=FixTradingPartner
> wrapper.ntservice.dependency.1=
> wrapper.ntservice.starttype=AUTO_START
> wrapper.ntservice.interactive=false
> wrapper.ntservice.console=false
> wrapper.working.dir=C:/Test/batch
>
> Awaiting for you valuable suggestions.
>
> Thanks in advance,
>
> Warm Regards,
> Balaji K M.
>
>
>
>
>

[Wrapper-user] Why does the wrapper fork a JVM process?

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

I noticed that when I run the wrapper I get two processes (wrapper.exe,
and java.exe), I know the wrapper.exe is the wrapper, and java.exe is
the JVM.  Isn't it possible to invoke the JVM programmatically so that
it starts as a thread, and thusly the java.exe process is never created?


=20

I am curious as to why the wrapper uses the approach it does.

=20

Dan

=20

  _____ =20

From: Balaji k. Madhavan [mailto:Ba...@el...]=20
Sent: Tuesday, September 21, 2004 4:44 AM
To: wra...@li...
Subject: [Wrapper-user] How to get a thread dump in a JVM freeze
incident?

=20

Dear All,=20

        I'm using java service wrapper 3.1.0 in my application which
runs on IBM JRE 1.3.0. When the application freezes, we are tring to get
thread dump using wrapperlistener's "D" command. We couldn't succeed in
getting a thread dump;no response from the wrapper service. We observed
that service was in hung state. Even in case of a freeze incident, how
should I configure the wrapper service to get a thread dump.

I have listed my app configurations as follows:=20

wrapper.java.command=3DC:/IBM/Java13/jre/bin/java=20
wrapper.java.mainclass=3Dcom.elind.service.fixgateway.common.FixMarketDat=
a
MainProcess=20
wrapper.max_failed_invocations=3D1=20
wrapper.ping.timeout=3D0=20
wrapper.java.classpath.1=3DC:/Test/lib/wrapper.jar=20
wrapper.java.classpath.2=3DC:/Test/lib/FixGateway.jar=20
wrapper.java.classpath.3=3DC:/Test/lib/jgl3.1.0.jar=20
wrapper.java.classpath.4=3DC:/Test/lib/xerces.jar=20
wrapper.java.classpath.5=3DC:/Test/lib/xmlparserv2.jar=20
wrapper.java.library.path.1=3DC:/Test/lib=20
wrapper.console.format=3DPM=20
wrapper.console.loglevel=3DINFO=20
wrapper.logfile=3D../logs/wrapper.log=20
wrapper.logfile.format=3DLPTM=20
wrapper.logfile.loglevel=3DINFO=20
wrapper.logfile.maxsize=3D0=20
wrapper.logfile.maxfiles=3D0=20
wrapper.syslog.loglevel=3DNONE=20
wrapper.ntservice.name=3DFixTradingPartner=20
wrapper.ntservice.displayname=3DFixTradingPartner=20
wrapper.ntservice.description=3DFixTradingPartner=20
wrapper.ntservice.dependency.1=3D=20
wrapper.ntservice.starttype=3DAUTO_START=20
wrapper.ntservice.interactive=3Dfalse=20
wrapper.ntservice.console=3Dfalse=20
wrapper.working.dir=3DC:/Test/batch=20

Awaiting for you valuable suggestions.=20

Thanks in advance,=20

Warm Regards,=20
Balaji K M.=20

[Wrapper-user] How to get a thread dump in a JVM freeze incident?

[Balaji KM <bal...@gm...>]

Dear All,

	I'm using java service wrapper 3.1.0 in my application which runs on
IBM JRE 1.3.0. When the application freezes, we are tring to get
thread dump using wrapperlistener's "D" command. We couldn't succeed
in getting a thread dump;no response from the wrapper service. We
observed that service was in hung state. Even in case of a freeze
incident, how should I configure the wrapper service to get a thread
dump.

I have listed my app configurations as follows:

wrapper.java.command=C:/IBM/Java13/jre/bin/java 
wrapper.java.mainclass=com.elind.service.fixgateway.common.FixMarketDataMainProcess
wrapper.max_failed_invocations=1 
wrapper.ping.timeout=0
wrapper.java.classpath.1=C:/Test/lib/wrapper.jar
wrapper.java.classpath.2=C:/Test/lib/FixGateway.jar
wrapper.java.classpath.3=C:/Test/lib/jgl3.1.0.jar
wrapper.java.classpath.4=C:/Test/lib/xerces.jar
wrapper.java.classpath.5=C:/Test/lib/xmlparserv2.jar
wrapper.java.library.path.1=C:/Test/lib
wrapper.console.format=PM
wrapper.console.loglevel=INFO
wrapper.logfile=../logs/wrapper.log
wrapper.logfile.format=LPTM
wrapper.logfile.loglevel=INFO
wrapper.logfile.maxsize=0
wrapper.logfile.maxfiles=0
wrapper.syslog.loglevel=NONE
wrapper.ntservice.name=FixTradingPartner
wrapper.ntservice.displayname=FixTradingPartner
wrapper.ntservice.description=FixTradingPartner
wrapper.ntservice.dependency.1=
wrapper.ntservice.starttype=AUTO_START
wrapper.ntservice.interactive=false
wrapper.ntservice.console=false
wrapper.working.dir=C:/Test/batch

Awaiting for you valuable suggestions.

Thanks in advance,

Warm Regards,
Balaji K M.

[Wrapper-user] How to get a thread dump in a JVM freeze incident?

[Balaji k. M. <Ba...@el...>]

Dear All,

	I'm using java service wrapper 3.1.0 in my application which
runs on IBM JRE 1.3.0. When the application freezes, we are tring to get
thread dump using wrapperlistener's "D" command. We couldn't succeed in
getting a thread dump;no response from the wrapper service. We observed
that service was in hung state. Even in case of a freeze incident, how
should I configure the wrapper service to get a thread dump.

I have listed my app configurations as follows:

wrapper.java.command=3DC:/IBM/Java13/jre/bin/java=20
wrapper.java.mainclass=3Dcom.elind.service.fixgateway.common.FixMarketDat=
a
MainProcess
wrapper.max_failed_invocations=3D1=20
wrapper.ping.timeout=3D0
wrapper.java.classpath.1=3DC:/Test/lib/wrapper.jar
wrapper.java.classpath.2=3DC:/Test/lib/FixGateway.jar
wrapper.java.classpath.3=3DC:/Test/lib/jgl3.1.0.jar
wrapper.java.classpath.4=3DC:/Test/lib/xerces.jar
wrapper.java.classpath.5=3DC:/Test/lib/xmlparserv2.jar
wrapper.java.library.path.1=3DC:/Test/lib
wrapper.console.format=3DPM
wrapper.console.loglevel=3DINFO
wrapper.logfile=3D../logs/wrapper.log
wrapper.logfile.format=3DLPTM
wrapper.logfile.loglevel=3DINFO
wrapper.logfile.maxsize=3D0
wrapper.logfile.maxfiles=3D0
wrapper.syslog.loglevel=3DNONE
wrapper.ntservice.name=3DFixTradingPartner
wrapper.ntservice.displayname=3DFixTradingPartner
wrapper.ntservice.description=3DFixTradingPartner
wrapper.ntservice.dependency.1=3D
wrapper.ntservice.starttype=3DAUTO_START
wrapper.ntservice.interactive=3Dfalse
wrapper.ntservice.console=3Dfalse
wrapper.working.dir=3DC:/Test/batch

Awaiting for you valuable suggestions.

Thanks in advance,

Warm Regards,
Balaji K M.

Re: [Wrapper-user] Controlling 2 separate JVMs using one wrapper?

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

Mitch,
    The Wrapper is only capable of launching a single JVM instance at 
any one time.
It sounds like rather than running two JVMs, you want to be running two 
applications
in the same JVM.

    If so, that should by possible by creating a simple bootstrap class 
whose main
method simply calls the main methods of the two applications you wish to 
start
just like any other static method.

public static void main( String[] args )
{
    ClassA.main( args );
    ClassB.main( args );
}

Only works if the first main method returns.   But you can create a new 
thread for each
if necessary.

The WrapperListener integration will only be helpful if you want to run 
both apps in the
same JVM.   You should be able to do the same thing with the 
WrapperSimpleApp or
WrapperStartStopApp methods however.

Cheers,
Leif

Mi...@bo... wrote:

> Is it possible to control 2 separate JVMs using one wrapper and give 
> each JVM all the benefits of running in the wrapper? I know this may 
> sound silly, but I like the fact that wrapper gives you the ability to 
> start/stop applications in a platform independent way, but I would 
> like to obscure the fact that 2 separate instances of Java are 
> actually running.
>
> Would I be able to use the WrapperListener integration method to 
> control this or is wrapper only specific to controlling a single JVM?
>
> Thanks!
>
> Mitch
>

[Wrapper-user] Controlling 2 separate JVMs using one wrapper?

[<Mi...@bo...>]

Is it possible to control 2 separate JVMs using one wrapper and give each
JVM all the benefits of running in the wrapper? I know this may sound silly,
but I like the fact that wrapper gives you the ability to start/stop
applications in a platform independent way, but I would like to obscure the
fact that 2 separate instances of Java are actually running.

Would I be able to use the WrapperListener integration method to control
this or is wrapper only specific to controlling a single JVM?

Thanks!

Mitch