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

[Wrapper-user] RE: getting a java.lang.IllegalStateException after stopping a service and then restarting

[l l <reg...@ho...>]

Leif,

   I am using Integration Methods 3.

   The purpose of this application is to run as a service that interface 
with Lotus Notes and Sametime Server to provide realtime persistent of 
instant messages and access to instant message.

   We have created a main class that implements the WrapperListener 
interface.

   When main(String[] args) is called, it reads some properties in and 
create some log files and the most important function is to do a 
WrapperManager.start(new SametimeAuthenticationMain(), args);

   I assumed that the WrapperManager.start calls
        public Integer start( String[] args )
        {
            //System.out.println("Entrying SametimePersistentChatMain 
start");
            logger.writeToDebugFile("Debug", className,"Entrying 
SametimeAuthenticationMain start");
            m_theApp = new ITSametimeAuthenticationApp(m_AppParameters, 
args, logger );
            m_theApp.start();

            return null;
        }

    The start function create an object that start up several threads that 
serve various purpose.
    Some access the Domino Server, listen for instant messages,  write to a 
database.

    Everything works fine until I shutdown the service and then restart it.  
From then on, no matter how many time I stop the service and restart, the 
exception takes place.  Only after rebooting the
system does the service come up without an exception.  If the service is 
stop and restarted, the exception is back.

     Here is a copy of my conf file.

#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application

# Example using system path:
#wrapper.java.command=java

#Example using JAVA_HOME environment variable:
#wrapper.java.command=%JAVA_HOME%/bin/java

#Example using full path (not platform independent):
#wrapper.java.command=c:/j2sdk1.4.0/bin/java

wrapper.java.command=C:\Lotus\Domino\ibm-jre\jre\bin\java.exe

# 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=itplacemanager.SametimePersistentChatMain

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=C:\Lotus\Domino\Notes.jar
wrapper.java.classpath.2=../lib/wrapper.jar
wrapper.java.classpath.3=../lib/wrappertest.jar
wrapper.java.classpath.4=../lib/ITPlaceManager.jar
wrapper.java.classpath.5=../lib/STComm.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=C:\Lotus\Domino
wrapper.java.library.path.2=../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="C:\Program Files\Sametime Persistent 
Chat\SametimePersistentChat.properties"
wrapper.app.parameter.2="C:\Program Files\Sametime Persistent 
Chat\logs\STPersistentChat.log"
wrapper.app.parameter.3=JAVAWRAPPERSERVICE

#********************************************************************
# 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=INFO
#wrapper.console.loglevel=DEBUG

# Log file to use for wrapper output logging.
wrapper.logfile=../logs/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=INFO
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=0

# 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=0

# 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=Sametime Persistent Chat

# Display name of the service
wrapper.ntservice.displayname=Sametime Persistent Chat Application

# Description of the service
wrapper.ntservice.description=Save place chat information thru Sametime

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

# 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


Thank You
         Luke







>Luke,
     Which integration method are you using?   The problem is that you
are calling
WrapperManager.start after the WrapperManager has already been started.
I will need to see your config file and know a little more about what
you are doing
before I can be helpful.

Cheers,
Leif

lukeysan wrote:

 > What could be causing this?
 > Is there any other information I can provide that help?
 >
 > Could it be thread not going away?
 >
 > Thank You
 >            Luke
 >
 > Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org
 > INFO   | jvm 1    | 2004/08/25 22:23:34 |
 > INFO   | jvm 1    | 2004/08/25 22:23:34 |
 > WrapperManager.start(itplacemanager.SametimePersistentChatMain@58e6fffc,
 > args["C:\Program Files\Sametime Persistent
 > Chat\properties\SametimePersistentChat.properties", "C:\Program
 > Files\Sametime Persistent Chat\logs\STPersistentChat.log",
 > "JAVAWRAPPERSERVICE"]) called by thread: main
 > INFO   | jvm 1    | 2004/08/25 22:23:34 |
 > java.lang.IllegalStateException: WrapperManager has already been
 > started with a WrapperListener.
 > INFO   | jvm 1    | 2004/08/25 22:23:34 |     at
 > org.tanukisoftware.wrapper.WrapperManager.start(WrapperManager.java:1392)
 > INFO   | jvm 1    | 2004/08/25 22:23:34 |     at
 > 
itplacemanager.SametimePersistentChatMain.main(SametimePersistentChatMain.java:131)
 >

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

Re: [Wrapper-user] getting a java.lang.IllegalStateException after stopping a service and then restarting

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

Luke,
    Which integration method are you using?   The problem is that you 
are calling
WrapperManager.start after the WrapperManager has already been started.
I will need to see your config file and know a little more about what 
you are doing
before I can be helpful.

Cheers,
Leif

lukeysan wrote:

> What could be causing this?
> Is there any other information I can provide that help?
>
> Could it be thread not going away?
>
> Thank You
>            Luke
>
> Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org
> INFO   | jvm 1    | 2004/08/25 22:23:34 |
> INFO   | jvm 1    | 2004/08/25 22:23:34 | 
> WrapperManager.start(itplacemanager.SametimePersistentChatMain@58e6fffc, 
> args["C:\Program Files\Sametime Persistent 
> Chat\properties\SametimePersistentChat.properties", "C:\Program 
> Files\Sametime Persistent Chat\logs\STPersistentChat.log", 
> "JAVAWRAPPERSERVICE"]) called by thread: main
> INFO   | jvm 1    | 2004/08/25 22:23:34 | 
> java.lang.IllegalStateException: WrapperManager has already been 
> started with a WrapperListener.
> INFO   | jvm 1    | 2004/08/25 22:23:34 |     at 
> org.tanukisoftware.wrapper.WrapperManager.start(WrapperManager.java:1392)
> INFO   | jvm 1    | 2004/08/25 22:23:34 |     at 
> itplacemanager.SametimePersistentChatMain.main(SametimePersistentChatMain.java:131) 
>

Re: [Wrapper-user] System classpath

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

Stefan,
The Wrapper does not directly support the use of the system classpath. Its
use is generally discouraged by most Java users because of all of the
problems
that you run into when running multiple applications. There are times when
everything is necessary though.

Anyway. You should be able to fake the Wrapper into using it by setting your
entire system classpath as a single classpath element. The Wrapper normally
breaks up the classpath into individual jars to make it platform
independent.
Because your system classpath will be correct for the current platform
it will
work.

Try the following:
wrapper.classpath.1=%CLASSPATH%

Let me know how that works. If you have any problems set
wrapper.debug=true. That will let you see the full classpath generated
by the Wrapper.

Cheers,
Leif



Pauwels Stefan wrote:

> Hello,
> I'm running a wrapper service on Solaris.
> My application uses JNDI, and needs JARS that are on the system classpath.
> How can I use the system classpath i.s.o. the wrapper.classpath.<n>
> properties ?
> Thanks,
> Stefan

[Wrapper-user] System classpath

[Pauwels S. <Ste...@si...>]

Hello,
 
I'm running a wrapper service on Solaris.
 
My application uses JNDI, and needs JARS that are on the system classpath.
How can I use the system classpath i.s.o. the wrapper.classpath.<n>
properties ?
 
 
Thanks,
Stefan

[Wrapper-user] getting a java.lang.IllegalStateException after stopping a service and then restarting

[lukeysan <luk...@co...>]

What could be causing this?
 Is there any other information I can provide that help?

Could it be thread not going away?

Thank You
            Luke

Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2004/08/25 22:23:34 |
INFO   | jvm 1    | 2004/08/25 22:23:34 | 
WrapperManager.start(itplacemanager.SametimePersistentChatMain@58e6fffc, 
args["C:\Program Files\Sametime Persistent 
Chat\properties\SametimePersistentChat.properties", "C:\Program 
Files\Sametime Persistent Chat\logs\STPersistentChat.log", 
"JAVAWRAPPERSERVICE"]) called by thread: main
INFO   | jvm 1    | 2004/08/25 22:23:34 | 
java.lang.IllegalStateException: WrapperManager has already been started 
with a WrapperListener.
INFO   | jvm 1    | 2004/08/25 22:23:34 |     at 
org.tanukisoftware.wrapper.WrapperManager.start(WrapperManager.java:1392)
INFO   | jvm 1    | 2004/08/25 22:23:34 |     at 
itplacemanager.SametimePersistentChatMain.main(SametimePersistentChatMain.java:131)

Re: [Wrapper-user] JdbcOdbc bridge problem

[Stan P. <sta...@ax...>]

Leif Mortenson wrote:

> Stan,
>    How did you declare your ODBC data source in the ODBC control panel?  
> Was it
> declared system-wide?  Or just for the current user?   As stated, when 
> running as a service,
> the Wrapper and its JVM will be run as the System user.  If the data 
> source is not declared
> to be system wide then it will not be available.  

The DSN was a system DSN.

I checked it, and saw that I had a User DSN with the same name...--> I 
deleted this USer DSN. I doesn't work better.

  Since you can't set
> the user, try that.
>    I am pretty sure this is not a library or class path issue as you are 
> using the sun ODBC
> JDBC driver.   Unfortunately, that exception message is not very 
> informative. :-/
> "General error".  Someone should be shot.

indeed. ;-)

