Menu
▾
▴
wrapper-user — User issues for Wrapper. (Support questions, etc.)
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(13) |
Nov
(16) |
Dec
(29) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(38) |
Feb
(51) |
Mar
(51) |
Apr
(115) |
May
(82) |
Jun
(30) |
Jul
(50) |
Aug
(68) |
Sep
(57) |
Oct
(160) |
Nov
(80) |
Dec
(78) |
| 2004 |
Jan
(71) |
Feb
(75) |
Mar
(108) |
Apr
(87) |
May
(79) |
Jun
(70) |
Jul
(69) |
Aug
(39) |
Sep
(52) |
Oct
(47) |
Nov
(50) |
Dec
(32) |
| 2005 |
Jan
(22) |
Feb
(122) |
Mar
(46) |
Apr
(76) |
May
(31) |
Jun
(51) |
Jul
(61) |
Aug
(70) |
Sep
(37) |
Oct
(46) |
Nov
(57) |
Dec
(83) |
| 2006 |
Jan
(55) |
Feb
(81) |
Mar
(51) |
Apr
(67) |
May
(77) |
Jun
(43) |
Jul
(106) |
Aug
(64) |
Sep
(47) |
Oct
(64) |
Nov
(60) |
Dec
(12) |
| 2007 |
Jan
(50) |
Feb
(93) |
Mar
(49) |
Apr
(56) |
May
(40) |
Jun
(63) |
Jul
(40) |
Aug
(47) |
Sep
(54) |
Oct
(37) |
Nov
(54) |
Dec
(37) |
| 2008 |
Jan
(35) |
Feb
(39) |
Mar
(26) |
Apr
(14) |
May
(23) |
Jun
(51) |
Jul
(43) |
Aug
(26) |
Sep
(29) |
Oct
(31) |
Nov
(24) |
Dec
(16) |
| 2009 |
Jan
(21) |
Feb
(30) |
Mar
(74) |
Apr
(26) |
May
(26) |
Jun
(43) |
Jul
(23) |
Aug
(23) |
Sep
(15) |
Oct
(27) |
Nov
(37) |
Dec
(10) |
| 2010 |
Jan
(16) |
Feb
(28) |
Mar
(16) |
Apr
(45) |
May
(8) |
Jun
(68) |
Jul
(45) |
Aug
(44) |
Sep
(51) |
Oct
(7) |
Nov
(20) |
Dec
(21) |
| 2011 |
Jan
(14) |
Feb
(17) |
Mar
(7) |
Apr
(7) |
May
(48) |
Jun
(23) |
Jul
(5) |
Aug
(33) |
Sep
(22) |
Oct
(14) |
Nov
(14) |
Dec
(5) |
| 2012 |
Jan
|
Feb
(10) |
Mar
(12) |
Apr
(51) |
May
(10) |
Jun
(8) |
Jul
(14) |
Aug
(22) |
Sep
(9) |
Oct
(24) |
Nov
(14) |
Dec
(13) |
| 2013 |
Jan
(12) |
Feb
(4) |
Mar
(14) |
Apr
(19) |
May
(2) |
Jun
(5) |
Jul
(13) |
Aug
(10) |
Sep
(4) |
Oct
(11) |
Nov
(13) |
Dec
(2) |
| 2014 |
Jan
(3) |
Feb
(14) |
Mar
(5) |
Apr
(10) |
May
(10) |
Jun
(11) |
Jul
(10) |
Aug
(3) |
Sep
(13) |
Oct
(22) |
Nov
(14) |
Dec
(32) |
| 2015 |
Jan
(8) |
Feb
(2) |
Mar
(17) |
Apr
(1) |
May
(24) |
Jun
|
Jul
(4) |
Aug
|
Sep
(9) |
Oct
(9) |
Nov
(5) |
Dec
(2) |
| 2016 |
Jan
(8) |
Feb
(6) |
Mar
(6) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(7) |
Aug
(6) |
Sep
|
Oct
|
Nov
(1) |
Dec
(6) |
| 2017 |
Jan
(9) |
Feb
(8) |
Mar
(6) |
Apr
|
May
|
Jun
(3) |
Jul
(13) |
Aug
(10) |
Sep
(8) |
Oct
|
Nov
(6) |
Dec
|
| 2018 |
Jan
|
Feb
(5) |
Mar
(7) |
Apr
(2) |
May
|
Jun
|
Jul
(3) |
Aug
(2) |
Sep
(9) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2019 |
Jan
(9) |
Feb
|
Mar
|
Apr
(10) |
May
(3) |
Jun
|
Jul
(7) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2020 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2021 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2023 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dittmar G. <gr...@if...> - 2008-09-18 09:02:43
|
Dittmar Gross ist wegen Urlaub bis 19-Sep-2008 nicht per eMail zu erreichen. Bitte wenden Sie sich in dringenden Faellen an Telefon +49 (69) 7680 50, Telefax +49 (69) 7680 5333 oder eMail fi...@if... Dittmar Gross is not available via eMail until Sep-19-2008 because of vacation. In urgent cases please contact us directly by Telephone +49 (69) 7680 50, Fax +49 (69) 7680 5333 or eMail fi...@if... ---------------------------------------------------------------------------- i:FAO Group Clemensstrasse 9, 60487 Frankfurt am Main, Germany Tel +49 (69) 7680-50, Fax +49 (69) 7680-5100, eMail information at ifao.net, www.cytric.info i:FAO Group GmbH Sitz in Frankfurt am Main Eingetragen beim Amtsgericht Frankfurt am Main, HRB 73600 Geschaeftsfuehrer: Louis Arnitz, Karin Froese To view the disclaimer text, click here: www.ifao.net/disclaimer |
|
From: Emmett W. <emm...@gm...> - 2008-09-17 03:43:23
|
Is it possible to remotely debug the Java service wrapper using eclipse and JPDA ? e.g. wrapper.java.additional.9=-Xdebug wrapper.java.additional.10=-Xnoagent wrapper.java.additional.11=-Djava.compiler=NONE wrapper.java.additional.12=-Xrunjdwp:transport\=dt_socket,server\=y,suspend\=y,address\=5005 I cannot seem to get it to work |
|
From: Shashidhar G. M. <Sha...@ar...> - 2008-09-17 03:19:19
|
Hi Leif, Thanks for your suggestion I found the issue basically I need to change the parameter -Xss128k to -Xss256K. Reducing it to 128k was not providing enough thread stack size to launch the spring deployer. ________________________________ From: wra...@li... [mailto:wra...@li...] On Behalf Of Shashidhar Gaurav Misra Sent: Tuesday, September 16, 2008 8:01 PM To: wra...@li... Subject: Re: [Wrapper-user] Java service wrapper not able to load the springdeployer on Solaris 64-bit Hi Leif, When I am trying to start my Jboss using run.sh (comes along with Jboss) then I am not getting this error. The error comes only when I am trying to start my Jboss server using wrapper. I have taken a snapshot of java command line in both the cases but I don't see much difference. When starting Jboss using run.sh JBOSS_HOME: /usr/local/jboss JAVA: /usr/java/bin/java JAVA_OPTS: -server -Xms128m -Xmx128m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh CLASSPATH: /usr/local/jboss/bin/run.jar:/usr/java/lib/tools.jar When starting Jboss using wrapper TATUS | wrapper | 2008/09/16 09:22:21 | --> Wrapper Started as Daemon INFO | wrapper | 2008/09/16 09:22:21 | Command[0] : /usr/java/bin/java INFO | wrapper | 2008/09/16 09:22:21 | Command[1] : -Dprogram.name=run.sh INFO | wrapper | 2008/09/16 09:22:21 | Command[2] : -Dmy.hostname=abc INFO | wrapper | 2008/09/16 09:22:21 | Command[3] : -Djava.endorsed.dirs=/usr/local/jboss/lib/endorsed INFO | wrapper | 2008/09/16 09:22:21 | Command[8] : -Djava.awt.headless=true INFO | wrapper | 2008/09/16 09:22:21 | Command[10] : -Ddrools.compiler=JANINO INFO | wrapper | 2008/09/16 09:22:21 | Command[11] : -server INFO | wrapper | 2008/09/16 09:22:21 | Command[12] : -Xss128k INFO | wrapper | 2008/09/16 09:22:21 | Command[13] : -Dnode.platform.model=sun4u INFO | wrapper | 2008/09/16 09:22:21 | Command[15] : -Dsun.rmi.dgc.server.gcInterval=3600000 INFO | wrapper | 2008/09/16 09:22:21 | Command[16] : -Dsun.rmi.dgc.client.gcInterval=3600000 INFO | wrapper | 2008/09/16 09:22:21 | Command[24] : -XX:MaxPermSize=128m INFO | wrapper | 2008/09/16 09:22:21 | Command[25] : -Dsecurity.services.mode=enabled INFO | wrapper | 2008/09/16 09:22:21 | Command[26] : -XX:NewRatio=3 INFO | wrapper | 2008/09/16 09:22:21 | Command[27] : -Xms128m INFO | wrapper | 2008/09/16 09:22:21 | Command[28] : -Xmx128m INFO | wrapper | 2008/09/16 09:22:21 | Command[29] : -Djava.library.path=/usr/local/jboss/lib INFO | wrapper | 2008/09/16 09:22:21 | Command[30] : -classpath INFO | wrapper | 2008/09/16 09:22:21 | Command[31] : /usr/local/jboss/lib/wrapper.jar:/usr/local/jboss/bin/run.jar:/usr/ja va/lib/tools.jar:/usr/local/jboss/server/default/lib/commons-lang-2.3.jar:/usr/local/jboss/server/default/lib/joda-time-1.4.j ar:/usr/local/jboss/server/default/lib/snmp-support.jar:/usr/local/jboss/cbs_workflow INFO | wrapper | 2008/09/16 09:22:21 | Command[32] : -Dwrapper.key=0gfBDmkCcjEcotd4 INFO | wrapper | 2008/09/16 09:22:21 | Command[33] : -Dwrapper.port=18100 INFO | wrapper | 2008/09/16 09:22:21 | Command[34] : -Dwrapper.jvm.port.min=31000 INFO | wrapper | 2008/09/16 09:22:21 | Command[35] : -Dwrapper.jvm.port.max=31999 INFO | wrapper | 2008/09/16 09:22:21 | Command[36] : -Dwrapper.pid=9451 INFO | wrapper | 2008/09/16 09:22:21 | Command[37] : -Dwrapper.version=3.2.3 INFO | wrapper | 2008/09/16 09:22:21 | Command[38] : -Dwrapper.native_library=wrapper INFO | wrapper | 2008/09/16 09:22:21 | Command[39] : -Dwrapper.service=TRUE INFO | wrapper | 2008/09/16 09:22:21 | Command[40] : -Dwrapper.cpu.timeout=10 INFO | wrapper | 2008/09/16 09:22:21 | Command[41] : -Dwrapper.jvmid=1 INFO | wrapper | 2008/09/16 09:22:21 | Command[42] : org.tanukisoftware.wrapper.WrapperSimpleApp INFO | wrapper | 2008/09/16 09:22:21 | Command[43] : org.jboss.Main I tried removing the parameters -Xss128k and -XX:NewRatio=3 but then I am getting some other error. Not sure why these parameters are being passed but some of my services are not able to start up which are otherwise getting started when using run.sh. The same configuration for wrapper.conf is working fine on Linux. Please suggest. Thanks Shashidhar ________________________________ "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." |
|
From: Shashidhar G. M. <Sha...@ar...> - 2008-09-17 00:28:19
|
Hi Leif, By removing the parameters -Xss128k and -XX:NewRatio=3 I am able to start my Jboss Server. But I am not able to understand as why these parameters are not working on Solaris machine whereas the same parameters work on Linux machines. Pls suggest. Thanks Shashidhar ________________________________ From: wra...@li... [mailto:wra...@li...] On Behalf Of Shashidhar Gaurav Misra Sent: Tuesday, September 16, 2008 8:01 PM To: wra...@li... Subject: Re: [Wrapper-user] Java service wrapper not able to load the springdeployer on Solaris 64-bit Hi Leif, When I am trying to start my Jboss using run.sh (comes along with Jboss) then I am not getting this error. The error comes only when I am trying to start my Jboss server using wrapper. I have taken a snapshot of java command line in both the cases but I don't see much difference. When starting Jboss using run.sh JBOSS_HOME: /usr/local/jboss JAVA: /usr/java/bin/java JAVA_OPTS: -server -Xms128m -Xmx128m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh CLASSPATH: /usr/local/jboss/bin/run.jar:/usr/java/lib/tools.jar When starting Jboss using wrapper TATUS | wrapper | 2008/09/16 09:22:21 | --> Wrapper Started as Daemon INFO | wrapper | 2008/09/16 09:22:21 | Command[0] : /usr/java/bin/java INFO | wrapper | 2008/09/16 09:22:21 | Command[1] : -Dprogram.name=run.sh INFO | wrapper | 2008/09/16 09:22:21 | Command[2] : -Dmy.hostname=abc INFO | wrapper | 2008/09/16 09:22:21 | Command[3] : -Djava.endorsed.dirs=/usr/local/jboss/lib/endorsed INFO | wrapper | 2008/09/16 09:22:21 | Command[8] : -Djava.awt.headless=true INFO | wrapper | 2008/09/16 09:22:21 | Command[10] : -Ddrools.compiler=JANINO INFO | wrapper | 2008/09/16 09:22:21 | Command[11] : -server INFO | wrapper | 2008/09/16 09:22:21 | Command[12] : -Xss128k INFO | wrapper | 2008/09/16 09:22:21 | Command[13] : -Dnode.platform.model=sun4u INFO | wrapper | 2008/09/16 09:22:21 | Command[15] : -Dsun.rmi.dgc.server.gcInterval=3600000 INFO | wrapper | 2008/09/16 09:22:21 | Command[16] : -Dsun.rmi.dgc.client.gcInterval=3600000 INFO | wrapper | 2008/09/16 09:22:21 | Command[24] : -XX:MaxPermSize=128m INFO | wrapper | 2008/09/16 09:22:21 | Command[25] : -Dsecurity.services.mode=enabled INFO | wrapper | 2008/09/16 09:22:21 | Command[26] : -XX:NewRatio=3 INFO | wrapper | 2008/09/16 09:22:21 | Command[27] : -Xms128m INFO | wrapper | 2008/09/16 09:22:21 | Command[28] : -Xmx128m INFO | wrapper | 2008/09/16 09:22:21 | Command[29] : -Djava.library.path=/usr/local/jboss/lib INFO | wrapper | 2008/09/16 09:22:21 | Command[30] : -classpath INFO | wrapper | 2008/09/16 09:22:21 | Command[31] : /usr/local/jboss/lib/wrapper.jar:/usr/local/jboss/bin/run.jar:/usr/ja va/lib/tools.jar:/usr/local/jboss/server/default/lib/commons-lang-2.3.jar:/usr/local/jboss/server/default/lib/joda-time-1.4.j ar:/usr/local/jboss/server/default/lib/snmp-support.jar:/usr/local/jboss/cbs_workflow INFO | wrapper | 2008/09/16 09:22:21 | Command[32] : -Dwrapper.key=0gfBDmkCcjEcotd4 INFO | wrapper | 2008/09/16 09:22:21 | Command[33] : -Dwrapper.port=18100 INFO | wrapper | 2008/09/16 09:22:21 | Command[34] : -Dwrapper.jvm.port.min=31000 INFO | wrapper | 2008/09/16 09:22:21 | Command[35] : -Dwrapper.jvm.port.max=31999 INFO | wrapper | 2008/09/16 09:22:21 | Command[36] : -Dwrapper.pid=9451 INFO | wrapper | 2008/09/16 09:22:21 | Command[37] : -Dwrapper.version=3.2.3 INFO | wrapper | 2008/09/16 09:22:21 | Command[38] : -Dwrapper.native_library=wrapper INFO | wrapper | 2008/09/16 09:22:21 | Command[39] : -Dwrapper.service=TRUE INFO | wrapper | 2008/09/16 09:22:21 | Command[40] : -Dwrapper.cpu.timeout=10 INFO | wrapper | 2008/09/16 09:22:21 | Command[41] : -Dwrapper.jvmid=1 INFO | wrapper | 2008/09/16 09:22:21 | Command[42] : org.tanukisoftware.wrapper.WrapperSimpleApp INFO | wrapper | 2008/09/16 09:22:21 | Command[43] : org.jboss.Main I tried removing the parameters -Xss128k and -XX:NewRatio=3 but then I am getting some other error. Not sure why these parameters are being passed but some of my services are not able to start up which are otherwise getting started when using run.sh. The same configuration for wrapper.conf is working fine on Linux. Please suggest. Thanks Shashidhar -----Original Message----- From: wra...@li... [mailto:wra...@li...] On Behalf Of Leif Mortenson Sent: Tuesday, September 16, 2008 8:04 AM To: wra...@li... Subject: Re: [Wrapper-user] Java service wrapper not able to load the springdeployer on Solaris 64-bit Shashidhar, The Wrapper launches the JVM with a command line generated from the Wrapper.conf. It does not do anything which would affect the way JBoss or any other application runs once it has been launched. My guess is that there are some differences between the wrapper.conf that you created and the default shell script that comes with JBoss. I would suggest setting the following property then comparing the output Java command line with the command line generated by your JBoss distribution. Most likely there is a system.property being passed in which is missing or has an incorrect value. wrapper.java.command.loglevel=INFO Another thing to check is the current working directory. The Wrapper forces the default working directory to the location of the wrapper binary. This may not be the same as what the JBoss script is working from. A third thing to check is the version of Java that is being run. You can see this by setting the wrapper.debug=true property. I have seen cases where due to path problems a different version of java was being run than was intended. Cheers, Leif On Mon, Sep 15, 2008 at 6:56 PM, Shashidhar Gaurav Misra <Sha...@ar...> wrote: > Hi, > > > > I am using the Java service wrapper community version 3.3.0 (32-bit) for > running my application as a Unix daemon on a Solaris machine. > > My application is a Jboss server with some services deployed and running. > > > > OS Details > > 64-bit sparcv9 > > > > My problem is that the wrapper is not able to deploy a spring descriptor. I > am getting following error when I am trying to start my Jboss server. > > > > INFO | jvm 1 | 2008/08/07 05:04:24 | 05:04:23,771 ERROR [MainDeployer] > Could not create deployment: file:/usr/local/jbos > > s/server/default/deploy/deploy.last/Myservice.sar/Authentication.spring/ > > INFO | jvm 1 | 2008/08/07 05:04:24 | java.lang.NoClassDefFoundError: > org/springframework/beans/factory/ListableBeanFacto > > ry > > > > I have my spring descriptor under > > /usr/local/jboss/server/default/deploy/deploy.last/ Myservice.sar > /Authentication.spring/META-INF > > > > My spring jars are present under > > /usr/local/jboss/server/default/deploy/jboss-spring.deployer > > > > The same thing works for other OS for e.g. Linux, AIX etc > > > > > > Please suggest in case if I need to use some other version of the wrapper. > Is there any workaround for this? > > > > Thanks & Regards > > Shashidhar > > ________________________________ "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." |
|
From: Leif M. <le...@ta...> - 2008-09-16 18:51:41
|
Stas, This is also not something that we normally see. Which process is consuming the CPU? Is it your Java process? A couple years ago another user had a similar problem. It turned out to be caused by a path problem where a configuration file was failing to be opened. That was throwing an exception which was being caught and ignored. Then the whole thing was in a loop without any delays. The result was that the program thrashed consuming 100% CPU. The log information requested in reply to your other email may help show the cause of this problem as well. Cheers, Leif On Wed, Sep 17, 2008 at 12:13 AM, Stas Oskin <sta...@gm...> wrote: > Hi. > > Additionally, I found something much more worrisome. > > When my app runs under the wrapper, it takes MUCH more resources then when > it runs in console. It basically makes my system unresponsive. > > Any idea why is that? > > Regards. > > 2008/9/16 Stas Oskin <sta...@gm...> >> >> Hi. >> >> Well, I sorted it out - it was an Enter key handler which somehow >> interfered and caused a chain reaction. >> >> I noticed a very serious issue in the wrapper - sometimes it exits/crashes >> together with the Java app, and hence can't restart it. >> >> Any idea what's going on, and how the wrapper can be reliably used? >> >> Regards. >> >> 2008/9/16 Leif Mortenson <le...@ta...> >>> >>> Stas, >>> What platform and version are you running on? I see a reference to a >>> UNIXProcess so I assume it is not Windows. >>> >>> On UNIX versions, there is really no difference in the way the Wrapper >>> launches the JVM between running in Console or Started as a daemon >>> process. There could be differences in the environment variables >>> available to the Wrapper when it launches however. For example, the >>> PATH, or LD_LIBRARY_PATH. There could also be file permission issues >>> if they are not being run as the same user. >>> >>> Either way however, the Wrapper and JVM appear to be working. Most >>> likely something in the application is failing for one of the above >>> reasons which is leading to it being in an unstable state, thus >>> causing the exceptions. >>> >>> As these appear to be JDBC driver related, I would guess that maybe a >>> native component of your driver is failing to load. Does MySQL have a >>> native driver? I have used the pure Java driver. I tried Googling >>> and found your question but not much else. >>> >>> I would be happy to help out with more information. >>> >>> Cheers, >>> Leif >>> >>> On Sat, Sep 13, 2008 at 7:11 PM, Stas Oskin <sta...@gm...> wrote: >>> > Hi. >>> > >>> > I'm trying to get my app packaged in jar to work with the Java Wrapper, >>> > and >>> > have set up all correctly.When I launch the service in console mode, >>> > all >>> > works correctly. >>> > >>> > When I do the same with service mode - the service shuts down after a >>> > few >>> > seconds, and has the following errors in the log: >>> > >>> > INFO | jvm 1 | 2008/09/13 00:05:01 | java.sql.SQLException: >>> > java.lang.ThreadDeath >>> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >>> > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) >>> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >>> > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) >>> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >>> > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926) >>> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >>> > com.mysql.jdbc.Util.handleNewInstance(Util.java:430) >>> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >>> > com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:302) >>> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >>> > >>> > com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:282) >>> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >>> > java.sql.DriverManager.getConnection(DriverManager.java:582) >>> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >>> > java.sql.DriverManager.getConnection(DriverManager.java:185) >>> > >>> > (Below it my own functions exceptions - but this is a standard JDBC >>> > connector for MySQL). >>> > >>> > And this comes next (where I have function launching external process >>> > via >>> > exec function): >>> > >>> > INFO | jvm 1 | 2008/09/13 00:05:03 | >>> > java.lang.InterruptedException >>> > INFO | jvm 1 | 2008/09/13 00:05:03 | at >>> > java.lang.Object.wait(Native Method) >>> > INFO | jvm 1 | 2008/09/13 00:05:03 | at >>> > java.lang.Object.wait(Object.java:485) >>> > INFO | jvm 1 | 2008/09/13 00:05:03 | at >>> > java.lang.UNIXProcess.waitFor(UNIXProcess.java:165) >>> > >>> > >>> > Any idea what different between the console and start modes, and why >>> > the >>> > basic functionality doesn't work in this mode? >>> > >>> > Regards. >>> > >>> > >>> > ------------------------------------------------------------------------- >>> > This SF.Net email is sponsored by the Moblin Your Move Developer's >>> > challenge >>> > Build the coolest Linux based applications with Moblin SDK & win great >>> > prizes >>> > Grand prize is a trip for two to an Open Source event anywhere in the >>> > world >>> > http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> > _______________________________________________ >>> > Wrapper-user mailing list >>> > Wra...@li... >>> > https://lists.sourceforge.net/lists/listinfo/wrapper-user >>> > >>> > >>> >>> ------------------------------------------------------------------------- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win great >>> prizes >>> Grand prize is a trip for two to an Open Source event anywhere in the >>> world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> _______________________________________________ >>> Wrapper-user mailing list >>> Wra...@li... >>> https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: Leif M. <le...@ta...> - 2008-09-16 18:48:02
|
Stas, See my replies in line. On Tue, Sep 16, 2008 at 10:29 PM, Stas Oskin <sta...@gm...> wrote: > Well, I sorted it out - it was an Enter key handler which somehow interfered > and caused a chain reaction. The Wrapper should be able to handle input streams from within Java. Could you describe a little more what you are doing? Maybe with a code fragment? I would like to try it out. > I noticed a very serious issue in the wrapper - sometimes it exits/crashes > together with the Java app, and hence can't restart it. That would not be good. What version of the Wrapper are you using and what platform are you running on? There are no crashes that I am aware of in the newest version, but some older versions have had a couple issues which could lead to this. If you are able to reproduce this, could you please set the following properties and then send me the resulting wrapper.log file up through the crash. It will be quite large, so please send it to me directly rather than on list. --- wrapper.debug=true wrapper.state_output=true --- That should show me exactly where the crash is happening. > Any idea what's going on, and how the wrapper can be reliably used? We'll get this figured out for you. Cheers, Leif > 2008/9/16 Leif Mortenson <le...@ta...> >> >> Stas, >> What platform and version are you running on? I see a reference to a >> UNIXProcess so I assume it is not Windows. >> >> On UNIX versions, there is really no difference in the way the Wrapper >> launches the JVM between running in Console or Started as a daemon >> process. There could be differences in the environment variables >> available to the Wrapper when it launches however. For example, the >> PATH, or LD_LIBRARY_PATH. There could also be file permission issues >> if they are not being run as the same user. >> >> Either way however, the Wrapper and JVM appear to be working. Most >> likely something in the application is failing for one of the above >> reasons which is leading to it being in an unstable state, thus >> causing the exceptions. >> >> As these appear to be JDBC driver related, I would guess that maybe a >> native component of your driver is failing to load. Does MySQL have a >> native driver? I have used the pure Java driver. I tried Googling >> and found your question but not much else. >> >> I would be happy to help out with more information. >> >> Cheers, >> Leif >> >> On Sat, Sep 13, 2008 at 7:11 PM, Stas Oskin <sta...@gm...> wrote: >> > Hi. >> > >> > I'm trying to get my app packaged in jar to work with the Java Wrapper, >> > and >> > have set up all correctly.When I launch the service in console mode, all >> > works correctly. >> > >> > When I do the same with service mode - the service shuts down after a >> > few >> > seconds, and has the following errors in the log: >> > >> > INFO | jvm 1 | 2008/09/13 00:05:01 | java.sql.SQLException: >> > java.lang.ThreadDeath >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > com.mysql.jdbc.Util.handleNewInstance(Util.java:430) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:302) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > >> > com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:282) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > java.sql.DriverManager.getConnection(DriverManager.java:582) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > java.sql.DriverManager.getConnection(DriverManager.java:185) >> > >> > (Below it my own functions exceptions - but this is a standard JDBC >> > connector for MySQL). >> > >> > And this comes next (where I have function launching external process >> > via >> > exec function): >> > >> > INFO | jvm 1 | 2008/09/13 00:05:03 | java.lang.InterruptedException >> > INFO | jvm 1 | 2008/09/13 00:05:03 | at >> > java.lang.Object.wait(Native Method) >> > INFO | jvm 1 | 2008/09/13 00:05:03 | at >> > java.lang.Object.wait(Object.java:485) >> > INFO | jvm 1 | 2008/09/13 00:05:03 | at >> > java.lang.UNIXProcess.waitFor(UNIXProcess.java:165) >> > >> > >> > Any idea what different between the console and start modes, and why the >> > basic functionality doesn't work in this mode? >> > >> > Regards. |
|
From: Stas O. <sta...@gm...> - 2008-09-16 08:13:54
|
Hi. Additionally, I found something much more worrisome. When my app runs under the wrapper, it takes MUCH more resources then when it runs in console. It basically makes my system unresponsive. Any idea why is that? Regards. 2008/9/16 Stas Oskin <sta...@gm...> > Hi. > > Well, I sorted it out - it was an Enter key handler which somehow > interfered and caused a chain reaction. > > I noticed a very serious issue in the wrapper - sometimes it exits/crashes > together with the Java app, and hence can't restart it. > > Any idea what's going on, and how the wrapper can be reliably used? > > Regards. > > 2008/9/16 Leif Mortenson <le...@ta...> > > Stas, >> What platform and version are you running on? I see a reference to a >> UNIXProcess so I assume it is not Windows. >> >> On UNIX versions, there is really no difference in the way the Wrapper >> launches the JVM between running in Console or Started as a daemon >> process. There could be differences in the environment variables >> available to the Wrapper when it launches however. For example, the >> PATH, or LD_LIBRARY_PATH. There could also be file permission issues >> if they are not being run as the same user. >> >> Either way however, the Wrapper and JVM appear to be working. Most >> likely something in the application is failing for one of the above >> reasons which is leading to it being in an unstable state, thus >> causing the exceptions. >> >> As these appear to be JDBC driver related, I would guess that maybe a >> native component of your driver is failing to load. Does MySQL have a >> native driver? I have used the pure Java driver. I tried Googling >> and found your question but not much else. >> >> I would be happy to help out with more information. >> >> Cheers, >> Leif >> >> On Sat, Sep 13, 2008 at 7:11 PM, Stas Oskin <sta...@gm...> wrote: >> > Hi. >> > >> > I'm trying to get my app packaged in jar to work with the Java Wrapper, >> and >> > have set up all correctly.When I launch the service in console mode, all >> > works correctly. >> > >> > When I do the same with service mode - the service shuts down after a >> few >> > seconds, and has the following errors in the log: >> > >> > INFO | jvm 1 | 2008/09/13 00:05:01 | java.sql.SQLException: >> > java.lang.ThreadDeath >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > com.mysql.jdbc.Util.handleNewInstance(Util.java:430) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:302) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > >> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:282) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > java.sql.DriverManager.getConnection(DriverManager.java:582) >> > INFO | jvm 1 | 2008/09/13 00:05:01 | at >> > java.sql.DriverManager.getConnection(DriverManager.java:185) >> > >> > (Below it my own functions exceptions - but this is a standard JDBC >> > connector for MySQL). >> > >> > And this comes next (where I have function launching external process >> via >> > exec function): >> > >> > INFO | jvm 1 | 2008/09/13 00:05:03 | java.lang.InterruptedException >> > INFO | jvm 1 | 2008/09/13 00:05:03 | at >> > java.lang.Object.wait(Native Method) >> > INFO | jvm 1 | 2008/09/13 00:05:03 | at >> > java.lang.Object.wait(Object.java:485) >> > INFO | jvm 1 | 2008/09/13 00:05:03 | at >> > java.lang.UNIXProcess.waitFor(UNIXProcess.java:165) >> > >> > >> > Any idea what different between the console and start modes, and why the >> > basic functionality doesn't work in this mode? >> > >> > Regards. >> > >> > >> ------------------------------------------------------------------------- >> > This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> > Build the coolest Linux based applications with Moblin SDK & win great >> > prizes >> > Grand prize is a trip for two to an Open Source event anywhere in the >> world >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> > _______________________________________________ >> > Wrapper-user mailing list >> > Wra...@li... >> > https://lists.sourceforge.net/lists/listinfo/wrapper-user >> > >> > >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> > |
|
From: Shashidhar G. M. <Sha...@ar...> - 2008-09-16 07:30:49
|
Hi Leif, When I am trying to start my Jboss using run.sh (comes along with Jboss) then I am not getting this error. The error comes only when I am trying to start my Jboss server using wrapper. I have taken a snapshot of java command line in both the cases but I don't see much difference. When starting Jboss using run.sh JBOSS_HOME: /usr/local/jboss JAVA: /usr/java/bin/java JAVA_OPTS: -server -Xms128m -Xmx128m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh CLASSPATH: /usr/local/jboss/bin/run.jar:/usr/java/lib/tools.jar When starting Jboss using wrapper TATUS | wrapper | 2008/09/16 09:22:21 | --> Wrapper Started as Daemon INFO | wrapper | 2008/09/16 09:22:21 | Command[0] : /usr/java/bin/java INFO | wrapper | 2008/09/16 09:22:21 | Command[1] : -Dprogram.name=run.sh INFO | wrapper | 2008/09/16 09:22:21 | Command[2] : -Dmy.hostname=abc INFO | wrapper | 2008/09/16 09:22:21 | Command[3] : -Djava.endorsed.dirs=/usr/local/jboss/lib/endorsed INFO | wrapper | 2008/09/16 09:22:21 | Command[8] : -Djava.awt.headless=true INFO | wrapper | 2008/09/16 09:22:21 | Command[10] : -Ddrools.compiler=JANINO INFO | wrapper | 2008/09/16 09:22:21 | Command[11] : -server INFO | wrapper | 2008/09/16 09:22:21 | Command[12] : -Xss128k INFO | wrapper | 2008/09/16 09:22:21 | Command[13] : -Dnode.platform.model=sun4u INFO | wrapper | 2008/09/16 09:22:21 | Command[15] : -Dsun.rmi.dgc.server.gcInterval=3600000 INFO | wrapper | 2008/09/16 09:22:21 | Command[16] : -Dsun.rmi.dgc.client.gcInterval=3600000 INFO | wrapper | 2008/09/16 09:22:21 | Command[24] : -XX:MaxPermSize=128m INFO | wrapper | 2008/09/16 09:22:21 | Command[25] : -Dsecurity.services.mode=enabled INFO | wrapper | 2008/09/16 09:22:21 | Command[26] : -XX:NewRatio=3 INFO | wrapper | 2008/09/16 09:22:21 | Command[27] : -Xms128m INFO | wrapper | 2008/09/16 09:22:21 | Command[28] : -Xmx128m INFO | wrapper | 2008/09/16 09:22:21 | Command[29] : -Djava.library.path=/usr/local/jboss/lib INFO | wrapper | 2008/09/16 09:22:21 | Command[30] : -classpath INFO | wrapper | 2008/09/16 09:22:21 | Command[31] : /usr/local/jboss/lib/wrapper.jar:/usr/local/jboss/bin/run.jar:/usr/ja va/lib/tools.jar:/usr/local/jboss/server/default/lib/commons-lang-2.3.jar:/usr/local/jboss/server/default/lib/joda-time-1.4.j ar:/usr/local/jboss/server/default/lib/snmp-support.jar:/usr/local/jboss/cbs_workflow INFO | wrapper | 2008/09/16 09:22:21 | Command[32] : -Dwrapper.key=0gfBDmkCcjEcotd4 INFO | wrapper | 2008/09/16 09:22:21 | Command[33] : -Dwrapper.port=18100 INFO | wrapper | 2008/09/16 09:22:21 | Command[34] : -Dwrapper.jvm.port.min=31000 INFO | wrapper | 2008/09/16 09:22:21 | Command[35] : -Dwrapper.jvm.port.max=31999 INFO | wrapper | 2008/09/16 09:22:21 | Command[36] : -Dwrapper.pid=9451 INFO | wrapper | 2008/09/16 09:22:21 | Command[37] : -Dwrapper.version=3.2.3 INFO | wrapper | 2008/09/16 09:22:21 | Command[38] : -Dwrapper.native_library=wrapper INFO | wrapper | 2008/09/16 09:22:21 | Command[39] : -Dwrapper.service=TRUE INFO | wrapper | 2008/09/16 09:22:21 | Command[40] : -Dwrapper.cpu.timeout=10 INFO | wrapper | 2008/09/16 09:22:21 | Command[41] : -Dwrapper.jvmid=1 INFO | wrapper | 2008/09/16 09:22:21 | Command[42] : org.tanukisoftware.wrapper.WrapperSimpleApp INFO | wrapper | 2008/09/16 09:22:21 | Command[43] : org.jboss.Main I tried removing the parameters -Xss128k and -XX:NewRatio=3 but then I am getting some other error. Not sure why these parameters are being passed but some of my services are not able to start up which are otherwise getting started when using run.sh. The same configuration for wrapper.conf is working fine on Linux. Please suggest. Thanks Shashidhar -----Original Message----- From: wra...@li... [mailto:wra...@li...] On Behalf Of Leif Mortenson Sent: Tuesday, September 16, 2008 8:04 AM To: wra...@li... Subject: Re: [Wrapper-user] Java service wrapper not able to load the springdeployer on Solaris 64-bit Shashidhar, The Wrapper launches the JVM with a command line generated from the Wrapper.conf. It does not do anything which would affect the way JBoss or any other application runs once it has been launched. My guess is that there are some differences between the wrapper.conf that you created and the default shell script that comes with JBoss. I would suggest setting the following property then comparing the output Java command line with the command line generated by your JBoss distribution. Most likely there is a system.property being passed in which is missing or has an incorrect value. wrapper.java.command.loglevel=INFO Another thing to check is the current working directory. The Wrapper forces the default working directory to the location of the wrapper binary. This may not be the same as what the JBoss script is working from. A third thing to check is the version of Java that is being run. You can see this by setting the wrapper.debug=true property. I have seen cases where due to path problems a different version of java was being run than was intended. Cheers, Leif On Mon, Sep 15, 2008 at 6:56 PM, Shashidhar Gaurav Misra <Sha...@ar...> wrote: > Hi, > > > > I am using the Java service wrapper community version 3.3.0 (32-bit) for > running my application as a Unix daemon on a Solaris machine. > > My application is a Jboss server with some services deployed and running. > > > > OS Details > > 64-bit sparcv9 > > > > My problem is that the wrapper is not able to deploy a spring descriptor. I > am getting following error when I am trying to start my Jboss server. > > > > INFO | jvm 1 | 2008/08/07 05:04:24 | 05:04:23,771 ERROR [MainDeployer] > Could not create deployment: file:/usr/local/jbos > > s/server/default/deploy/deploy.last/Myservice.sar/Authentication.spring/ > > INFO | jvm 1 | 2008/08/07 05:04:24 | java.lang.NoClassDefFoundError: > org/springframework/beans/factory/ListableBeanFacto > > ry > > > > I have my spring descriptor under > > /usr/local/jboss/server/default/deploy/deploy.last/ Myservice.sar > /Authentication.spring/META-INF > > > > My spring jars are present under > > /usr/local/jboss/server/default/deploy/jboss-spring.deployer > > > > The same thing works for other OS for e.g. Linux, AIX etc > > > > > > Please suggest in case if I need to use some other version of the wrapper. > Is there any workaround for this? > > > > Thanks & Regards > > Shashidhar > > ________________________________ > "DISCLAIMER: This message is proprietary to Aricent and is intended solely > for the use of the individual to whom it is addressed. It may contain > privileged or confidential information and should not be circulated or used > for any purpose other than for what it is intended. If you have received > this message in error,please notify the originator immediately. If you are > not the intended recipient, you are notified that you are strictly > prohibited from using, copying, altering, or disclosing the contents of this > message. Aricent accepts no responsibility for loss or damage arising from > the use of the information transmitted by this email including damage from > virus." > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user ________________________________ "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." |
|
From: Stas O. <sta...@gm...> - 2008-09-16 06:29:23
|
Hi. Well, I sorted it out - it was an Enter key handler which somehow interfered and caused a chain reaction. I noticed a very serious issue in the wrapper - sometimes it exits/crashes together with the Java app, and hence can't restart it. Any idea what's going on, and how the wrapper can be reliably used? Regards. 2008/9/16 Leif Mortenson <le...@ta...> > Stas, > What platform and version are you running on? I see a reference to a > UNIXProcess so I assume it is not Windows. > > On UNIX versions, there is really no difference in the way the Wrapper > launches the JVM between running in Console or Started as a daemon > process. There could be differences in the environment variables > available to the Wrapper when it launches however. For example, the > PATH, or LD_LIBRARY_PATH. There could also be file permission issues > if they are not being run as the same user. > > Either way however, the Wrapper and JVM appear to be working. Most > likely something in the application is failing for one of the above > reasons which is leading to it being in an unstable state, thus > causing the exceptions. > > As these appear to be JDBC driver related, I would guess that maybe a > native component of your driver is failing to load. Does MySQL have a > native driver? I have used the pure Java driver. I tried Googling > and found your question but not much else. > > I would be happy to help out with more information. > > Cheers, > Leif > > On Sat, Sep 13, 2008 at 7:11 PM, Stas Oskin <sta...@gm...> wrote: > > Hi. > > > > I'm trying to get my app packaged in jar to work with the Java Wrapper, > and > > have set up all correctly.When I launch the service in console mode, all > > works correctly. > > > > When I do the same with service mode - the service shuts down after a few > > seconds, and has the following errors in the log: > > > > INFO | jvm 1 | 2008/09/13 00:05:01 | java.sql.SQLException: > > java.lang.ThreadDeath > > INFO | jvm 1 | 2008/09/13 00:05:01 | at > > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) > > INFO | jvm 1 | 2008/09/13 00:05:01 | at > > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) > > INFO | jvm 1 | 2008/09/13 00:05:01 | at > > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926) > > INFO | jvm 1 | 2008/09/13 00:05:01 | at > > com.mysql.jdbc.Util.handleNewInstance(Util.java:430) > > INFO | jvm 1 | 2008/09/13 00:05:01 | at > > com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:302) > > INFO | jvm 1 | 2008/09/13 00:05:01 | at > > > com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:282) > > INFO | jvm 1 | 2008/09/13 00:05:01 | at > > java.sql.DriverManager.getConnection(DriverManager.java:582) > > INFO | jvm 1 | 2008/09/13 00:05:01 | at > > java.sql.DriverManager.getConnection(DriverManager.java:185) > > > > (Below it my own functions exceptions - but this is a standard JDBC > > connector for MySQL). > > > > And this comes next (where I have function launching external process via > > exec function): > > > > INFO | jvm 1 | 2008/09/13 00:05:03 | java.lang.InterruptedException > > INFO | jvm 1 | 2008/09/13 00:05:03 | at > > java.lang.Object.wait(Native Method) > > INFO | jvm 1 | 2008/09/13 00:05:03 | at > > java.lang.Object.wait(Object.java:485) > > INFO | jvm 1 | 2008/09/13 00:05:03 | at > > java.lang.UNIXProcess.waitFor(UNIXProcess.java:165) > > > > > > Any idea what different between the console and start modes, and why the > > basic functionality doesn't work in this mode? > > > > Regards. > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > > Build the coolest Linux based applications with Moblin SDK & win great > > prizes > > Grand prize is a trip for two to an Open Source event anywhere in the > world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2008-09-15 19:34:18
|
Shashidhar, The Wrapper launches the JVM with a command line generated from the Wrapper.conf. It does not do anything which would affect the way JBoss or any other application runs once it has been launched. My guess is that there are some differences between the wrapper.conf that you created and the default shell script that comes with JBoss. I would suggest setting the following property then comparing the output Java command line with the command line generated by your JBoss distribution. Most likely there is a system.property being passed in which is missing or has an incorrect value. wrapper.java.command.loglevel=INFO Another thing to check is the current working directory. The Wrapper forces the default working directory to the location of the wrapper binary. This may not be the same as what the JBoss script is working from. A third thing to check is the version of Java that is being run. You can see this by setting the wrapper.debug=true property. I have seen cases where due to path problems a different version of java was being run than was intended. Cheers, Leif On Mon, Sep 15, 2008 at 6:56 PM, Shashidhar Gaurav Misra <Sha...@ar...> wrote: > Hi, > > > > I am using the Java service wrapper community version 3.3.0 (32-bit) for > running my application as a Unix daemon on a Solaris machine. > > My application is a Jboss server with some services deployed and running. > > > > OS Details > > 64-bit sparcv9 > > > > My problem is that the wrapper is not able to deploy a spring descriptor. I > am getting following error when I am trying to start my Jboss server. > > > > INFO | jvm 1 | 2008/08/07 05:04:24 | 05:04:23,771 ERROR [MainDeployer] > Could not create deployment: file:/usr/local/jbos > > s/server/default/deploy/deploy.last/Myservice.sar/Authentication.spring/ > > INFO | jvm 1 | 2008/08/07 05:04:24 | java.lang.NoClassDefFoundError: > org/springframework/beans/factory/ListableBeanFacto > > ry > > > > I have my spring descriptor under > > /usr/local/jboss/server/default/deploy/deploy.last/ Myservice.sar > /Authentication.spring/META-INF > > > > My spring jars are present under > > /usr/local/jboss/server/default/deploy/jboss-spring.deployer > > > > The same thing works for other OS for e.g. Linux, AIX etc > > > > > > Please suggest in case if I need to use some other version of the wrapper. > Is there any workaround for this? > > > > Thanks & Regards > > Shashidhar > > ________________________________ > "DISCLAIMER: This message is proprietary to Aricent and is intended solely > for the use of the individual to whom it is addressed. It may contain > privileged or confidential information and should not be circulated or used > for any purpose other than for what it is intended. If you have received > this message in error,please notify the originator immediately. If you are > not the intended recipient, you are notified that you are strictly > prohibited from using, copying, altering, or disclosing the contents of this > message. Aricent accepts no responsibility for loss or damage arising from > the use of the information transmitted by this email including damage from > virus." > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: Leif M. <le...@ta...> - 2008-09-15 19:27:04
|
Stas, What platform and version are you running on? I see a reference to a UNIXProcess so I assume it is not Windows. On UNIX versions, there is really no difference in the way the Wrapper launches the JVM between running in Console or Started as a daemon process. There could be differences in the environment variables available to the Wrapper when it launches however. For example, the PATH, or LD_LIBRARY_PATH. There could also be file permission issues if they are not being run as the same user. Either way however, the Wrapper and JVM appear to be working. Most likely something in the application is failing for one of the above reasons which is leading to it being in an unstable state, thus causing the exceptions. As these appear to be JDBC driver related, I would guess that maybe a native component of your driver is failing to load. Does MySQL have a native driver? I have used the pure Java driver. I tried Googling and found your question but not much else. I would be happy to help out with more information. Cheers, Leif On Sat, Sep 13, 2008 at 7:11 PM, Stas Oskin <sta...@gm...> wrote: > Hi. > > I'm trying to get my app packaged in jar to work with the Java Wrapper, and > have set up all correctly.When I launch the service in console mode, all > works correctly. > > When I do the same with service mode - the service shuts down after a few > seconds, and has the following errors in the log: > > INFO | jvm 1 | 2008/09/13 00:05:01 | java.sql.SQLException: > java.lang.ThreadDeath > INFO | jvm 1 | 2008/09/13 00:05:01 | at > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) > INFO | jvm 1 | 2008/09/13 00:05:01 | at > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) > INFO | jvm 1 | 2008/09/13 00:05:01 | at > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926) > INFO | jvm 1 | 2008/09/13 00:05:01 | at > com.mysql.jdbc.Util.handleNewInstance(Util.java:430) > INFO | jvm 1 | 2008/09/13 00:05:01 | at > com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:302) > INFO | jvm 1 | 2008/09/13 00:05:01 | at > com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:282) > INFO | jvm 1 | 2008/09/13 00:05:01 | at > java.sql.DriverManager.getConnection(DriverManager.java:582) > INFO | jvm 1 | 2008/09/13 00:05:01 | at > java.sql.DriverManager.getConnection(DriverManager.java:185) > > (Below it my own functions exceptions - but this is a standard JDBC > connector for MySQL). > > And this comes next (where I have function launching external process via > exec function): > > INFO | jvm 1 | 2008/09/13 00:05:03 | java.lang.InterruptedException > INFO | jvm 1 | 2008/09/13 00:05:03 | at > java.lang.Object.wait(Native Method) > INFO | jvm 1 | 2008/09/13 00:05:03 | at > java.lang.Object.wait(Object.java:485) > INFO | jvm 1 | 2008/09/13 00:05:03 | at > java.lang.UNIXProcess.waitFor(UNIXProcess.java:165) > > > Any idea what different between the console and start modes, and why the > basic functionality doesn't work in this mode? > > Regards. > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: Stas O. <sta...@gm...> - 2008-09-15 16:45:41
|
Hello. Can anyone advice on this issue? I need to resolve it ASAP. Regards. ---------- Forwarded message ---------- From: Stas Oskin <sta...@gm...> Date: 2008/9/13 Subject: Jar works with console, throws exceptions when launched via start? To: wra...@li... Hi. I'm trying to get my app packaged in jar to work with the Java Wrapper, and have set up all correctly.When I launch the service in console mode, all works correctly. When I do the same with service mode - the service shuts down after a few seconds, and has the following errors in the log: INFO | jvm 1 | 2008/09/13 00:05:01 | java.sql.SQLException: java.lang.ThreadDeath INFO | jvm 1 | 2008/09/13 00:05:01 | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) INFO | jvm 1 | 2008/09/13 00:05:01 | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) INFO | jvm 1 | 2008/09/13 00:05:01 | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926) INFO | jvm 1 | 2008/09/13 00:05:01 | at com.mysql.jdbc.Util.handleNewInstance(Util.java:430) INFO | jvm 1 | 2008/09/13 00:05:01 | at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:302) INFO | jvm 1 | 2008/09/13 00:05:01 | at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:282) INFO | jvm 1 | 2008/09/13 00:05:01 | at java.sql.DriverManager.getConnection(DriverManager.java:582) INFO | jvm 1 | 2008/09/13 00:05:01 | at java.sql.DriverManager.getConnection(DriverManager.java:185) (Below it my own functions exceptions - but this is a standard JDBC connector for MySQL). And this comes next (where I have function launching external process via exec function): INFO | jvm 1 | 2008/09/13 00:05:03 | java.lang.InterruptedException INFO | jvm 1 | 2008/09/13 00:05:03 | at java.lang.Object.wait(Native Method) INFO | jvm 1 | 2008/09/13 00:05:03 | at java.lang.Object.wait(Object.java:485) INFO | jvm 1 | 2008/09/13 00:05:03 | at java.lang.UNIXProcess.waitFor(UNIXProcess.java:165) Any idea what different between the console and start modes, and why the basic functionality doesn't work in this mode? Regards. |
|
From: Shashidhar G. M. <Sha...@ar...> - 2008-09-15 09:56:53
|
Hi, I am using the Java service wrapper community version 3.3.0 (32-bit) for running my application as a Unix daemon on a Solaris machine. My application is a Jboss server with some services deployed and running. OS Details 64-bit sparcv9 My problem is that the wrapper is not able to deploy a spring descriptor. I am getting following error when I am trying to start my Jboss server. INFO | jvm 1 | 2008/08/07 05:04:24 | 05:04:23,771 ERROR [MainDeployer] Could not create deployment: file:/usr/local/jbos s/server/default/deploy/deploy.last/Myservice.sar/Authentication.spring/ INFO | jvm 1 | 2008/08/07 05:04:24 | java.lang.NoClassDefFoundError: org/springframework/beans/factory/ListableBeanFacto ry I have my spring descriptor under /usr/local/jboss/server/default/deploy/deploy.last/ Myservice.sar /Authentication.spring/META-INF My spring jars are present under /usr/local/jboss/server/default/deploy/jboss-spring.deployer The same thing works for other OS for e.g. Linux, AIX etc Please suggest in case if I need to use some other version of the wrapper. Is there any workaround for this? Thanks & Regards Shashidhar ________________________________ "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." |
|
From: Stas O. <sta...@gm...> - 2008-09-13 10:11:57
|
Hi. I'm trying to get my app packaged in jar to work with the Java Wrapper, and have set up all correctly.When I launch the service in console mode, all works correctly. When I do the same with service mode - the service shuts down after a few seconds, and has the following errors in the log: INFO | jvm 1 | 2008/09/13 00:05:01 | java.sql.SQLException: java.lang.ThreadDeath INFO | jvm 1 | 2008/09/13 00:05:01 | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) INFO | jvm 1 | 2008/09/13 00:05:01 | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) INFO | jvm 1 | 2008/09/13 00:05:01 | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926) INFO | jvm 1 | 2008/09/13 00:05:01 | at com.mysql.jdbc.Util.handleNewInstance(Util.java:430) INFO | jvm 1 | 2008/09/13 00:05:01 | at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:302) INFO | jvm 1 | 2008/09/13 00:05:01 | at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:282) INFO | jvm 1 | 2008/09/13 00:05:01 | at java.sql.DriverManager.getConnection(DriverManager.java:582) INFO | jvm 1 | 2008/09/13 00:05:01 | at java.sql.DriverManager.getConnection(DriverManager.java:185) (Below it my own functions exceptions - but this is a standard JDBC connector for MySQL). And this comes next (where I have function launching external process via exec function): INFO | jvm 1 | 2008/09/13 00:05:03 | java.lang.InterruptedException INFO | jvm 1 | 2008/09/13 00:05:03 | at java.lang.Object.wait(Native Method) INFO | jvm 1 | 2008/09/13 00:05:03 | at java.lang.Object.wait(Object.java:485) INFO | jvm 1 | 2008/09/13 00:05:03 | at java.lang.UNIXProcess.waitFor(UNIXProcess.java:165) Any idea what different between the console and start modes, and why the basic functionality doesn't work in this mode? Regards. |
|
From: Laurent C. <Lau...@jp...> - 2008-09-13 08:09:00
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Hi Leif,<br> <br> I apologize for the late answer.<br> The second option (launching the second process under the wrapper) is the one that works best for me.<br> I really appreciate your help, thanks a lot!<br> <br> -Laurent<br> <br> Leif Mortenson wrote: <blockquote cite="mid:c0a...@ma..." type="cite"> <pre wrap="">Laurent, In your setup, JVM A is being launched by the Wrapper and protected from the logout signal using its JNI native library. JVM B is just a standalone JVM and will thus exit when it gets the logout signal. Would it be possible for you to create a second Service for JVM B running under the Wrapper which is setup to launch manually? Then when the timing is correct, JVM A can start or stop the JVM B service using the WrapperManager.sendServiceControlCode method. <a class="moz-txt-link-freetext" href="http://wrapper.tanukisoftware.org/doc/english/javadocs.html">http://wrapper.tanukisoftware.org/doc/english/javadocs.html</a> You would also want to make JVM B dependent on JVM A so it would always be stopped if JVM A was stopped. Does this sound like it would work? Another option would be to simply launch JVM B under the wrapper rather than launching JVM B directly. If you do this, you will want to set the following property which was added for this specific case where the Wrapper was launched from another service but is not a service itself. <a class="moz-txt-link-freetext" href="http://wrapper.tanukisoftware.org/doc/english/prop-ignore-user-logoffs.html">http://wrapper.tanukisoftware.org/doc/english/prop-ignore-user-logoffs.html</a> Cheers, Leif On Sat, Sep 6, 2008 at 10:05 PM, Laurent Cohen <a class="moz-txt-link-rfc2396E" href="mailto:Lau...@jp..."><Lau...@jp...></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Hello, I am having an issue with a windows service stopping when the user logs out. I'm using Java Service Wrapper 3.3.1 (CE) on Windows XP sp2, Sun JDK 1.6_u4 Here's what happens: - my app is made in fact of 2 Java processes A and B - process A launches process B when it starts - process A starts a ServerSocket, accepts a connection from process B, then reads from that connection. this tells A when B is killed using Ctrl-C or the task manager, it also tells B when A is killed as well. In either case the other process stops - if B exits "normally", using a System.exit(x), A gets the exit code, if the code is 2 it restarts B, otherwise it exits as well. The goal of this is to enable a remote restart of process B from a JMX-enabled GUI - what I have noticed is that when I logout, then login again, the service is stopped, and I see a connection reset exception in the log of process A, which means that process B died somehow, thus getting process A to exit. Do you have any hints as to why the process B is killed when login out, and are there any configuration options I can use to prevent it? Thanks for your time, -Laurent --------------------------------- Laurent Cohen Visit JPPF at <a class="moz-txt-link-freetext" href="http://www.jppf.org">http://www.jppf.org</a> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world <a class="moz-txt-link-freetext" href="http://moblin-contest.org/redirect.php?banner_id=100&url=/">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a> _______________________________________________ Wrapper-user mailing list <a class="moz-txt-link-abbreviated" href="mailto:Wra...@li...">Wra...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/wrapper-user">https://lists.sourceforge.net/lists/listinfo/wrapper-user</a> </pre> </blockquote> <pre wrap=""><!----> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world <a class="moz-txt-link-freetext" href="http://moblin-contest.org/redirect.php?banner_id=100&url=/">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a> _______________________________________________ Wrapper-user mailing list <a class="moz-txt-link-abbreviated" href="mailto:Wra...@li...">Wra...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/wrapper-user">https://lists.sourceforge.net/lists/listinfo/wrapper-user</a> </pre> </blockquote> </body> </html> |
|
From: Amr A. A. <aa...@re...> - 2008-09-12 20:05:07
|
Hello, I've got a problem with getting my application to run on a Solaris machine. I've had no problem getting it to run on a linux machine. Basically, here's the error: Running xxx... ld.so.1: wrapper-solaris-sparc-32: fatal: libm.so.2: open failed: No such file or directory Killed So it can't find libm.so.2 A workaround I've found was to create a symlink to libm.so.1 I tried that and now get this message instead: Running xxx... Illegal Instruction - core dumped So, there seems to be a dependency on that math library that can't be satisfied with that symlink hack. Anyone have issues like this? Or has any suggestions? I can't seem to be able to find libm.so.2 to download online, so a link to that would be great, then I could at least just bundle it with the application. Thanks, Amr. -- Refractions Research Suite 300 - 1207 Douglas St Victoria, BC, V8W 2E7, Canada ph: (250) 383-3022 fax:(250) 383-2140 |
|
From: Leif M. <le...@ta...> - 2008-09-07 13:25:08
|
Laurent, In your setup, JVM A is being launched by the Wrapper and protected from the logout signal using its JNI native library. JVM B is just a standalone JVM and will thus exit when it gets the logout signal. Would it be possible for you to create a second Service for JVM B running under the Wrapper which is setup to launch manually? Then when the timing is correct, JVM A can start or stop the JVM B service using the WrapperManager.sendServiceControlCode method. http://wrapper.tanukisoftware.org/doc/english/javadocs.html You would also want to make JVM B dependent on JVM A so it would always be stopped if JVM A was stopped. Does this sound like it would work? Another option would be to simply launch JVM B under the wrapper rather than launching JVM B directly. If you do this, you will want to set the following property which was added for this specific case where the Wrapper was launched from another service but is not a service itself. http://wrapper.tanukisoftware.org/doc/english/prop-ignore-user-logoffs.html Cheers, Leif On Sat, Sep 6, 2008 at 10:05 PM, Laurent Cohen <Lau...@jp...> wrote: > Hello, > > I am having an issue with a windows service stopping when the user logs out. > > I'm using Java Service Wrapper 3.3.1 (CE) on Windows XP sp2, Sun JDK 1.6_u4 > Here's what happens: > - my app is made in fact of 2 Java processes A and B > - process A launches process B when it starts > - process A starts a ServerSocket, accepts a connection from process B, > then reads from that connection. > this tells A when B is killed using Ctrl-C or the task manager, it also > tells B when A is killed as well. In either case the other process stops > - if B exits "normally", using a System.exit(x), A gets the exit code, > if the code is 2 it restarts B, otherwise it exits as well. The goal of > this is to enable a remote restart of process B from a JMX-enabled GUI > - what I have noticed is that when I logout, then login again, the > service is stopped, and I see a connection reset exception in the log of > process A, which means that process B died somehow, thus getting process > A to exit. > > Do you have any hints as to why the process B is killed when login out, > and are there any configuration options I can use to prevent it? > > Thanks for your time, > -Laurent > > --------------------------------- > Laurent Cohen > Visit JPPF at http://www.jppf.org > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Laurent C. <Lau...@jp...> - 2008-09-06 13:05:09
|
Hello, I am having an issue with a windows service stopping when the user logs out. I'm using Java Service Wrapper 3.3.1 (CE) on Windows XP sp2, Sun JDK 1.6_u4 Here's what happens: - my app is made in fact of 2 Java processes A and B - process A launches process B when it starts - process A starts a ServerSocket, accepts a connection from process B, then reads from that connection. this tells A when B is killed using Ctrl-C or the task manager, it also tells B when A is killed as well. In either case the other process stops - if B exits "normally", using a System.exit(x), A gets the exit code, if the code is 2 it restarts B, otherwise it exits as well. The goal of this is to enable a remote restart of process B from a JMX-enabled GUI - what I have noticed is that when I logout, then login again, the service is stopped, and I see a connection reset exception in the log of process A, which means that process B died somehow, thus getting process A to exit. Do you have any hints as to why the process B is killed when login out, and are there any configuration options I can use to prevent it? Thanks for your time, -Laurent --------------------------------- Laurent Cohen Visit JPPF at http://www.jppf.org |
|
From: Leif M. <le...@ta...> - 2008-09-05 02:41:24
|
Dave, Ok glad you are using 3.3.1. The problem I was referring to would not affect the initial restart. But it might have been why the second JVM did not start up. If we can avoid the initial restart, then the startup timeout should not matter. Lets try setting it just to be safe however. wrapper.debug=true wrapper.ping.timeout=300 wrapper.startup.timeout=300 Are you able to identify which process is bogging down the machine? It can often be helpful to run that process with a nice level that allows other processes to get enough CPU to stay alive. Regardless, the debug log output should be very helpful in narrowing down the problem. Cheers, Leif On Fri, Sep 5, 2008 at 10:54 AM, David Hoffer <dho...@gm...> wrote: > It looks like I am already using 3.3.1. I have set wrapper.ping.timeout=60 > but I have not set wrapper.startup.timeout. What do you recommend I set > this to? > > Regarding the Linux server, I do suspect that it gets heavy CPU usage at > times. > > -Dave > > On Thu, Sep 4, 2008 at 5:50 PM, Leif Mortenson <le...@ta...> > wrote: >> >> David, >> What version of the Wrapper are you running? There was a bug in >> 3.3.0 where the JVM process was not always being killed correctly if >> it was found to be frozen. That might explain why the JVM was not >> restarting. You should try upgrading to 3.3.1 and see if that >> resolves the problem for you. >> http://wrapper.tanukisoftware.org/doc/english/release-notes.html >> >> Lengthening the wrapper.ping.timeout and wrapper.startup.timeout s >> would help if the problem is indeed CPU related. >> >> Cheers, >> Leif >> >> On Fri, Sep 5, 2008 at 8:19 AM, David Hoffer <dho...@gm...> wrote: >> > Leif, >> > >> > I have made the debug change to the conf file. Previously I had bumped >> > up >> > the timeout to 60 seconds so who knows it may not happen again. >> > >> > Ideally, since I have seen this happen twice now, is that I would like >> > an >> > auto retry/restart feature so that it will continually try to restart if >> > for >> > whatever reason it shuts down. Is this possible on Linux? >> > >> > -Dave >> > >> > On Thu, Sep 4, 2008 at 10:00 AM, Leif Mortenson >> > <le...@ta...> >> > wrote: >> >> >> >> David, >> >> Assuming that the Wrapper has been working correctly for a few days as >> >> you say, I am unsure as to what is happening here with just the >> >> information you provided. >> >> Could you please set the wrapper.debug=true property and reproduce >> >> this? Then send me the resulting full wrapper.log file to my email >> >> directly as it is large for the list. >> >> >> >> >From the log, the JVM appears to have frozen and was killed for some >> >> reason. When the Wrapper then attempts to relaunch the JVM process, >> >> it fails to start within 30 seconds. >> >> >> >> What is the status of your system when this happens? Is it possible >> >> that the system is being bogged down by another process? If the JVM >> >> is failing to receive any CPU for a long period of time, it could >> >> appear to be frozen. That would also explain why it would take a long >> >> time for the next JVM invocation to start up. In either case, there >> >> are timeouts which can be extended to avoid this problem. >> >> >> >> Cheers, >> >> Leif >> >> >> >> On Thu, Sep 4, 2008 at 11:47 AM, David Hoffer <dho...@gm...> >> >> wrote: >> >> > I am using the wrapper on Linux running as a daemon. For some reason >> >> > after >> >> > running for a while (few days) it shuts down. Here is the log: >> >> > >> >> > INFO | jvm 1 | 2008/08/31 15:22:52 | >> >> > -------------------------------------- >> >> > ERROR | wrapper | 2008/09/02 07:49:32 | JVM appears hung: Timed out >> >> > waiting for signal from JVM. >> >> > ERROR | wrapper | 2008/09/02 07:49:33 | JVM did not exit on >> >> > request, >> >> > terminated >> >> > STATUS | wrapper | 2008/09/02 07:49:40 | Launching a JVM... >> >> > ERROR | wrapper | 2008/09/02 07:50:10 | Startup failed: Timed out >> >> > waiting >> >> > for a signal from the JVM. >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | >> >> > >> >> > ------------------------------------------------------------------------ >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Advice: >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | The Wrapper consists of a >> >> > native >> >> > component as well as a set of classes >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | which run within the JVM >> >> > that >> >> > it >> >> > launches. The Java component of the >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper must be initialized >> >> > promptly after the JVM is launched or the >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper will timeout, as >> >> > just >> >> > happened. Most likely the main class >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | specified in the Wrapper >> >> > configuration file is not correctly initializing >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | the Wrapper classes: >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | >> >> > com.dhs.service.JavaServiceWrapperWebServiceLauncher >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | While it is possible to do >> >> > so >> >> > manually, the Wrapper ships with helper >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | classes to make this >> >> > initialization processes automatic. >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Please review the >> >> > integration >> >> > section of the Wrapper's documentation >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | for the various methods >> >> > which >> >> > can >> >> > be employed to launch an application >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | within the Wrapper: >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | >> >> > http://wrapper.tanukisoftware.org/doc/english/integrate.html >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | >> >> > >> >> > ------------------------------------------------------------------------ >> >> > ADVICE | wrapper | 2008/09/02 07:50:10 | >> >> > ERROR | wrapper | 2008/09/02 07:50:11 | JVM did not exit on >> >> > request, >> >> > terminated >> >> > STATUS | wrapper | 2008/09/02 07:50:11 | JVM received a signal >> >> > SIGKILL >> >> > (9). >> >> > STATUS | wrapper | 2008/09/02 07:50:16 | Launching a JVM... >> >> > ERROR | wrapper | 2008/09/02 07:50:46 | Startup failed: Timed out >> >> > waiting >> >> > for a signal from the JVM. >> >> > ADVICE | wrapper | 2008/09/02 07:50:46 | >> >> > >> >> > What may be causing this? I am not a Linux guur. I have used the >> >> > wrapper >> >> > on Windows with no issues. My code to handle controlEvents is: >> >> > >> >> > if (WrapperManager.isControlledByNativeWrapper()) { >> >> > // The Wrapper will take care of this event >> >> > } else { >> >> > // We are not being controlled by the Wrapper, so >> >> > // handle the event ourselves. >> >> > if ((event == WrapperManager.WRAPPER_CTRL_C_EVENT) || >> >> > (event >> >> > == WrapperManager.WRAPPER_CTRL_CLOSE_EVENT) || (event == >> >> > WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT)) { >> >> > log.warn("We are handling the received event >> >> > ourselves >> >> > and we are stopping the service"); >> >> > WrapperManager.stop(0); >> >> > } >> >> > } >> >> > >> >> > I am using the wrapper integrated, that is I implement >> >> > WrapperListener >> >> > interface. >> >> > >> >> > Since I am running as a daemon, I don't want this to ever shut down, >> >> > and >> >> > if >> >> > does for some reason I would like it to auto restart (don't know how >> >> > to >> >> > do >> >> > this on Linux). >> >> > >> >> > Why might I be getting these JVM appears hung: Timed out waiting for >> >> > signal >> >> > from JVM. errors? >> >> > >> >> > -Dave >> >> > >> >> > >> >> > >> >> > ------------------------------------------------------------------------- >> >> > This SF.Net email is sponsored by the Moblin Your Move Developer's >> >> > challenge >> >> > Build the coolest Linux based applications with Moblin SDK & win >> >> > great >> >> > prizes >> >> > Grand prize is a trip for two to an Open Source event anywhere in the >> >> > world >> >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> >> > _______________________________________________ >> >> > Wrapper-user mailing list >> >> > Wra...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > >> >> > >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> >> challenge >> >> Build the coolest Linux based applications with Moblin SDK & win great >> >> prizes >> >> Grand prize is a trip for two to an Open Source event anywhere in the >> >> world >> >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> >> _______________________________________________ >> >> Wrapper-user mailing list >> >> Wra...@li... >> >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> > >> > >> > >> > ------------------------------------------------------------------------- >> > This SF.Net email is sponsored by the Moblin Your Move Developer's >> > challenge >> > Build the coolest Linux based applications with Moblin SDK & win great >> > prizes >> > Grand prize is a trip for two to an Open Source event anywhere in the >> > world >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> > _______________________________________________ >> > Wrapper-user mailing list >> > Wra...@li... >> > https://lists.sourceforge.net/lists/listinfo/wrapper-user >> > >> > >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: David H. <dho...@gm...> - 2008-09-05 01:55:01
|
It looks like I am already using 3.3.1. I have set wrapper.ping.timeout=60 but I have not set wrapper.startup.timeout. What do you recommend I set this to? Regarding the Linux server, I do suspect that it gets heavy CPU usage at times. -Dave On Thu, Sep 4, 2008 at 5:50 PM, Leif Mortenson <le...@ta...>wrote: > David, > What version of the Wrapper are you running? There was a bug in > 3.3.0 where the JVM process was not always being killed correctly if > it was found to be frozen. That might explain why the JVM was not > restarting. You should try upgrading to 3.3.1 and see if that > resolves the problem for you. > http://wrapper.tanukisoftware.org/doc/english/release-notes.html > > Lengthening the wrapper.ping.timeout and wrapper.startup.timeout s > would help if the problem is indeed CPU related. > > Cheers, > Leif > > On Fri, Sep 5, 2008 at 8:19 AM, David Hoffer <dho...@gm...> wrote: > > Leif, > > > > I have made the debug change to the conf file. Previously I had bumped > up > > the timeout to 60 seconds so who knows it may not happen again. > > > > Ideally, since I have seen this happen twice now, is that I would like an > > auto retry/restart feature so that it will continually try to restart if > for > > whatever reason it shuts down. Is this possible on Linux? > > > > -Dave > > > > On Thu, Sep 4, 2008 at 10:00 AM, Leif Mortenson <le...@ta... > > > > wrote: > >> > >> David, > >> Assuming that the Wrapper has been working correctly for a few days as > >> you say, I am unsure as to what is happening here with just the > >> information you provided. > >> Could you please set the wrapper.debug=true property and reproduce > >> this? Then send me the resulting full wrapper.log file to my email > >> directly as it is large for the list. > >> > >> >From the log, the JVM appears to have frozen and was killed for some > >> reason. When the Wrapper then attempts to relaunch the JVM process, > >> it fails to start within 30 seconds. > >> > >> What is the status of your system when this happens? Is it possible > >> that the system is being bogged down by another process? If the JVM > >> is failing to receive any CPU for a long period of time, it could > >> appear to be frozen. That would also explain why it would take a long > >> time for the next JVM invocation to start up. In either case, there > >> are timeouts which can be extended to avoid this problem. > >> > >> Cheers, > >> Leif > >> > >> On Thu, Sep 4, 2008 at 11:47 AM, David Hoffer <dho...@gm...> > wrote: > >> > I am using the wrapper on Linux running as a daemon. For some reason > >> > after > >> > running for a while (few days) it shuts down. Here is the log: > >> > > >> > INFO | jvm 1 | 2008/08/31 15:22:52 | > >> > -------------------------------------- > >> > ERROR | wrapper | 2008/09/02 07:49:32 | JVM appears hung: Timed out > >> > waiting for signal from JVM. > >> > ERROR | wrapper | 2008/09/02 07:49:33 | JVM did not exit on request, > >> > terminated > >> > STATUS | wrapper | 2008/09/02 07:49:40 | Launching a JVM... > >> > ERROR | wrapper | 2008/09/02 07:50:10 | Startup failed: Timed out > >> > waiting > >> > for a signal from the JVM. > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | > >> > > ------------------------------------------------------------------------ > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Advice: > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | The Wrapper consists of a > >> > native > >> > component as well as a set of classes > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | which run within the JVM > that > >> > it > >> > launches. The Java component of the > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper must be initialized > >> > promptly after the JVM is launched or the > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper will timeout, as > just > >> > happened. Most likely the main class > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | specified in the Wrapper > >> > configuration file is not correctly initializing > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | the Wrapper classes: > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | > >> > com.dhs.service.JavaServiceWrapperWebServiceLauncher > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | While it is possible to do > so > >> > manually, the Wrapper ships with helper > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | classes to make this > >> > initialization processes automatic. > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Please review the > integration > >> > section of the Wrapper's documentation > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | for the various methods > which > >> > can > >> > be employed to launch an application > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | within the Wrapper: > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | > >> > http://wrapper.tanukisoftware.org/doc/english/integrate.html > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | > >> > > ------------------------------------------------------------------------ > >> > ADVICE | wrapper | 2008/09/02 07:50:10 | > >> > ERROR | wrapper | 2008/09/02 07:50:11 | JVM did not exit on request, > >> > terminated > >> > STATUS | wrapper | 2008/09/02 07:50:11 | JVM received a signal > SIGKILL > >> > (9). > >> > STATUS | wrapper | 2008/09/02 07:50:16 | Launching a JVM... > >> > ERROR | wrapper | 2008/09/02 07:50:46 | Startup failed: Timed out > >> > waiting > >> > for a signal from the JVM. > >> > ADVICE | wrapper | 2008/09/02 07:50:46 | > >> > > >> > What may be causing this? I am not a Linux guur. I have used the > >> > wrapper > >> > on Windows with no issues. My code to handle controlEvents is: > >> > > >> > if (WrapperManager.isControlledByNativeWrapper()) { > >> > // The Wrapper will take care of this event > >> > } else { > >> > // We are not being controlled by the Wrapper, so > >> > // handle the event ourselves. > >> > if ((event == WrapperManager.WRAPPER_CTRL_C_EVENT) || > >> > (event > >> > == WrapperManager.WRAPPER_CTRL_CLOSE_EVENT) || (event == > >> > WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT)) { > >> > log.warn("We are handling the received event > >> > ourselves > >> > and we are stopping the service"); > >> > WrapperManager.stop(0); > >> > } > >> > } > >> > > >> > I am using the wrapper integrated, that is I implement WrapperListener > >> > interface. > >> > > >> > Since I am running as a daemon, I don't want this to ever shut down, > and > >> > if > >> > does for some reason I would like it to auto restart (don't know how > to > >> > do > >> > this on Linux). > >> > > >> > Why might I be getting these JVM appears hung: Timed out waiting for > >> > signal > >> > from JVM. errors? > >> > > >> > -Dave > >> > > >> > > >> > > ------------------------------------------------------------------------- > >> > This SF.Net email is sponsored by the Moblin Your Move Developer's > >> > challenge > >> > Build the coolest Linux based applications with Moblin SDK & win great > >> > prizes > >> > Grand prize is a trip for two to an Open Source event anywhere in the > >> > world > >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >> > _______________________________________________ > >> > Wrapper-user mailing list > >> > Wra...@li... > >> > https://lists.sourceforge.net/lists/listinfo/wrapper-user > >> > > >> > > >> > >> > ------------------------------------------------------------------------- > >> This SF.Net email is sponsored by the Moblin Your Move Developer's > >> challenge > >> Build the coolest Linux based applications with Moblin SDK & win great > >> prizes > >> Grand prize is a trip for two to an Open Source event anywhere in the > >> world > >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >> _______________________________________________ > >> Wrapper-user mailing list > >> Wra...@li... > >> https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > > Build the coolest Linux based applications with Moblin SDK & win great > > prizes > > Grand prize is a trip for two to an Open Source event anywhere in the > world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2008-09-04 23:50:48
|
David, What version of the Wrapper are you running? There was a bug in 3.3.0 where the JVM process was not always being killed correctly if it was found to be frozen. That might explain why the JVM was not restarting. You should try upgrading to 3.3.1 and see if that resolves the problem for you. http://wrapper.tanukisoftware.org/doc/english/release-notes.html Lengthening the wrapper.ping.timeout and wrapper.startup.timeout s would help if the problem is indeed CPU related. Cheers, Leif On Fri, Sep 5, 2008 at 8:19 AM, David Hoffer <dho...@gm...> wrote: > Leif, > > I have made the debug change to the conf file. Previously I had bumped up > the timeout to 60 seconds so who knows it may not happen again. > > Ideally, since I have seen this happen twice now, is that I would like an > auto retry/restart feature so that it will continually try to restart if for > whatever reason it shuts down. Is this possible on Linux? > > -Dave > > On Thu, Sep 4, 2008 at 10:00 AM, Leif Mortenson <le...@ta...> > wrote: >> >> David, >> Assuming that the Wrapper has been working correctly for a few days as >> you say, I am unsure as to what is happening here with just the >> information you provided. >> Could you please set the wrapper.debug=true property and reproduce >> this? Then send me the resulting full wrapper.log file to my email >> directly as it is large for the list. >> >> >From the log, the JVM appears to have frozen and was killed for some >> reason. When the Wrapper then attempts to relaunch the JVM process, >> it fails to start within 30 seconds. >> >> What is the status of your system when this happens? Is it possible >> that the system is being bogged down by another process? If the JVM >> is failing to receive any CPU for a long period of time, it could >> appear to be frozen. That would also explain why it would take a long >> time for the next JVM invocation to start up. In either case, there >> are timeouts which can be extended to avoid this problem. >> >> Cheers, >> Leif >> >> On Thu, Sep 4, 2008 at 11:47 AM, David Hoffer <dho...@gm...> wrote: >> > I am using the wrapper on Linux running as a daemon. For some reason >> > after >> > running for a while (few days) it shuts down. Here is the log: >> > >> > INFO | jvm 1 | 2008/08/31 15:22:52 | >> > -------------------------------------- >> > ERROR | wrapper | 2008/09/02 07:49:32 | JVM appears hung: Timed out >> > waiting for signal from JVM. >> > ERROR | wrapper | 2008/09/02 07:49:33 | JVM did not exit on request, >> > terminated >> > STATUS | wrapper | 2008/09/02 07:49:40 | Launching a JVM... >> > ERROR | wrapper | 2008/09/02 07:50:10 | Startup failed: Timed out >> > waiting >> > for a signal from the JVM. >> > ADVICE | wrapper | 2008/09/02 07:50:10 | >> > ADVICE | wrapper | 2008/09/02 07:50:10 | >> > ------------------------------------------------------------------------ >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Advice: >> > ADVICE | wrapper | 2008/09/02 07:50:10 | The Wrapper consists of a >> > native >> > component as well as a set of classes >> > ADVICE | wrapper | 2008/09/02 07:50:10 | which run within the JVM that >> > it >> > launches. The Java component of the >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper must be initialized >> > promptly after the JVM is launched or the >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper will timeout, as just >> > happened. Most likely the main class >> > ADVICE | wrapper | 2008/09/02 07:50:10 | specified in the Wrapper >> > configuration file is not correctly initializing >> > ADVICE | wrapper | 2008/09/02 07:50:10 | the Wrapper classes: >> > ADVICE | wrapper | 2008/09/02 07:50:10 | >> > com.dhs.service.JavaServiceWrapperWebServiceLauncher >> > ADVICE | wrapper | 2008/09/02 07:50:10 | While it is possible to do so >> > manually, the Wrapper ships with helper >> > ADVICE | wrapper | 2008/09/02 07:50:10 | classes to make this >> > initialization processes automatic. >> > ADVICE | wrapper | 2008/09/02 07:50:10 | Please review the integration >> > section of the Wrapper's documentation >> > ADVICE | wrapper | 2008/09/02 07:50:10 | for the various methods which >> > can >> > be employed to launch an application >> > ADVICE | wrapper | 2008/09/02 07:50:10 | within the Wrapper: >> > ADVICE | wrapper | 2008/09/02 07:50:10 | >> > http://wrapper.tanukisoftware.org/doc/english/integrate.html >> > ADVICE | wrapper | 2008/09/02 07:50:10 | >> > ------------------------------------------------------------------------ >> > ADVICE | wrapper | 2008/09/02 07:50:10 | >> > ERROR | wrapper | 2008/09/02 07:50:11 | JVM did not exit on request, >> > terminated >> > STATUS | wrapper | 2008/09/02 07:50:11 | JVM received a signal SIGKILL >> > (9). >> > STATUS | wrapper | 2008/09/02 07:50:16 | Launching a JVM... >> > ERROR | wrapper | 2008/09/02 07:50:46 | Startup failed: Timed out >> > waiting >> > for a signal from the JVM. >> > ADVICE | wrapper | 2008/09/02 07:50:46 | >> > >> > What may be causing this? I am not a Linux guur. I have used the >> > wrapper >> > on Windows with no issues. My code to handle controlEvents is: >> > >> > if (WrapperManager.isControlledByNativeWrapper()) { >> > // The Wrapper will take care of this event >> > } else { >> > // We are not being controlled by the Wrapper, so >> > // handle the event ourselves. >> > if ((event == WrapperManager.WRAPPER_CTRL_C_EVENT) || >> > (event >> > == WrapperManager.WRAPPER_CTRL_CLOSE_EVENT) || (event == >> > WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT)) { >> > log.warn("We are handling the received event >> > ourselves >> > and we are stopping the service"); >> > WrapperManager.stop(0); >> > } >> > } >> > >> > I am using the wrapper integrated, that is I implement WrapperListener >> > interface. >> > >> > Since I am running as a daemon, I don't want this to ever shut down, and >> > if >> > does for some reason I would like it to auto restart (don't know how to >> > do >> > this on Linux). >> > >> > Why might I be getting these JVM appears hung: Timed out waiting for >> > signal >> > from JVM. errors? >> > >> > -Dave >> > >> > >> > ------------------------------------------------------------------------- >> > This SF.Net email is sponsored by the Moblin Your Move Developer's >> > challenge >> > Build the coolest Linux based applications with Moblin SDK & win great >> > prizes >> > Grand prize is a trip for two to an Open Source event anywhere in the >> > world >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> > _______________________________________________ >> > Wrapper-user mailing list >> > Wra...@li... >> > https://lists.sourceforge.net/lists/listinfo/wrapper-user >> > >> > >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: David H. <dho...@gm...> - 2008-09-04 23:19:45
|
Leif, I have made the debug change to the conf file. Previously I had bumped up the timeout to 60 seconds so who knows it may not happen again. Ideally, since I have seen this happen twice now, is that I would like an auto retry/restart feature so that it will continually try to restart if for whatever reason it shuts down. Is this possible on Linux? -Dave On Thu, Sep 4, 2008 at 10:00 AM, Leif Mortenson <le...@ta...>wrote: > David, > Assuming that the Wrapper has been working correctly for a few days as > you say, I am unsure as to what is happening here with just the > information you provided. > Could you please set the wrapper.debug=true property and reproduce > this? Then send me the resulting full wrapper.log file to my email > directly as it is large for the list. > > >From the log, the JVM appears to have frozen and was killed for some > reason. When the Wrapper then attempts to relaunch the JVM process, > it fails to start within 30 seconds. > > What is the status of your system when this happens? Is it possible > that the system is being bogged down by another process? If the JVM > is failing to receive any CPU for a long period of time, it could > appear to be frozen. That would also explain why it would take a long > time for the next JVM invocation to start up. In either case, there > are timeouts which can be extended to avoid this problem. > > Cheers, > Leif > > On Thu, Sep 4, 2008 at 11:47 AM, David Hoffer <dho...@gm...> wrote: > > I am using the wrapper on Linux running as a daemon. For some reason > after > > running for a while (few days) it shuts down. Here is the log: > > > > INFO | jvm 1 | 2008/08/31 15:22:52 | > > -------------------------------------- > > ERROR | wrapper | 2008/09/02 07:49:32 | JVM appears hung: Timed out > > waiting for signal from JVM. > > ERROR | wrapper | 2008/09/02 07:49:33 | JVM did not exit on request, > > terminated > > STATUS | wrapper | 2008/09/02 07:49:40 | Launching a JVM... > > ERROR | wrapper | 2008/09/02 07:50:10 | Startup failed: Timed out > waiting > > for a signal from the JVM. > > ADVICE | wrapper | 2008/09/02 07:50:10 | > > ADVICE | wrapper | 2008/09/02 07:50:10 | > > ------------------------------------------------------------------------ > > ADVICE | wrapper | 2008/09/02 07:50:10 | Advice: > > ADVICE | wrapper | 2008/09/02 07:50:10 | The Wrapper consists of a > native > > component as well as a set of classes > > ADVICE | wrapper | 2008/09/02 07:50:10 | which run within the JVM that > it > > launches. The Java component of the > > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper must be initialized > > promptly after the JVM is launched or the > > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper will timeout, as just > > happened. Most likely the main class > > ADVICE | wrapper | 2008/09/02 07:50:10 | specified in the Wrapper > > configuration file is not correctly initializing > > ADVICE | wrapper | 2008/09/02 07:50:10 | the Wrapper classes: > > ADVICE | wrapper | 2008/09/02 07:50:10 | > > com.dhs.service.JavaServiceWrapperWebServiceLauncher > > ADVICE | wrapper | 2008/09/02 07:50:10 | While it is possible to do so > > manually, the Wrapper ships with helper > > ADVICE | wrapper | 2008/09/02 07:50:10 | classes to make this > > initialization processes automatic. > > ADVICE | wrapper | 2008/09/02 07:50:10 | Please review the integration > > section of the Wrapper's documentation > > ADVICE | wrapper | 2008/09/02 07:50:10 | for the various methods which > can > > be employed to launch an application > > ADVICE | wrapper | 2008/09/02 07:50:10 | within the Wrapper: > > ADVICE | wrapper | 2008/09/02 07:50:10 | > > http://wrapper.tanukisoftware.org/doc/english/integrate.html > > ADVICE | wrapper | 2008/09/02 07:50:10 | > > ------------------------------------------------------------------------ > > ADVICE | wrapper | 2008/09/02 07:50:10 | > > ERROR | wrapper | 2008/09/02 07:50:11 | JVM did not exit on request, > > terminated > > STATUS | wrapper | 2008/09/02 07:50:11 | JVM received a signal SIGKILL > (9). > > STATUS | wrapper | 2008/09/02 07:50:16 | Launching a JVM... > > ERROR | wrapper | 2008/09/02 07:50:46 | Startup failed: Timed out > waiting > > for a signal from the JVM. > > ADVICE | wrapper | 2008/09/02 07:50:46 | > > > > What may be causing this? I am not a Linux guur. I have used the > wrapper > > on Windows with no issues. My code to handle controlEvents is: > > > > if (WrapperManager.isControlledByNativeWrapper()) { > > // The Wrapper will take care of this event > > } else { > > // We are not being controlled by the Wrapper, so > > // handle the event ourselves. > > if ((event == WrapperManager.WRAPPER_CTRL_C_EVENT) || > (event > > == WrapperManager.WRAPPER_CTRL_CLOSE_EVENT) || (event == > > WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT)) { > > log.warn("We are handling the received event > ourselves > > and we are stopping the service"); > > WrapperManager.stop(0); > > } > > } > > > > I am using the wrapper integrated, that is I implement WrapperListener > > interface. > > > > Since I am running as a daemon, I don't want this to ever shut down, and > if > > does for some reason I would like it to auto restart (don't know how to > do > > this on Linux). > > > > Why might I be getting these JVM appears hung: Timed out waiting for > signal > > from JVM. errors? > > > > -Dave > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > > Build the coolest Linux based applications with Moblin SDK & win great > > prizes > > Grand prize is a trip for two to an Open Source event anywhere in the > world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Nicholas D. <nd...@gm...> - 2008-09-04 16:24:32
|
We've seen this behavior using a certain version of Sun's 1.5 JVM, which had
a bug that caused the JVM to chew on the processor for longer than the
wrapper would tolerate. We're using 1.5.10 now, the version in which the
following bug was fixed:
http://bugs.sun.com/view_bug.do?bug_id=6433335
Regrads,
Nick
On Thu, Sep 4, 2008 at 10:00 AM, Leif Mortenson <le...@ta...>wrote:
> David,
> Assuming that the Wrapper has been working correctly for a few days as
> you say, I am unsure as to what is happening here with just the
> information you provided.
> Could you please set the wrapper.debug=true property and reproduce
> this? Then send me the resulting full wrapper.log file to my email
> directly as it is large for the list.
>
> >From the log, the JVM appears to have frozen and was killed for some
> reason. When the Wrapper then attempts to relaunch the JVM process,
> it fails to start within 30 seconds.
>
> What is the status of your system when this happens? Is it possible
> that the system is being bogged down by another process? If the JVM
> is failing to receive any CPU for a long period of time, it could
> appear to be frozen. That would also explain why it would take a long
> time for the next JVM invocation to start up. In either case, there
> are timeouts which can be extended to avoid this problem.
>
> Cheers,
> Leif
>
> On Thu, Sep 4, 2008 at 11:47 AM, David Hoffer <dho...@gm...> wrote:
> > I am using the wrapper on Linux running as a daemon. For some reason
> after
> > running for a while (few days) it shuts down. Here is the log:
> >
> > INFO | jvm 1 | 2008/08/31 15:22:52 |
> > --------------------------------------
> > ERROR | wrapper | 2008/09/02 07:49:32 | JVM appears hung: Timed out
> > waiting for signal from JVM.
> > ERROR | wrapper | 2008/09/02 07:49:33 | JVM did not exit on request,
> > terminated
> > STATUS | wrapper | 2008/09/02 07:49:40 | Launching a JVM...
> > ERROR | wrapper | 2008/09/02 07:50:10 | Startup failed: Timed out
> waiting
> > for a signal from the JVM.
> > ADVICE | wrapper | 2008/09/02 07:50:10 |
> > ADVICE | wrapper | 2008/09/02 07:50:10 |
> > ------------------------------------------------------------------------
> > ADVICE | wrapper | 2008/09/02 07:50:10 | Advice:
> > ADVICE | wrapper | 2008/09/02 07:50:10 | The Wrapper consists of a
> native
> > component as well as a set of classes
> > ADVICE | wrapper | 2008/09/02 07:50:10 | which run within the JVM that
> it
> > launches. The Java component of the
> > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper must be initialized
> > promptly after the JVM is launched or the
> > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper will timeout, as just
> > happened. Most likely the main class
> > ADVICE | wrapper | 2008/09/02 07:50:10 | specified in the Wrapper
> > configuration file is not correctly initializing
> > ADVICE | wrapper | 2008/09/02 07:50:10 | the Wrapper classes:
> > ADVICE | wrapper | 2008/09/02 07:50:10 |
> > com.dhs.service.JavaServiceWrapperWebServiceLauncher
> > ADVICE | wrapper | 2008/09/02 07:50:10 | While it is possible to do so
> > manually, the Wrapper ships with helper
> > ADVICE | wrapper | 2008/09/02 07:50:10 | classes to make this
> > initialization processes automatic.
> > ADVICE | wrapper | 2008/09/02 07:50:10 | Please review the integration
> > section of the Wrapper's documentation
> > ADVICE | wrapper | 2008/09/02 07:50:10 | for the various methods which
> can
> > be employed to launch an application
> > ADVICE | wrapper | 2008/09/02 07:50:10 | within the Wrapper:
> > ADVICE | wrapper | 2008/09/02 07:50:10 |
> > http://wrapper.tanukisoftware.org/doc/english/integrate.html
> > ADVICE | wrapper | 2008/09/02 07:50:10 |
> > ------------------------------------------------------------------------
> > ADVICE | wrapper | 2008/09/02 07:50:10 |
> > ERROR | wrapper | 2008/09/02 07:50:11 | JVM did not exit on request,
> > terminated
> > STATUS | wrapper | 2008/09/02 07:50:11 | JVM received a signal SIGKILL
> (9).
> > STATUS | wrapper | 2008/09/02 07:50:16 | Launching a JVM...
> > ERROR | wrapper | 2008/09/02 07:50:46 | Startup failed: Timed out
> waiting
> > for a signal from the JVM.
> > ADVICE | wrapper | 2008/09/02 07:50:46 |
> >
> > What may be causing this? I am not a Linux guur. I have used the
> wrapper
> > on Windows with no issues. My code to handle controlEvents is:
> >
> > if (WrapperManager.isControlledByNativeWrapper()) {
> > // The Wrapper will take care of this event
> > } else {
> > // We are not being controlled by the Wrapper, so
> > // handle the event ourselves.
> > if ((event == WrapperManager.WRAPPER_CTRL_C_EVENT) ||
> (event
> > == WrapperManager.WRAPPER_CTRL_CLOSE_EVENT) || (event ==
> > WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT)) {
> > log.warn("We are handling the received event
> ourselves
> > and we are stopping the service");
> > WrapperManager.stop(0);
> > }
> > }
> >
> > I am using the wrapper integrated, that is I implement WrapperListener
> > interface.
> >
> > Since I am running as a daemon, I don't want this to ever shut down, and
> if
> > does for some reason I would like it to auto restart (don't know how to
> do
> > this on Linux).
> >
> > Why might I be getting these JVM appears hung: Timed out waiting for
> signal
> > from JVM. errors?
> >
> > -Dave
> >
> > -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> > Build the coolest Linux based applications with Moblin SDK & win great
> > prizes
> > Grand prize is a trip for two to an Open Source event anywhere in the
> world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> >
> >
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
|
|
From: Leif M. <le...@ta...> - 2008-09-04 16:01:08
|
David, Assuming that the Wrapper has been working correctly for a few days as you say, I am unsure as to what is happening here with just the information you provided. Could you please set the wrapper.debug=true property and reproduce this? Then send me the resulting full wrapper.log file to my email directly as it is large for the list. >From the log, the JVM appears to have frozen and was killed for some reason. When the Wrapper then attempts to relaunch the JVM process, it fails to start within 30 seconds. What is the status of your system when this happens? Is it possible that the system is being bogged down by another process? If the JVM is failing to receive any CPU for a long period of time, it could appear to be frozen. That would also explain why it would take a long time for the next JVM invocation to start up. In either case, there are timeouts which can be extended to avoid this problem. Cheers, Leif On Thu, Sep 4, 2008 at 11:47 AM, David Hoffer <dho...@gm...> wrote: > I am using the wrapper on Linux running as a daemon. For some reason after > running for a while (few days) it shuts down. Here is the log: > > INFO | jvm 1 | 2008/08/31 15:22:52 | > -------------------------------------- > ERROR | wrapper | 2008/09/02 07:49:32 | JVM appears hung: Timed out > waiting for signal from JVM. > ERROR | wrapper | 2008/09/02 07:49:33 | JVM did not exit on request, > terminated > STATUS | wrapper | 2008/09/02 07:49:40 | Launching a JVM... > ERROR | wrapper | 2008/09/02 07:50:10 | Startup failed: Timed out waiting > for a signal from the JVM. > ADVICE | wrapper | 2008/09/02 07:50:10 | > ADVICE | wrapper | 2008/09/02 07:50:10 | > ------------------------------------------------------------------------ > ADVICE | wrapper | 2008/09/02 07:50:10 | Advice: > ADVICE | wrapper | 2008/09/02 07:50:10 | The Wrapper consists of a native > component as well as a set of classes > ADVICE | wrapper | 2008/09/02 07:50:10 | which run within the JVM that it > launches. The Java component of the > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper must be initialized > promptly after the JVM is launched or the > ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper will timeout, as just > happened. Most likely the main class > ADVICE | wrapper | 2008/09/02 07:50:10 | specified in the Wrapper > configuration file is not correctly initializing > ADVICE | wrapper | 2008/09/02 07:50:10 | the Wrapper classes: > ADVICE | wrapper | 2008/09/02 07:50:10 | > com.dhs.service.JavaServiceWrapperWebServiceLauncher > ADVICE | wrapper | 2008/09/02 07:50:10 | While it is possible to do so > manually, the Wrapper ships with helper > ADVICE | wrapper | 2008/09/02 07:50:10 | classes to make this > initialization processes automatic. > ADVICE | wrapper | 2008/09/02 07:50:10 | Please review the integration > section of the Wrapper's documentation > ADVICE | wrapper | 2008/09/02 07:50:10 | for the various methods which can > be employed to launch an application > ADVICE | wrapper | 2008/09/02 07:50:10 | within the Wrapper: > ADVICE | wrapper | 2008/09/02 07:50:10 | > http://wrapper.tanukisoftware.org/doc/english/integrate.html > ADVICE | wrapper | 2008/09/02 07:50:10 | > ------------------------------------------------------------------------ > ADVICE | wrapper | 2008/09/02 07:50:10 | > ERROR | wrapper | 2008/09/02 07:50:11 | JVM did not exit on request, > terminated > STATUS | wrapper | 2008/09/02 07:50:11 | JVM received a signal SIGKILL (9). > STATUS | wrapper | 2008/09/02 07:50:16 | Launching a JVM... > ERROR | wrapper | 2008/09/02 07:50:46 | Startup failed: Timed out waiting > for a signal from the JVM. > ADVICE | wrapper | 2008/09/02 07:50:46 | > > What may be causing this? I am not a Linux guur. I have used the wrapper > on Windows with no issues. My code to handle controlEvents is: > > if (WrapperManager.isControlledByNativeWrapper()) { > // The Wrapper will take care of this event > } else { > // We are not being controlled by the Wrapper, so > // handle the event ourselves. > if ((event == WrapperManager.WRAPPER_CTRL_C_EVENT) || (event > == WrapperManager.WRAPPER_CTRL_CLOSE_EVENT) || (event == > WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT)) { > log.warn("We are handling the received event ourselves > and we are stopping the service"); > WrapperManager.stop(0); > } > } > > I am using the wrapper integrated, that is I implement WrapperListener > interface. > > Since I am running as a daemon, I don't want this to ever shut down, and if > does for some reason I would like it to auto restart (don't know how to do > this on Linux). > > Why might I be getting these JVM appears hung: Timed out waiting for signal > from JVM. errors? > > -Dave > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: David H. <dho...@gm...> - 2008-09-04 02:48:00
|
I am using the wrapper on Linux running as a daemon. For some reason after running for a while (few days) it shuts down. Here is the log: INFO | jvm 1 | 2008/08/31 15:22:52 | -------------------------------------- ERROR | wrapper | 2008/09/02 07:49:32 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2008/09/02 07:49:33 | JVM did not exit on request, terminated STATUS | wrapper | 2008/09/02 07:49:40 | Launching a JVM... ERROR | wrapper | 2008/09/02 07:50:10 | Startup failed: Timed out waiting for a signal from the JVM. ADVICE | wrapper | 2008/09/02 07:50:10 | ADVICE | wrapper | 2008/09/02 07:50:10 | ------------------------------------------------------------------------ ADVICE | wrapper | 2008/09/02 07:50:10 | Advice: ADVICE | wrapper | 2008/09/02 07:50:10 | The Wrapper consists of a native component as well as a set of classes ADVICE | wrapper | 2008/09/02 07:50:10 | which run within the JVM that it launches. The Java component of the ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper must be initialized promptly after the JVM is launched or the ADVICE | wrapper | 2008/09/02 07:50:10 | Wrapper will timeout, as just happened. Most likely the main class ADVICE | wrapper | 2008/09/02 07:50:10 | specified in the Wrapper configuration file is not correctly initializing ADVICE | wrapper | 2008/09/02 07:50:10 | the Wrapper classes: ADVICE | wrapper | 2008/09/02 07:50:10 | com.dhs.service.JavaServiceWrapperWebServiceLauncher ADVICE | wrapper | 2008/09/02 07:50:10 | While it is possible to do so manually, the Wrapper ships with helper ADVICE | wrapper | 2008/09/02 07:50:10 | classes to make this initialization processes automatic. ADVICE | wrapper | 2008/09/02 07:50:10 | Please review the integration section of the Wrapper's documentation ADVICE | wrapper | 2008/09/02 07:50:10 | for the various methods which can be employed to launch an application ADVICE | wrapper | 2008/09/02 07:50:10 | within the Wrapper: ADVICE | wrapper | 2008/09/02 07:50:10 | http://wrapper.tanukisoftware.org/doc/english/integrate.html ADVICE | wrapper | 2008/09/02 07:50:10 | ------------------------------------------------------------------------ ADVICE | wrapper | 2008/09/02 07:50:10 | ERROR | wrapper | 2008/09/02 07:50:11 | JVM did not exit on request, terminated STATUS | wrapper | 2008/09/02 07:50:11 | JVM received a signal SIGKILL (9). STATUS | wrapper | 2008/09/02 07:50:16 | Launching a JVM... ERROR | wrapper | 2008/09/02 07:50:46 | Startup failed: Timed out waiting for a signal from the JVM. ADVICE | wrapper | 2008/09/02 07:50:46 | What may be causing this? I am not a Linux guur. I have used the wrapper on Windows with no issues. My code to handle controlEvents is: if (WrapperManager.isControlledByNativeWrapper()) { // The Wrapper will take care of this event } else { // We are not being controlled by the Wrapper, so // handle the event ourselves. if ((event == WrapperManager.WRAPPER_CTRL_C_EVENT) || (event == WrapperManager.WRAPPER_CTRL_CLOSE_EVENT) || (event == WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT)) { log.warn("We are handling the received event ourselves and we are stopping the service"); WrapperManager.stop(0); } } I am using the wrapper integrated, that is I implement WrapperListener interface. Since I am running as a daemon, I don't want this to ever shut down, and if does for some reason I would like it to auto restart (don't know how to do this on Linux). Why might I be getting these JVM appears hung: Timed out waiting for signal from JVM. errors? -Dave |
165 messages has been excluded from this view by a project administrator.