thanks for the help!!

Maybe the culprit is just windows XP home edition...

> 
> Cheers,
> Leif
> 
> Stan Pinte wrote:
> 
>> Earnie Dyke wrote:
>>
>>> This is probably a permissions issue. Access has to be able to create a
>>> "lock" file in the same directory as the "mdb" file. Are you running
>>> your service under a user account or localsystem? 
>>
>>
>>
>> I am using the LocalSystem...and I tried to chmod the directory in 
>> which access is running, with no luck...
>>
>> As I am running windows XP home edition, I cannot grant the "Logon as 
>> Service" right to the user...
>>
>> I'll try on another machine!
>>
>> thanks.
>>
>> I would think you
>>
>>> would be better served by using a real user account rather than
>>> localsystem.
>>>
>>> Earnie!
>>>
>>> -----Original Message-----
>>> From: wra...@li...
>>> [mailto:wra...@li...]On Behalf Of Stan Pinte
>>> Sent: Thursday, August 19, 2004 12:43 PM
>>> To: wra...@li...; Eric Baelen
>>> Subject: [Wrapper-user] JdbcOdbc bridge problem
>>>
>>>
>>> hello,
>>>
>>> I have a web application connecting to an access database using Sun's 
>>> JdbcOdbc bridge...
>>>
>>> It works well when I run the wrapper from the command-line...but not 
>>> when started as a service.
>>>
>>> It says:
>>>
>>> INFO   | jvm 1    | 2004/08/19 18:40:15 | Caused by: 
>>> java.sql.SQLException: Gene
>>> ral error
>>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>>> sun.jdbc.odbc.JdbcOdbc.create
>>> SQLException(JdbcOdbc.java:6987)
>>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>>> sun.jdbc.odbc.JdbcOdbc.standa
>>> rdError(JdbcOdbc.java:7115)
>>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>>> sun.jdbc.odbc.JdbcOdbc.SQLDri
>>> verConnect(JdbcOdbc.java:3074)
>>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>>> sun.jdbc.odbc.JdbcOdbcConnect
>>> ion.initialize(JdbcOdbcConnection.java:323)
>>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>>> sun.jdbc.odbc.JdbcOdbcDriver.
>>> connect(JdbcOdbcDriver.java:174)
>>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>>> java.sql.DriverManager.getCon
>>> nection(DriverManager.java:512)
>>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>>> java.sql.DriverManager.getCon
>>> nection(DriverManager.java:140)
>>>
>>> --> any idea what I could try out?
>>>
>>> I have tried the following:
>>>
>>> 1: adding this
>>>
>>> wrapper.java.library.path.2=C:/Program Files/j2sdk_nb/j2sdk1.4.2/bin/ 
>>> (so that JdbcOdbc.dll and related dlls are in the path)
>>>
>>> 2: running the service under another account like this:
>>>
>>> # runs under another account...
>>> wrapper.ntservice.account=stan
>>> wrapper.ntservice.account=XXXXX
>>>
>>> 3: copying JdbcOdbc.dll in JBOSS_HOME/lib directory, where we find 
>>> wrapper.dll
>>>
>>> thanks a lot for insights...
>>>
>>> Stan.
>>
>>
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 

Re: [Wrapper-user] JdbcOdbc bridge problem

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

Stan,
    How did you declare your ODBC data source in the ODBC control 
panel?  Was it
declared system-wide?  Or just for the current user?   As stated, when 
running as a service,
the Wrapper and its JVM will be run as the System user.  If the data 
source is not declared
to be system wide then it will not be available.   Since you can't set 
the user, try that.
    I am pretty sure this is not a library or class path issue as you 
are using the sun ODBC
JDBC driver.   Unfortunately, that exception message is not very 
informative. :-/
"General error".  Someone should be shot.

Cheers,
Leif

Stan Pinte wrote:

> Earnie Dyke wrote:
>
>> This is probably a permissions issue. Access has to be able to create a
>> "lock" file in the same directory as the "mdb" file. Are you running
>> your service under a user account or localsystem? 
>
>
> I am using the LocalSystem...and I tried to chmod the directory in 
> which access is running, with no luck...
>
> As I am running windows XP home edition, I cannot grant the "Logon as 
> Service" right to the user...
>
> I'll try on another machine!
>
> thanks.
>
> I would think you
>
>> would be better served by using a real user account rather than
>> localsystem.
>>
>> Earnie!
>>
>> -----Original Message-----
>> From: wra...@li...
>> [mailto:wra...@li...]On Behalf Of Stan Pinte
>> Sent: Thursday, August 19, 2004 12:43 PM
>> To: wra...@li...; Eric Baelen
>> Subject: [Wrapper-user] JdbcOdbc bridge problem
>>
>>
>> hello,
>>
>> I have a web application connecting to an access database using Sun's 
>> JdbcOdbc bridge...
>>
>> It works well when I run the wrapper from the command-line...but not 
>> when started as a service.
>>
>> It says:
>>
>> INFO   | jvm 1    | 2004/08/19 18:40:15 | Caused by: 
>> java.sql.SQLException: Gene
>> ral error
>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>> sun.jdbc.odbc.JdbcOdbc.create
>> SQLException(JdbcOdbc.java:6987)
>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>> sun.jdbc.odbc.JdbcOdbc.standa
>> rdError(JdbcOdbc.java:7115)
>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>> sun.jdbc.odbc.JdbcOdbc.SQLDri
>> verConnect(JdbcOdbc.java:3074)
>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>> sun.jdbc.odbc.JdbcOdbcConnect
>> ion.initialize(JdbcOdbcConnection.java:323)
>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>> sun.jdbc.odbc.JdbcOdbcDriver.
>> connect(JdbcOdbcDriver.java:174)
>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>> java.sql.DriverManager.getCon
>> nection(DriverManager.java:512)
>> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
>> java.sql.DriverManager.getCon
>> nection(DriverManager.java:140)
>>
>> --> any idea what I could try out?
>>
>> I have tried the following:
>>
>> 1: adding this
>>
>> wrapper.java.library.path.2=C:/Program Files/j2sdk_nb/j2sdk1.4.2/bin/ 
>> (so that JdbcOdbc.dll and related dlls are in the path)
>>
>> 2: running the service under another account like this:
>>
>> # runs under another account...
>> wrapper.ntservice.account=stan
>> wrapper.ntservice.account=XXXXX
>>
>> 3: copying JdbcOdbc.dll in JBOSS_HOME/lib directory, where we find 
>> wrapper.dll
>>
>> thanks a lot for insights...
>>
>> Stan.
>

Re: [Wrapper-user] JdbcOdbc bridge problem

[Stan P. <sta...@ax...>]

Earnie Dyke wrote:
> This is probably a permissions issue. Access has to be able to create a
> "lock" file in the same directory as the "mdb" file. Are you running
> your service under a user account or localsystem? 

I am using the LocalSystem...and I tried to chmod the directory in which 
access is running, with no luck...

As I am running windows XP home edition, I cannot grant the "Logon as 
Service" right to the user...

I'll try on another machine!

thanks.

I would think you
> would be better served by using a real user account rather than
> localsystem.
> 
> Earnie!
> 
> -----Original Message-----
> From: wra...@li...
> [mailto:wra...@li...]On Behalf Of Stan Pinte
> Sent: Thursday, August 19, 2004 12:43 PM
> To: wra...@li...; Eric Baelen
> Subject: [Wrapper-user] JdbcOdbc bridge problem
> 
> 
> hello,
> 
> I have a web application connecting to an access database using Sun's 
> JdbcOdbc bridge...
> 
> It works well when I run the wrapper from the command-line...but not 
> when started as a service.
> 
> It says:
> 
> INFO   | jvm 1    | 2004/08/19 18:40:15 | Caused by: 
> java.sql.SQLException: Gene
> ral error
> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
> sun.jdbc.odbc.JdbcOdbc.create
> SQLException(JdbcOdbc.java:6987)
> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
> sun.jdbc.odbc.JdbcOdbc.standa
> rdError(JdbcOdbc.java:7115)
> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
> sun.jdbc.odbc.JdbcOdbc.SQLDri
> verConnect(JdbcOdbc.java:3074)
> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
> sun.jdbc.odbc.JdbcOdbcConnect
> ion.initialize(JdbcOdbcConnection.java:323)
> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
> sun.jdbc.odbc.JdbcOdbcDriver.
> connect(JdbcOdbcDriver.java:174)
> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
> java.sql.DriverManager.getCon
> nection(DriverManager.java:512)
> INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
> java.sql.DriverManager.getCon
> nection(DriverManager.java:140)
> 
> --> any idea what I could try out?
> 
> I have tried the following:
> 
> 1: adding this
> 
> wrapper.java.library.path.2=C:/Program Files/j2sdk_nb/j2sdk1.4.2/bin/ 
> (so that JdbcOdbc.dll and related dlls are in the path)
> 
> 2: running the service under another account like this:
> 
> # runs under another account...
> wrapper.ntservice.account=stan
> wrapper.ntservice.account=XXXXX
> 
> 3: copying JdbcOdbc.dll in JBOSS_HOME/lib directory, where we find 
> wrapper.dll
> 
> thanks a lot for insights...
> 
> Stan.
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 

Re: [Wrapper-user] Java 1.5 compatible?

[Ted H. <thu...@mi...>]

It works.  Tried it with jboss 4.0RC1

On Thu, 19 Aug 2004 1:15pm, Jon Hancock wrote:
> Hello,
> I'm new to the Java Service Wrapper.  It looks like what I need but I 
> would like to know if anyone has tested it with Sun JDK 1.5 Beta 2 ???  
> Any reason why it wouldn't work?
> thanks, Jon
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
--
Ted Hudacko
ted...@ie...
--Note: I receive 100+ emails per day.  If it's important, CALL me.

[Wrapper-user] Java 1.5 compatible?

[Jon H. <jha...@pa...>]

Hello,
I'm new to the Java Service Wrapper.  It looks like what I need but I 
would like to know if anyone has tested it with Sun JDK 1.5 Beta 2 ???  
Any reason why it wouldn't work?
thanks, Jon

RE: [Wrapper-user] JdbcOdbc bridge problem

[Earnie D. <ed...@vr...>]

This is probably a permissions issue. Access has to be able to create a
"lock" file in the same directory as the "mdb" file. Are you running
your service under a user account or localsystem? I would think you
would be better served by using a real user account rather than
localsystem.

Earnie!

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of Stan Pinte
Sent: Thursday, August 19, 2004 12:43 PM
To: wra...@li...; Eric Baelen
Subject: [Wrapper-user] JdbcOdbc bridge problem


hello,

I have a web application connecting to an access database using Sun's=20
JdbcOdbc bridge...

It works well when I run the wrapper from the command-line...but not=20
when started as a service.

It says:

INFO   | jvm 1    | 2004/08/19 18:40:15 | Caused by:=20
java.sql.SQLException: Gene
ral error
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at=20
sun.jdbc.odbc.JdbcOdbc.create
SQLException(JdbcOdbc.java:6987)
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at=20
sun.jdbc.odbc.JdbcOdbc.standa
rdError(JdbcOdbc.java:7115)
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at=20
sun.jdbc.odbc.JdbcOdbc.SQLDri
verConnect(JdbcOdbc.java:3074)
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at=20
sun.jdbc.odbc.JdbcOdbcConnect
ion.initialize(JdbcOdbcConnection.java:323)
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at=20
sun.jdbc.odbc.JdbcOdbcDriver.
connect(JdbcOdbcDriver.java:174)
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at=20
java.sql.DriverManager.getCon
nection(DriverManager.java:512)
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at=20
java.sql.DriverManager.getCon
nection(DriverManager.java:140)

--> any idea what I could try out?

I have tried the following:

1: adding this

wrapper.java.library.path.2=3DC:/Program Files/j2sdk_nb/j2sdk1.4.2/bin/=20
(so that JdbcOdbc.dll and related dlls are in the path)

2: running the service under another account like this:

# runs under another account...
wrapper.ntservice.account=3Dstan
wrapper.ntservice.account=3DXXXXX

3: copying JdbcOdbc.dll in JBOSS_HOME/lib directory, where we find=20
wrapper.dll

thanks a lot for insights...

Stan.




-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

[Wrapper-user] JdbcOdbc bridge problem

[Stan P. <sta...@ax...>]

hello,

I have a web application connecting to an access database using Sun's 
JdbcOdbc bridge...

It works well when I run the wrapper from the command-line...but not 
when started as a service.

It says:

INFO   | jvm 1    | 2004/08/19 18:40:15 | Caused by: 
java.sql.SQLException: Gene
ral error
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
sun.jdbc.odbc.JdbcOdbc.create
SQLException(JdbcOdbc.java:6987)
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
sun.jdbc.odbc.JdbcOdbc.standa
rdError(JdbcOdbc.java:7115)
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
sun.jdbc.odbc.JdbcOdbc.SQLDri
verConnect(JdbcOdbc.java:3074)
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
sun.jdbc.odbc.JdbcOdbcConnect
ion.initialize(JdbcOdbcConnection.java:323)
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
sun.jdbc.odbc.JdbcOdbcDriver.
connect(JdbcOdbcDriver.java:174)
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
java.sql.DriverManager.getCon
nection(DriverManager.java:512)
INFO   | jvm 1    | 2004/08/19 18:40:15 |       at 
java.sql.DriverManager.getCon
nection(DriverManager.java:140)

--> any idea what I could try out?

I have tried the following:

1: adding this

wrapper.java.library.path.2=C:/Program Files/j2sdk_nb/j2sdk1.4.2/bin/ 
(so that JdbcOdbc.dll and related dlls are in the path)

2: running the service under another account like this:

# runs under another account...
wrapper.ntservice.account=stan
wrapper.ntservice.account=XXXXX

3: copying JdbcOdbc.dll in JBOSS_HOME/lib directory, where we find 
wrapper.dll

thanks a lot for insights...

Stan.

Re: [Wrapper-user] Ping

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

Taikei,
    Great.  Glad you got things working.  As I said before though.  Be 
careful of setting
timeouts to 0.   That tells the wrapper to NEVER timeout.   Even if you 
set to a very
long value like 1 hour (3600)  It will at least restart eventually 
should something bad
happen on startup.

Cheers,
Leif

v1...@za... wrote:

>Thank you.  I am using method #3.  I was pointed out by my leader, that
>there is no evidence of pinging during listener.start().  There is a
>critical issue, which listener.start() is waiting about 5 minutes to finish.
>This is due to listener.start() awaiting for a particular host to connect
>and initialize.  We just don't want to send "STARTED"  packet before all of
>the initialization have finished.  I set the ping and ping interval to
>default and wrapper.startup.timeout=0, so far working good for us.
>
>Thanks
>
>Taikei Matsushita
>  
>

Re: [Wrapper-user] Ping

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

Thank you.  I am using method #3.  I was pointed out by my leader, that
there is no evidence of pinging during listener.start().  There is a
critical issue, which listener.start() is waiting about 5 minutes to finish.
This is due to listener.start() awaiting for a particular host to connect
and initialize.  We just don't want to send "STARTED"  packet before all of
the initialization have finished.  I set the ping and ping interval to
default and wrapper.startup.timeout=0, so far working good for us.

Thanks

Taikei Matsushita


> Taikei,
> What integration method are you using?   Both the WrapperSimpleApp and
> WrapperStartStopApp helper classes launch the user program in the
background
> so the Wrapper will be notified that the application is started even if
> the user's
> main method has not completed.
>
> It sounds like you are using method #3, implementing your own
> WrapperListener?
> In this case, the pings do not start until after the
> WrapperListener.start method has
> completed.
>
> If your start method is going to take longer than 30 seconds to complete
> then you
> will need to set the wrapper.startup.timeout to a larger value.
>
> There was a bug fixed in 3.1.0 in which the very first ping timeout was
> hardcoded
> at 30 seconds.   It is possible that you are encountering problems
> related to this
> as it was still a bug in 3.0.5.   (If you upgrade, I suggest 3.1.1 over
> 3.1.0.  There
> were a couple significant bugs fixed in 3.1.1.)
>
> If you could post your debug output either on list or to me directly, I
> would be able
> to better explain what is happening with your application and how best
> to resolve it.
> Delete your existing wrapper.log file.  Set wrapper.debug=true.   Then
> run your
> application a single time all the way to shutdown.  I should then be
> able to tell you
> exactly what is happening.  Send your wrapper.conf as well so I can see
your
> timeout values.   If it is larger than 40Kb or contains sensitive
> information, then
> sent it to me off list.
>
> Cheers,
> Leif
>
>
> v103 wrote:
>
> >On JSW 3.0.5, Does ping between  wrapper and Java Side WrapperManager
start
> >after listener.start() completion.
> >In another words, is ping thrown to Java side while listener.start() is
in
> >process.
> >
> >I am having difficulty with this, the startup(listenter.start()) takes
more
> >than 5 minutes to complete, and before this completion.
> >
> >I set
> >wrapper.startup.timeout=0
> >wrapper.ping.interval=3600
> >wrapper.ping.timeout=7200
> >
> >I know this is an extreme amount of settings, however I don't want any
> >timeout and JVM shutdowns during listener.start().
> >
> >The wrapper.log at the end tells "JVM appears hung: TImed out waiting for
> >signal from JVM."
> >"JVM did not exit on request, terminated".
> >
> >Taikei Matsushita
> >
> >
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

Re: [Wrapper-user] Ping

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

Taikei,
What integration method are you using?   Both the WrapperSimpleApp and
WrapperStartStopApp helper classes launch the user program in the background
so the Wrapper will be notified that the application is started even if 
the user's
main method has not completed.

It sounds like you are using method #3, implementing your own 
WrapperListener?
In this case, the pings do not start until after the 
WrapperListener.start method has
completed.

If your start method is going to take longer than 30 seconds to complete 
then you
will need to set the wrapper.startup.timeout to a larger value.

There was a bug fixed in 3.1.0 in which the very first ping timeout was 
hardcoded
at 30 seconds.   It is possible that you are encountering problems 
related to this
as it was still a bug in 3.0.5.   (If you upgrade, I suggest 3.1.1 over 
3.1.0.  There
were a couple significant bugs fixed in 3.1.1.)

If you could post your debug output either on list or to me directly, I 
would be able
to better explain what is happening with your application and how best 
to resolve it.
Delete your existing wrapper.log file.  Set wrapper.debug=true.   Then 
run your
application a single time all the way to shutdown.  I should then be 
able to tell you
exactly what is happening.  Send your wrapper.conf as well so I can see your
timeout values.   If it is larger than 40Kb or contains sensitive 
information, then
sent it to me off list.

Cheers,
Leif


v103 wrote:

>On JSW 3.0.5, Does ping between  wrapper and Java Side WrapperManager start
>after listener.start() completion.
>In another words, is ping thrown to Java side while listener.start() is in
>process.
>  
>I am having difficulty with this, the startup(listenter.start()) takes more
>than 5 minutes to complete, and before this completion.
>
>I set 
>wrapper.startup.timeout=0
>wrapper.ping.interval=3600
>wrapper.ping.timeout=7200
>
>I know this is an extreme amount of settings, however I don't want any
>timeout and JVM shutdowns during listener.start().
>
>The wrapper.log at the end tells "JVM appears hung: TImed out waiting for
>signal from JVM."
>"JVM did not exit on request, terminated".
>
>Taikei Matsushita
>  
>

[Wrapper-user] Ping

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

On JSW 3.0.5, Does ping between  wrapper and Java Side WrapperManager start
after listener.start() completion.
In another words, is ping thrown to Java side while listener.start() is in
process.
  
I am having difficulty with this, the startup(listenter.start()) takes more
than 5 minutes to complete, and before this completion.

I set 
wrapper.startup.timeout=0
wrapper.ping.interval=3600
wrapper.ping.timeout=7200

I know this is an extreme amount of settings, however I don't want any
timeout and JVM shutdowns during listener.start().

The wrapper.log at the end tells "JVM appears hung: TImed out waiting for
signal from JVM."
"JVM did not exit on request, terminated".

Taikei Matsushita

Re: [Wrapper-user] Daily Auto Restart

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

Omar,
    Currently there is no way to schedule a restart at a specific time 
from within the Wrapper.
There are a couple ways to implement this yourself however.

1) If you are using a UNIX platform, you can simply create a cron job 
which will execute
the shell script with the "restart" command.

2) On any platform, you could create a timer thread in your Java 
application and then simply
call WrapperManager.restart() at the appropriate time.

Cheers,
Leif


Omar Al-Kalaldeh wrote:

>Hi,
>
>I wonder are there any way to restart the Wrapper service at specified time in the 
>day, or after a period of running time. 
>
>Best regards.
>  
>

Re: [Wrapper-user] wrapper.sh

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

Taikei,
The shell script does not read the Wrapper.conf file at all. When you
shutdown
the Wrapper using the shell script, it has its own 5 minute timeout
after which the
script kills the Wrapper process. This was done to prevent the system from
having problems shutting down.
You can extend that time by changing the "300" in the shell script to a
larger
value. But if your application is taking longer than 5 minutes to
shutdown cleanly
after being requested to do so, then you probably have other problems that
should be fixed. :-)
It would add a great deal of complexity to the shell script to have it
use the
wrapper.jvm_exit.timeout value from the wrapper.conf file. To date, I
have not
heard any other complaints about the 5 minute timeout in the shell script.
After timing out however, the Wrapper process is killed forcibly. If
possible,
a clean shutdown would be better there. So I am open to suggestions.

Cheers,
Leif


v103 wrote:

>Leif, I have a question regarding wrapper.sh.
>
>There is a section in wrapper.sh(AIX version) that forces to kill the
>process "kill -9 $pid".  
>It tells  if["X$pid" != "X" ] and then "kill -9 pid".  
>
>Does this take effect regardless "wrapper.shutdown.timeout" is set to zero.
>
>
>Taikei Matsushita
>  
>

[Wrapper-user] Daily Auto Restart

[Omar Al-K. <om...@sp...>]

Hi,

I wonder are there any way to restart the Wrapper service at specified ti=
me in the=20
day, or after a period of running time.=20

Best regards.

---- Introducing Spymac MailPro: http://www.spymac.com/mailpro/

[Wrapper-user] wrapper.sh

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

Leif, I have a question regarding wrapper.sh.

There is a section in wrapper.sh(AIX version) that forces to kill the
process "kill -9 $pid".  
It tells  if["X$pid" != "X" ] and then "kill -9 pid".  

Does this take effect regardless "wrapper.shutdown.timeout" is set to zero.


Taikei Matsushita




wrapper.sh



#! /bin/sh

#
# Skeleton sh script suitable for starting and stopping # wrapped Java apps
on the Solaris platform. 
#
# Make sure that PIDFILE points to the correct location, # if you have
changed the default location set in the # wrapper configuration file.
#

#---------------------------------------------------------------------------
--
# These settings can be modified to fit the needs of your application

# Application
APP_NAME="BW"
APP_LONG_NAME="Bプロセス"

# Wrapper
WRAPPER_CMD="./wrapper"
WRAPPER_CONF="./wrapper.conf"

# Priority at which to run the wrapper.  See "man nice" for valid
priorities.
#  nice is only used if a priority is specified.
PRIORITY=

# Location of the pid file.
PIDDIR="/tmp"

# Do not modify anything beyond this point
#---------------------------------------------------------------------------
--

# Get the fully qualified path to the script case $0 in
    /*)
        SCRIPT="$0"
        ;;
    *)
        PWD=`pwd`
        SCRIPT="$PWD/$0"
        ;;
esac

# Change spaces to ":" so the tokens can be parsed.
SCRIPT=`echo $SCRIPT | sed -e 's; ;:;g'` # Get the real path to this script,
resolving any symbolic links TOKENS=`echo $SCRIPT | sed -e 's;/; ;g'`
REALPATH= for C in $TOKENS; do
    REALPATH="$REALPATH/$C"
    while [ -h "$REALPATH" ] ; do
        LS="`ls -ld "$REALPATH"`"
        LINK="`expr "$LS" : '.*-> \(.*\)$'`"
        if expr "$LINK" : '/.*' > /dev/null; then
            REALPATH="$LINK"
        else
            REALPATH="`dirname "$REALPATH"`""/$LINK"
        fi
    done
done
# Change ":" chars back to spaces.
REALPATH=`echo $REALPATH | sed -e 's;:; ;g'`

# Change the current directory to the location of the script cd "`dirname
"$REALPATH"`"

# Process ID
PIDFILE="$PIDDIR/$APP_NAME.pid"
pid=""

# Resolve the location of the 'ps' command PSEXE="/usr/bin/ps"
if [ ! -x $PSEXE ]
then
    PSEXE="/bin/ps"
    if [ ! -x $PSEXE ]
    then
        echo "Unable to locate 'ps'."
        echo "Please report this with the location on your system."
        exit 1
    fi
fi

# Build the nice clause
if [ "X$PRIORITY" = "X" ]
then
    CMDNICE=""
else
    CMDNICE="nice -$PRIORITY"
fi

getpid() {
    if [ -f $PIDFILE ]
    then
        if [ -r $PIDFILE ]
        then
            pid=`cat $PIDFILE`
            if [ "X$pid" != "X" ]
            then
                # Verify that a process with this pid is still running.
                pid=`$PSEXE -p $pid | grep $pid | grep -v grep | awk '{print
$1}' | tail -1`
                if [ "X$pid" = "X" ]
                then
                    # This is a stale pid file.
                    rm -f $PIDFILE
                    echo "Removed stale pid file: $PIDFILE"
                fi
            fi
        else
            echo "Cannot read $PIDFILE."
            exit 1
        fi
    fi
}

testpid() {
    pid=`$PSEXE -p $pid | grep $pid | grep -v grep | awk '{print $1}' | tail
-1`
    if [ "X$pid" = "X" ]
    then
        # Process is gone so remove the pid file.
        rm -f $PIDFILE
    fi
}

console() {
    echo "Running $APP_LONG_NAME..."
    getpid
    if [ "X$pid" = "X" ]
    then
        exec $CMDNICE $WRAPPER_CMD $WRAPPER_CONF wrapper.pidfile=$PIDFILE
    else
        echo "$APP_LONG_NAME is already running."
        exit 1
    fi
}
 
start() {
    echo "Starting $APP_LONG_NAME..."
    getpid
    if [ "X$pid" = "X" ]
    then
        exec $CMDNICE $WRAPPER_CMD $WRAPPER_CONF wrapper.pidfile=$PIDFILE
wrapper.daemonize=TRUE
    else
        echo "$APP_LONG_NAME is already running."
        exit 1
    fi
}
 
stopit() {
    echo "Stopping $APP_LONG_NAME..."
    getpid
    if [ "X$pid" = "X" ]
    then
        echo "$APP_LONG_NAME was not running."
    else
         # Running so try to stop it.
        kill $pid
        if [ $? -ne 0 ]
        then
            # An explanation for the failure should have been given
            echo "Unable to stop $APP_LONG_NAME."
            exit 1
        fi

        # We can not predict how long it will take for the wrapper to
        #  actually stop as it depends on settings in wrapper.conf.
        #  Loop until it does.
        savepid=$pid
        CNT=0
        TOTCNT=0
        while [ "X$pid" != "X" ]
        do
            # Loop for up to 5 minutes
            if [ "$TOTCNT" -lt "300" ]
            then
                if [ "$CNT" -lt "5" ]
                then
                    CNT=`expr $CNT + 1`
                else
                    echo "Waiting for $APP_LONG_NAME to exit..."
                    CNT=0
                fi
                TOTCNT=`expr $TOTCNT + 1`

                sleep 1

                testpid
            else
                pid=
            fi
        done

        pid=$savepid
        testpid
        if [ "X$pid" != "X" ]
        then
            echo "Timed out waiting for $APP_LONG_NAME to exit."
            echo "  Attempting a forced exit..."
            kill -9 $pid
        fi

        pid=$savepid
        testpid
        if [ "X$pid" != "X" ]
        then
            echo "Failed to stop $APP_LONG_NAME."
            exit 1
        else
            echo "Stopped $APP_LONG_NAME."
        fi
    fi
}

dump() {
    echo "Dumping $APP_LONG_NAME..."
    getpid
    if [ "X$pid" = "X" ]
    then
        echo "$APP_LONG_NAME was not running."

    else
        kill -3 $pid

        if [ $? -ne 0 ]
        then
            echo "Failed to dump $APP_LONG_NAME."
            exit 1
        else
            echo "Dumped $APP_LONG_NAME."
        fi
    fi
}

case "$1" in

    'console')
        console
        ;;

    'start')
        start
        ;;

    'stop')
        stopit
        ;;

    'restart')
        stopit
        start
        ;;

    'dump')
        dump
        ;;

    *)
        echo "Usage: $0 { console | start | stop | restart | dump }"
        exit 1
        ;;
esac

exit 0

Re: [Wrapper-user] Wrapper code received an unknown packet type

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

Oliver,
    Packet code #113 is the Wrapper telling the WrapperManager in the 
JVM what the ping
timeout should be.   My guess is that your Wrapper binary and 
wrapper.jar versions do not
match.  The WrapperManager is complaining that it does not know what 
that packet code
is.

    I added some tests in 3.1.0 to display warnings when there are 
version mismatches.

    If you don't think this is the problem, please send me your Wrapper 
version as well as
your wrapper.log generated with wrapper.debug=true set.

    Cheers,
    Leif

Komoll, Oliver wrote:

>Hi,
> 
>any idea what that message is
> 
>Wrapper code received an unknown packet type: 113
> 
>Any application i startup with the Wrapper shows thsi message
> 
>TIA
> 
>Oliver
>  
>

[Wrapper-user] Wrapper code received an unknown packet type

[Komoll, O. <O.K...@kl...>]

Hi,
=20
any idea what that message is
=20
Wrapper code received an unknown packet type: 113
=20
Any application i startup with the Wrapper shows thsi message
=20
TIA
=20
Oliver

RE: [Wrapper-user] wrapper.shutdown.timeout properties

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

Thank you Leif.

Seems to be working good so far.   Basically the Application on JSW platform
is connected to other middleware. And sometimes the application may take
time to close down due to this dependency on middleware(When this process
has hung up for some reason).  Therefore I had to add some time to this
parameter.

Taikei Matsushita

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Leif
Mortenson
Sent: Monday, August 16, 2004 1:49 PM
To: wra...@li...
Subject: Re: [Wrapper-user] wrapper.shutdown.timeout properties

Matsushita-san,

>I am currently woking on with wrapper version 3.0.5(due to project 
>policy, we cannot upgrade JSW to latest version).  I had problem with 
>JVM shutting down before the application actually wants it.  I seem to 
>solve this by setting wrapper.shutdown.time.out to a relatively large
number.
>
>I have few questions about this property.
>
>1. Having set this to zero, wrapper will not shutdown JVM unless the 
>"STOPPED" packet is sent from Java side?
>  
>
That is correct.   After the Wrapper asks the application running in the 
JVM to stop, it
will wait up to "wrapper.shutdown.timeout" seconds for the WrapperManager in
the JVM to signal that the application has stopped.  This is done by sending
a STOPPED packet to the Wrapper.

By setting it to 0.  You are allowing an infinite amount of time for your
application to
stop.   If you really want a large value, I strongly suggest using a 
value like 300 (5 minutes)
rather than 0.

>2. I don't understand the difference between wrapper.shutdown.time.out 
>and wrapper.jvm.exit.timeout.  In the document, it says 
>wrapper.jvm.exit.timeout as the "later phase".  Supposely the 
>"wrapper.jvm.exit.timeout" waits for STOPPED packet, what does
wrapper.jvm.exit.timeout wait for?
>  
>
Once the Wrapper has been notified that the Application running in the JVM
has STOPPED, the Wrapper will wait "wrapper.jvm_exit.timeout" additional
seconds
for the JVM process to actually exit.   If it does not exit within the 
timeout then the
Wrapper will forcibly kill the JVM process.

If your application registers its own shutdown hooks, then it is possible
that the WrapperManager's shutdown hook could complete before yours have
completed.
In such cases, the JVM could take a while to shutdown after the STOPPED
packet
has been sent.   I'll take a look at clarifying this in the docs.

If your post your wrapper.log with wrapper.debug=true.  I may be able to
tell you which of the timeouts you need to be setting to solve your shutdown
problems.

Cheers, (Yoroshiku onegaishimasu)
Leif

Re: [Wrapper-user] wrapper.shutdown.timeout properties

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

Matsushita-san,

>I am currently woking on with wrapper version 3.0.5(due to project policy,
>we cannot upgrade JSW to latest version).  I had problem with JVM shutting
>down before the application actually wants it.  I seem to solve this by
>setting wrapper.shutdown.time.out to a relatively large number.
>
>I have few questions about this property.
>
>1. Having set this to zero, wrapper will not shutdown JVM unless the
>"STOPPED" packet is sent from Java side?
>  
>
That is correct.   After the Wrapper asks the application running in the 
JVM to stop, it
will wait up to "wrapper.shutdown.timeout" seconds for the 
WrapperManager in the
JVM to signal that the application has stopped.  This is done by sending 
a STOPPED
packet to the Wrapper.

By setting it to 0.  You are allowing an infinite amount of time for 
your application to
stop.   If you really want a large value, I strongly suggest using a 
value like 300 (5 minutes)
rather than 0.

>2. I don't understand the difference between wrapper.shutdown.time.out and
>wrapper.jvm.exit.timeout.  In the document, it says wrapper.jvm.exit.timeout
>as the "later phase".  Supposely the "wrapper.jvm.exit.timeout" waits for
>STOPPED packet, what does wrapper.jvm.exit.timeout wait for?
>  
>
Once the Wrapper has been notified that the Application running in the 
JVM has
STOPPED, the Wrapper will wait "wrapper.jvm_exit.timeout" additional seconds
for the JVM process to actually exit.   If it does not exit within the 
timeout then the
Wrapper will forcibly kill the JVM process.

If your application registers its own shutdown hooks, then it is 
possible that the
WrapperManager's shutdown hook could complete before yours have completed.
In such cases, the JVM could take a while to shutdown after the STOPPED 
packet
has been sent.   I'll take a look at clarifying this in the docs.

If your post your wrapper.log with wrapper.debug=true.  I may be able to 
tell you
which of the timeouts you need to be setting to solve your shutdown 
problems.

Cheers, (Yoroshiku onegaishimasu)
Leif

[Wrapper-user] wrapper.shutdown.timeout properties

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

I am currently woking on with wrapper version 3.0.5(due to project policy,
we cannot upgrade JSW to latest version).  I had problem with JVM shutting
down before the application actually wants it.  I seem to solve this by
setting wrapper.shutdown.time.out to a relatively large number.

I have few questions about this property.

1. Having set this to zero, wrapper will not shutdown JVM unless the
"STOPPED" packet is sent from Java side?
2. I don't understand the difference between wrapper.shutdown.time.out and
wrapper.jvm.exit.timeout.  In the document, it says wrapper.jvm.exit.timeout
as the "later phase".  Supposely the "wrapper.jvm.exit.timeout" waits for
STOPPED packet, what does wrapper.jvm.exit.timeout wait for?


Thanks.

Taikei Matsushita