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: Shashidhar G. M. <Sha...@ar...> - 2009-03-24 10:17:49
|
Thanks Leif...its done -----Original Message----- From: Leif Mortenson [mailto:lei...@ta...] Sent: Tuesday, March 24, 2009 3:33 PM To: wra...@li... Subject: Re: [Wrapper-user] FW: How to configure the jboss.bind.addressusingJava service wrapper Shashidhar, It is done by adding additional app parameters as follows: # Application parameters. Add parameters as needed starting from 1 wrapper.app.parameter.1=org.jboss.Main wrapper.app.parameter.2=-b wrapper.app.parameter.3=0.0.0.0 If you need to be able to pass the "0.0.0.0" parameter in from the command line, you will need to modify the shell scripts and bat files slightly so the wrapper is called as follows: wrapper.exe -c ../conf/wrapper.conf wrapper.app.parameter.3=0.0.0.0 Cheers, Leif 2009/3/24 Shashidhar Gaurav Misra <Sha...@ar...>: > Hi Leif, > > > > Thanks for the reply > > > > The output from the run.sh on running (./run.sh -b 0.0.0.0) > > /usr/java/jdk1.5.0_14/bin/java -Dprogram.name=run.sh -server -Xms128m > -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 > -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true > -Djava.endorsed.dirs=/home/jboss/lib/endorsed -classpath > /home/jboss/bin/run.jar:/usr/java/jdk1.5.0_14/lib/tools.jar org.jboss.Main > -b 0.0.0.0 > > > > So as you can see that -b 0.0.0.0 is passed as a command line option to > org.jboss.Main class. This is something which I don't think we can pass > through wrapper.conf. As whatever we pass in wrapper.conf will be passed as > an option to java and not to org.jboss.Main. > > > > Please suggest. > > Attached is my wrapper.conf. > > > > Shashidhar > > > > > > -----Original Message----- > From: Leif Mortenson [mailto:lei...@ta...] > Sent: Tuesday, March 24, 2009 2:55 PM > To: wra...@li... > Subject: Re: [Wrapper-user] FW: How to configure the jboss.bind.addressusing > Java service wrapper > > > > Shashidhar, > > First you need to see how JBoss's run.sh is converting that parameter > > into the Java command line. You can do this by echoing the output > > from the original run.sh script and running it. > > > > Then take the resulting java command line and modify the wrapper.conf > > file as appropriate. If you get the above and still have questions, > > please post the above java command line along with your existing > > wrapper.conf and I will help you with the changes. > > > > Cheers, > > Leif > > > > 2009/3/24 Shashidhar Gaurav Misra <Sha...@ar...>: > >> > >> > >> Hi, > >> > >> > >> > >> I am using method 1 to integrate my application (Jboss) with Java service > >> wrapper. I believe the wrapper doesn't internally calls the run.sh to >> start > >> the Jboss Server. > >> > >> Now my problem is that I want to configure the jboss.bind.address, I found > >> that it can be configured using the -b option to the Jboss startup script > >> (run.sh). For example, run -b 0.0.0.0 enables jboss to listen for > >> connections on all IP addresses of the machine. > >> > >> > >> > >> How should I pas this option when I am using the Java Service Wrapper? > >> > >> > >> > >> Please suggest. > >> > >> Shashi ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ 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: Leif M. <lei...@ta...> - 2009-03-24 10:03:12
|
Shashidhar, It is done by adding additional app parameters as follows: # Application parameters. Add parameters as needed starting from 1 wrapper.app.parameter.1=org.jboss.Main wrapper.app.parameter.2=-b wrapper.app.parameter.3=0.0.0.0 If you need to be able to pass the "0.0.0.0" parameter in from the command line, you will need to modify the shell scripts and bat files slightly so the wrapper is called as follows: wrapper.exe -c ../conf/wrapper.conf wrapper.app.parameter.3=0.0.0.0 Cheers, Leif 2009/3/24 Shashidhar Gaurav Misra <Sha...@ar...>: > Hi Leif, > > > > Thanks for the reply > > > > The output from the run.sh on running (./run.sh –b 0.0.0.0) > > /usr/java/jdk1.5.0_14/bin/java -Dprogram.name=run.sh -server -Xms128m > -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 > -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true > -Djava.endorsed.dirs=/home/jboss/lib/endorsed -classpath > /home/jboss/bin/run.jar:/usr/java/jdk1.5.0_14/lib/tools.jar org.jboss.Main > -b 0.0.0.0 > > > > So as you can see that -b 0.0.0.0 is passed as a command line option to > org.jboss.Main class. This is something which I don’t think we can pass > through wrapper.conf. As whatever we pass in wrapper.conf will be passed as > an option to java and not to org.jboss.Main. > > > > Please suggest. > > Attached is my wrapper.conf. > > > > Shashidhar > > > > > > -----Original Message----- > From: Leif Mortenson [mailto:lei...@ta...] > Sent: Tuesday, March 24, 2009 2:55 PM > To: wra...@li... > Subject: Re: [Wrapper-user] FW: How to configure the jboss.bind.addressusing > Java service wrapper > > > > Shashidhar, > > First you need to see how JBoss's run.sh is converting that parameter > > into the Java command line. You can do this by echoing the output > > from the original run.sh script and running it. > > > > Then take the resulting java command line and modify the wrapper.conf > > file as appropriate. If you get the above and still have questions, > > please post the above java command line along with your existing > > wrapper.conf and I will help you with the changes. > > > > Cheers, > > Leif > > > > 2009/3/24 Shashidhar Gaurav Misra <Sha...@ar...>: > >> > >> > >> Hi, > >> > >> > >> > >> I am using method 1 to integrate my application (Jboss) with Java service > >> wrapper. I believe the wrapper doesn’t internally calls the run.sh to >> start > >> the Jboss Server. > >> > >> Now my problem is that I want to configure the jboss.bind.address, I found > >> that it can be configured using the –b option to the Jboss startup script > >> (run.sh). For example, run -b 0.0.0.0 enables jboss to listen for > >> connections on all IP addresses of the machine. > >> > >> > >> > >> How should I pas this option when I am using the Java Service Wrapper? > >> > >> > >> > >> Please suggest. > >> > >> Shashi |
|
From: Leif M. <lei...@ta...> - 2009-03-24 09:58:41
|
Elias, 1) So you are specifying the Java to run in your wrapper.conf file so we are sure that it is always using the correct JVM? Just to rule out a particular problem in my mind, could you please set the wrapper.java.command.loglevel=INFO property in your wrapper.conf file and then post the generated command line when you run as a service? I want to make 100% sure that you are running the correct JVM. In your original post, your command line was this: --- "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" -Dwrapper.key="fREO9IxlyMDSknzk" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=4020 -Dwrapper.version="3.3.3" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 com.gvs.AXConnectorServer.AXConnectorServiceWin32 --- Notice that the java being run is not the same as when you run in a console. If this is still the case then this is most likely the cause of your problems. If your java command is specified as follows then it will searched for on the PATH. This is not very reliable. wrapper.java.command=java The PATH when run as a service will most likely be quite different. I strongly suggest using one of the following: wrapper.java.command=%JAVA_HOME%/bin/java This second option is most likely even better because it appears that your application includes its own JRE. The path is relative to the location of the wrapper.exe: wrapper.java.command=../jre/bin/java 2) Please post your wrapper.conf file as a an attachment. Cheers, Leif On Tue, Mar 24, 2009 at 1:50 AM, ejml <eli...@gm...> wrote: > > Sorry Leif, > > False Alarm, it still fails when it's configured like service. > > Greetings!!. > > ejml wrote: >> >> Hello Leif, >> >> My answers: >> >> 1) I have run the service in console mode with the command: wrapper.exe -c >> ../conf/wrapper.conf and it works fine. >> >> 2) The command that I use to run the application when it works is: >> >> "C:\Archivos de programa\Java\jre1.5.0_12\bin\java" >> -Djava.library.path="../lib" -classpath >> "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar;C:/Archivos >> de programa/jetty-6.1.3/lib/servlet-api-2.5-6.1.3.jar;C:/Archivos de >> programa/jacob-1.14/jacob.jar;C:/Archivos de >> programa/jetty-6.1.3/lib/jetty-6.1.3.jar;C:/Archivos de >> programa/jetty-6.1.3/lib/jetty-util-6.1.3.jar;C:/Archivos de >> programa/spring-framework-2.5.1/dist/spring.jar;C:/Archivos de >> programa/spring-framework-2.5.1/dist/modules/spring-context.jar;C:/Archivos >> de programa/spring-framework-2.5.1/dist/spring-test.jar;C:/Archivos de >> programa/spring-framework-2.5.1/lib/jakarta-commons/commons-logging.jar" >> com.gvs.AXConnectorServer.AXConnectorServiceWin32 >> >> This is the same effect that I execute: wrapper.exe -c >> ../conf/wrapper.conf >> >> 3) I don't find win32com.dll, I have searched in sun and RXTX and the new >> versions not contain win32com.dll. >> >> Thanks and greetings!!. >> >> Leif Mortenson-2 wrote: >>> >>> Elias, >>> Can you answer a few questions? >>> >>> 1) You have said that it fails when run as a service, but that it >>> works from the command line. Have you tried running under the >>> Wrapper in console mode? Ie by running as follows: wrapper.exe -c >>> ..¥conf¥wrapper.conf >>> What happens? >>> >>> 2) Please post the java command line you are using when it works, and >>> the one generated by the Wrapper. You can get the command line >>> generated by the Wrapper by running in debug mode or by setting >>> wrapper.java.command.loglevel=INFO >>> >>> 2) Have you seen the FAQ entry on this subject? >>> http://wrapper.tanukisoftware.org/doc/english/faq.html#4 >>> The win32com.dll needs to be on your java library path. By default, >>> Java searches the PATH, but when running under the Wrapper, this is >>> disabled because a library path is specified. It is necessary to add >>> the location of win32com.dll to your library path in the wrapper.conf >>> file. >>> >>> Cheers, >>> Leif >>> >>> 2009/3/20 Elías Manchón López <eli...@gm...>: >>>> Hi Leif, >>>> >>>> The problem was the creation of instance of the class wrap by >>>> WrapperListener. Now I haven't problem with the start of Service. But >>>> it's >>>> not work yet. I think that the problem is very difficult of resolve. >>>> Although my level of English not is very good, I will try to explain the >>>> better possible for if you can help me. >>>> >>>> My application is made with Spring Framework. This application use Jetty >>>> embedded to publish it through 8080 port and use the remote feature of >>>> Spring to the web server can do request to it. This application is >>>> communicated with my ERP throught COM+ and translate the request of web >>>> server to my ERP using JACOB >>>> (http://sourceforge.net/projects/jacob-project/). >>>> >>>> When I use Java Service Wrapper, I can see that I have problems with the >>>> Initialization of COM Object, and I get NullPointer to object >>>> instantiated >>>> with JACOB. I thought that problem was by permission on the COM of >>>> Microsoft, but I checked this issue and there isn't problems. As well >>>> as, If >>>> I run my application throught command line, with the same command that >>>> Java >>>> Service Wrapper and using the same jar packet, the curious is that it >>>> works >>>> fine. >>>> >>>> I don't know to think, I don't know if it is problem of COM+ or If it is >>>> problem of Java Service Wrapper?. Could you give me some indication?. >>>> >>>> Thanks again!!. >>>> 2009/3/18 Leif Mortenson <lei...@ta...> >>>>> >>>>> Elias, >>>>> What does the content of your WrapperListener.start method look like? >>>>> >>>>> If you create a new thread, it will be non-daemon unless you >>>>> specifically call the thread.setDaemon(true) method. If you are using >>>>> existing class to start your application then it will be more >>>>> difficult to check. One solution is to add a wait for 1 second at >>>>> the end of your start method then call >>>>> WrapperManager.requestThreadDump(). That will let you see all of your >>>>> threads as well as see easily which have their daemon flag set. >>>>> >>>>> Cheers, >>>>> Leif >>> >>> (snip) |
|
From: Leif M. <lei...@ta...> - 2009-03-24 09:25:03
|
Shashidhar, First you need to see how JBoss's run.sh is converting that parameter into the Java command line. You can do this by echoing the output from the original run.sh script and running it. Then take the resulting java command line and modify the wrapper.conf file as appropriate. If you get the above and still have questions, please post the above java command line along with your existing wrapper.conf and I will help you with the changes. Cheers, Leif 2009/3/24 Shashidhar Gaurav Misra <Sha...@ar...>: > > > Hi, > > > > I am using method 1 to integrate my application (Jboss) with Java service > wrapper. I believe the wrapper doesn’t internally calls the run.sh to start > the Jboss Server. > > Now my problem is that I want to configure the jboss.bind.address, I found > that it can be configured using the –b option to the Jboss startup script > (run.sh). For example, run -b 0.0.0.0 enables jboss to listen for > connections on all IP addresses of the machine. > > > > How should I pas this option when I am using the Java Service Wrapper? > > > > Please suggest. > > Shashi |
|
From: Shashidhar G. M. <Sha...@ar...> - 2009-03-24 08:53:20
|
Hi, I am using method 1 to integrate my application (Jboss) with Java service wrapper. I believe the wrapper doesn't internally calls the run.sh to start the Jboss Server. Now my problem is that I want to configure the jboss.bind.address, I found that it can be configured using the -b option to the Jboss startup script (run.sh). For example, run -b 0.0.0.0 enables jboss to listen for connections on all IP addresses of the machine. How should I pas this option when I am using the Java Service Wrapper? Please suggest. Shashi ________________________________ "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: ejml <eli...@gm...> - 2009-03-23 16:50:38
|
Sorry Leif, False Alarm, it still fails when it's configured like service. Greetings!!. ejml wrote: > > Hello Leif, > > My answers: > > 1) I have run the service in console mode with the command: wrapper.exe -c > ../conf/wrapper.conf and it works fine. > > 2) The command that I use to run the application when it works is: > > "C:\Archivos de programa\Java\jre1.5.0_12\bin\java" > -Djava.library.path="../lib" -classpath > "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar;C:/Archivos > de programa/jetty-6.1.3/lib/servlet-api-2.5-6.1.3.jar;C:/Archivos de > programa/jacob-1.14/jacob.jar;C:/Archivos de > programa/jetty-6.1.3/lib/jetty-6.1.3.jar;C:/Archivos de > programa/jetty-6.1.3/lib/jetty-util-6.1.3.jar;C:/Archivos de > programa/spring-framework-2.5.1/dist/spring.jar;C:/Archivos de > programa/spring-framework-2.5.1/dist/modules/spring-context.jar;C:/Archivos > de programa/spring-framework-2.5.1/dist/spring-test.jar;C:/Archivos de > programa/spring-framework-2.5.1/lib/jakarta-commons/commons-logging.jar" > com.gvs.AXConnectorServer.AXConnectorServiceWin32 > > This is the same effect that I execute: wrapper.exe -c > ../conf/wrapper.conf > > 3) I don't find win32com.dll, I have searched in sun and RXTX and the new > versions not contain win32com.dll. > > Thanks and greetings!!. > > Leif Mortenson-2 wrote: >> >> Elias, >> Can you answer a few questions? >> >> 1) You have said that it fails when run as a service, but that it >> works from the command line. Have you tried running under the >> Wrapper in console mode? Ie by running as follows: wrapper.exe -c >> ..¥conf¥wrapper.conf >> What happens? >> >> 2) Please post the java command line you are using when it works, and >> the one generated by the Wrapper. You can get the command line >> generated by the Wrapper by running in debug mode or by setting >> wrapper.java.command.loglevel=INFO >> >> 2) Have you seen the FAQ entry on this subject? >> http://wrapper.tanukisoftware.org/doc/english/faq.html#4 >> The win32com.dll needs to be on your java library path. By default, >> Java searches the PATH, but when running under the Wrapper, this is >> disabled because a library path is specified. It is necessary to add >> the location of win32com.dll to your library path in the wrapper.conf >> file. >> >> Cheers, >> Leif >> >> 2009/3/20 Elías Manchón López <eli...@gm...>: >>> Hi Leif, >>> >>> The problem was the creation of instance of the class wrap by >>> WrapperListener. Now I haven't problem with the start of Service. But >>> it's >>> not work yet. I think that the problem is very difficult of resolve. >>> Although my level of English not is very good, I will try to explain the >>> better possible for if you can help me. >>> >>> My application is made with Spring Framework. This application use Jetty >>> embedded to publish it through 8080 port and use the remote feature of >>> Spring to the web server can do request to it. This application is >>> communicated with my ERP throught COM+ and translate the request of web >>> server to my ERP using JACOB >>> (http://sourceforge.net/projects/jacob-project/). >>> >>> When I use Java Service Wrapper, I can see that I have problems with the >>> Initialization of COM Object, and I get NullPointer to object >>> instantiated >>> with JACOB. I thought that problem was by permission on the COM of >>> Microsoft, but I checked this issue and there isn't problems. As well >>> as, If >>> I run my application throught command line, with the same command that >>> Java >>> Service Wrapper and using the same jar packet, the curious is that it >>> works >>> fine. >>> >>> I don't know to think, I don't know if it is problem of COM+ or If it is >>> problem of Java Service Wrapper?. Could you give me some indication?. >>> >>> Thanks again!!. >>> 2009/3/18 Leif Mortenson <lei...@ta...> >>>> >>>> Elias, >>>> What does the content of your WrapperListener.start method look like? >>>> >>>> If you create a new thread, it will be non-daemon unless you >>>> specifically call the thread.setDaemon(true) method. If you are using >>>> existing class to start your application then it will be more >>>> difficult to check. One solution is to add a wait for 1 second at >>>> the end of your start method then call >>>> WrapperManager.requestThreadDump(). That will let you see all of your >>>> threads as well as see easily which have their daemon flag set. >>>> >>>> Cheers, >>>> Leif >> >> (snip) >> >> ------------------------------------------------------------------------------ >> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are >> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and >> easily build your RIAs with Flex Builder, the Eclipse(TM)based >> development >> software that enables intelligent coding and step-through debugging. >> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > > -- View this message in context: http://www.nabble.com/Wrapper-stopped-after-startup-tp22554782p22663877.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: ejml <eli...@gm...> - 2009-03-23 14:04:45
|
Hi Lief, I have done the installation in other machine and now works all fine. Thanks by all. ejml wrote: > > Hello Leif, > > My answers: > > 1) I have run the service in console mode with the command: wrapper.exe -c > ../conf/wrapper.conf and it works fine. > > 2) The command that I use to run the application when it works is: > > "C:\Archivos de programa\Java\jre1.5.0_12\bin\java" > -Djava.library.path="../lib" -classpath > "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar;C:/Archivos > de programa/jetty-6.1.3/lib/servlet-api-2.5-6.1.3.jar;C:/Archivos de > programa/jacob-1.14/jacob.jar;C:/Archivos de > programa/jetty-6.1.3/lib/jetty-6.1.3.jar;C:/Archivos de > programa/jetty-6.1.3/lib/jetty-util-6.1.3.jar;C:/Archivos de > programa/spring-framework-2.5.1/dist/spring.jar;C:/Archivos de > programa/spring-framework-2.5.1/dist/modules/spring-context.jar;C:/Archivos > de programa/spring-framework-2.5.1/dist/spring-test.jar;C:/Archivos de > programa/spring-framework-2.5.1/lib/jakarta-commons/commons-logging.jar" > com.gvs.AXConnectorServer.AXConnectorServiceWin32 > > This is the same effect that I execute: wrapper.exe -c > ../conf/wrapper.conf > > 3) I don't find win32com.dll, I have searched in sun and RXTX and the new > versions not contain win32com.dll. > > Thanks and greetings!!. > > Leif Mortenson-2 wrote: >> >> Elias, >> Can you answer a few questions? >> >> 1) You have said that it fails when run as a service, but that it >> works from the command line. Have you tried running under the >> Wrapper in console mode? Ie by running as follows: wrapper.exe -c >> ..¥conf¥wrapper.conf >> What happens? >> >> 2) Please post the java command line you are using when it works, and >> the one generated by the Wrapper. You can get the command line >> generated by the Wrapper by running in debug mode or by setting >> wrapper.java.command.loglevel=INFO >> >> 2) Have you seen the FAQ entry on this subject? >> http://wrapper.tanukisoftware.org/doc/english/faq.html#4 >> The win32com.dll needs to be on your java library path. By default, >> Java searches the PATH, but when running under the Wrapper, this is >> disabled because a library path is specified. It is necessary to add >> the location of win32com.dll to your library path in the wrapper.conf >> file. >> >> Cheers, >> Leif >> >> 2009/3/20 Elías Manchón López <eli...@gm...>: >>> Hi Leif, >>> >>> The problem was the creation of instance of the class wrap by >>> WrapperListener. Now I haven't problem with the start of Service. But >>> it's >>> not work yet. I think that the problem is very difficult of resolve. >>> Although my level of English not is very good, I will try to explain the >>> better possible for if you can help me. >>> >>> My application is made with Spring Framework. This application use Jetty >>> embedded to publish it through 8080 port and use the remote feature of >>> Spring to the web server can do request to it. This application is >>> communicated with my ERP throught COM+ and translate the request of web >>> server to my ERP using JACOB >>> (http://sourceforge.net/projects/jacob-project/). >>> >>> When I use Java Service Wrapper, I can see that I have problems with the >>> Initialization of COM Object, and I get NullPointer to object >>> instantiated >>> with JACOB. I thought that problem was by permission on the COM of >>> Microsoft, but I checked this issue and there isn't problems. As well >>> as, If >>> I run my application throught command line, with the same command that >>> Java >>> Service Wrapper and using the same jar packet, the curious is that it >>> works >>> fine. >>> >>> I don't know to think, I don't know if it is problem of COM+ or If it is >>> problem of Java Service Wrapper?. Could you give me some indication?. >>> >>> Thanks again!!. >>> 2009/3/18 Leif Mortenson <lei...@ta...> >>>> >>>> Elias, >>>> What does the content of your WrapperListener.start method look like? >>>> >>>> If you create a new thread, it will be non-daemon unless you >>>> specifically call the thread.setDaemon(true) method. If you are using >>>> existing class to start your application then it will be more >>>> difficult to check. One solution is to add a wait for 1 second at >>>> the end of your start method then call >>>> WrapperManager.requestThreadDump(). That will let you see all of your >>>> threads as well as see easily which have their daemon flag set. >>>> >>>> Cheers, >>>> Leif >> >> (snip) >> >> ------------------------------------------------------------------------------ >> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are >> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and >> easily build your RIAs with Flex Builder, the Eclipse(TM)based >> development >> software that enables intelligent coding and step-through debugging. >> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > > -- View this message in context: http://www.nabble.com/Wrapper-stopped-after-startup-tp22554782p22660775.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: ejml <eli...@gm...> - 2009-03-22 19:15:21
|
Hello Leif, My answers: 1) I have run the service in console mode with the command: wrapper.exe -c ../conf/wrapper.conf and it works fine. 2) The command that I use to run the application when it works is: "C:\Archivos de programa\Java\jre1.5.0_12\bin\java" -Djava.library.path="../lib" -classpath "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar;C:/Archivos de programa/jetty-6.1.3/lib/servlet-api-2.5-6.1.3.jar;C:/Archivos de programa/jacob-1.14/jacob.jar;C:/Archivos de programa/jetty-6.1.3/lib/jetty-6.1.3.jar;C:/Archivos de programa/jetty-6.1.3/lib/jetty-util-6.1.3.jar;C:/Archivos de programa/spring-framework-2.5.1/dist/spring.jar;C:/Archivos de programa/spring-framework-2.5.1/dist/modules/spring-context.jar;C:/Archivos de programa/spring-framework-2.5.1/dist/spring-test.jar;C:/Archivos de programa/spring-framework-2.5.1/lib/jakarta-commons/commons-logging.jar" com.gvs.AXConnectorServer.AXConnectorServiceWin32 This is the same effect that I execute: wrapper.exe -c ../conf/wrapper.conf 3) I don't find win32com.dll, I have searched in sun and RXTX and the new versions not contain win32com.dll. Thanks and greetings!!. Leif Mortenson-2 wrote: > > Elias, > Can you answer a few questions? > > 1) You have said that it fails when run as a service, but that it > works from the command line. Have you tried running under the > Wrapper in console mode? Ie by running as follows: wrapper.exe -c > ..¥conf¥wrapper.conf > What happens? > > 2) Please post the java command line you are using when it works, and > the one generated by the Wrapper. You can get the command line > generated by the Wrapper by running in debug mode or by setting > wrapper.java.command.loglevel=INFO > > 2) Have you seen the FAQ entry on this subject? > http://wrapper.tanukisoftware.org/doc/english/faq.html#4 > The win32com.dll needs to be on your java library path. By default, > Java searches the PATH, but when running under the Wrapper, this is > disabled because a library path is specified. It is necessary to add > the location of win32com.dll to your library path in the wrapper.conf > file. > > Cheers, > Leif > > 2009/3/20 Elías Manchón López <eli...@gm...>: >> Hi Leif, >> >> The problem was the creation of instance of the class wrap by >> WrapperListener. Now I haven't problem with the start of Service. But >> it's >> not work yet. I think that the problem is very difficult of resolve. >> Although my level of English not is very good, I will try to explain the >> better possible for if you can help me. >> >> My application is made with Spring Framework. This application use Jetty >> embedded to publish it through 8080 port and use the remote feature of >> Spring to the web server can do request to it. This application is >> communicated with my ERP throught COM+ and translate the request of web >> server to my ERP using JACOB >> (http://sourceforge.net/projects/jacob-project/). >> >> When I use Java Service Wrapper, I can see that I have problems with the >> Initialization of COM Object, and I get NullPointer to object >> instantiated >> with JACOB. I thought that problem was by permission on the COM of >> Microsoft, but I checked this issue and there isn't problems. As well as, >> If >> I run my application throught command line, with the same command that >> Java >> Service Wrapper and using the same jar packet, the curious is that it >> works >> fine. >> >> I don't know to think, I don't know if it is problem of COM+ or If it is >> problem of Java Service Wrapper?. Could you give me some indication?. >> >> Thanks again!!. >> 2009/3/18 Leif Mortenson <lei...@ta...> >>> >>> Elias, >>> What does the content of your WrapperListener.start method look like? >>> >>> If you create a new thread, it will be non-daemon unless you >>> specifically call the thread.setDaemon(true) method. If you are using >>> existing class to start your application then it will be more >>> difficult to check. One solution is to add a wait for 1 second at >>> the end of your start method then call >>> WrapperManager.requestThreadDump(). That will let you see all of your >>> threads as well as see easily which have their daemon flag set. >>> >>> Cheers, >>> Leif > > (snip) > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > -- View this message in context: http://www.nabble.com/Wrapper-stopped-after-startup-tp22554782p22649421.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Elías M. L. <eli...@gm...> - 2009-03-22 19:14:04
|
Hello Leif, My answers: 1) I have run the service in console mode with the command: wrapper.exe -c ../conf/wrapper.conf and it works fine. 2) The command that I use to run the application when it works is: "C:\Archivos de programa\Java\jre1.5.0_12\bin\java" -Djava.library.path="../lib" -classpath "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar;C:/Archivos de programa/jetty-6.1.3/lib/servlet-api-2.5-6.1.3.jar;C:/Archivos de programa/jacob-1.14/jacob.jar;C:/Archivos de programa/jetty-6.1.3/lib/jetty-6.1.3.jar;C:/Archivos de programa/jetty-6.1.3/lib/jetty-util-6.1.3.jar;C:/Archivos de programa/spring-framework-2.5.1/dist/spring.jar;C:/Archivos de programa/spring-framework-2.5.1/dist/modules/spring-context.jar;C:/Archivos de programa/spring-framework-2.5.1/dist/spring-test.jar;C:/Archivos de programa/spring-framework-2.5.1/lib/jakarta-commons/commons-logging.jar" com.gvs.AXConnectorServer.AXConnectorServiceWin32 This is the same effect that I execute: wrapper.exe -c ../conf/wrapper.conf 3) I don't find win32com.dll, I have searched in sun and RXTX and the new versions not contain win32com.dll. Thanks and greetings!!. 2009/3/22 Leif Mortenson <le...@ta...> > Elias, > Can you answer a few questions? > > 1) You have said that it fails when run as a service, but that it > works from the command line. Have you tried running under the > Wrapper in console mode? Ie by running as follows: wrapper.exe -c > ..¥conf¥wrapper.conf > What happens? > > 2) Please post the java command line you are using when it works, and > the one generated by the Wrapper. You can get the command line > generated by the Wrapper by running in debug mode or by setting > wrapper.java.command.loglevel=INFO > > 2) Have you seen the FAQ entry on this subject? > http://wrapper.tanukisoftware.org/doc/english/faq.html#4 > The win32com.dll needs to be on your java library path. By default, > Java searches the PATH, but when running under the Wrapper, this is > disabled because a library path is specified. It is necessary to add > the location of win32com.dll to your library path in the wrapper.conf > file. > > Cheers, > Leif > > 2009/3/20 Elías Manchón López <eli...@gm...>: > > Hi Leif, > > > > The problem was the creation of instance of the class wrap by > > WrapperListener. Now I haven't problem with the start of Service. But > it's > > not work yet. I think that the problem is very difficult of resolve. > > Although my level of English not is very good, I will try to explain the > > better possible for if you can help me. > > > > My application is made with Spring Framework. This application use Jetty > > embedded to publish it through 8080 port and use the remote feature of > > Spring to the web server can do request to it. This application is > > communicated with my ERP throught COM+ and translate the request of web > > server to my ERP using JACOB > > (http://sourceforge.net/projects/jacob-project/). > > > > When I use Java Service Wrapper, I can see that I have problems with the > > Initialization of COM Object, and I get NullPointer to object > instantiated > > with JACOB. I thought that problem was by permission on the COM of > > Microsoft, but I checked this issue and there isn't problems. As well as, > If > > I run my application throught command line, with the same command that > Java > > Service Wrapper and using the same jar packet, the curious is that it > works > > fine. > > > > I don't know to think, I don't know if it is problem of COM+ or If it is > > problem of Java Service Wrapper?. Could you give me some indication?. > > > > Thanks again!!. > > 2009/3/18 Leif Mortenson <lei...@ta...> > >> > >> Elias, > >> What does the content of your WrapperListener.start method look like? > >> > >> If you create a new thread, it will be non-daemon unless you > >> specifically call the thread.setDaemon(true) method. If you are using > >> existing class to start your application then it will be more > >> difficult to check. One solution is to add a wait for 1 second at > >> the end of your start method then call > >> WrapperManager.requestThreadDump(). That will let you see all of your > >> threads as well as see easily which have their daemon flag set. > >> > >> Cheers, > >> Leif > > (snip) > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2009-03-22 13:53:21
|
Elias, Can you answer a few questions? 1) You have said that it fails when run as a service, but that it works from the command line. Have you tried running under the Wrapper in console mode? Ie by running as follows: wrapper.exe -c ..¥conf¥wrapper.conf What happens? 2) Please post the java command line you are using when it works, and the one generated by the Wrapper. You can get the command line generated by the Wrapper by running in debug mode or by setting wrapper.java.command.loglevel=INFO 2) Have you seen the FAQ entry on this subject? http://wrapper.tanukisoftware.org/doc/english/faq.html#4 The win32com.dll needs to be on your java library path. By default, Java searches the PATH, but when running under the Wrapper, this is disabled because a library path is specified. It is necessary to add the location of win32com.dll to your library path in the wrapper.conf file. Cheers, Leif 2009/3/20 Elías Manchón López <eli...@gm...>: > Hi Leif, > > The problem was the creation of instance of the class wrap by > WrapperListener. Now I haven't problem with the start of Service. But it's > not work yet. I think that the problem is very difficult of resolve. > Although my level of English not is very good, I will try to explain the > better possible for if you can help me. > > My application is made with Spring Framework. This application use Jetty > embedded to publish it through 8080 port and use the remote feature of > Spring to the web server can do request to it. This application is > communicated with my ERP throught COM+ and translate the request of web > server to my ERP using JACOB > (http://sourceforge.net/projects/jacob-project/). > > When I use Java Service Wrapper, I can see that I have problems with the > Initialization of COM Object, and I get NullPointer to object instantiated > with JACOB. I thought that problem was by permission on the COM of > Microsoft, but I checked this issue and there isn't problems. As well as, If > I run my application throught command line, with the same command that Java > Service Wrapper and using the same jar packet, the curious is that it works > fine. > > I don't know to think, I don't know if it is problem of COM+ or If it is > problem of Java Service Wrapper?. Could you give me some indication?. > > Thanks again!!. > 2009/3/18 Leif Mortenson <lei...@ta...> >> >> Elias, >> What does the content of your WrapperListener.start method look like? >> >> If you create a new thread, it will be non-daemon unless you >> specifically call the thread.setDaemon(true) method. If you are using >> existing class to start your application then it will be more >> difficult to check. One solution is to add a wait for 1 second at >> the end of your start method then call >> WrapperManager.requestThreadDump(). That will let you see all of your >> threads as well as see easily which have their daemon flag set. >> >> Cheers, >> Leif (snip) |
|
From: ejml <eli...@gm...> - 2009-03-20 09:48:59
|
Hi Leif, The problem was the creation of instance of the class wrap by WrapperListener. Now I haven't problem with the start of Service. But it's not work yet. I think that the problem is very difficult of resolve. Although my level of English not is very good, I will try to explain the better possible for if you can help me. My application is made with Spring Framework. This application use Jetty embedded to publish it through 8080 port and use the remote feature of Spring to the web server can do request to it. This application is communicated with my ERP throught COM+ and translate the request of web server to my ERP using JACOB (http://sourceforge.net/projects/jacob-project/). When I use Java Service Wrapper, I can see that I have problems with the Initialization of COM Object, and I get NullPointer to object instantiated with JACOB. I thought that problem was by permission on the COM of Microsoft, but I checked this issue and there isn't problems. As well as, If I run my application throught command line, with the same command that Java Service Wrapper and using the same jar packet, the curious is that it works fine. I don't know to think, I don't know if it is problem of COM+ or If it is problem of Java Service Wrapper?. Could you give me some indication?. Thanks again!!. Leif Mortenson-3 wrote: > > Elias, > What does the content of your WrapperListener.start method look like? > > If you create a new thread, it will be non-daemon unless you > specifically call the thread.setDaemon(true) method. If you are using > existing class to start your application then it will be more > difficult to check. One solution is to add a wait for 1 second at > the end of your start method then call > WrapperManager.requestThreadDump(). That will let you see all of your > threads as well as see easily which have their daemon flag set. > > Cheers, > Leif > > On Tue, Mar 17, 2009 at 9:02 PM, ejml <eli...@gm...> wrote: >> >> Hello again Leif, >> >> Sorry by my ignorance but How can I'm sure that there is at least one >> non-daemon thread?. >> >> Thanks. >> >> >> Leif Mortenson-3 wrote: >>> >>> Elias, >>> Ok. Now the problem is that when your WrapperListener.start method >>> returns, there are not any non-daemon threads running. Because of >>> this, the JVM, not the Wrapper is initiating its own shutdown. The >>> Wrapper's shutdown is initiated when its own Shutdown Hook is started >>> by the JVM. >>> >>> Please make sure that you have started at least one non-daemon thread. >>> >>> Java will shutdown when run without the Wrapper as well if the main >>> method completes and there are no non-daemon threads running. >>> >>> Let me know if this doesn't make sense. >>> >>> Cheers, >>> Leif >>> >>> On Tue, Mar 17, 2009 at 7:42 PM, ejml <eli...@gm...> wrote: >>>> >>>> Thanks Leif by your response. >>>> Yes, I'm making use of Method 3 and your had reason. I had my variable >>>> initialized to 0. I have corrected this issue, but it doesn't works >>>> yet. >>>> My >>>> log says this: >>>> >>>> DEBUG | wrapper | 2009/03/17 11:38:41 | Allocating a console for the >>>> service. >>>> DEBUG | wrapper | 2009/03/17 11:38:41 | Found console window. >>>> STATUS | wrapper | 2009/03/17 11:38:41 | --> Wrapper Started as >>>> Service >>>> STATUS | wrapper | 2009/03/17 11:38:41 | Java Service Wrapper >>>> Community >>>> Edition 3.3.3 >>>> STATUS | wrapper | 2009/03/17 11:38:41 | Copyright (C) 1999-2009 >>>> Tanuki >>>> Software, Ltd. All Rights Reserved. >>>> STATUS | wrapper | 2009/03/17 11:38:41 | >>>> http://wrapper.tanukisoftware.org >>>> STATUS | wrapper | 2009/03/17 11:38:41 | >>>> DEBUG | wrapper | 2009/03/17 11:38:41 | Using tick timer. >>>> DEBUG | wrapperp | 2009/03/17 11:38:41 | server listening on port >>>> 32000. >>>> DEBUG | wrapper | 2009/03/17 11:38:41 | Ping settings: >>>> wrapper.ping.interval=5, wrapper.ping.interval.logged=1, >>>> wrapper.ping.timeout=30 >>>> STATUS | wrapper | 2009/03/17 11:38:41 | Launching a JVM... >>>> DEBUG | wrapper | 2009/03/17 11:38:41 | command: >>>> "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath >>>> "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" >>>> -Dwrapper.key="YaKrFRBk8gEnOuzE" -Dwrapper.port=32000 >>>> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >>>> -Dwrapper.debug="TRUE" -Dwrapper.pid=3516 -Dwrapper.version="3.3.3" >>>> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" >>>> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 >>>> com.gvs.AXConnectorServer.AXConnectorServiceWin32 >>>> DEBUG | wrapper | 2009/03/17 11:38:41 | JVM started (PID=4892) >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> WrapperManager class initialized by thread: main Using classloader: >>>> sun.misc.Launcher$AppClassLoader@11b86e7 >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager: >>>> Initializing... >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: JVM #1 >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Running >>>> a >>>> 32-bit JVM. >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> Registering >>>> shutdown hook >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Using >>>> wrapper >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Load >>>> native >>>> library. One or more attempts may fail if platform specific libraries >>>> do >>>> not exist. This is NORMAL and is only a problem if they all fail. >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> Unable >>>> to >>>> load native library: wrapper-windows-x86-32.dll Cause: no >>>> wrapper-windows-x86-32 in java.library.path >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> Loaded >>>> native library: wrapper.dll >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Calling >>>> native initialization method. >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: >>>> Initializing >>>> WrapperManager native library. >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Java >>>> Executable: >>>> C:\WINNT\system32\java.exe >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Windows >>>> version: >>>> 5.0.2195 >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java >>>> Version >>>> : 1.6.0_11-b03 Java HotSpot(TM) Client VM >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java VM >>>> Vendor : Sun Microsystems Inc. >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Name >>>> : Windows 2000 >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Arch >>>> : x86 >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Control >>>> event monitor thread started. >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9, >>>> args[]) called by thread: main >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup >>>> runner thread started. >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> Communications runner thread started. >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Open >>>> socket >>>> to wrapper...Wrapper-Connection >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Opened >>>> Socket from 31000 to 32000 >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a >>>> packet KEY : YaKrFRBk8gEnOuzE >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) >>>> DEBUG | wrapperp | 2009/03/17 11:38:42 | accepted a socket from >>>> 127.0.0.1 >>>> on port 31000 >>>> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet KEY : >>>> YaKrFRBk8gEnOuzE >>>> DEBUG | wrapper | 2009/03/17 11:38:42 | Got key from JVM: >>>> YaKrFRBk8gEnOuzE >>>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet LOW_LOG_LEVEL : >>>> 1 >>>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PING_TIMEOUT : >>>> 30 >>>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PROPERTIES : >>>> (Property Values) >>>> DEBUG | wrapper | 2009/03/17 11:38:42 | Start Application. >>>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet START : start >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> Received >>>> a >>>> packet LOW_LOG_LEVEL : 1 >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> LowLogLevel >>>> from Wrapper is 1 >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> Received >>>> a >>>> packet PING_TIMEOUT : 30 >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> PingTimeout >>>> from Wrapper is 30000 >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> Received >>>> a >>>> packet PROPERTIES : (Property Values) >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> Received >>>> a >>>> packet START : start >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: calling >>>> WrapperListener.start() >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> WrapperListener.start runner thread started. >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> returned >>>> from WrapperListener.start() >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a >>>> packet STARTED : >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> WrapperListener.start runner thread stopped. >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup >>>> runner thread stopped. >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> ShutdownHook >>>> started >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a >>>> packet STOP : 0 >>>> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STARTED : >>>> DEBUG | wrapper | 2009/03/17 11:38:42 | JVM signalled that it was >>>> started. >>>> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STOP : 0 >>>> DEBUG | wrapper | 2009/03/17 11:38:42 | JVM requested a shutdown. (0) >>>> DEBUG | wrapper | 2009/03/17 11:38:42 | wrapperStopProcess(0) called. >>>> DEBUG | wrapper | 2009/03/17 11:38:42 | Sending stop signal to JVM >>>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet STOP : NULL >>>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>>> Received >>>> a >>>> packet STOP : >>>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Thread, >>>> Wrapper-Shutdown-Hook, handling the shutdown process. >>>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: calling >>>> listener.stop() >>>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: >>>> returned >>>> from listener.stop() -> 0 >>>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: >>>> shutdownJVM(0) Thread:Wrapper-Shutdown-Hook >>>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: wait >>>> for >>>> 0 >>>> shutdown locs to be released. >>>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Send a >>>> packet STOPPED : 0 >>>> DEBUG | wrapperp | 2009/03/17 11:38:43 | read a packet STOPPED : 0 >>>> DEBUG | wrapper | 2009/03/17 11:38:43 | JVM signalled that it was >>>> stopped. >>>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Closing >>>> socket. >>>> DEBUG | wrapperp | 2009/03/17 11:38:43 | socket read no code >>>> (closed?). >>>> DEBUG | wrapperp | 2009/03/17 11:38:43 | socket not open, so packet >>>> not >>>> sent SERVICE_CONTROL_CODE : 4 >>>> DEBUG | wrapper | 2009/03/17 11:38:43 | SERVICE_CONTROL_INTERROGATE >>>> INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: Server >>>> daemon shut down >>>> INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: >>>> ShutdownHook >>>> complete >>>> DEBUG | wrapper | 2009/03/17 11:38:44 | JVM process exited with a >>>> code >>>> of >>>> 0, leaving the wrapper exit code set to 0. >>>> DEBUG | wrapper | 2009/03/17 11:38:44 | JVM exited normally. >>>> STATUS | wrapper | 2009/03/17 11:38:44 | <-- Wrapper Stopped >>>> >>>> Very thanks by your help. >>>> >>>> Greetings!!. >>>> >>>> >>>> >>>> >>>> >>>> Leif Mortenson-3 wrote: >>>>> >>>>> Elias, >>>>>>From the java command line, it looks like you are making use of >>>>> Integration Method #3 for your application. >>>>> Is the com.gvs.AXConnectorServer.AXConnectorServiceWin32 class >>>>> something that you created? It appears to be working pretty much >>>>> correctly. >>>>> The problem is that your WrapperListener.start implementation is >>>>> returning an exit code of 0. This is telling the Wrapper that the JVM >>>>> should exit with exit code 0. If the application is meant to continue >>>>> running then the WrapperListener.start method should be returning >>>>> null. >>>>> >>>>> See the Java docs for the WrapperListener class for more information: >>>>> http://wrapper.tanukisoftware.org/doc/english/javadocs.html >>>>> >>>>> This is also described on the following page: >>>>> http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html >>>>> >>>>> Cheers, >>>>> Leif >>>>> >>>>> On Tue, Mar 17, 2009 at 6:41 PM, ejml <eli...@gm...> wrote: >>>>>> >>>>>> Hello Folks!, >>>>>> >>>>>> I'm trying to use Java Service Wrapper to implement my java project >>>>>> like >>>>>> windows service. My Project is made with Spring using Jetty. In other >>>>>> words, >>>>>> I use spring to startup jetty. This setup in eclipse work fine but I >>>>>> try >>>>>> to >>>>>> configure my application with Java Service Wrapper I get the next: >>>>>> >>>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Allocating a console for >>>>>> the >>>>>> service. >>>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Found console window. >>>>>> STATUS | wrapper | 2009/03/17 09:40:35 | --> Wrapper Started as >>>>>> Service >>>>>> STATUS | wrapper | 2009/03/17 09:40:35 | Java Service Wrapper >>>>>> Community >>>>>> Edition 3.3.3 >>>>>> STATUS | wrapper | 2009/03/17 09:40:35 | Copyright (C) 1999-2009 >>>>>> Tanuki >>>>>> Software, Ltd. All Rights Reserved. >>>>>> STATUS | wrapper | 2009/03/17 09:40:35 | >>>>>> http://wrapper.tanukisoftware.org >>>>>> STATUS | wrapper | 2009/03/17 09:40:35 | >>>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Using tick timer. >>>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | server listening on port >>>>>> 32000. >>>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Ping settings: >>>>>> wrapper.ping.interval=5, wrapper.ping.interval.logged=1, >>>>>> wrapper.ping.timeout=30 >>>>>> STATUS | wrapper | 2009/03/17 09:40:35 | Launching a JVM... >>>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | command: >>>>>> "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath >>>>>> "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" >>>>>> -Dwrapper.key="fREO9IxlyMDSknzk" -Dwrapper.port=32000 >>>>>> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >>>>>> -Dwrapper.debug="TRUE" -Dwrapper.pid=4020 -Dwrapper.version="3.3.3" >>>>>> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" >>>>>> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 >>>>>> com.gvs.AXConnectorServer.AXConnectorServiceWin32 >>>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM started (PID=3756) >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> WrapperManager class initialized by thread: main Using classloader: >>>>>> sun.misc.Launcher$AppClassLoader@11b86e7 >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager: >>>>>> Initializing... >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: JVM >>>>>> #1 >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Running >>>>>> a >>>>>> 32-bit JVM. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Registering >>>>>> shutdown hook >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Using >>>>>> wrapper >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Load >>>>>> native >>>>>> library. One or more attempts may fail if platform specific >>>>>> libraries >>>>>> do >>>>>> not exist. This is NORMAL and is only a problem if they all fail. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Unable >>>>>> to >>>>>> load native library: wrapper-windows-x86-32.dll Cause: no >>>>>> wrapper-windows-x86-32 in java.library.path >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Loaded >>>>>> native library: wrapper.dll >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Calling >>>>>> native initialization method. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: >>>>>> Initializing >>>>>> WrapperManager native library. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Java >>>>>> Executable: >>>>>> C:\WINNT\system32\java.exe >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Windows >>>>>> version: >>>>>> 5.0.2195 >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java >>>>>> Version >>>>>> : 1.6.0_11-b03 Java HotSpot(TM) Client VM >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java >>>>>> VM >>>>>> Vendor : Sun Microsystems Inc. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS >>>>>> Name >>>>>> : Windows 2000 >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS >>>>>> Arch >>>>>> : x86 >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9, >>>>>> args[]) called by thread: main >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Startup >>>>>> runner thread started. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Control >>>>>> event monitor thread started. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Communications runner thread started. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Open >>>>>> socket >>>>>> to wrapper...Wrapper-Connection >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Failed >>>>>> attempt to bind using local port 31000 >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Opened >>>>>> Socket from 31001 to 32000 >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send >>>>>> a >>>>>> packet KEY : fREO9IxlyMDSknzk >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001]) >>>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | accepted a socket from >>>>>> 127.0.0.1 >>>>>> on port 31001 >>>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet KEY : >>>>>> fREO9IxlyMDSknzk >>>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Got key from JVM: >>>>>> fREO9IxlyMDSknzk >>>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet LOW_LOG_LEVEL >>>>>> : >>>>>> 1 >>>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PING_TIMEOUT >>>>>> : >>>>>> 30 >>>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PROPERTIES : >>>>>> (Property Values) >>>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Start Application. >>>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet START : start >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Received >>>>>> a >>>>>> packet LOW_LOG_LEVEL : 1 >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> LowLogLevel >>>>>> from Wrapper is 1 >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Received >>>>>> a >>>>>> packet PING_TIMEOUT : 30 >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> PingTimeout >>>>>> from Wrapper is 30000 >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Received >>>>>> a >>>>>> packet PROPERTIES : (Property Values) >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> Received >>>>>> a >>>>>> packet START : start >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> calling >>>>>> WrapperListener.start() >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> WrapperListener.start runner thread started. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> returned >>>>>> from WrapperListener.start() >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> WrapperListener.start() returned an exit code of 0. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>>> WrapperManager.stop(0) called by thread: WrapperListener_start_runner >>>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send >>>>>> a >>>>>> packet STOP : 0 >>>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet STOP : 0 >>>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM requested a shutdown. >>>>>> (0) >>>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | wrapperStopProcess(0) >>>>>> called. >>>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Sending stop signal to JVM >>>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet STOP : NULL >>>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: >>>>>> Received >>>>>> a >>>>>> packet STOP : >>>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: >>>>>> Thread, >>>>>> WrapperListener_start_runner, handling the shutdown process. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: >>>>>> shutdownJVM(0) Thread:WrapperListener_start_runner >>>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: wait >>>>>> for >>>>>> 0 >>>>>> shutdown locs to be released. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Send >>>>>> a >>>>>> packet STOPPED : 0 >>>>>> DEBUG | wrapperp | 2009/03/17 09:40:36 | read a packet STOPPED : 0 >>>>>> DEBUG | wrapper | 2009/03/17 09:40:36 | JVM signalled that it was >>>>>> stopped. >>>>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: >>>>>> Closing >>>>>> socket. >>>>>> DEBUG | wrapperp | 2009/03/17 09:40:37 | socket read no code >>>>>> (closed?). >>>>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: >>>>>> calling >>>>>> System.exit(0) >>>>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: >>>>>> Server >>>>>> daemon shut down >>>>>> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM process exited with a >>>>>> code >>>>>> of >>>>>> 0, leaving the wrapper exit code set to 0. >>>>>> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM exited normally. >>>>>> STATUS | wrapper | 2009/03/17 09:40:37 | <-- Wrapper Stopped >>>>>> >>>>>> This log say us something. >>>>>> >>>>>> Thanks in advance!!. > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > -- View this message in context: http://www.nabble.com/Wrapper-stopped-after-startup-tp22554782p22617198.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Elías M. L. <eli...@gm...> - 2009-03-20 09:43:42
|
Hi Leif, The problem was the creation of instance of the class wrap by WrapperListener. Now I haven't problem with the start of Service. But it's not work yet. I think that the problem is very difficult of resolve. Although my level of English not is very good, I will try to explain the better possible for if you can help me. My application is made with Spring Framework. This application use Jetty embedded to publish it through 8080 port and use the remote feature of Spring to the web server can do request to it. This application is communicated with my ERP throught COM+ and translate the request of web server to my ERP using JACOB (http://sourceforge.net/projects/jacob-project/ ). When I use Java Service Wrapper, I can see that I have problems with the Initialization of COM Object, and I get NullPointer to object instantiated with JACOB. I thought that problem was by permission on the COM of Microsoft, but I checked this issue and there isn't problems. As well as, If I run my application throught command line, with the same command that Java Service Wrapper and using the same jar packet, the curious is that it works fine. I don't know to think, I don't know if it is problem of COM+ or If it is problem of Java Service Wrapper?. Could you give me some indication?. Thanks again!!. 2009/3/18 Leif Mortenson <lei...@ta...> > Elias, > What does the content of your WrapperListener.start method look like? > > If you create a new thread, it will be non-daemon unless you > specifically call the thread.setDaemon(true) method. If you are using > existing class to start your application then it will be more > difficult to check. One solution is to add a wait for 1 second at > the end of your start method then call > WrapperManager.requestThreadDump(). That will let you see all of your > threads as well as see easily which have their daemon flag set. > > Cheers, > Leif > > On Tue, Mar 17, 2009 at 9:02 PM, ejml <eli...@gm...> wrote: > > > > Hello again Leif, > > > > Sorry by my ignorance but How can I'm sure that there is at least one > > non-daemon thread?. > > > > Thanks. > > > > > > Leif Mortenson-3 wrote: > >> > >> Elias, > >> Ok. Now the problem is that when your WrapperListener.start method > >> returns, there are not any non-daemon threads running. Because of > >> this, the JVM, not the Wrapper is initiating its own shutdown. The > >> Wrapper's shutdown is initiated when its own Shutdown Hook is started > >> by the JVM. > >> > >> Please make sure that you have started at least one non-daemon thread. > >> > >> Java will shutdown when run without the Wrapper as well if the main > >> method completes and there are no non-daemon threads running. > >> > >> Let me know if this doesn't make sense. > >> > >> Cheers, > >> Leif > >> > >> On Tue, Mar 17, 2009 at 7:42 PM, ejml <eli...@gm...> wrote: > >>> > >>> Thanks Leif by your response. > >>> Yes, I'm making use of Method 3 and your had reason. I had my variable > >>> initialized to 0. I have corrected this issue, but it doesn't works > yet. > >>> My > >>> log says this: > >>> > >>> DEBUG | wrapper | 2009/03/17 11:38:41 | Allocating a console for the > >>> service. > >>> DEBUG | wrapper | 2009/03/17 11:38:41 | Found console window. > >>> STATUS | wrapper | 2009/03/17 11:38:41 | --> Wrapper Started as > Service > >>> STATUS | wrapper | 2009/03/17 11:38:41 | Java Service Wrapper > Community > >>> Edition 3.3.3 > >>> STATUS | wrapper | 2009/03/17 11:38:41 | Copyright (C) 1999-2009 > >>> Tanuki > >>> Software, Ltd. All Rights Reserved. > >>> STATUS | wrapper | 2009/03/17 11:38:41 | > >>> http://wrapper.tanukisoftware.org > >>> STATUS | wrapper | 2009/03/17 11:38:41 | > >>> DEBUG | wrapper | 2009/03/17 11:38:41 | Using tick timer. > >>> DEBUG | wrapperp | 2009/03/17 11:38:41 | server listening on port > 32000. > >>> DEBUG | wrapper | 2009/03/17 11:38:41 | Ping settings: > >>> wrapper.ping.interval=5, wrapper.ping.interval.logged=1, > >>> wrapper.ping.timeout=30 > >>> STATUS | wrapper | 2009/03/17 11:38:41 | Launching a JVM... > >>> DEBUG | wrapper | 2009/03/17 11:38:41 | command: > >>> "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath > >>> > "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" > >>> -Dwrapper.key="YaKrFRBk8gEnOuzE" -Dwrapper.port=32000 > >>> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 > >>> -Dwrapper.debug="TRUE" -Dwrapper.pid=3516 -Dwrapper.version="3.3.3" > >>> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" > >>> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 > >>> com.gvs.AXConnectorServer.AXConnectorServiceWin32 > >>> DEBUG | wrapper | 2009/03/17 11:38:41 | JVM started (PID=4892) > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >>> WrapperManager class initialized by thread: main Using classloader: > >>> sun.misc.Launcher$AppClassLoader@11b86e7 > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager: > Initializing... > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: JVM #1 > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Running > a > >>> 32-bit JVM. > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >>> Registering > >>> shutdown hook > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Using > >>> wrapper > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Load > >>> native > >>> library. One or more attempts may fail if platform specific libraries > do > >>> not exist. This is NORMAL and is only a problem if they all fail. > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > Unable > >>> to > >>> load native library: wrapper-windows-x86-32.dll Cause: no > >>> wrapper-windows-x86-32 in java.library.path > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > Loaded > >>> native library: wrapper.dll > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Calling > >>> native initialization method. > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: > Initializing > >>> WrapperManager native library. > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Java > >>> Executable: > >>> C:\WINNT\system32\java.exe > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Windows > >>> version: > >>> 5.0.2195 > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java > >>> Version > >>> : 1.6.0_11-b03 Java HotSpot(TM) Client VM > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java VM > >>> Vendor : Sun Microsystems Inc. > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Name > >>> : Windows 2000 > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Arch > >>> : x86 > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Control > >>> event monitor thread started. > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >>> > WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9 > , > >>> args[]) called by thread: main > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup > >>> runner thread started. > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >>> Communications runner thread started. > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Open > >>> socket > >>> to wrapper...Wrapper-Connection > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Opened > >>> Socket from 31000 to 32000 > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a > >>> packet KEY : YaKrFRBk8gEnOuzE > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >>> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) > >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | accepted a socket from > >>> 127.0.0.1 > >>> on port 31000 > >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet KEY : > >>> YaKrFRBk8gEnOuzE > >>> DEBUG | wrapper | 2009/03/17 11:38:42 | Got key from JVM: > >>> YaKrFRBk8gEnOuzE > >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet LOW_LOG_LEVEL : > 1 > >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PING_TIMEOUT : > 30 > >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PROPERTIES : > >>> (Property Values) > >>> DEBUG | wrapper | 2009/03/17 11:38:42 | Start Application. > >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet START : start > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > Received > >>> a > >>> packet LOW_LOG_LEVEL : 1 > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >>> LowLogLevel > >>> from Wrapper is 1 > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > Received > >>> a > >>> packet PING_TIMEOUT : 30 > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >>> PingTimeout > >>> from Wrapper is 30000 > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > Received > >>> a > >>> packet PROPERTIES : (Property Values) > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > Received > >>> a > >>> packet START : start > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: calling > >>> WrapperListener.start() > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >>> WrapperListener.start runner thread started. > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > returned > >>> from WrapperListener.start() > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a > >>> packet STARTED : > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >>> WrapperListener.start runner thread stopped. > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup > >>> runner thread stopped. > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >>> ShutdownHook > >>> started > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >>> WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a > >>> packet STOP : 0 > >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STARTED : > >>> DEBUG | wrapper | 2009/03/17 11:38:42 | JVM signalled that it was > >>> started. > >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STOP : 0 > >>> DEBUG | wrapper | 2009/03/17 11:38:42 | JVM requested a shutdown. (0) > >>> DEBUG | wrapper | 2009/03/17 11:38:42 | wrapperStopProcess(0) called. > >>> DEBUG | wrapper | 2009/03/17 11:38:42 | Sending stop signal to JVM > >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet STOP : NULL > >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > Received > >>> a > >>> packet STOP : > >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Thread, > >>> Wrapper-Shutdown-Hook, handling the shutdown process. > >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: calling > >>> listener.stop() > >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: > returned > >>> from listener.stop() -> 0 > >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: > >>> shutdownJVM(0) Thread:Wrapper-Shutdown-Hook > >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: wait > for > >>> 0 > >>> shutdown locs to be released. > >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Send a > >>> packet STOPPED : 0 > >>> DEBUG | wrapperp | 2009/03/17 11:38:43 | read a packet STOPPED : 0 > >>> DEBUG | wrapper | 2009/03/17 11:38:43 | JVM signalled that it was > >>> stopped. > >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Closing > >>> socket. > >>> DEBUG | wrapperp | 2009/03/17 11:38:43 | socket read no code > (closed?). > >>> DEBUG | wrapperp | 2009/03/17 11:38:43 | socket not open, so packet > not > >>> sent SERVICE_CONTROL_CODE : 4 > >>> DEBUG | wrapper | 2009/03/17 11:38:43 | SERVICE_CONTROL_INTERROGATE > >>> INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: Server > >>> daemon shut down > >>> INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: > >>> ShutdownHook > >>> complete > >>> DEBUG | wrapper | 2009/03/17 11:38:44 | JVM process exited with a > code > >>> of > >>> 0, leaving the wrapper exit code set to 0. > >>> DEBUG | wrapper | 2009/03/17 11:38:44 | JVM exited normally. > >>> STATUS | wrapper | 2009/03/17 11:38:44 | <-- Wrapper Stopped > >>> > >>> Very thanks by your help. > >>> > >>> Greetings!!. > >>> > >>> > >>> > >>> > >>> > >>> Leif Mortenson-3 wrote: > >>>> > >>>> Elias, > >>>>>From the java command line, it looks like you are making use of > >>>> Integration Method #3 for your application. > >>>> Is the com.gvs.AXConnectorServer.AXConnectorServiceWin32 class > >>>> something that you created? It appears to be working pretty much > >>>> correctly. > >>>> The problem is that your WrapperListener.start implementation is > >>>> returning an exit code of 0. This is telling the Wrapper that the JVM > >>>> should exit with exit code 0. If the application is meant to continue > >>>> running then the WrapperListener.start method should be returning > >>>> null. > >>>> > >>>> See the Java docs for the WrapperListener class for more information: > >>>> http://wrapper.tanukisoftware.org/doc/english/javadocs.html > >>>> > >>>> This is also described on the following page: > >>>> http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html > >>>> > >>>> Cheers, > >>>> Leif > >>>> > >>>> On Tue, Mar 17, 2009 at 6:41 PM, ejml <eli...@gm...> > wrote: > >>>>> > >>>>> Hello Folks!, > >>>>> > >>>>> I'm trying to use Java Service Wrapper to implement my java project > >>>>> like > >>>>> windows service. My Project is made with Spring using Jetty. In other > >>>>> words, > >>>>> I use spring to startup jetty. This setup in eclipse work fine but I > >>>>> try > >>>>> to > >>>>> configure my application with Java Service Wrapper I get the next: > >>>>> > >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Allocating a console for > the > >>>>> service. > >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Found console window. > >>>>> STATUS | wrapper | 2009/03/17 09:40:35 | --> Wrapper Started as > >>>>> Service > >>>>> STATUS | wrapper | 2009/03/17 09:40:35 | Java Service Wrapper > >>>>> Community > >>>>> Edition 3.3.3 > >>>>> STATUS | wrapper | 2009/03/17 09:40:35 | Copyright (C) 1999-2009 > >>>>> Tanuki > >>>>> Software, Ltd. All Rights Reserved. > >>>>> STATUS | wrapper | 2009/03/17 09:40:35 | > >>>>> http://wrapper.tanukisoftware.org > >>>>> STATUS | wrapper | 2009/03/17 09:40:35 | > >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Using tick timer. > >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | server listening on port > >>>>> 32000. > >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Ping settings: > >>>>> wrapper.ping.interval=5, wrapper.ping.interval.logged=1, > >>>>> wrapper.ping.timeout=30 > >>>>> STATUS | wrapper | 2009/03/17 09:40:35 | Launching a JVM... > >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | command: > >>>>> "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath > >>>>> > "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" > >>>>> -Dwrapper.key="fREO9IxlyMDSknzk" -Dwrapper.port=32000 > >>>>> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 > >>>>> -Dwrapper.debug="TRUE" -Dwrapper.pid=4020 -Dwrapper.version="3.3.3" > >>>>> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" > >>>>> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 > >>>>> com.gvs.AXConnectorServer.AXConnectorServiceWin32 > >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM started (PID=3756) > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> WrapperManager class initialized by thread: main Using classloader: > >>>>> sun.misc.Launcher$AppClassLoader@11b86e7 > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager: > >>>>> Initializing... > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: JVM > #1 > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > Running > >>>>> a > >>>>> 32-bit JVM. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> Registering > >>>>> shutdown hook > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Using > >>>>> wrapper > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Load > >>>>> native > >>>>> library. One or more attempts may fail if platform specific > libraries > >>>>> do > >>>>> not exist. This is NORMAL and is only a problem if they all fail. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> Unable > >>>>> to > >>>>> load native library: wrapper-windows-x86-32.dll Cause: no > >>>>> wrapper-windows-x86-32 in java.library.path > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> Loaded > >>>>> native library: wrapper.dll > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > Calling > >>>>> native initialization method. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: > >>>>> Initializing > >>>>> WrapperManager native library. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Java > >>>>> Executable: > >>>>> C:\WINNT\system32\java.exe > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Windows > >>>>> version: > >>>>> 5.0.2195 > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java > >>>>> Version > >>>>> : 1.6.0_11-b03 Java HotSpot(TM) Client VM > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java > VM > >>>>> Vendor : Sun Microsystems Inc. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS > Name > >>>>> : Windows 2000 > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS > Arch > >>>>> : x86 > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> > WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9 > , > >>>>> args[]) called by thread: main > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > Startup > >>>>> runner thread started. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > Control > >>>>> event monitor thread started. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> Communications runner thread started. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Open > >>>>> socket > >>>>> to wrapper...Wrapper-Connection > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > Failed > >>>>> attempt to bind using local port 31000 > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > Opened > >>>>> Socket from 31001 to 32000 > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send > a > >>>>> packet KEY : fREO9IxlyMDSknzk > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001]) > >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | accepted a socket from > >>>>> 127.0.0.1 > >>>>> on port 31001 > >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet KEY : > >>>>> fREO9IxlyMDSknzk > >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Got key from JVM: > >>>>> fREO9IxlyMDSknzk > >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet LOW_LOG_LEVEL > : > >>>>> 1 > >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PING_TIMEOUT > : > >>>>> 30 > >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PROPERTIES : > >>>>> (Property Values) > >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Start Application. > >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet START : start > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> Received > >>>>> a > >>>>> packet LOW_LOG_LEVEL : 1 > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> LowLogLevel > >>>>> from Wrapper is 1 > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> Received > >>>>> a > >>>>> packet PING_TIMEOUT : 30 > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> PingTimeout > >>>>> from Wrapper is 30000 > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> Received > >>>>> a > >>>>> packet PROPERTIES : (Property Values) > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> Received > >>>>> a > >>>>> packet START : start > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > calling > >>>>> WrapperListener.start() > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> WrapperListener.start runner thread started. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> returned > >>>>> from WrapperListener.start() > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> WrapperListener.start() returned an exit code of 0. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>>> WrapperManager.stop(0) called by thread: WrapperListener_start_runner > >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send > a > >>>>> packet STOP : 0 > >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet STOP : 0 > >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM requested a shutdown. > (0) > >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | wrapperStopProcess(0) > called. > >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Sending stop signal to JVM > >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet STOP : NULL > >>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: > >>>>> Received > >>>>> a > >>>>> packet STOP : > >>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: > Thread, > >>>>> WrapperListener_start_runner, handling the shutdown process. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: > >>>>> shutdownJVM(0) Thread:WrapperListener_start_runner > >>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: wait > >>>>> for > >>>>> 0 > >>>>> shutdown locs to be released. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Send > a > >>>>> packet STOPPED : 0 > >>>>> DEBUG | wrapperp | 2009/03/17 09:40:36 | read a packet STOPPED : 0 > >>>>> DEBUG | wrapper | 2009/03/17 09:40:36 | JVM signalled that it was > >>>>> stopped. > >>>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: > Closing > >>>>> socket. > >>>>> DEBUG | wrapperp | 2009/03/17 09:40:37 | socket read no code > >>>>> (closed?). > >>>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: > calling > >>>>> System.exit(0) > >>>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: > Server > >>>>> daemon shut down > >>>>> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM process exited with a > >>>>> code > >>>>> of > >>>>> 0, leaving the wrapper exit code set to 0. > >>>>> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM exited normally. > >>>>> STATUS | wrapper | 2009/03/17 09:40:37 | <-- Wrapper Stopped > >>>>> > >>>>> This log say us something. > >>>>> > >>>>> Thanks in advance!!. > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: no s. <mrs...@gm...> - 2009-03-19 14:31:44
|
Hi Leif Thanks for your reply, I will enable this. 1) The Wrapper has a property which lets you monitor the JVM and > Wrapper memory usage at regular intervals over time. This tends to be > more accurate than the values that can be taken from within Java. > They are not yet documented as I have waiting to add support on UNIX > platforms as well. The following will dump memory stats to the log > file once every minute. Hopefully this will help you to pinpoint the > precise actions which are causing the problem. > --- > wrapper.memory_output=TRUE > wrapper.memory_output.interval=60 > --- > We don't need super fast performance since we're just starting records and then monitoring them. We can test this on our reference machine first, of course we've not been able to duplicate it in that environment. > > 2) Enable profiling in the JVM. This will greatly decrease the > performance of the JVM but it will produce very detailed heap dumps > that let you find the precise stack traces where objects are being > created. It is possible that you have some kind of an object leak in > your code someplace. The first property is to enable the profiling. > Be sure to change the "7" to whatever is appropriate for your > configuration. The long shutdown timeouts are to make sure that the > Wrapper gives the JVM time to write out its dump file on shutdown. > --- > wrapper.java.additional.7=-Xrunhprof:heap=sites,depth=8 > wrapper.shutdown.timeout=1800 > wrapper.jvm_exit.timeout=1800 > --- > I would suggest running on a test machine for a few hours and then > hitting CTRL-C to kill the JVM. After a couple minutes, the Wrapper > will stop and you will find a profile file in the directory where the > wrapper.exe is located. The very end of the file contains object > counts in order of their total number. Next to each object is a > location number where that object is created. Search for that number > in the first 95% of the file to get the stack trace where it is being > created. The format can take a little work to get used to and you > will need an editor that is capable of handling such huge files. I > have used SitePadPro for many years, a great editor. > We have 2 machines controlling records. When we reboot a machine we have to ensure no records will start during that interval. It can't be automated unfortunately. > > 3) The Professional Edition of the Wrapper has a feature which will > let you avoid this problem before it gets too bad while you are > attempting to get the root cause resolved. The following properties > can be used to tell the Wrapper to restart the JVM at specific times > when you know it will not affect your customer's business. > http://wrapper.tanukisoftware.org/doc/english/prop-timer-n.html > --- > wrapper.timer.action.1=RESTART > wrapper.timer.interval.1=day-of-week=1; hour=4 > --- > That will restart the JVM every Sunday morning at 4am. > The following settings will also tell the Wrapper to invoke a thread > dump once every 3 hours > --- > wrapper.timer.action.2=DUMP > wrapper.timer.interval.2=hour=*/3 > --- > I would be happy to provide you with a trial license to test this out. > > 4) An aside, but you can greatly clean up your classpath configuration > by using wildcards as follows: > wrapper.java.classpath.1=../javawrapper/lib/wrapper.jar > wrapper.java.classpath.2=classes > wrapper.java.classpath.3=lib/*.jar > > The last dump had this in the java service wrapper output which leads me to believe it may be a native library problem: The JVM process terminated due to an uncaught exception: EXCEPTION_ACCESS_VIOLATION (0xc0000005) ERROR | wrapper | 2009/03/17 15:10:52 | JVM exited unexpectedly. STATUS | wrapper | 2009/03/17 15:10:56 | Launching a JVM... > > I notice that you are using some other JNI libraries. Memory leaks > in there will appear to be part of the JVM's memory but you will not > be able to locate many of those problems using the profiling in 2) > unless the memory being leaked is Java objects. In that case 3) may > be the best short term solution for you. > > Cheers, > Leif > > 2009/3/19 no spam <mrs...@gm...>: > > I have a production application that dumps every few months and takes out > a > > large number of recording devices. Needless to say my client is not > happy. > > I don't always get a thread dump ( I'd like to know how to always get > one ) > > but I managed to capture one of them below from the hotspot jvm. You'll > see > > at the bottom of the dump that this is a windows server 2003 server and > it > > has 4 gigs of memory. I am running 2 separate jvms on this machine both > via > > java service wrapper. > > Here is my java service wrapper setup. Currently I have it set to 512 > megs > > of ram and just last week we looked and it wasn't taking up around 220 > megs > > as shown via the task manager. It consumes memory at a slow rate. > > > > #******************************************************************** > > # Java Application > > > > wrapper.java.command=C:/Program Files/Java/jre1.6.0_03/bin/java > > > > # > > # Memory / GC Tuning > > # > > wrapper.java.maxmemory=512 > > wrapper.ping.timeout=600 > > wrapper.ntservice.account=<user> > > wrapper.ntservice.password.prompt=TRUE > > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp > > wrapper.app.parameter.1=com.proxygen.mvcp.MVCPDaemon > > wrapper.working.dir=c:/<working dir> > > wrapper.java.classpath.1=../javawrapper/lib/wrapper.jar > > wrapper.java.classpath.2=classes > > wrapper.java.classpath.3=lib/antlr-2.7.6.jar > > wrapper.java.classpath.4=lib/asm-1.5.3.jar > > wrapper.java.classpath.5=lib/asm-attrs-1.5.3.jar > > > wrapper.java.classpath.6=lib/cglib-2.1.3.jar;lib/commons-beanutils-1.7.0.jar > > wrapper.java.classpath.7=lib/commons-codec-1.3.jar > > wrapper.java.classpath.8=lib/commons-collections-3.2.jar > > wrapper.java.classpath.9=lib/commons-dbcp-1.2.1.jar > > wrapper.java.classpath.10=lib/commons-httpclient-3.0.1.jar > > wrapper.java.classpath.11=lib/commons-lang-2.1.jar > > wrapper.java.classpath.12=lib/commons-logging-1.0.4.jar > > wrapper.java.classpath.13=lib/commons-net-1.2.2.jar > > wrapper.java.classpath.14=lib/commons-pool-1.3.jar > > wrapper.java.classpath.15=lib/dom4j-1.6.1.jar > > wrapper.java.classpath.16=lib/ehcache-1.2.3.jar > > wrapper.java.classpath.17=lib/hibernate-3.2.1.ga.jar > > wrapper.java.classpath.18=lib/jdom-1.0.jar > > wrapper.java.classpath.19=lib/jta-1.0.1B.jar > > wrapper.java.classpath.20=lib/kfservice-1.0.0.16.jar > > wrapper.java.classpath.21=lib/log4j-1.2.13.jar > > . > > . > > . > > wrapper.java.classpath.25=lib/ojdbc-9.0.2.0.0.jar > > wrapper.java.classpath.26=lib/proxybrowse-1.0.0.12.jar > > wrapper.java.classpath.27=lib/spring-2.0.1.jar > > wrapper.java.classpath.28=lib/xpp3_min-1.1.3.4.O.jar > > wrapper.java.classpath.29=lib/xstream-1.2.1.jar > > wrapper.java.classpath.30=lib/ifxjdbc_3_0_jc3.jar > > wrapper.java.classpath.31=lib/jintegra.jar > > wrapper.java.classpath.32=lib/concurrent.jar > > > > > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > > wrapper.java.library.path.1=../javawrapper/lib > > wrapper.java.library.path.2=lib/jintegra > > wrapper.java.library.path.3=lib/jintegra/international > > > > #******************************************************************** > > # Wrapper Logging Properties > > #******************************************************************** > > # Format of output for the console. (See docs for formats) > > wrapper.console.format=PM > > # Log Level for console output. (See docs for log levels) > > wrapper.console.loglevel=INFO > > # Log file to use for wrapper output logging. > > wrapper.logfile=log/wrapper_mvcp-YYYYMMDD.log > > # Format of output for the log file. (See docs for formats) > > wrapper.logfile.format=LPTM > > # Log Level for log file output. (See docs for log levels) > > wrapper.logfile.loglevel=INFO > > # Maximum size that the log file will be allowed to grow to before > > # the log is rolled. Size is specified in bytes. The default value > > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or > > # 'm' (mb) suffix. For example: 10m = 10 megabytes. > > # wrapper.logfile.maxsize=10m > > # Maximum number of rolled log files which will be allowed before old > > # files are deleted. The default value of 0 implies no limit. > > wrapper.logfile.maxfiles=30 > > # > > # roll daily > > wrapper.logfile.rollmode=DATE > > # Log Level for sys/event log output. (See docs for log levels) > > wrapper.syslog.loglevel=NONE > > # Mode in which the service is installed. AUTO_START or DEMAND_START > > wrapper.ntservice.starttype=AUTO_START > > # Allow the service to interact with the desktop. > > wrapper.ntservice.interactive=false > > > > > > > > # > > # An unexpected error has been detected by Java Runtime Environment: > > # > > # java.lang.OutOfMemoryError: requested 32756 bytes for > ChunkPool::allocate. > > Out of swap space? > > # > > # Internal Error (414C4C4F434154494F4E0E4350500065), pid=9928, tid=5936 > > # > > # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-b05 mixed mode, sharing) > > # If you would like to submit a bug report, please visit: > > # http://java.sun.com/webapps/bugreport/crash.jsp > > # > > --------------- T H R E A D --------------- > > Current thread (0x03205c00): JavaThread "J-Integra COM initialization > > thread (please don't touch)" daemon [_thread_in_vm, id=5936] > > Stack: [0x03bb0000,0x03c00000) > > [error occurred during error reporting, step 110, id 0xc0000005] > > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > > j > com.linar.jintegra.NativeObjRef.initializeCOM(IZZZZZ)Ljava/lang/String;+0 > > j com.linar.jintegra.NativeInitThread.run()V+32 > > j java.lang.Thread.run()V+11 > > v ~StubRoutines::call_stub > > --------------- P R O C E S S --------------- > > Java Threads: ( => current thread ) > > =>0x03205c00 JavaThread "J-Integra COM initialization thread (please > don't > > touch)" daemon [_thread_in_vm, id=5936] > > 0x03198400 JavaThread "Protocol Worker" [_thread_blocked, id=7660] > > 0x0311a800 JavaThread "MVCP Daemon" [_thread_in_native, id=10056] > > 0x0323e400 JavaThread "Mediasource QueueWorker" [_thread_blocked, > > id=10052] > > 0x03206800 JavaThread "RestRequest QueueWorker" [_thread_blocked, > id=9988] > > 0x031e3800 JavaThread "Client Command Manager" [_thread_blocked, > id=9996] > > 0x03227400 JavaThread "record cleanup" [_thread_blocked, id=10048] > > 0x02d7d800 JavaThread "Timer-2" [_thread_blocked, id=10044] > > 0x02e08000 JavaThread "Timer-1" [_thread_blocked, id=10040] > > 0x02e09400 JavaThread "Timer-0" [_thread_blocked, id=10036] > > 0x02e5f800 JavaThread "record cleanup" [_thread_blocked, id=10032] > > 0x00297800 JavaThread "DestroyJavaVM" [_thread_blocked, id=9936] > > 0x02dd1800 JavaThread "Wrapper-Connection" daemon [_thread_in_native, > > id=7484] > > 0x02d74c00 JavaThread "Wrapper-Control-Event-Monitor" daemon > > [_thread_blocked, id=9976] > > 0x0290dc00 JavaThread "Low Memory Detector" daemon [_thread_blocked, > > id=9968] > > 0x02909000 JavaThread "CompilerThread0" daemon [_thread_blocked, > id=7332] > > 0x02908000 JavaThread "Attach Listener" daemon [_thread_blocked, > id=9960] > > 0x02907000 JavaThread "Signal Dispatcher" daemon [_thread_blocked, > > id=9952] > > 0x028ff400 JavaThread "Finalizer" daemon [_thread_blocked, id=9948] > > 0x028fe400 JavaThread "Reference Handler" daemon [_thread_blocked, > > id=9944] > > Other Threads: > > 0x028fd000 VMThread [id=9940] > > 0x02918400 WatcherThread [id=9972] > > VM state:not at safepoint (normal execution) > > VM Mutex/Monitor currently owned by a thread: None > > Heap > > def new generation total 960K, used 413K [0x06970000, 0x06a70000, > > 0x090d0000) > > eden space 896K, 38% used [0x06970000, 0x069c7478, 0x06a50000) > > from space 64K, 100% used [0x06a50000, 0x06a60000, 0x06a60000) > > to space 64K, 0% used [0x06a60000, 0x06a60000, 0x06a70000) > > tenured generation total 4096K, used 1104K [0x090d0000, 0x094d0000, > > 0x26970000) > > the space 4096K, 26% used [0x090d0000, 0x091e41c8, 0x091e4200, > > 0x094d0000) > > compacting perm gen total 12288K, used 4494K [0x26970000, 0x27570000, > > 0x2a970000) > > the space 12288K, 36% used [0x26970000, 0x26dd3bd8, 0x26dd3c00, > > 0x27570000) > > ro space 8192K, 62% used [0x2a970000, 0x2ae714a8, 0x2ae71600, > > 0x2b170000) > > rw space 12288K, 52% used [0x2b170000, 0x2b7b7278, 0x2b7b7400, > > 0x2bd70000) > > Dynamic libraries: > > 0x00400000 - 0x00423000 C:\Program Files\Java\jre1.6.0_03\bin\java.exe > > 0x7c800000 - 0x7c8c0000 C:\WINDOWS\system32\ntdll.dll > > 0x77e40000 - 0x77f42000 C:\WINDOWS\system32\kernel32.dll > > 0x77f50000 - 0x77feb000 C:\WINDOWS\system32\ADVAPI32.dll > > 0x77c50000 - 0x77cef000 C:\WINDOWS\system32\RPCRT4.dll > > 0x76f50000 - 0x76f63000 C:\WINDOWS\system32\Secur32.dll > > 0x7c340000 - 0x7c396000 C:\Program Files\Java\jre1.6.0_03\bin\msvcr71.dll > > 0x6d7c0000 - 0x6da0a000 C:\Program > Files\Java\jre1.6.0_03\bin\client\jvm.dll > > 0x77380000 - 0x77411000 C:\WINDOWS\system32\USER32.dll > > 0x77c00000 - 0x77c48000 C:\WINDOWS\system32\GDI32.dll > > 0x76aa0000 - 0x76acd000 C:\WINDOWS\system32\WINMM.dll > > 0x76290000 - 0x762ad000 C:\WINDOWS\system32\IMM32.DLL > > 0x6d310000 - 0x6d318000 C:\Program Files\Java\jre1.6.0_03\bin\hpi.dll > > 0x76b70000 - 0x76b7b000 C:\WINDOWS\system32\PSAPI.DLL > > 0x6d770000 - 0x6d77c000 C:\Program Files\Java\jre1.6.0_03\bin\verify.dll > > 0x6d3b0000 - 0x6d3cf000 C:\Program Files\Java\jre1.6.0_03\bin\java.dll > > 0x6d7b0000 - 0x6d7bf000 C:\Program Files\Java\jre1.6.0_03\bin\zip.dll > > 0x02e60000 - 0x02e77000 C:\ipe\javawrapper\lib\wrapper.dll > > 0x6d570000 - 0x6d583000 C:\Program Files\Java\jre1.6.0_03\bin\net.dll > > 0x71c00000 - 0x71c17000 C:\WINDOWS\system32\WS2_32.dll > > 0x77ba0000 - 0x77bfa000 C:\WINDOWS\system32\msvcrt.dll > > 0x71bf0000 - 0x71bf8000 C:\WINDOWS\system32\WS2HELP.dll > > 0x71b20000 - 0x71b61000 C:\WINDOWS\system32\mswsock.dll > > 0x5f270000 - 0x5f2ca000 C:\WINDOWS\system32\hnetcfg.dll > > 0x71ae0000 - 0x71ae8000 C:\WINDOWS\System32\wshtcpip.dll > > 0x76ed0000 - 0x76efa000 C:\WINDOWS\system32\DNSAPI.dll > > 0x76f70000 - 0x76f77000 C:\WINDOWS\System32\winrnr.dll > > 0x76f10000 - 0x76f3e000 C:\WINDOWS\system32\WLDAP32.dll > > 0x76f80000 - 0x76f85000 C:\WINDOWS\system32\rasadhlp.dll > > 0x68000000 - 0x68035000 C:\WINDOWS\system32\rsaenh.dll > > 0x76920000 - 0x769e2000 C:\WINDOWS\system32\USERENV.dll > > 0x71c40000 - 0x71c97000 C:\WINDOWS\system32\netapi32.dll > > 0x03760000 - 0x037a0000 C:\ipe\mvcp\lib\jintegra\ntvinv.dll > > 0x77670000 - 0x777a9000 C:\WINDOWS\system32\ole32.dll > > 0x77d00000 - 0x77d8b000 C:\WINDOWS\system32\OLEAUT32.dll > > 0x5fcc0000 - 0x5fcc5000 C:\WINDOWS\system32\mtxex.dll > > 0x4a710000 - 0x4a855000 C:\WINDOWS\system32\COMSVCS.dll > > 0x03900000 - 0x03907000 > > C:\ipe\mvcp\lib\jintegra\International\ntvinvenglishresourcedll.dll > > 0x73eb0000 - 0x73fd1000 C:\WINDOWS\system32\MFC42.DLL > > 0x46a70000 - 0x46b40000 C:\WINDOWS\system32\WININET.dll > > 0x77da0000 - 0x77df2000 C:\WINDOWS\system32\SHLWAPI.dll > > 0x03910000 - 0x03919000 C:\WINDOWS\system32\Normaliz.dll > > 0x46300000 - 0x46345000 C:\WINDOWS\system32\iertutil.dll > > 0x71bb0000 - 0x71bb9000 C:\WINDOWS\system32\WSOCK32.dll > > 0x48890000 - 0x488cd000 C:\WINDOWS\system32\ODBC32.dll > > 0x77530000 - 0x775c7000 > > > C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_5.82.3790.3959_x-ww_78FCF8D0\COMCTL32.dll > > 0x7c8d0000 - 0x7d0cf000 C:\WINDOWS\system32\SHELL32.dll > > 0x762b0000 - 0x762f9000 C:\WINDOWS\system32\comdlg32.dll > > 0x77420000 - 0x77523000 > > > C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.3959_x-ww_D8713E55\comctl32.dll > > 0x03b10000 - 0x03b27000 C:\WINDOWS\system32\odbcint.dll > > VM Arguments: > > jvm_args: -Xmx512m > > > -Djava.library.path=../javawrapper/lib;lib/jintegra;lib/jintegra/international > > -Dwrapper.key=ewtHOrkX3QrgQGVo -Dwrapper.port=32000 > > -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 > -Dwrapper.pid=1388 > > -Dwrapper.version=3.2.3 -Dwrapper.native_library=wrapper > > -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=2 > > java_command: org.tanukisoftware.wrapper.WrapperSimpleApp > > com.proxygen.mvcp.MVCPDaemon > > Launcher Type: SUN_STANDARD > > Environment Variables: > > PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem > > USERNAME=<user> > > OS=Windows_NT > > PROCESSOR_IDENTIFIER=x86 Family 6 Model 15 Stepping 6, GenuineIntel > > > > > > --------------- S Y S T E M --------------- > > OS: Windows Server 2003 family Build 3790 Service Pack 2 > > CPU:total 4 (2 cores per cpu, 1 threads per core) family 6 model 15 > stepping > > 6, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3 > > Memory: 4k page, physical 2097151k(66888k free), swap 4194303k(5132k > free) > > vm_info: Java HotSpot(TM) Client VM (1.6.0_03-b05) for windows-x86, built > on > > Sep 24 2007 22:24:33 by "java_re" with unknown MS VC++:1310 > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2009-03-19 02:42:02
|
There are a number of things we can try out to help you track this down. 1) The Wrapper has a property which lets you monitor the JVM and Wrapper memory usage at regular intervals over time. This tends to be more accurate than the values that can be taken from within Java. They are not yet documented as I have waiting to add support on UNIX platforms as well. The following will dump memory stats to the log file once every minute. Hopefully this will help you to pinpoint the precise actions which are causing the problem. --- wrapper.memory_output=TRUE wrapper.memory_output.interval=60 --- 2) Enable profiling in the JVM. This will greatly decrease the performance of the JVM but it will produce very detailed heap dumps that let you find the precise stack traces where objects are being created. It is possible that you have some kind of an object leak in your code someplace. The first property is to enable the profiling. Be sure to change the "7" to whatever is appropriate for your configuration. The long shutdown timeouts are to make sure that the Wrapper gives the JVM time to write out its dump file on shutdown. --- wrapper.java.additional.7=-Xrunhprof:heap=sites,depth=8 wrapper.shutdown.timeout=1800 wrapper.jvm_exit.timeout=1800 --- I would suggest running on a test machine for a few hours and then hitting CTRL-C to kill the JVM. After a couple minutes, the Wrapper will stop and you will find a profile file in the directory where the wrapper.exe is located. The very end of the file contains object counts in order of their total number. Next to each object is a location number where that object is created. Search for that number in the first 95% of the file to get the stack trace where it is being created. The format can take a little work to get used to and you will need an editor that is capable of handling such huge files. I have used SitePadPro for many years, a great editor. 3) The Professional Edition of the Wrapper has a feature which will let you avoid this problem before it gets too bad while you are attempting to get the root cause resolved. The following properties can be used to tell the Wrapper to restart the JVM at specific times when you know it will not affect your customer's business. http://wrapper.tanukisoftware.org/doc/english/prop-timer-n.html --- wrapper.timer.action.1=RESTART wrapper.timer.interval.1=day-of-week=1; hour=4 --- That will restart the JVM every Sunday morning at 4am. The following settings will also tell the Wrapper to invoke a thread dump once every 3 hours --- wrapper.timer.action.2=DUMP wrapper.timer.interval.2=hour=*/3 --- I would be happy to provide you with a trial license to test this out. 4) An aside, but you can greatly clean up your classpath configuration by using wildcards as follows: wrapper.java.classpath.1=../javawrapper/lib/wrapper.jar wrapper.java.classpath.2=classes wrapper.java.classpath.3=lib/*.jar I notice that you are using some other JNI libraries. Memory leaks in there will appear to be part of the JVM's memory but you will not be able to locate many of those problems using the profiling in 2) unless the memory being leaked is Java objects. In that case 3) may be the best short term solution for you. Cheers, Leif 2009/3/19 no spam <mrs...@gm...>: > I have a production application that dumps every few months and takes out a > large number of recording devices. Needless to say my client is not happy. > I don't always get a thread dump ( I'd like to know how to always get one ) > but I managed to capture one of them below from the hotspot jvm. You'll see > at the bottom of the dump that this is a windows server 2003 server and it > has 4 gigs of memory. I am running 2 separate jvms on this machine both via > java service wrapper. > Here is my java service wrapper setup. Currently I have it set to 512 megs > of ram and just last week we looked and it wasn't taking up around 220 megs > as shown via the task manager. It consumes memory at a slow rate. > > #******************************************************************** > # Java Application > > wrapper.java.command=C:/Program Files/Java/jre1.6.0_03/bin/java > > # > # Memory / GC Tuning > # > wrapper.java.maxmemory=512 > wrapper.ping.timeout=600 > wrapper.ntservice.account=<user> > wrapper.ntservice.password.prompt=TRUE > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp > wrapper.app.parameter.1=com.proxygen.mvcp.MVCPDaemon > wrapper.working.dir=c:/<working dir> > wrapper.java.classpath.1=../javawrapper/lib/wrapper.jar > wrapper.java.classpath.2=classes > wrapper.java.classpath.3=lib/antlr-2.7.6.jar > wrapper.java.classpath.4=lib/asm-1.5.3.jar > wrapper.java.classpath.5=lib/asm-attrs-1.5.3.jar > wrapper.java.classpath.6=lib/cglib-2.1.3.jar;lib/commons-beanutils-1.7.0.jar > wrapper.java.classpath.7=lib/commons-codec-1.3.jar > wrapper.java.classpath.8=lib/commons-collections-3.2.jar > wrapper.java.classpath.9=lib/commons-dbcp-1.2.1.jar > wrapper.java.classpath.10=lib/commons-httpclient-3.0.1.jar > wrapper.java.classpath.11=lib/commons-lang-2.1.jar > wrapper.java.classpath.12=lib/commons-logging-1.0.4.jar > wrapper.java.classpath.13=lib/commons-net-1.2.2.jar > wrapper.java.classpath.14=lib/commons-pool-1.3.jar > wrapper.java.classpath.15=lib/dom4j-1.6.1.jar > wrapper.java.classpath.16=lib/ehcache-1.2.3.jar > wrapper.java.classpath.17=lib/hibernate-3.2.1.ga.jar > wrapper.java.classpath.18=lib/jdom-1.0.jar > wrapper.java.classpath.19=lib/jta-1.0.1B.jar > wrapper.java.classpath.20=lib/kfservice-1.0.0.16.jar > wrapper.java.classpath.21=lib/log4j-1.2.13.jar > . > . > . > wrapper.java.classpath.25=lib/ojdbc-9.0.2.0.0.jar > wrapper.java.classpath.26=lib/proxybrowse-1.0.0.12.jar > wrapper.java.classpath.27=lib/spring-2.0.1.jar > wrapper.java.classpath.28=lib/xpp3_min-1.1.3.4.O.jar > wrapper.java.classpath.29=lib/xstream-1.2.1.jar > wrapper.java.classpath.30=lib/ifxjdbc_3_0_jc3.jar > wrapper.java.classpath.31=lib/jintegra.jar > wrapper.java.classpath.32=lib/concurrent.jar > > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > wrapper.java.library.path.1=../javawrapper/lib > wrapper.java.library.path.2=lib/jintegra > wrapper.java.library.path.3=lib/jintegra/international > > #******************************************************************** > # Wrapper Logging Properties > #******************************************************************** > # Format of output for the console. (See docs for formats) > wrapper.console.format=PM > # Log Level for console output. (See docs for log levels) > wrapper.console.loglevel=INFO > # Log file to use for wrapper output logging. > wrapper.logfile=log/wrapper_mvcp-YYYYMMDD.log > # Format of output for the log file. (See docs for formats) > wrapper.logfile.format=LPTM > # Log Level for log file output. (See docs for log levels) > wrapper.logfile.loglevel=INFO > # Maximum size that the log file will be allowed to grow to before > # the log is rolled. Size is specified in bytes. The default value > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or > # 'm' (mb) suffix. For example: 10m = 10 megabytes. > # wrapper.logfile.maxsize=10m > # Maximum number of rolled log files which will be allowed before old > # files are deleted. The default value of 0 implies no limit. > wrapper.logfile.maxfiles=30 > # > # roll daily > wrapper.logfile.rollmode=DATE > # Log Level for sys/event log output. (See docs for log levels) > wrapper.syslog.loglevel=NONE > # Mode in which the service is installed. AUTO_START or DEMAND_START > wrapper.ntservice.starttype=AUTO_START > # Allow the service to interact with the desktop. > wrapper.ntservice.interactive=false > > > > # > # An unexpected error has been detected by Java Runtime Environment: > # > # java.lang.OutOfMemoryError: requested 32756 bytes for ChunkPool::allocate. > Out of swap space? > # > # Internal Error (414C4C4F434154494F4E0E4350500065), pid=9928, tid=5936 > # > # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-b05 mixed mode, sharing) > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # > --------------- T H R E A D --------------- > Current thread (0x03205c00): JavaThread "J-Integra COM initialization > thread (please don't touch)" daemon [_thread_in_vm, id=5936] > Stack: [0x03bb0000,0x03c00000) > [error occurred during error reporting, step 110, id 0xc0000005] > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j com.linar.jintegra.NativeObjRef.initializeCOM(IZZZZZ)Ljava/lang/String;+0 > j com.linar.jintegra.NativeInitThread.run()V+32 > j java.lang.Thread.run()V+11 > v ~StubRoutines::call_stub > --------------- P R O C E S S --------------- > Java Threads: ( => current thread ) > =>0x03205c00 JavaThread "J-Integra COM initialization thread (please don't > touch)" daemon [_thread_in_vm, id=5936] > 0x03198400 JavaThread "Protocol Worker" [_thread_blocked, id=7660] > 0x0311a800 JavaThread "MVCP Daemon" [_thread_in_native, id=10056] > 0x0323e400 JavaThread "Mediasource QueueWorker" [_thread_blocked, > id=10052] > 0x03206800 JavaThread "RestRequest QueueWorker" [_thread_blocked, id=9988] > 0x031e3800 JavaThread "Client Command Manager" [_thread_blocked, id=9996] > 0x03227400 JavaThread "record cleanup" [_thread_blocked, id=10048] > 0x02d7d800 JavaThread "Timer-2" [_thread_blocked, id=10044] > 0x02e08000 JavaThread "Timer-1" [_thread_blocked, id=10040] > 0x02e09400 JavaThread "Timer-0" [_thread_blocked, id=10036] > 0x02e5f800 JavaThread "record cleanup" [_thread_blocked, id=10032] > 0x00297800 JavaThread "DestroyJavaVM" [_thread_blocked, id=9936] > 0x02dd1800 JavaThread "Wrapper-Connection" daemon [_thread_in_native, > id=7484] > 0x02d74c00 JavaThread "Wrapper-Control-Event-Monitor" daemon > [_thread_blocked, id=9976] > 0x0290dc00 JavaThread "Low Memory Detector" daemon [_thread_blocked, > id=9968] > 0x02909000 JavaThread "CompilerThread0" daemon [_thread_blocked, id=7332] > 0x02908000 JavaThread "Attach Listener" daemon [_thread_blocked, id=9960] > 0x02907000 JavaThread "Signal Dispatcher" daemon [_thread_blocked, > id=9952] > 0x028ff400 JavaThread "Finalizer" daemon [_thread_blocked, id=9948] > 0x028fe400 JavaThread "Reference Handler" daemon [_thread_blocked, > id=9944] > Other Threads: > 0x028fd000 VMThread [id=9940] > 0x02918400 WatcherThread [id=9972] > VM state:not at safepoint (normal execution) > VM Mutex/Monitor currently owned by a thread: None > Heap > def new generation total 960K, used 413K [0x06970000, 0x06a70000, > 0x090d0000) > eden space 896K, 38% used [0x06970000, 0x069c7478, 0x06a50000) > from space 64K, 100% used [0x06a50000, 0x06a60000, 0x06a60000) > to space 64K, 0% used [0x06a60000, 0x06a60000, 0x06a70000) > tenured generation total 4096K, used 1104K [0x090d0000, 0x094d0000, > 0x26970000) > the space 4096K, 26% used [0x090d0000, 0x091e41c8, 0x091e4200, > 0x094d0000) > compacting perm gen total 12288K, used 4494K [0x26970000, 0x27570000, > 0x2a970000) > the space 12288K, 36% used [0x26970000, 0x26dd3bd8, 0x26dd3c00, > 0x27570000) > ro space 8192K, 62% used [0x2a970000, 0x2ae714a8, 0x2ae71600, > 0x2b170000) > rw space 12288K, 52% used [0x2b170000, 0x2b7b7278, 0x2b7b7400, > 0x2bd70000) > Dynamic libraries: > 0x00400000 - 0x00423000 C:\Program Files\Java\jre1.6.0_03\bin\java.exe > 0x7c800000 - 0x7c8c0000 C:\WINDOWS\system32\ntdll.dll > 0x77e40000 - 0x77f42000 C:\WINDOWS\system32\kernel32.dll > 0x77f50000 - 0x77feb000 C:\WINDOWS\system32\ADVAPI32.dll > 0x77c50000 - 0x77cef000 C:\WINDOWS\system32\RPCRT4.dll > 0x76f50000 - 0x76f63000 C:\WINDOWS\system32\Secur32.dll > 0x7c340000 - 0x7c396000 C:\Program Files\Java\jre1.6.0_03\bin\msvcr71.dll > 0x6d7c0000 - 0x6da0a000 C:\Program Files\Java\jre1.6.0_03\bin\client\jvm.dll > 0x77380000 - 0x77411000 C:\WINDOWS\system32\USER32.dll > 0x77c00000 - 0x77c48000 C:\WINDOWS\system32\GDI32.dll > 0x76aa0000 - 0x76acd000 C:\WINDOWS\system32\WINMM.dll > 0x76290000 - 0x762ad000 C:\WINDOWS\system32\IMM32.DLL > 0x6d310000 - 0x6d318000 C:\Program Files\Java\jre1.6.0_03\bin\hpi.dll > 0x76b70000 - 0x76b7b000 C:\WINDOWS\system32\PSAPI.DLL > 0x6d770000 - 0x6d77c000 C:\Program Files\Java\jre1.6.0_03\bin\verify.dll > 0x6d3b0000 - 0x6d3cf000 C:\Program Files\Java\jre1.6.0_03\bin\java.dll > 0x6d7b0000 - 0x6d7bf000 C:\Program Files\Java\jre1.6.0_03\bin\zip.dll > 0x02e60000 - 0x02e77000 C:\ipe\javawrapper\lib\wrapper.dll > 0x6d570000 - 0x6d583000 C:\Program Files\Java\jre1.6.0_03\bin\net.dll > 0x71c00000 - 0x71c17000 C:\WINDOWS\system32\WS2_32.dll > 0x77ba0000 - 0x77bfa000 C:\WINDOWS\system32\msvcrt.dll > 0x71bf0000 - 0x71bf8000 C:\WINDOWS\system32\WS2HELP.dll > 0x71b20000 - 0x71b61000 C:\WINDOWS\system32\mswsock.dll > 0x5f270000 - 0x5f2ca000 C:\WINDOWS\system32\hnetcfg.dll > 0x71ae0000 - 0x71ae8000 C:\WINDOWS\System32\wshtcpip.dll > 0x76ed0000 - 0x76efa000 C:\WINDOWS\system32\DNSAPI.dll > 0x76f70000 - 0x76f77000 C:\WINDOWS\System32\winrnr.dll > 0x76f10000 - 0x76f3e000 C:\WINDOWS\system32\WLDAP32.dll > 0x76f80000 - 0x76f85000 C:\WINDOWS\system32\rasadhlp.dll > 0x68000000 - 0x68035000 C:\WINDOWS\system32\rsaenh.dll > 0x76920000 - 0x769e2000 C:\WINDOWS\system32\USERENV.dll > 0x71c40000 - 0x71c97000 C:\WINDOWS\system32\netapi32.dll > 0x03760000 - 0x037a0000 C:\ipe\mvcp\lib\jintegra\ntvinv.dll > 0x77670000 - 0x777a9000 C:\WINDOWS\system32\ole32.dll > 0x77d00000 - 0x77d8b000 C:\WINDOWS\system32\OLEAUT32.dll > 0x5fcc0000 - 0x5fcc5000 C:\WINDOWS\system32\mtxex.dll > 0x4a710000 - 0x4a855000 C:\WINDOWS\system32\COMSVCS.dll > 0x03900000 - 0x03907000 > C:\ipe\mvcp\lib\jintegra\International\ntvinvenglishresourcedll.dll > 0x73eb0000 - 0x73fd1000 C:\WINDOWS\system32\MFC42.DLL > 0x46a70000 - 0x46b40000 C:\WINDOWS\system32\WININET.dll > 0x77da0000 - 0x77df2000 C:\WINDOWS\system32\SHLWAPI.dll > 0x03910000 - 0x03919000 C:\WINDOWS\system32\Normaliz.dll > 0x46300000 - 0x46345000 C:\WINDOWS\system32\iertutil.dll > 0x71bb0000 - 0x71bb9000 C:\WINDOWS\system32\WSOCK32.dll > 0x48890000 - 0x488cd000 C:\WINDOWS\system32\ODBC32.dll > 0x77530000 - 0x775c7000 > C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_5.82.3790.3959_x-ww_78FCF8D0\COMCTL32.dll > 0x7c8d0000 - 0x7d0cf000 C:\WINDOWS\system32\SHELL32.dll > 0x762b0000 - 0x762f9000 C:\WINDOWS\system32\comdlg32.dll > 0x77420000 - 0x77523000 > C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.3959_x-ww_D8713E55\comctl32.dll > 0x03b10000 - 0x03b27000 C:\WINDOWS\system32\odbcint.dll > VM Arguments: > jvm_args: -Xmx512m > -Djava.library.path=../javawrapper/lib;lib/jintegra;lib/jintegra/international > -Dwrapper.key=ewtHOrkX3QrgQGVo -Dwrapper.port=32000 > -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=1388 > -Dwrapper.version=3.2.3 -Dwrapper.native_library=wrapper > -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=2 > java_command: org.tanukisoftware.wrapper.WrapperSimpleApp > com.proxygen.mvcp.MVCPDaemon > Launcher Type: SUN_STANDARD > Environment Variables: > PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem > USERNAME=<user> > OS=Windows_NT > PROCESSOR_IDENTIFIER=x86 Family 6 Model 15 Stepping 6, GenuineIntel > > > --------------- S Y S T E M --------------- > OS: Windows Server 2003 family Build 3790 Service Pack 2 > CPU:total 4 (2 cores per cpu, 1 threads per core) family 6 model 15 stepping > 6, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3 > Memory: 4k page, physical 2097151k(66888k free), swap 4194303k(5132k free) > vm_info: Java HotSpot(TM) Client VM (1.6.0_03-b05) for windows-x86, built on > Sep 24 2007 22:24:33 by "java_re" with unknown MS VC++:1310 |
|
From: no s. <mrs...@gm...> - 2009-03-19 02:08:04
|
I have a production application that dumps every few months and takes out a large number of recording devices. Needless to say my client is not happy. I don't always get a thread dump ( I'd like to know how to always get one ) but I managed to capture one of them below from the hotspot jvm. You'll see at the bottom of the dump that this is a windows server 2003 server and it has 4 gigs of memory. I am running 2 separate jvms on this machine both via java service wrapper. Here is my java service wrapper setup. Currently I have it set to 512 megs of ram and just last week we looked and it wasn't taking up around 220 megs as shown via the task manager. It consumes memory at a slow rate. #******************************************************************** # Java Application wrapper.java.command=C:/Program Files/Java/jre1.6.0_03/bin/java # # Memory / GC Tuning # wrapper.java.maxmemory=512 wrapper.ping.timeout=600 wrapper.ntservice.account=<user> wrapper.ntservice.password.prompt=TRUE wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp wrapper.app.parameter.1=com.proxygen.mvcp.MVCPDaemon wrapper.working.dir=c:/<working dir> wrapper.java.classpath.1=../javawrapper/lib/wrapper.jar wrapper.java.classpath.2=classes wrapper.java.classpath.3=lib/antlr-2.7.6.jar wrapper.java.classpath.4=lib/asm-1.5.3.jar wrapper.java.classpath.5=lib/asm-attrs-1.5.3.jar wrapper.java.classpath.6=lib/cglib-2.1.3.jar;lib/commons-beanutils-1.7.0.jar wrapper.java.classpath.7=lib/commons-codec-1.3.jar wrapper.java.classpath.8=lib/commons-collections-3.2.jar wrapper.java.classpath.9=lib/commons-dbcp-1.2.1.jar wrapper.java.classpath.10=lib/commons-httpclient-3.0.1.jar wrapper.java.classpath.11=lib/commons-lang-2.1.jar wrapper.java.classpath.12=lib/commons-logging-1.0.4.jar wrapper.java.classpath.13=lib/commons-net-1.2.2.jar wrapper.java.classpath.14=lib/commons-pool-1.3.jar wrapper.java.classpath.15=lib/dom4j-1.6.1.jar wrapper.java.classpath.16=lib/ehcache-1.2.3.jar wrapper.java.classpath.17=lib/hibernate-3.2.1.ga.jar wrapper.java.classpath.18=lib/jdom-1.0.jar wrapper.java.classpath.19=lib/jta-1.0.1B.jar wrapper.java.classpath.20=lib/kfservice-1.0.0.16.jar wrapper.java.classpath.21=lib/log4j-1.2.13.jar . . . wrapper.java.classpath.25=lib/ojdbc-9.0.2.0.0.jar wrapper.java.classpath.26=lib/proxybrowse-1.0.0.12.jar wrapper.java.classpath.27=lib/spring-2.0.1.jar wrapper.java.classpath.28=lib/xpp3_min-1.1.3.4.O.jar wrapper.java.classpath.29=lib/xstream-1.2.1.jar wrapper.java.classpath.30=lib/ifxjdbc_3_0_jc3.jar wrapper.java.classpath.31=lib/jintegra.jar wrapper.java.classpath.32=lib/concurrent.jar # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1=../javawrapper/lib wrapper.java.library.path.2=lib/jintegra wrapper.java.library.path.3=lib/jintegra/international #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Format of output for the console. (See docs for formats) wrapper.console.format=PM # Log Level for console output. (See docs for log levels) wrapper.console.loglevel=INFO # Log file to use for wrapper output logging. wrapper.logfile=log/wrapper_mvcp-YYYYMMDD.log # Format of output for the log file. (See docs for formats) wrapper.logfile.format=LPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=INFO # Maximum size that the log file will be allowed to grow to before # the log is rolled. Size is specified in bytes. The default value # of 0, disables log rolling. May abbreviate with the 'k' (kb) or # 'm' (mb) suffix. For example: 10m = 10 megabytes. # wrapper.logfile.maxsize=10m # Maximum number of rolled log files which will be allowed before old # files are deleted. The default value of 0 implies no limit. wrapper.logfile.maxfiles=30 # # roll daily wrapper.logfile.rollmode=DATE # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=NONE # Mode in which the service is installed. AUTO_START or DEMAND_START wrapper.ntservice.starttype=AUTO_START # Allow the service to interact with the desktop. wrapper.ntservice.interactive=false # # An unexpected error has been detected by Java Runtime Environment: # # java.lang.OutOfMemoryError: requested 32756 bytes for ChunkPool::allocate. Out of swap space? # # Internal Error (414C4C4F434154494F4E0E4350500065), pid=9928, tid=5936 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-b05 mixed mode, sharing) # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # --------------- T H R E A D --------------- Current thread (0x03205c00): JavaThread "J-Integra COM initialization thread (please don't touch)" daemon [_thread_in_vm, id=5936] Stack: [0x03bb0000,0x03c00000) [error occurred during error reporting, step 110, id 0xc0000005] Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j com.linar.jintegra.NativeObjRef.initializeCOM(IZZZZZ)Ljava/lang/String;+0 j com.linar.jintegra.NativeInitThread.run()V+32 j java.lang.Thread.run()V+11 v ~StubRoutines::call_stub --------------- P R O C E S S --------------- Java Threads: ( => current thread ) =>0x03205c00 JavaThread "J-Integra COM initialization thread (please don't touch)" daemon [_thread_in_vm, id=5936] 0x03198400 JavaThread "Protocol Worker" [_thread_blocked, id=7660] 0x0311a800 JavaThread "MVCP Daemon" [_thread_in_native, id=10056] 0x0323e400 JavaThread "Mediasource QueueWorker" [_thread_blocked, id=10052] 0x03206800 JavaThread "RestRequest QueueWorker" [_thread_blocked, id=9988] 0x031e3800 JavaThread "Client Command Manager" [_thread_blocked, id=9996] 0x03227400 JavaThread "record cleanup" [_thread_blocked, id=10048] 0x02d7d800 JavaThread "Timer-2" [_thread_blocked, id=10044] 0x02e08000 JavaThread "Timer-1" [_thread_blocked, id=10040] 0x02e09400 JavaThread "Timer-0" [_thread_blocked, id=10036] 0x02e5f800 JavaThread "record cleanup" [_thread_blocked, id=10032] 0x00297800 JavaThread "DestroyJavaVM" [_thread_blocked, id=9936] 0x02dd1800 JavaThread "Wrapper-Connection" daemon [_thread_in_native, id=7484] 0x02d74c00 JavaThread "Wrapper-Control-Event-Monitor" daemon [_thread_blocked, id=9976] 0x0290dc00 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=9968] 0x02909000 JavaThread "CompilerThread0" daemon [_thread_blocked, id=7332] 0x02908000 JavaThread "Attach Listener" daemon [_thread_blocked, id=9960] 0x02907000 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=9952] 0x028ff400 JavaThread "Finalizer" daemon [_thread_blocked, id=9948] 0x028fe400 JavaThread "Reference Handler" daemon [_thread_blocked, id=9944] Other Threads: 0x028fd000 VMThread [id=9940] 0x02918400 WatcherThread [id=9972] VM state:not at safepoint (normal execution) VM Mutex/Monitor currently owned by a thread: None Heap def new generation total 960K, used 413K [0x06970000, 0x06a70000, 0x090d0000) eden space 896K, 38% used [0x06970000, 0x069c7478, 0x06a50000) from space 64K, 100% used [0x06a50000, 0x06a60000, 0x06a60000) to space 64K, 0% used [0x06a60000, 0x06a60000, 0x06a70000) tenured generation total 4096K, used 1104K [0x090d0000, 0x094d0000, 0x26970000) the space 4096K, 26% used [0x090d0000, 0x091e41c8, 0x091e4200, 0x094d0000) compacting perm gen total 12288K, used 4494K [0x26970000, 0x27570000, 0x2a970000) the space 12288K, 36% used [0x26970000, 0x26dd3bd8, 0x26dd3c00, 0x27570000) ro space 8192K, 62% used [0x2a970000, 0x2ae714a8, 0x2ae71600, 0x2b170000) rw space 12288K, 52% used [0x2b170000, 0x2b7b7278, 0x2b7b7400, 0x2bd70000) Dynamic libraries: 0x00400000 - 0x00423000 C:\Program Files\Java\jre1.6.0_03\bin\java.exe 0x7c800000 - 0x7c8c0000 C:\WINDOWS\system32\ntdll.dll 0x77e40000 - 0x77f42000 C:\WINDOWS\system32\kernel32.dll 0x77f50000 - 0x77feb000 C:\WINDOWS\system32\ADVAPI32.dll 0x77c50000 - 0x77cef000 C:\WINDOWS\system32\RPCRT4.dll 0x76f50000 - 0x76f63000 C:\WINDOWS\system32\Secur32.dll 0x7c340000 - 0x7c396000 C:\Program Files\Java\jre1.6.0_03\bin\msvcr71.dll 0x6d7c0000 - 0x6da0a000 C:\Program Files\Java\jre1.6.0_03\bin\client\jvm.dll 0x77380000 - 0x77411000 C:\WINDOWS\system32\USER32.dll 0x77c00000 - 0x77c48000 C:\WINDOWS\system32\GDI32.dll 0x76aa0000 - 0x76acd000 C:\WINDOWS\system32\WINMM.dll 0x76290000 - 0x762ad000 C:\WINDOWS\system32\IMM32.DLL 0x6d310000 - 0x6d318000 C:\Program Files\Java\jre1.6.0_03\bin\hpi.dll 0x76b70000 - 0x76b7b000 C:\WINDOWS\system32\PSAPI.DLL 0x6d770000 - 0x6d77c000 C:\Program Files\Java\jre1.6.0_03\bin\verify.dll 0x6d3b0000 - 0x6d3cf000 C:\Program Files\Java\jre1.6.0_03\bin\java.dll 0x6d7b0000 - 0x6d7bf000 C:\Program Files\Java\jre1.6.0_03\bin\zip.dll 0x02e60000 - 0x02e77000 C:\ipe\javawrapper\lib\wrapper.dll 0x6d570000 - 0x6d583000 C:\Program Files\Java\jre1.6.0_03\bin\net.dll 0x71c00000 - 0x71c17000 C:\WINDOWS\system32\WS2_32.dll 0x77ba0000 - 0x77bfa000 C:\WINDOWS\system32\msvcrt.dll 0x71bf0000 - 0x71bf8000 C:\WINDOWS\system32\WS2HELP.dll 0x71b20000 - 0x71b61000 C:\WINDOWS\system32\mswsock.dll 0x5f270000 - 0x5f2ca000 C:\WINDOWS\system32\hnetcfg.dll 0x71ae0000 - 0x71ae8000 C:\WINDOWS\System32\wshtcpip.dll 0x76ed0000 - 0x76efa000 C:\WINDOWS\system32\DNSAPI.dll 0x76f70000 - 0x76f77000 C:\WINDOWS\System32\winrnr.dll 0x76f10000 - 0x76f3e000 C:\WINDOWS\system32\WLDAP32.dll 0x76f80000 - 0x76f85000 C:\WINDOWS\system32\rasadhlp.dll 0x68000000 - 0x68035000 C:\WINDOWS\system32\rsaenh.dll 0x76920000 - 0x769e2000 C:\WINDOWS\system32\USERENV.dll 0x71c40000 - 0x71c97000 C:\WINDOWS\system32\netapi32.dll 0x03760000 - 0x037a0000 C:\ipe\mvcp\lib\jintegra\ntvinv.dll 0x77670000 - 0x777a9000 C:\WINDOWS\system32\ole32.dll 0x77d00000 - 0x77d8b000 C:\WINDOWS\system32\OLEAUT32.dll 0x5fcc0000 - 0x5fcc5000 C:\WINDOWS\system32\mtxex.dll 0x4a710000 - 0x4a855000 C:\WINDOWS\system32\COMSVCS.dll 0x03900000 - 0x03907000 C:\ipe\mvcp\lib\jintegra\International\ntvinvenglishresourcedll.dll 0x73eb0000 - 0x73fd1000 C:\WINDOWS\system32\MFC42.DLL 0x46a70000 - 0x46b40000 C:\WINDOWS\system32\WININET.dll 0x77da0000 - 0x77df2000 C:\WINDOWS\system32\SHLWAPI.dll 0x03910000 - 0x03919000 C:\WINDOWS\system32\Normaliz.dll 0x46300000 - 0x46345000 C:\WINDOWS\system32\iertutil.dll 0x71bb0000 - 0x71bb9000 C:\WINDOWS\system32\WSOCK32.dll 0x48890000 - 0x488cd000 C:\WINDOWS\system32\ODBC32.dll 0x77530000 - 0x775c7000 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_5.82.3790.3959_x-ww_78FCF8D0\COMCTL32.dll 0x7c8d0000 - 0x7d0cf000 C:\WINDOWS\system32\SHELL32.dll 0x762b0000 - 0x762f9000 C:\WINDOWS\system32\comdlg32.dll 0x77420000 - 0x77523000 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.3959_x-ww_D8713E55\comctl32.dll 0x03b10000 - 0x03b27000 C:\WINDOWS\system32\odbcint.dll VM Arguments: jvm_args: -Xmx512m -Djava.library.path=../javawrapper/lib;lib/jintegra;lib/jintegra/international -Dwrapper.key=ewtHOrkX3QrgQGVo -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=1388 -Dwrapper.version=3.2.3 -Dwrapper.native_library=wrapper -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=2 java_command: org.tanukisoftware.wrapper.WrapperSimpleApp com.proxygen.mvcp.MVCPDaemon Launcher Type: SUN_STANDARD Environment Variables: PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem USERNAME=<user> OS=Windows_NT PROCESSOR_IDENTIFIER=x86 Family 6 Model 15 Stepping 6, GenuineIntel --------------- S Y S T E M --------------- OS: Windows Server 2003 family Build 3790 Service Pack 2 CPU:total 4 (2 cores per cpu, 1 threads per core) family 6 model 15 stepping 6, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3 Memory: 4k page, physical 2097151k(66888k free), swap 4194303k(5132k free) vm_info: Java HotSpot(TM) Client VM (1.6.0_03-b05) for windows-x86, built on Sep 24 2007 22:24:33 by "java_re" with unknown MS VC++:1310 |
|
From: Erik D. <eri...@fj...> - 2009-03-18 11:58:02
|
Erik Drolshammer wrote: > Leif Mortenson wrote: >> The Wrapper is receiving a SIGCHLD signal from the OS and interpreting >> it as the Java process having stopped. From the log however, it >> appears that JVM still exists as it continues on to shut it down. So something _outside_ the wrapper and my application is sending a SIGCHLD signal which the wrapper picks up? Any suggestions on how I can debug this further? We are not that comfortable with behavior we cannot explain. It happens rather quickly when put under (light) load, so it is easy to test if you have anything I can try. -- Best regards, Erik Drolshammer |
|
From: Leif M. <lei...@ta...> - 2009-03-18 08:32:04
|
Elias, What does the content of your WrapperListener.start method look like? If you create a new thread, it will be non-daemon unless you specifically call the thread.setDaemon(true) method. If you are using existing class to start your application then it will be more difficult to check. One solution is to add a wait for 1 second at the end of your start method then call WrapperManager.requestThreadDump(). That will let you see all of your threads as well as see easily which have their daemon flag set. Cheers, Leif On Tue, Mar 17, 2009 at 9:02 PM, ejml <eli...@gm...> wrote: > > Hello again Leif, > > Sorry by my ignorance but How can I'm sure that there is at least one > non-daemon thread?. > > Thanks. > > > Leif Mortenson-3 wrote: >> >> Elias, >> Ok. Now the problem is that when your WrapperListener.start method >> returns, there are not any non-daemon threads running. Because of >> this, the JVM, not the Wrapper is initiating its own shutdown. The >> Wrapper's shutdown is initiated when its own Shutdown Hook is started >> by the JVM. >> >> Please make sure that you have started at least one non-daemon thread. >> >> Java will shutdown when run without the Wrapper as well if the main >> method completes and there are no non-daemon threads running. >> >> Let me know if this doesn't make sense. >> >> Cheers, >> Leif >> >> On Tue, Mar 17, 2009 at 7:42 PM, ejml <eli...@gm...> wrote: >>> >>> Thanks Leif by your response. >>> Yes, I'm making use of Method 3 and your had reason. I had my variable >>> initialized to 0. I have corrected this issue, but it doesn't works yet. >>> My >>> log says this: >>> >>> DEBUG | wrapper | 2009/03/17 11:38:41 | Allocating a console for the >>> service. >>> DEBUG | wrapper | 2009/03/17 11:38:41 | Found console window. >>> STATUS | wrapper | 2009/03/17 11:38:41 | --> Wrapper Started as Service >>> STATUS | wrapper | 2009/03/17 11:38:41 | Java Service Wrapper Community >>> Edition 3.3.3 >>> STATUS | wrapper | 2009/03/17 11:38:41 | Copyright (C) 1999-2009 >>> Tanuki >>> Software, Ltd. All Rights Reserved. >>> STATUS | wrapper | 2009/03/17 11:38:41 | >>> http://wrapper.tanukisoftware.org >>> STATUS | wrapper | 2009/03/17 11:38:41 | >>> DEBUG | wrapper | 2009/03/17 11:38:41 | Using tick timer. >>> DEBUG | wrapperp | 2009/03/17 11:38:41 | server listening on port 32000. >>> DEBUG | wrapper | 2009/03/17 11:38:41 | Ping settings: >>> wrapper.ping.interval=5, wrapper.ping.interval.logged=1, >>> wrapper.ping.timeout=30 >>> STATUS | wrapper | 2009/03/17 11:38:41 | Launching a JVM... >>> DEBUG | wrapper | 2009/03/17 11:38:41 | command: >>> "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath >>> "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" >>> -Dwrapper.key="YaKrFRBk8gEnOuzE" -Dwrapper.port=32000 >>> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >>> -Dwrapper.debug="TRUE" -Dwrapper.pid=3516 -Dwrapper.version="3.3.3" >>> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" >>> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 >>> com.gvs.AXConnectorServer.AXConnectorServiceWin32 >>> DEBUG | wrapper | 2009/03/17 11:38:41 | JVM started (PID=4892) >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>> WrapperManager class initialized by thread: main Using classloader: >>> sun.misc.Launcher$AppClassLoader@11b86e7 >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager: Initializing... >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: JVM #1 >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Running a >>> 32-bit JVM. >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>> Registering >>> shutdown hook >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Using >>> wrapper >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Load >>> native >>> library. One or more attempts may fail if platform specific libraries do >>> not exist. This is NORMAL and is only a problem if they all fail. >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Unable >>> to >>> load native library: wrapper-windows-x86-32.dll Cause: no >>> wrapper-windows-x86-32 in java.library.path >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Loaded >>> native library: wrapper.dll >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Calling >>> native initialization method. >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Initializing >>> WrapperManager native library. >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Java >>> Executable: >>> C:\WINNT\system32\java.exe >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Windows >>> version: >>> 5.0.2195 >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java >>> Version >>> : 1.6.0_11-b03 Java HotSpot(TM) Client VM >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java VM >>> Vendor : Sun Microsystems Inc. >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Name >>> : Windows 2000 >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Arch >>> : x86 >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Control >>> event monitor thread started. >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>> WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9, >>> args[]) called by thread: main >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup >>> runner thread started. >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>> Communications runner thread started. >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Open >>> socket >>> to wrapper...Wrapper-Connection >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Opened >>> Socket from 31000 to 32000 >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a >>> packet KEY : YaKrFRBk8gEnOuzE >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | accepted a socket from >>> 127.0.0.1 >>> on port 31000 >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet KEY : >>> YaKrFRBk8gEnOuzE >>> DEBUG | wrapper | 2009/03/17 11:38:42 | Got key from JVM: >>> YaKrFRBk8gEnOuzE >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet LOW_LOG_LEVEL : 1 >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PING_TIMEOUT : 30 >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PROPERTIES : >>> (Property Values) >>> DEBUG | wrapper | 2009/03/17 11:38:42 | Start Application. >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet START : start >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received >>> a >>> packet LOW_LOG_LEVEL : 1 >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>> LowLogLevel >>> from Wrapper is 1 >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received >>> a >>> packet PING_TIMEOUT : 30 >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>> PingTimeout >>> from Wrapper is 30000 >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received >>> a >>> packet PROPERTIES : (Property Values) >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received >>> a >>> packet START : start >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: calling >>> WrapperListener.start() >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>> WrapperListener.start runner thread started. >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: returned >>> from WrapperListener.start() >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a >>> packet STARTED : >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>> WrapperListener.start runner thread stopped. >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup >>> runner thread stopped. >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>> ShutdownHook >>> started >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >>> WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a >>> packet STOP : 0 >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STARTED : >>> DEBUG | wrapper | 2009/03/17 11:38:42 | JVM signalled that it was >>> started. >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STOP : 0 >>> DEBUG | wrapper | 2009/03/17 11:38:42 | JVM requested a shutdown. (0) >>> DEBUG | wrapper | 2009/03/17 11:38:42 | wrapperStopProcess(0) called. >>> DEBUG | wrapper | 2009/03/17 11:38:42 | Sending stop signal to JVM >>> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet STOP : NULL >>> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received >>> a >>> packet STOP : >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Thread, >>> Wrapper-Shutdown-Hook, handling the shutdown process. >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: calling >>> listener.stop() >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: returned >>> from listener.stop() -> 0 >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: >>> shutdownJVM(0) Thread:Wrapper-Shutdown-Hook >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: wait for >>> 0 >>> shutdown locs to be released. >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Send a >>> packet STOPPED : 0 >>> DEBUG | wrapperp | 2009/03/17 11:38:43 | read a packet STOPPED : 0 >>> DEBUG | wrapper | 2009/03/17 11:38:43 | JVM signalled that it was >>> stopped. >>> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Closing >>> socket. >>> DEBUG | wrapperp | 2009/03/17 11:38:43 | socket read no code (closed?). >>> DEBUG | wrapperp | 2009/03/17 11:38:43 | socket not open, so packet not >>> sent SERVICE_CONTROL_CODE : 4 >>> DEBUG | wrapper | 2009/03/17 11:38:43 | SERVICE_CONTROL_INTERROGATE >>> INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: Server >>> daemon shut down >>> INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: >>> ShutdownHook >>> complete >>> DEBUG | wrapper | 2009/03/17 11:38:44 | JVM process exited with a code >>> of >>> 0, leaving the wrapper exit code set to 0. >>> DEBUG | wrapper | 2009/03/17 11:38:44 | JVM exited normally. >>> STATUS | wrapper | 2009/03/17 11:38:44 | <-- Wrapper Stopped >>> >>> Very thanks by your help. >>> >>> Greetings!!. >>> >>> >>> >>> >>> >>> Leif Mortenson-3 wrote: >>>> >>>> Elias, >>>>>From the java command line, it looks like you are making use of >>>> Integration Method #3 for your application. >>>> Is the com.gvs.AXConnectorServer.AXConnectorServiceWin32 class >>>> something that you created? It appears to be working pretty much >>>> correctly. >>>> The problem is that your WrapperListener.start implementation is >>>> returning an exit code of 0. This is telling the Wrapper that the JVM >>>> should exit with exit code 0. If the application is meant to continue >>>> running then the WrapperListener.start method should be returning >>>> null. >>>> >>>> See the Java docs for the WrapperListener class for more information: >>>> http://wrapper.tanukisoftware.org/doc/english/javadocs.html >>>> >>>> This is also described on the following page: >>>> http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html >>>> >>>> Cheers, >>>> Leif >>>> >>>> On Tue, Mar 17, 2009 at 6:41 PM, ejml <eli...@gm...> wrote: >>>>> >>>>> Hello Folks!, >>>>> >>>>> I'm trying to use Java Service Wrapper to implement my java project >>>>> like >>>>> windows service. My Project is made with Spring using Jetty. In other >>>>> words, >>>>> I use spring to startup jetty. This setup in eclipse work fine but I >>>>> try >>>>> to >>>>> configure my application with Java Service Wrapper I get the next: >>>>> >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Allocating a console for the >>>>> service. >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Found console window. >>>>> STATUS | wrapper | 2009/03/17 09:40:35 | --> Wrapper Started as >>>>> Service >>>>> STATUS | wrapper | 2009/03/17 09:40:35 | Java Service Wrapper >>>>> Community >>>>> Edition 3.3.3 >>>>> STATUS | wrapper | 2009/03/17 09:40:35 | Copyright (C) 1999-2009 >>>>> Tanuki >>>>> Software, Ltd. All Rights Reserved. >>>>> STATUS | wrapper | 2009/03/17 09:40:35 | >>>>> http://wrapper.tanukisoftware.org >>>>> STATUS | wrapper | 2009/03/17 09:40:35 | >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Using tick timer. >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | server listening on port >>>>> 32000. >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Ping settings: >>>>> wrapper.ping.interval=5, wrapper.ping.interval.logged=1, >>>>> wrapper.ping.timeout=30 >>>>> STATUS | wrapper | 2009/03/17 09:40:35 | Launching a JVM... >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | command: >>>>> "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath >>>>> "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" >>>>> -Dwrapper.key="fREO9IxlyMDSknzk" -Dwrapper.port=32000 >>>>> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >>>>> -Dwrapper.debug="TRUE" -Dwrapper.pid=4020 -Dwrapper.version="3.3.3" >>>>> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" >>>>> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 >>>>> com.gvs.AXConnectorServer.AXConnectorServiceWin32 >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM started (PID=3756) >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> WrapperManager class initialized by thread: main Using classloader: >>>>> sun.misc.Launcher$AppClassLoader@11b86e7 >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager: >>>>> Initializing... >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: JVM #1 >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Running >>>>> a >>>>> 32-bit JVM. >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> Registering >>>>> shutdown hook >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Using >>>>> wrapper >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Load >>>>> native >>>>> library. One or more attempts may fail if platform specific libraries >>>>> do >>>>> not exist. This is NORMAL and is only a problem if they all fail. >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> Unable >>>>> to >>>>> load native library: wrapper-windows-x86-32.dll Cause: no >>>>> wrapper-windows-x86-32 in java.library.path >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> Loaded >>>>> native library: wrapper.dll >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Calling >>>>> native initialization method. >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: >>>>> Initializing >>>>> WrapperManager native library. >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Java >>>>> Executable: >>>>> C:\WINNT\system32\java.exe >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Windows >>>>> version: >>>>> 5.0.2195 >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java >>>>> Version >>>>> : 1.6.0_11-b03 Java HotSpot(TM) Client VM >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java VM >>>>> Vendor : Sun Microsystems Inc. >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS Name >>>>> : Windows 2000 >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS Arch >>>>> : x86 >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9, >>>>> args[]) called by thread: main >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Startup >>>>> runner thread started. >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Control >>>>> event monitor thread started. >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> Communications runner thread started. >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Open >>>>> socket >>>>> to wrapper...Wrapper-Connection >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Failed >>>>> attempt to bind using local port 31000 >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Opened >>>>> Socket from 31001 to 32000 >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a >>>>> packet KEY : fREO9IxlyMDSknzk >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001]) >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | accepted a socket from >>>>> 127.0.0.1 >>>>> on port 31001 >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet KEY : >>>>> fREO9IxlyMDSknzk >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Got key from JVM: >>>>> fREO9IxlyMDSknzk >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet LOW_LOG_LEVEL : >>>>> 1 >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PING_TIMEOUT : >>>>> 30 >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PROPERTIES : >>>>> (Property Values) >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Start Application. >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet START : start >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> Received >>>>> a >>>>> packet LOW_LOG_LEVEL : 1 >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> LowLogLevel >>>>> from Wrapper is 1 >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> Received >>>>> a >>>>> packet PING_TIMEOUT : 30 >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> PingTimeout >>>>> from Wrapper is 30000 >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> Received >>>>> a >>>>> packet PROPERTIES : (Property Values) >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> Received >>>>> a >>>>> packet START : start >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: calling >>>>> WrapperListener.start() >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> WrapperListener.start runner thread started. >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> returned >>>>> from WrapperListener.start() >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> WrapperListener.start() returned an exit code of 0. >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>>> WrapperManager.stop(0) called by thread: WrapperListener_start_runner >>>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a >>>>> packet STOP : 0 >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet STOP : 0 >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM requested a shutdown. (0) >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | wrapperStopProcess(0) called. >>>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Sending stop signal to JVM >>>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet STOP : NULL >>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: >>>>> Received >>>>> a >>>>> packet STOP : >>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Thread, >>>>> WrapperListener_start_runner, handling the shutdown process. >>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: >>>>> shutdownJVM(0) Thread:WrapperListener_start_runner >>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: wait >>>>> for >>>>> 0 >>>>> shutdown locs to be released. >>>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Send a >>>>> packet STOPPED : 0 >>>>> DEBUG | wrapperp | 2009/03/17 09:40:36 | read a packet STOPPED : 0 >>>>> DEBUG | wrapper | 2009/03/17 09:40:36 | JVM signalled that it was >>>>> stopped. >>>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Closing >>>>> socket. >>>>> DEBUG | wrapperp | 2009/03/17 09:40:37 | socket read no code >>>>> (closed?). >>>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: calling >>>>> System.exit(0) >>>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Server >>>>> daemon shut down >>>>> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM process exited with a >>>>> code >>>>> of >>>>> 0, leaving the wrapper exit code set to 0. >>>>> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM exited normally. >>>>> STATUS | wrapper | 2009/03/17 09:40:37 | <-- Wrapper Stopped >>>>> >>>>> This log say us something. >>>>> >>>>> Thanks in advance!!. |
|
From: Ilya V. <ivo...@cl...> - 2009-03-17 21:24:09
|
Leif, Thank you for the response. It is great if you have plans to add this feature. Do you want me to add it to the Feature Requests? When do you think you would be able to complete it and how I could learn about it? From release notes? Regards, Ilya -----Original Message----- From: Leif Mortenson [mailto:lei...@ta...] Sent: Thursday, February 19, 2009 10:38 PM To: wra...@li... Subject: Re: [Wrapper-user] Dynamic environment variables Ilya, I like this idea and have added it to my todo list for a future release. There are memory leaks in the OS on most platforms when repeatedly setting environment variables so there are a few things that I have to restructure to make this work without those leaks. The values also need to be evaluated each time the JVM is restarted even when those values are stored in other property values. Thanks for the feedback. Cheers, Leif On Wed, Feb 11, 2009 at 3:36 PM, Ilya Volvovski <ivo...@cl...> wrote: > Hi, > > > > I would like to use names in wrapper configuration that would carry run time > information, such as timestamp, random number. The prime reason is to > generate various file names for each java invocation (I really need it for > gc.log). I could not find anything of the kind. What I suggest is having > predefined variables such as %TIMESTAMP%, %RANDOM% much like %WRAPPER_ARCH % > etc, but they are evaluated at java invocation time. > > > > Is it reasonable? Or something like that already exists? > > > > Thank you, > > Ilya Volvovski ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Elías M. L. <eli...@gm...> - 2009-03-17 16:10:39
|
Thanks by all Leif, I have solved my issue. Greetings||. 2009/3/17 ejml <eli...@gm...> > > Hello again Leif, > > Sorry by my ignorance but How can I'm sure that there is at least one > non-daemon thread?. > > Thanks. > > > Leif Mortenson-3 wrote: > > > > Elias, > > Ok. Now the problem is that when your WrapperListener.start method > > returns, there are not any non-daemon threads running. Because of > > this, the JVM, not the Wrapper is initiating its own shutdown. The > > Wrapper's shutdown is initiated when its own Shutdown Hook is started > > by the JVM. > > > > Please make sure that you have started at least one non-daemon thread. > > > > Java will shutdown when run without the Wrapper as well if the main > > method completes and there are no non-daemon threads running. > > > > Let me know if this doesn't make sense. > > > > Cheers, > > Leif > > > > On Tue, Mar 17, 2009 at 7:42 PM, ejml <eli...@gm...> wrote: > >> > >> Thanks Leif by your response. > >> Yes, I'm making use of Method 3 and your had reason. I had my variable > >> initialized to 0. I have corrected this issue, but it doesn't works yet. > >> My > >> log says this: > >> > >> DEBUG | wrapper | 2009/03/17 11:38:41 | Allocating a console for the > >> service. > >> DEBUG | wrapper | 2009/03/17 11:38:41 | Found console window. > >> STATUS | wrapper | 2009/03/17 11:38:41 | --> Wrapper Started as Service > >> STATUS | wrapper | 2009/03/17 11:38:41 | Java Service Wrapper Community > >> Edition 3.3.3 > >> STATUS | wrapper | 2009/03/17 11:38:41 | Copyright (C) 1999-2009 > >> Tanuki > >> Software, Ltd. All Rights Reserved. > >> STATUS | wrapper | 2009/03/17 11:38:41 | > >> http://wrapper.tanukisoftware.org > >> STATUS | wrapper | 2009/03/17 11:38:41 | > >> DEBUG | wrapper | 2009/03/17 11:38:41 | Using tick timer. > >> DEBUG | wrapperp | 2009/03/17 11:38:41 | server listening on port > 32000. > >> DEBUG | wrapper | 2009/03/17 11:38:41 | Ping settings: > >> wrapper.ping.interval=5, wrapper.ping.interval.logged=1, > >> wrapper.ping.timeout=30 > >> STATUS | wrapper | 2009/03/17 11:38:41 | Launching a JVM... > >> DEBUG | wrapper | 2009/03/17 11:38:41 | command: > >> "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath > >> "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" > >> -Dwrapper.key="YaKrFRBk8gEnOuzE" -Dwrapper.port=32000 > >> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 > >> -Dwrapper.debug="TRUE" -Dwrapper.pid=3516 -Dwrapper.version="3.3.3" > >> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" > >> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 > >> com.gvs.AXConnectorServer.AXConnectorServiceWin32 > >> DEBUG | wrapper | 2009/03/17 11:38:41 | JVM started (PID=4892) > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >> WrapperManager class initialized by thread: main Using classloader: > >> sun.misc.Launcher$AppClassLoader@11b86e7 > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager: > Initializing... > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: JVM #1 > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Running > a > >> 32-bit JVM. > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >> Registering > >> shutdown hook > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Using > >> wrapper > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Load > >> native > >> library. One or more attempts may fail if platform specific libraries > do > >> not exist. This is NORMAL and is only a problem if they all fail. > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Unable > >> to > >> load native library: wrapper-windows-x86-32.dll Cause: no > >> wrapper-windows-x86-32 in java.library.path > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Loaded > >> native library: wrapper.dll > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Calling > >> native initialization method. > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Initializing > >> WrapperManager native library. > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Java > >> Executable: > >> C:\WINNT\system32\java.exe > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Windows > >> version: > >> 5.0.2195 > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java > >> Version > >> : 1.6.0_11-b03 Java HotSpot(TM) Client VM > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java VM > >> Vendor : Sun Microsystems Inc. > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Name > >> : Windows 2000 > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Arch > >> : x86 > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Control > >> event monitor thread started. > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >> > WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9 > , > >> args[]) called by thread: main > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup > >> runner thread started. > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >> Communications runner thread started. > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Open > >> socket > >> to wrapper...Wrapper-Connection > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Opened > >> Socket from 31000 to 32000 > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a > >> packet KEY : YaKrFRBk8gEnOuzE > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) > >> DEBUG | wrapperp | 2009/03/17 11:38:42 | accepted a socket from > >> 127.0.0.1 > >> on port 31000 > >> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet KEY : > >> YaKrFRBk8gEnOuzE > >> DEBUG | wrapper | 2009/03/17 11:38:42 | Got key from JVM: > >> YaKrFRBk8gEnOuzE > >> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet LOW_LOG_LEVEL : > 1 > >> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PING_TIMEOUT : > 30 > >> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PROPERTIES : > >> (Property Values) > >> DEBUG | wrapper | 2009/03/17 11:38:42 | Start Application. > >> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet START : start > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received > >> a > >> packet LOW_LOG_LEVEL : 1 > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >> LowLogLevel > >> from Wrapper is 1 > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received > >> a > >> packet PING_TIMEOUT : 30 > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >> PingTimeout > >> from Wrapper is 30000 > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received > >> a > >> packet PROPERTIES : (Property Values) > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received > >> a > >> packet START : start > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: calling > >> WrapperListener.start() > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >> WrapperListener.start runner thread started. > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: returned > >> from WrapperListener.start() > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a > >> packet STARTED : > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >> WrapperListener.start runner thread stopped. > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup > >> runner thread stopped. > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >> ShutdownHook > >> started > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > >> WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a > >> packet STOP : 0 > >> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STARTED : > >> DEBUG | wrapper | 2009/03/17 11:38:42 | JVM signalled that it was > >> started. > >> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STOP : 0 > >> DEBUG | wrapper | 2009/03/17 11:38:42 | JVM requested a shutdown. (0) > >> DEBUG | wrapper | 2009/03/17 11:38:42 | wrapperStopProcess(0) called. > >> DEBUG | wrapper | 2009/03/17 11:38:42 | Sending stop signal to JVM > >> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet STOP : NULL > >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received > >> a > >> packet STOP : > >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Thread, > >> Wrapper-Shutdown-Hook, handling the shutdown process. > >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: calling > >> listener.stop() > >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: returned > >> from listener.stop() -> 0 > >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: > >> shutdownJVM(0) Thread:Wrapper-Shutdown-Hook > >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: wait for > >> 0 > >> shutdown locs to be released. > >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Send a > >> packet STOPPED : 0 > >> DEBUG | wrapperp | 2009/03/17 11:38:43 | read a packet STOPPED : 0 > >> DEBUG | wrapper | 2009/03/17 11:38:43 | JVM signalled that it was > >> stopped. > >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Closing > >> socket. > >> DEBUG | wrapperp | 2009/03/17 11:38:43 | socket read no code (closed?). > >> DEBUG | wrapperp | 2009/03/17 11:38:43 | socket not open, so packet not > >> sent SERVICE_CONTROL_CODE : 4 > >> DEBUG | wrapper | 2009/03/17 11:38:43 | SERVICE_CONTROL_INTERROGATE > >> INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: Server > >> daemon shut down > >> INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: > >> ShutdownHook > >> complete > >> DEBUG | wrapper | 2009/03/17 11:38:44 | JVM process exited with a code > >> of > >> 0, leaving the wrapper exit code set to 0. > >> DEBUG | wrapper | 2009/03/17 11:38:44 | JVM exited normally. > >> STATUS | wrapper | 2009/03/17 11:38:44 | <-- Wrapper Stopped > >> > >> Very thanks by your help. > >> > >> Greetings!!. > >> > >> > >> > >> > >> > >> Leif Mortenson-3 wrote: > >>> > >>> Elias, > >>>>From the java command line, it looks like you are making use of > >>> Integration Method #3 for your application. > >>> Is the com.gvs.AXConnectorServer.AXConnectorServiceWin32 class > >>> something that you created? It appears to be working pretty much > >>> correctly. > >>> The problem is that your WrapperListener.start implementation is > >>> returning an exit code of 0. This is telling the Wrapper that the JVM > >>> should exit with exit code 0. If the application is meant to continue > >>> running then the WrapperListener.start method should be returning > >>> null. > >>> > >>> See the Java docs for the WrapperListener class for more information: > >>> http://wrapper.tanukisoftware.org/doc/english/javadocs.html > >>> > >>> This is also described on the following page: > >>> http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html > >>> > >>> Cheers, > >>> Leif > >>> > >>> On Tue, Mar 17, 2009 at 6:41 PM, ejml <eli...@gm...> wrote: > >>>> > >>>> Hello Folks!, > >>>> > >>>> I'm trying to use Java Service Wrapper to implement my java project > >>>> like > >>>> windows service. My Project is made with Spring using Jetty. In other > >>>> words, > >>>> I use spring to startup jetty. This setup in eclipse work fine but I > >>>> try > >>>> to > >>>> configure my application with Java Service Wrapper I get the next: > >>>> > >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Allocating a console for the > >>>> service. > >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Found console window. > >>>> STATUS | wrapper | 2009/03/17 09:40:35 | --> Wrapper Started as > >>>> Service > >>>> STATUS | wrapper | 2009/03/17 09:40:35 | Java Service Wrapper > >>>> Community > >>>> Edition 3.3.3 > >>>> STATUS | wrapper | 2009/03/17 09:40:35 | Copyright (C) 1999-2009 > >>>> Tanuki > >>>> Software, Ltd. All Rights Reserved. > >>>> STATUS | wrapper | 2009/03/17 09:40:35 | > >>>> http://wrapper.tanukisoftware.org > >>>> STATUS | wrapper | 2009/03/17 09:40:35 | > >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Using tick timer. > >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | server listening on port > >>>> 32000. > >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Ping settings: > >>>> wrapper.ping.interval=5, wrapper.ping.interval.logged=1, > >>>> wrapper.ping.timeout=30 > >>>> STATUS | wrapper | 2009/03/17 09:40:35 | Launching a JVM... > >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | command: > >>>> "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath > >>>> > "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" > >>>> -Dwrapper.key="fREO9IxlyMDSknzk" -Dwrapper.port=32000 > >>>> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 > >>>> -Dwrapper.debug="TRUE" -Dwrapper.pid=4020 -Dwrapper.version="3.3.3" > >>>> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" > >>>> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 > >>>> com.gvs.AXConnectorServer.AXConnectorServiceWin32 > >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM started (PID=3756) > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> WrapperManager class initialized by thread: main Using classloader: > >>>> sun.misc.Launcher$AppClassLoader@11b86e7 > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager: > >>>> Initializing... > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: JVM #1 > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > Running > >>>> a > >>>> 32-bit JVM. > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> Registering > >>>> shutdown hook > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Using > >>>> wrapper > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Load > >>>> native > >>>> library. One or more attempts may fail if platform specific libraries > >>>> do > >>>> not exist. This is NORMAL and is only a problem if they all fail. > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> Unable > >>>> to > >>>> load native library: wrapper-windows-x86-32.dll Cause: no > >>>> wrapper-windows-x86-32 in java.library.path > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> Loaded > >>>> native library: wrapper.dll > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > Calling > >>>> native initialization method. > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: > >>>> Initializing > >>>> WrapperManager native library. > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Java > >>>> Executable: > >>>> C:\WINNT\system32\java.exe > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Windows > >>>> version: > >>>> 5.0.2195 > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java > >>>> Version > >>>> : 1.6.0_11-b03 Java HotSpot(TM) Client VM > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java > VM > >>>> Vendor : Sun Microsystems Inc. > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS > Name > >>>> : Windows 2000 > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS > Arch > >>>> : x86 > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> > WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9 > , > >>>> args[]) called by thread: main > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > Startup > >>>> runner thread started. > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > Control > >>>> event monitor thread started. > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> Communications runner thread started. > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Open > >>>> socket > >>>> to wrapper...Wrapper-Connection > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Failed > >>>> attempt to bind using local port 31000 > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Opened > >>>> Socket from 31001 to 32000 > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a > >>>> packet KEY : fREO9IxlyMDSknzk > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001]) > >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | accepted a socket from > >>>> 127.0.0.1 > >>>> on port 31001 > >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet KEY : > >>>> fREO9IxlyMDSknzk > >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Got key from JVM: > >>>> fREO9IxlyMDSknzk > >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet LOW_LOG_LEVEL > : > >>>> 1 > >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PING_TIMEOUT : > >>>> 30 > >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PROPERTIES : > >>>> (Property Values) > >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Start Application. > >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet START : start > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> Received > >>>> a > >>>> packet LOW_LOG_LEVEL : 1 > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> LowLogLevel > >>>> from Wrapper is 1 > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> Received > >>>> a > >>>> packet PING_TIMEOUT : 30 > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> PingTimeout > >>>> from Wrapper is 30000 > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> Received > >>>> a > >>>> packet PROPERTIES : (Property Values) > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> Received > >>>> a > >>>> packet START : start > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > calling > >>>> WrapperListener.start() > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> WrapperListener.start runner thread started. > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> returned > >>>> from WrapperListener.start() > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> WrapperListener.start() returned an exit code of 0. > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > >>>> WrapperManager.stop(0) called by thread: WrapperListener_start_runner > >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a > >>>> packet STOP : 0 > >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet STOP : 0 > >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM requested a shutdown. > (0) > >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | wrapperStopProcess(0) > called. > >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Sending stop signal to JVM > >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet STOP : NULL > >>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: > >>>> Received > >>>> a > >>>> packet STOP : > >>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: > Thread, > >>>> WrapperListener_start_runner, handling the shutdown process. > >>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: > >>>> shutdownJVM(0) Thread:WrapperListener_start_runner > >>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: wait > >>>> for > >>>> 0 > >>>> shutdown locs to be released. > >>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Send a > >>>> packet STOPPED : 0 > >>>> DEBUG | wrapperp | 2009/03/17 09:40:36 | read a packet STOPPED : 0 > >>>> DEBUG | wrapper | 2009/03/17 09:40:36 | JVM signalled that it was > >>>> stopped. > >>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: > Closing > >>>> socket. > >>>> DEBUG | wrapperp | 2009/03/17 09:40:37 | socket read no code > >>>> (closed?). > >>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: > calling > >>>> System.exit(0) > >>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Server > >>>> daemon shut down > >>>> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM process exited with a > >>>> code > >>>> of > >>>> 0, leaving the wrapper exit code set to 0. > >>>> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM exited normally. > >>>> STATUS | wrapper | 2009/03/17 09:40:37 | <-- Wrapper Stopped > >>>> > >>>> This log say us something. > >>>> > >>>> Thanks in advance!!. > > > > > ------------------------------------------------------------------------------ > > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > > easily build your RIAs with Flex Builder, the Eclipse(TM)based > development > > software that enables intelligent coding and step-through debugging. > > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > > -- > View this message in context: > http://www.nabble.com/Wrapper-stopped-after-startup-tp22554782p22557667.html > Sent from the Java Service Wrapper mailing list archive at Nabble.com. > > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Erik D. <eri...@fj...> - 2009-03-17 14:22:20
|
Leif Mortenson wrote: > The Wrapper is receiving a SIGCHLD signal from the OS and interpreting > it as the Java process having stopped. From the log however, it > appears that JVM still exists as it continues on to shut it down. Yes, we have implemented a shutdown hook in the application, so the application shuts down cleanly when it receives the shutdown notification. > Can you tell me a little about your application? Does your Java > application run any child processes of its own? I am wondering if > such a grandchild process exiting might be causing this. I am going > to need to go back and run some more tests if that is the case. No child processes. > As a note, when you query the status, it is reporting as running > because the Wrapper process itself is still running. At the end of > the log, it appears the Wrapper is just about to launch a second JVM > invocation to recover from this problem. It doesn't appear to try to relaunch the app, as far as I can see. As a note, we have the same application deployed on other nodes where this problem does not occur. Which types of environment differences might be related? (The Java version, JSW version and distro is as far as I can tell identical) -- Best regards, Erik Drolshammer |
|
From: ejml <eli...@gm...> - 2009-03-17 12:02:28
|
Hello again Leif, Sorry by my ignorance but How can I'm sure that there is at least one non-daemon thread?. Thanks. Leif Mortenson-3 wrote: > > Elias, > Ok. Now the problem is that when your WrapperListener.start method > returns, there are not any non-daemon threads running. Because of > this, the JVM, not the Wrapper is initiating its own shutdown. The > Wrapper's shutdown is initiated when its own Shutdown Hook is started > by the JVM. > > Please make sure that you have started at least one non-daemon thread. > > Java will shutdown when run without the Wrapper as well if the main > method completes and there are no non-daemon threads running. > > Let me know if this doesn't make sense. > > Cheers, > Leif > > On Tue, Mar 17, 2009 at 7:42 PM, ejml <eli...@gm...> wrote: >> >> Thanks Leif by your response. >> Yes, I'm making use of Method 3 and your had reason. I had my variable >> initialized to 0. I have corrected this issue, but it doesn't works yet. >> My >> log says this: >> >> DEBUG | wrapper | 2009/03/17 11:38:41 | Allocating a console for the >> service. >> DEBUG | wrapper | 2009/03/17 11:38:41 | Found console window. >> STATUS | wrapper | 2009/03/17 11:38:41 | --> Wrapper Started as Service >> STATUS | wrapper | 2009/03/17 11:38:41 | Java Service Wrapper Community >> Edition 3.3.3 >> STATUS | wrapper | 2009/03/17 11:38:41 | Copyright (C) 1999-2009 >> Tanuki >> Software, Ltd. All Rights Reserved. >> STATUS | wrapper | 2009/03/17 11:38:41 | >> http://wrapper.tanukisoftware.org >> STATUS | wrapper | 2009/03/17 11:38:41 | >> DEBUG | wrapper | 2009/03/17 11:38:41 | Using tick timer. >> DEBUG | wrapperp | 2009/03/17 11:38:41 | server listening on port 32000. >> DEBUG | wrapper | 2009/03/17 11:38:41 | Ping settings: >> wrapper.ping.interval=5, wrapper.ping.interval.logged=1, >> wrapper.ping.timeout=30 >> STATUS | wrapper | 2009/03/17 11:38:41 | Launching a JVM... >> DEBUG | wrapper | 2009/03/17 11:38:41 | command: >> "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath >> "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" >> -Dwrapper.key="YaKrFRBk8gEnOuzE" -Dwrapper.port=32000 >> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >> -Dwrapper.debug="TRUE" -Dwrapper.pid=3516 -Dwrapper.version="3.3.3" >> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" >> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 >> com.gvs.AXConnectorServer.AXConnectorServiceWin32 >> DEBUG | wrapper | 2009/03/17 11:38:41 | JVM started (PID=4892) >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >> WrapperManager class initialized by thread: main Using classloader: >> sun.misc.Launcher$AppClassLoader@11b86e7 >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager: Initializing... >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: JVM #1 >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Running a >> 32-bit JVM. >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >> Registering >> shutdown hook >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Using >> wrapper >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Load >> native >> library. One or more attempts may fail if platform specific libraries do >> not exist. This is NORMAL and is only a problem if they all fail. >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Unable >> to >> load native library: wrapper-windows-x86-32.dll Cause: no >> wrapper-windows-x86-32 in java.library.path >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Loaded >> native library: wrapper.dll >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Calling >> native initialization method. >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Initializing >> WrapperManager native library. >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Java >> Executable: >> C:\WINNT\system32\java.exe >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Windows >> version: >> 5.0.2195 >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java >> Version >> : 1.6.0_11-b03 Java HotSpot(TM) Client VM >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java VM >> Vendor : Sun Microsystems Inc. >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Name >> : Windows 2000 >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Arch >> : x86 >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Control >> event monitor thread started. >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >> WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9, >> args[]) called by thread: main >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup >> runner thread started. >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >> Communications runner thread started. >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Open >> socket >> to wrapper...Wrapper-Connection >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Opened >> Socket from 31000 to 32000 >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a >> packet KEY : YaKrFRBk8gEnOuzE >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) >> DEBUG | wrapperp | 2009/03/17 11:38:42 | accepted a socket from >> 127.0.0.1 >> on port 31000 >> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet KEY : >> YaKrFRBk8gEnOuzE >> DEBUG | wrapper | 2009/03/17 11:38:42 | Got key from JVM: >> YaKrFRBk8gEnOuzE >> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet LOW_LOG_LEVEL : 1 >> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PING_TIMEOUT : 30 >> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PROPERTIES : >> (Property Values) >> DEBUG | wrapper | 2009/03/17 11:38:42 | Start Application. >> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet START : start >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received >> a >> packet LOW_LOG_LEVEL : 1 >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >> LowLogLevel >> from Wrapper is 1 >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received >> a >> packet PING_TIMEOUT : 30 >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >> PingTimeout >> from Wrapper is 30000 >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received >> a >> packet PROPERTIES : (Property Values) >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received >> a >> packet START : start >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: calling >> WrapperListener.start() >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >> WrapperListener.start runner thread started. >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: returned >> from WrapperListener.start() >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a >> packet STARTED : >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >> WrapperListener.start runner thread stopped. >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup >> runner thread stopped. >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >> ShutdownHook >> started >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: >> WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a >> packet STOP : 0 >> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STARTED : >> DEBUG | wrapper | 2009/03/17 11:38:42 | JVM signalled that it was >> started. >> DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STOP : 0 >> DEBUG | wrapper | 2009/03/17 11:38:42 | JVM requested a shutdown. (0) >> DEBUG | wrapper | 2009/03/17 11:38:42 | wrapperStopProcess(0) called. >> DEBUG | wrapper | 2009/03/17 11:38:42 | Sending stop signal to JVM >> DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet STOP : NULL >> INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received >> a >> packet STOP : >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Thread, >> Wrapper-Shutdown-Hook, handling the shutdown process. >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: calling >> listener.stop() >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: returned >> from listener.stop() -> 0 >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: >> shutdownJVM(0) Thread:Wrapper-Shutdown-Hook >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: wait for >> 0 >> shutdown locs to be released. >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Send a >> packet STOPPED : 0 >> DEBUG | wrapperp | 2009/03/17 11:38:43 | read a packet STOPPED : 0 >> DEBUG | wrapper | 2009/03/17 11:38:43 | JVM signalled that it was >> stopped. >> INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Closing >> socket. >> DEBUG | wrapperp | 2009/03/17 11:38:43 | socket read no code (closed?). >> DEBUG | wrapperp | 2009/03/17 11:38:43 | socket not open, so packet not >> sent SERVICE_CONTROL_CODE : 4 >> DEBUG | wrapper | 2009/03/17 11:38:43 | SERVICE_CONTROL_INTERROGATE >> INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: Server >> daemon shut down >> INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: >> ShutdownHook >> complete >> DEBUG | wrapper | 2009/03/17 11:38:44 | JVM process exited with a code >> of >> 0, leaving the wrapper exit code set to 0. >> DEBUG | wrapper | 2009/03/17 11:38:44 | JVM exited normally. >> STATUS | wrapper | 2009/03/17 11:38:44 | <-- Wrapper Stopped >> >> Very thanks by your help. >> >> Greetings!!. >> >> >> >> >> >> Leif Mortenson-3 wrote: >>> >>> Elias, >>>>From the java command line, it looks like you are making use of >>> Integration Method #3 for your application. >>> Is the com.gvs.AXConnectorServer.AXConnectorServiceWin32 class >>> something that you created? It appears to be working pretty much >>> correctly. >>> The problem is that your WrapperListener.start implementation is >>> returning an exit code of 0. This is telling the Wrapper that the JVM >>> should exit with exit code 0. If the application is meant to continue >>> running then the WrapperListener.start method should be returning >>> null. >>> >>> See the Java docs for the WrapperListener class for more information: >>> http://wrapper.tanukisoftware.org/doc/english/javadocs.html >>> >>> This is also described on the following page: >>> http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html >>> >>> Cheers, >>> Leif >>> >>> On Tue, Mar 17, 2009 at 6:41 PM, ejml <eli...@gm...> wrote: >>>> >>>> Hello Folks!, >>>> >>>> I'm trying to use Java Service Wrapper to implement my java project >>>> like >>>> windows service. My Project is made with Spring using Jetty. In other >>>> words, >>>> I use spring to startup jetty. This setup in eclipse work fine but I >>>> try >>>> to >>>> configure my application with Java Service Wrapper I get the next: >>>> >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Allocating a console for the >>>> service. >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Found console window. >>>> STATUS | wrapper | 2009/03/17 09:40:35 | --> Wrapper Started as >>>> Service >>>> STATUS | wrapper | 2009/03/17 09:40:35 | Java Service Wrapper >>>> Community >>>> Edition 3.3.3 >>>> STATUS | wrapper | 2009/03/17 09:40:35 | Copyright (C) 1999-2009 >>>> Tanuki >>>> Software, Ltd. All Rights Reserved. >>>> STATUS | wrapper | 2009/03/17 09:40:35 | >>>> http://wrapper.tanukisoftware.org >>>> STATUS | wrapper | 2009/03/17 09:40:35 | >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Using tick timer. >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | server listening on port >>>> 32000. >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Ping settings: >>>> wrapper.ping.interval=5, wrapper.ping.interval.logged=1, >>>> wrapper.ping.timeout=30 >>>> STATUS | wrapper | 2009/03/17 09:40:35 | Launching a JVM... >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | command: >>>> "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath >>>> "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" >>>> -Dwrapper.key="fREO9IxlyMDSknzk" -Dwrapper.port=32000 >>>> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >>>> -Dwrapper.debug="TRUE" -Dwrapper.pid=4020 -Dwrapper.version="3.3.3" >>>> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" >>>> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 >>>> com.gvs.AXConnectorServer.AXConnectorServiceWin32 >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM started (PID=3756) >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> WrapperManager class initialized by thread: main Using classloader: >>>> sun.misc.Launcher$AppClassLoader@11b86e7 >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager: >>>> Initializing... >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: JVM #1 >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Running >>>> a >>>> 32-bit JVM. >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> Registering >>>> shutdown hook >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Using >>>> wrapper >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Load >>>> native >>>> library. One or more attempts may fail if platform specific libraries >>>> do >>>> not exist. This is NORMAL and is only a problem if they all fail. >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> Unable >>>> to >>>> load native library: wrapper-windows-x86-32.dll Cause: no >>>> wrapper-windows-x86-32 in java.library.path >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> Loaded >>>> native library: wrapper.dll >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Calling >>>> native initialization method. >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: >>>> Initializing >>>> WrapperManager native library. >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Java >>>> Executable: >>>> C:\WINNT\system32\java.exe >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Windows >>>> version: >>>> 5.0.2195 >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java >>>> Version >>>> : 1.6.0_11-b03 Java HotSpot(TM) Client VM >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java VM >>>> Vendor : Sun Microsystems Inc. >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS Name >>>> : Windows 2000 >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS Arch >>>> : x86 >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9, >>>> args[]) called by thread: main >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Startup >>>> runner thread started. >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Control >>>> event monitor thread started. >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> Communications runner thread started. >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Open >>>> socket >>>> to wrapper...Wrapper-Connection >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Failed >>>> attempt to bind using local port 31000 >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Opened >>>> Socket from 31001 to 32000 >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a >>>> packet KEY : fREO9IxlyMDSknzk >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001]) >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | accepted a socket from >>>> 127.0.0.1 >>>> on port 31001 >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet KEY : >>>> fREO9IxlyMDSknzk >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Got key from JVM: >>>> fREO9IxlyMDSknzk >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet LOW_LOG_LEVEL : >>>> 1 >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PING_TIMEOUT : >>>> 30 >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PROPERTIES : >>>> (Property Values) >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Start Application. >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet START : start >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> Received >>>> a >>>> packet LOW_LOG_LEVEL : 1 >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> LowLogLevel >>>> from Wrapper is 1 >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> Received >>>> a >>>> packet PING_TIMEOUT : 30 >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> PingTimeout >>>> from Wrapper is 30000 >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> Received >>>> a >>>> packet PROPERTIES : (Property Values) >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> Received >>>> a >>>> packet START : start >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: calling >>>> WrapperListener.start() >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> WrapperListener.start runner thread started. >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> returned >>>> from WrapperListener.start() >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> WrapperListener.start() returned an exit code of 0. >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>>> WrapperManager.stop(0) called by thread: WrapperListener_start_runner >>>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a >>>> packet STOP : 0 >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet STOP : 0 >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM requested a shutdown. (0) >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | wrapperStopProcess(0) called. >>>> DEBUG | wrapper | 2009/03/17 09:40:35 | Sending stop signal to JVM >>>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet STOP : NULL >>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: >>>> Received >>>> a >>>> packet STOP : >>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Thread, >>>> WrapperListener_start_runner, handling the shutdown process. >>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: >>>> shutdownJVM(0) Thread:WrapperListener_start_runner >>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: wait >>>> for >>>> 0 >>>> shutdown locs to be released. >>>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Send a >>>> packet STOPPED : 0 >>>> DEBUG | wrapperp | 2009/03/17 09:40:36 | read a packet STOPPED : 0 >>>> DEBUG | wrapper | 2009/03/17 09:40:36 | JVM signalled that it was >>>> stopped. >>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Closing >>>> socket. >>>> DEBUG | wrapperp | 2009/03/17 09:40:37 | socket read no code >>>> (closed?). >>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: calling >>>> System.exit(0) >>>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Server >>>> daemon shut down >>>> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM process exited with a >>>> code >>>> of >>>> 0, leaving the wrapper exit code set to 0. >>>> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM exited normally. >>>> STATUS | wrapper | 2009/03/17 09:40:37 | <-- Wrapper Stopped >>>> >>>> This log say us something. >>>> >>>> Thanks in advance!!. > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > -- View this message in context: http://www.nabble.com/Wrapper-stopped-after-startup-tp22554782p22557667.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Leif M. <lei...@ta...> - 2009-03-17 11:41:07
|
Elias, Ok. Now the problem is that when your WrapperListener.start method returns, there are not any non-daemon threads running. Because of this, the JVM, not the Wrapper is initiating its own shutdown. The Wrapper's shutdown is initiated when its own Shutdown Hook is started by the JVM. Please make sure that you have started at least one non-daemon thread. Java will shutdown when run without the Wrapper as well if the main method completes and there are no non-daemon threads running. Let me know if this doesn't make sense. Cheers, Leif On Tue, Mar 17, 2009 at 7:42 PM, ejml <eli...@gm...> wrote: > > Thanks Leif by your response. > Yes, I'm making use of Method 3 and your had reason. I had my variable > initialized to 0. I have corrected this issue, but it doesn't works yet. My > log says this: > > DEBUG | wrapper | 2009/03/17 11:38:41 | Allocating a console for the > service. > DEBUG | wrapper | 2009/03/17 11:38:41 | Found console window. > STATUS | wrapper | 2009/03/17 11:38:41 | --> Wrapper Started as Service > STATUS | wrapper | 2009/03/17 11:38:41 | Java Service Wrapper Community > Edition 3.3.3 > STATUS | wrapper | 2009/03/17 11:38:41 | Copyright (C) 1999-2009 Tanuki > Software, Ltd. All Rights Reserved. > STATUS | wrapper | 2009/03/17 11:38:41 | > http://wrapper.tanukisoftware.org > STATUS | wrapper | 2009/03/17 11:38:41 | > DEBUG | wrapper | 2009/03/17 11:38:41 | Using tick timer. > DEBUG | wrapperp | 2009/03/17 11:38:41 | server listening on port 32000. > DEBUG | wrapper | 2009/03/17 11:38:41 | Ping settings: > wrapper.ping.interval=5, wrapper.ping.interval.logged=1, > wrapper.ping.timeout=30 > STATUS | wrapper | 2009/03/17 11:38:41 | Launching a JVM... > DEBUG | wrapper | 2009/03/17 11:38:41 | command: > "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath > "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" > -Dwrapper.key="YaKrFRBk8gEnOuzE" -Dwrapper.port=32000 > -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 > -Dwrapper.debug="TRUE" -Dwrapper.pid=3516 -Dwrapper.version="3.3.3" > -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" > -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 > com.gvs.AXConnectorServer.AXConnectorServiceWin32 > DEBUG | wrapper | 2009/03/17 11:38:41 | JVM started (PID=4892) > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > WrapperManager class initialized by thread: main Using classloader: > sun.misc.Launcher$AppClassLoader@11b86e7 > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager: Initializing... > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: JVM #1 > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Running a > 32-bit JVM. > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Registering > shutdown hook > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Using > wrapper > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Load native > library. One or more attempts may fail if platform specific libraries do > not exist. This is NORMAL and is only a problem if they all fail. > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Unable to > load native library: wrapper-windows-x86-32.dll Cause: no > wrapper-windows-x86-32 in java.library.path > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Loaded > native library: wrapper.dll > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Calling > native initialization method. > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Initializing > WrapperManager native library. > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Java Executable: > C:\WINNT\system32\java.exe > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Windows version: > 5.0.2195 > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java Version > : 1.6.0_11-b03 Java HotSpot(TM) Client VM > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java VM > Vendor : Sun Microsystems Inc. > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Name > : Windows 2000 > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Arch > : x86 > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Control > event monitor thread started. > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9, > args[]) called by thread: main > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup > runner thread started. > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > Communications runner thread started. > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Open socket > to wrapper...Wrapper-Connection > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Opened > Socket from 31000 to 32000 > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a > packet KEY : YaKrFRBk8gEnOuzE > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) > DEBUG | wrapperp | 2009/03/17 11:38:42 | accepted a socket from 127.0.0.1 > on port 31000 > DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet KEY : > YaKrFRBk8gEnOuzE > DEBUG | wrapper | 2009/03/17 11:38:42 | Got key from JVM: YaKrFRBk8gEnOuzE > DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet LOW_LOG_LEVEL : 1 > DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PING_TIMEOUT : 30 > DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PROPERTIES : > (Property Values) > DEBUG | wrapper | 2009/03/17 11:38:42 | Start Application. > DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet START : start > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received a > packet LOW_LOG_LEVEL : 1 > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: LowLogLevel > from Wrapper is 1 > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received a > packet PING_TIMEOUT : 30 > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: PingTimeout > from Wrapper is 30000 > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received a > packet PROPERTIES : (Property Values) > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received a > packet START : start > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: calling > WrapperListener.start() > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > WrapperListener.start runner thread started. > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: returned > from WrapperListener.start() > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a > packet STARTED : > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > WrapperListener.start runner thread stopped. > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup > runner thread stopped. > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: ShutdownHook > started > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: > WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a > packet STOP : 0 > DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STARTED : > DEBUG | wrapper | 2009/03/17 11:38:42 | JVM signalled that it was started. > DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STOP : 0 > DEBUG | wrapper | 2009/03/17 11:38:42 | JVM requested a shutdown. (0) > DEBUG | wrapper | 2009/03/17 11:38:42 | wrapperStopProcess(0) called. > DEBUG | wrapper | 2009/03/17 11:38:42 | Sending stop signal to JVM > DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet STOP : NULL > INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received a > packet STOP : > INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Thread, > Wrapper-Shutdown-Hook, handling the shutdown process. > INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: calling > listener.stop() > INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: returned > from listener.stop() -> 0 > INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: > shutdownJVM(0) Thread:Wrapper-Shutdown-Hook > INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: wait for 0 > shutdown locs to be released. > INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Send a > packet STOPPED : 0 > DEBUG | wrapperp | 2009/03/17 11:38:43 | read a packet STOPPED : 0 > DEBUG | wrapper | 2009/03/17 11:38:43 | JVM signalled that it was stopped. > INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Closing > socket. > DEBUG | wrapperp | 2009/03/17 11:38:43 | socket read no code (closed?). > DEBUG | wrapperp | 2009/03/17 11:38:43 | socket not open, so packet not > sent SERVICE_CONTROL_CODE : 4 > DEBUG | wrapper | 2009/03/17 11:38:43 | SERVICE_CONTROL_INTERROGATE > INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: Server > daemon shut down > INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: ShutdownHook > complete > DEBUG | wrapper | 2009/03/17 11:38:44 | JVM process exited with a code of > 0, leaving the wrapper exit code set to 0. > DEBUG | wrapper | 2009/03/17 11:38:44 | JVM exited normally. > STATUS | wrapper | 2009/03/17 11:38:44 | <-- Wrapper Stopped > > Very thanks by your help. > > Greetings!!. > > > > > > Leif Mortenson-3 wrote: >> >> Elias, >>>From the java command line, it looks like you are making use of >> Integration Method #3 for your application. >> Is the com.gvs.AXConnectorServer.AXConnectorServiceWin32 class >> something that you created? It appears to be working pretty much >> correctly. >> The problem is that your WrapperListener.start implementation is >> returning an exit code of 0. This is telling the Wrapper that the JVM >> should exit with exit code 0. If the application is meant to continue >> running then the WrapperListener.start method should be returning >> null. >> >> See the Java docs for the WrapperListener class for more information: >> http://wrapper.tanukisoftware.org/doc/english/javadocs.html >> >> This is also described on the following page: >> http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html >> >> Cheers, >> Leif >> >> On Tue, Mar 17, 2009 at 6:41 PM, ejml <eli...@gm...> wrote: >>> >>> Hello Folks!, >>> >>> I'm trying to use Java Service Wrapper to implement my java project like >>> windows service. My Project is made with Spring using Jetty. In other >>> words, >>> I use spring to startup jetty. This setup in eclipse work fine but I try >>> to >>> configure my application with Java Service Wrapper I get the next: >>> >>> DEBUG | wrapper | 2009/03/17 09:40:35 | Allocating a console for the >>> service. >>> DEBUG | wrapper | 2009/03/17 09:40:35 | Found console window. >>> STATUS | wrapper | 2009/03/17 09:40:35 | --> Wrapper Started as Service >>> STATUS | wrapper | 2009/03/17 09:40:35 | Java Service Wrapper Community >>> Edition 3.3.3 >>> STATUS | wrapper | 2009/03/17 09:40:35 | Copyright (C) 1999-2009 >>> Tanuki >>> Software, Ltd. All Rights Reserved. >>> STATUS | wrapper | 2009/03/17 09:40:35 | >>> http://wrapper.tanukisoftware.org >>> STATUS | wrapper | 2009/03/17 09:40:35 | >>> DEBUG | wrapper | 2009/03/17 09:40:35 | Using tick timer. >>> DEBUG | wrapperp | 2009/03/17 09:40:35 | server listening on port 32000. >>> DEBUG | wrapper | 2009/03/17 09:40:35 | Ping settings: >>> wrapper.ping.interval=5, wrapper.ping.interval.logged=1, >>> wrapper.ping.timeout=30 >>> STATUS | wrapper | 2009/03/17 09:40:35 | Launching a JVM... >>> DEBUG | wrapper | 2009/03/17 09:40:35 | command: >>> "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath >>> "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" >>> -Dwrapper.key="fREO9IxlyMDSknzk" -Dwrapper.port=32000 >>> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >>> -Dwrapper.debug="TRUE" -Dwrapper.pid=4020 -Dwrapper.version="3.3.3" >>> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" >>> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 >>> com.gvs.AXConnectorServer.AXConnectorServiceWin32 >>> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM started (PID=3756) >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>> WrapperManager class initialized by thread: main Using classloader: >>> sun.misc.Launcher$AppClassLoader@11b86e7 >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager: Initializing... >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: JVM #1 >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Running a >>> 32-bit JVM. >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>> Registering >>> shutdown hook >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Using >>> wrapper >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Load >>> native >>> library. One or more attempts may fail if platform specific libraries do >>> not exist. This is NORMAL and is only a problem if they all fail. >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Unable >>> to >>> load native library: wrapper-windows-x86-32.dll Cause: no >>> wrapper-windows-x86-32 in java.library.path >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Loaded >>> native library: wrapper.dll >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Calling >>> native initialization method. >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Initializing >>> WrapperManager native library. >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Java >>> Executable: >>> C:\WINNT\system32\java.exe >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Windows >>> version: >>> 5.0.2195 >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java >>> Version >>> : 1.6.0_11-b03 Java HotSpot(TM) Client VM >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java VM >>> Vendor : Sun Microsystems Inc. >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS Name >>> : Windows 2000 >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS Arch >>> : x86 >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>> WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9, >>> args[]) called by thread: main >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Startup >>> runner thread started. >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Control >>> event monitor thread started. >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>> Communications runner thread started. >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Open >>> socket >>> to wrapper...Wrapper-Connection >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Failed >>> attempt to bind using local port 31000 >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Opened >>> Socket from 31001 to 32000 >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a >>> packet KEY : fREO9IxlyMDSknzk >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001]) >>> DEBUG | wrapperp | 2009/03/17 09:40:35 | accepted a socket from >>> 127.0.0.1 >>> on port 31001 >>> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet KEY : >>> fREO9IxlyMDSknzk >>> DEBUG | wrapper | 2009/03/17 09:40:35 | Got key from JVM: >>> fREO9IxlyMDSknzk >>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet LOW_LOG_LEVEL : 1 >>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PING_TIMEOUT : 30 >>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PROPERTIES : >>> (Property Values) >>> DEBUG | wrapper | 2009/03/17 09:40:35 | Start Application. >>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet START : start >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received >>> a >>> packet LOW_LOG_LEVEL : 1 >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>> LowLogLevel >>> from Wrapper is 1 >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received >>> a >>> packet PING_TIMEOUT : 30 >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>> PingTimeout >>> from Wrapper is 30000 >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received >>> a >>> packet PROPERTIES : (Property Values) >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received >>> a >>> packet START : start >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: calling >>> WrapperListener.start() >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>> WrapperListener.start runner thread started. >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: returned >>> from WrapperListener.start() >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>> WrapperListener.start() returned an exit code of 0. >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >>> WrapperManager.stop(0) called by thread: WrapperListener_start_runner >>> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a >>> packet STOP : 0 >>> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet STOP : 0 >>> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM requested a shutdown. (0) >>> DEBUG | wrapper | 2009/03/17 09:40:35 | wrapperStopProcess(0) called. >>> DEBUG | wrapper | 2009/03/17 09:40:35 | Sending stop signal to JVM >>> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet STOP : NULL >>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Received >>> a >>> packet STOP : >>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Thread, >>> WrapperListener_start_runner, handling the shutdown process. >>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: >>> shutdownJVM(0) Thread:WrapperListener_start_runner >>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: wait for >>> 0 >>> shutdown locs to be released. >>> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Send a >>> packet STOPPED : 0 >>> DEBUG | wrapperp | 2009/03/17 09:40:36 | read a packet STOPPED : 0 >>> DEBUG | wrapper | 2009/03/17 09:40:36 | JVM signalled that it was >>> stopped. >>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Closing >>> socket. >>> DEBUG | wrapperp | 2009/03/17 09:40:37 | socket read no code (closed?). >>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: calling >>> System.exit(0) >>> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Server >>> daemon shut down >>> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM process exited with a code >>> of >>> 0, leaving the wrapper exit code set to 0. >>> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM exited normally. >>> STATUS | wrapper | 2009/03/17 09:40:37 | <-- Wrapper Stopped >>> >>> This log say us something. >>> >>> Thanks in advance!!. |
|
From: ejml <eli...@gm...> - 2009-03-17 10:40:29
|
Thanks Leif by your response. Yes, I'm making use of Method 3 and your had reason. I had my variable initialized to 0. I have corrected this issue, but it doesn't works yet. My log says this: DEBUG | wrapper | 2009/03/17 11:38:41 | Allocating a console for the service. DEBUG | wrapper | 2009/03/17 11:38:41 | Found console window. STATUS | wrapper | 2009/03/17 11:38:41 | --> Wrapper Started as Service STATUS | wrapper | 2009/03/17 11:38:41 | Java Service Wrapper Community Edition 3.3.3 STATUS | wrapper | 2009/03/17 11:38:41 | Copyright (C) 1999-2009 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2009/03/17 11:38:41 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2009/03/17 11:38:41 | DEBUG | wrapper | 2009/03/17 11:38:41 | Using tick timer. DEBUG | wrapperp | 2009/03/17 11:38:41 | server listening on port 32000. DEBUG | wrapper | 2009/03/17 11:38:41 | Ping settings: wrapper.ping.interval=5, wrapper.ping.interval.logged=1, wrapper.ping.timeout=30 STATUS | wrapper | 2009/03/17 11:38:41 | Launching a JVM... DEBUG | wrapper | 2009/03/17 11:38:41 | command: "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" -Dwrapper.key="YaKrFRBk8gEnOuzE" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=3516 -Dwrapper.version="3.3.3" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 com.gaviotasimbac.AXConnectorServer.AXConnectorServiceWin32 DEBUG | wrapper | 2009/03/17 11:38:41 | JVM started (PID=4892) INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoader@11b86e7 INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager: Initializing... INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: JVM #1 INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Running a 32-bit JVM. INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Registering shutdown hook INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Using wrapper INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Load native library. One or more attempts may fail if platform specific libraries do not exist. This is NORMAL and is only a problem if they all fail. INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Unable to load native library: wrapper-windows-x86-32.dll Cause: no wrapper-windows-x86-32 in java.library.path INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Loaded native library: wrapper.dll INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Calling native initialization method. INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Initializing WrapperManager native library. INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Java Executable: C:\WINNT\system32\java.exe INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperJNI Debug: Windows version: 5.0.2195 INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java Version : 1.6.0_11-b03 Java HotSpot(TM) Client VM INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Java VM Vendor : Sun Microsystems Inc. INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Name : Windows 2000 INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: OS Arch : x86 INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Control event monitor thread started. INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: WrapperManager.start(com.gaviotasimbac.AXConnectorServer.AXConnectorServiceWin32@201f9, args[]) called by thread: main INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup runner thread started. INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Communications runner thread started. INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Open socket to wrapper...Wrapper-Connection INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Opened Socket from 31000 to 32000 INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a packet KEY : YaKrFRBk8gEnOuzE INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) DEBUG | wrapperp | 2009/03/17 11:38:42 | accepted a socket from 127.0.0.1 on port 31000 DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet KEY : YaKrFRBk8gEnOuzE DEBUG | wrapper | 2009/03/17 11:38:42 | Got key from JVM: YaKrFRBk8gEnOuzE DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet LOW_LOG_LEVEL : 1 DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PING_TIMEOUT : 30 DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet PROPERTIES : (Property Values) DEBUG | wrapper | 2009/03/17 11:38:42 | Start Application. DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet START : start INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received a packet LOW_LOG_LEVEL : 1 INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: LowLogLevel from Wrapper is 1 INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received a packet PING_TIMEOUT : 30 INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: PingTimeout from Wrapper is 30000 INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received a packet PROPERTIES : (Property Values) INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received a packet START : start INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: calling WrapperListener.start() INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: WrapperListener.start runner thread started. INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: returned from WrapperListener.start() INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a packet STARTED : INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: WrapperListener.start runner thread stopped. INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Startup runner thread stopped. INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: ShutdownHook started INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Send a packet STOP : 0 DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STARTED : DEBUG | wrapper | 2009/03/17 11:38:42 | JVM signalled that it was started. DEBUG | wrapperp | 2009/03/17 11:38:42 | read a packet STOP : 0 DEBUG | wrapper | 2009/03/17 11:38:42 | JVM requested a shutdown. (0) DEBUG | wrapper | 2009/03/17 11:38:42 | wrapperStopProcess(0) called. DEBUG | wrapper | 2009/03/17 11:38:42 | Sending stop signal to JVM DEBUG | wrapperp | 2009/03/17 11:38:42 | send a packet STOP : NULL INFO | jvm 1 | 2009/03/17 11:38:42 | WrapperManager Debug: Received a packet STOP : INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Thread, Wrapper-Shutdown-Hook, handling the shutdown process. INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: calling listener.stop() INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: returned from listener.stop() -> 0 INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: shutdownJVM(0) Thread:Wrapper-Shutdown-Hook INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: wait for 0 shutdown locs to be released. INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Send a packet STOPPED : 0 DEBUG | wrapperp | 2009/03/17 11:38:43 | read a packet STOPPED : 0 DEBUG | wrapper | 2009/03/17 11:38:43 | JVM signalled that it was stopped. INFO | jvm 1 | 2009/03/17 11:38:43 | WrapperManager Debug: Closing socket. DEBUG | wrapperp | 2009/03/17 11:38:43 | socket read no code (closed?). DEBUG | wrapperp | 2009/03/17 11:38:43 | socket not open, so packet not sent SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2009/03/17 11:38:43 | SERVICE_CONTROL_INTERROGATE INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: Server daemon shut down INFO | jvm 1 | 2009/03/17 11:38:44 | WrapperManager Debug: ShutdownHook complete DEBUG | wrapper | 2009/03/17 11:38:44 | JVM process exited with a code of 0, leaving the wrapper exit code set to 0. DEBUG | wrapper | 2009/03/17 11:38:44 | JVM exited normally. STATUS | wrapper | 2009/03/17 11:38:44 | <-- Wrapper Stopped Very thanks by your help. Greetings!!. Leif Mortenson-3 wrote: > > Elias, >>From the java command line, it looks like you are making use of > Integration Method #3 for your application. > Is the com.gvs.AXConnectorServer.AXConnectorServiceWin32 class > something that you created? It appears to be working pretty much > correctly. > The problem is that your WrapperListener.start implementation is > returning an exit code of 0. This is telling the Wrapper that the JVM > should exit with exit code 0. If the application is meant to continue > running then the WrapperListener.start method should be returning > null. > > See the Java docs for the WrapperListener class for more information: > http://wrapper.tanukisoftware.org/doc/english/javadocs.html > > This is also described on the following page: > http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html > > Cheers, > Leif > > On Tue, Mar 17, 2009 at 6:41 PM, ejml <eli...@gm...> wrote: >> >> Hello Folks!, >> >> I'm trying to use Java Service Wrapper to implement my java project like >> windows service. My Project is made with Spring using Jetty. In other >> words, >> I use spring to startup jetty. This setup in eclipse work fine but I try >> to >> configure my application with Java Service Wrapper I get the next: >> >> DEBUG | wrapper | 2009/03/17 09:40:35 | Allocating a console for the >> service. >> DEBUG | wrapper | 2009/03/17 09:40:35 | Found console window. >> STATUS | wrapper | 2009/03/17 09:40:35 | --> Wrapper Started as Service >> STATUS | wrapper | 2009/03/17 09:40:35 | Java Service Wrapper Community >> Edition 3.3.3 >> STATUS | wrapper | 2009/03/17 09:40:35 | Copyright (C) 1999-2009 >> Tanuki >> Software, Ltd. All Rights Reserved. >> STATUS | wrapper | 2009/03/17 09:40:35 | >> http://wrapper.tanukisoftware.org >> STATUS | wrapper | 2009/03/17 09:40:35 | >> DEBUG | wrapper | 2009/03/17 09:40:35 | Using tick timer. >> DEBUG | wrapperp | 2009/03/17 09:40:35 | server listening on port 32000. >> DEBUG | wrapper | 2009/03/17 09:40:35 | Ping settings: >> wrapper.ping.interval=5, wrapper.ping.interval.logged=1, >> wrapper.ping.timeout=30 >> STATUS | wrapper | 2009/03/17 09:40:35 | Launching a JVM... >> DEBUG | wrapper | 2009/03/17 09:40:35 | command: >> "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath >> "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" >> -Dwrapper.key="fREO9IxlyMDSknzk" -Dwrapper.port=32000 >> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >> -Dwrapper.debug="TRUE" -Dwrapper.pid=4020 -Dwrapper.version="3.3.3" >> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" >> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 >> com.gvs.AXConnectorServer.AXConnectorServiceWin32 >> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM started (PID=3756) >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >> WrapperManager class initialized by thread: main Using classloader: >> sun.misc.Launcher$AppClassLoader@11b86e7 >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager: Initializing... >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: JVM #1 >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Running a >> 32-bit JVM. >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >> Registering >> shutdown hook >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Using >> wrapper >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Load >> native >> library. One or more attempts may fail if platform specific libraries do >> not exist. This is NORMAL and is only a problem if they all fail. >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Unable >> to >> load native library: wrapper-windows-x86-32.dll Cause: no >> wrapper-windows-x86-32 in java.library.path >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Loaded >> native library: wrapper.dll >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Calling >> native initialization method. >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Initializing >> WrapperManager native library. >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Java >> Executable: >> C:\WINNT\system32\java.exe >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Windows >> version: >> 5.0.2195 >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java >> Version >> : 1.6.0_11-b03 Java HotSpot(TM) Client VM >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java VM >> Vendor : Sun Microsystems Inc. >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS Name >> : Windows 2000 >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS Arch >> : x86 >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >> WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9, >> args[]) called by thread: main >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Startup >> runner thread started. >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Control >> event monitor thread started. >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >> Communications runner thread started. >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Open >> socket >> to wrapper...Wrapper-Connection >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Failed >> attempt to bind using local port 31000 >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Opened >> Socket from 31001 to 32000 >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a >> packet KEY : fREO9IxlyMDSknzk >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001]) >> DEBUG | wrapperp | 2009/03/17 09:40:35 | accepted a socket from >> 127.0.0.1 >> on port 31001 >> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet KEY : >> fREO9IxlyMDSknzk >> DEBUG | wrapper | 2009/03/17 09:40:35 | Got key from JVM: >> fREO9IxlyMDSknzk >> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet LOW_LOG_LEVEL : 1 >> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PING_TIMEOUT : 30 >> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PROPERTIES : >> (Property Values) >> DEBUG | wrapper | 2009/03/17 09:40:35 | Start Application. >> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet START : start >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received >> a >> packet LOW_LOG_LEVEL : 1 >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >> LowLogLevel >> from Wrapper is 1 >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received >> a >> packet PING_TIMEOUT : 30 >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >> PingTimeout >> from Wrapper is 30000 >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received >> a >> packet PROPERTIES : (Property Values) >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received >> a >> packet START : start >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: calling >> WrapperListener.start() >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >> WrapperListener.start runner thread started. >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: returned >> from WrapperListener.start() >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >> WrapperListener.start() returned an exit code of 0. >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: >> WrapperManager.stop(0) called by thread: WrapperListener_start_runner >> INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a >> packet STOP : 0 >> DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet STOP : 0 >> DEBUG | wrapper | 2009/03/17 09:40:35 | JVM requested a shutdown. (0) >> DEBUG | wrapper | 2009/03/17 09:40:35 | wrapperStopProcess(0) called. >> DEBUG | wrapper | 2009/03/17 09:40:35 | Sending stop signal to JVM >> DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet STOP : NULL >> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Received >> a >> packet STOP : >> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Thread, >> WrapperListener_start_runner, handling the shutdown process. >> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: >> shutdownJVM(0) Thread:WrapperListener_start_runner >> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: wait for >> 0 >> shutdown locs to be released. >> INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Send a >> packet STOPPED : 0 >> DEBUG | wrapperp | 2009/03/17 09:40:36 | read a packet STOPPED : 0 >> DEBUG | wrapper | 2009/03/17 09:40:36 | JVM signalled that it was >> stopped. >> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Closing >> socket. >> DEBUG | wrapperp | 2009/03/17 09:40:37 | socket read no code (closed?). >> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: calling >> System.exit(0) >> INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Server >> daemon shut down >> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM process exited with a code >> of >> 0, leaving the wrapper exit code set to 0. >> DEBUG | wrapper | 2009/03/17 09:40:37 | JVM exited normally. >> STATUS | wrapper | 2009/03/17 09:40:37 | <-- Wrapper Stopped >> >> This log say us something. >> >> Thanks in advance!!. > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > -- View this message in context: http://www.nabble.com/Wrapper-stopped-after-startup-tp22554782p22556425.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Leif M. <lei...@ta...> - 2009-03-17 10:12:48
|
Elias, >From the java command line, it looks like you are making use of Integration Method #3 for your application. Is the com.gvs.AXConnectorServer.AXConnectorServiceWin32 class something that you created? It appears to be working pretty much correctly. The problem is that your WrapperListener.start implementation is returning an exit code of 0. This is telling the Wrapper that the JVM should exit with exit code 0. If the application is meant to continue running then the WrapperListener.start method should be returning null. See the Java docs for the WrapperListener class for more information: http://wrapper.tanukisoftware.org/doc/english/javadocs.html This is also described on the following page: http://wrapper.tanukisoftware.org/doc/english/integrate-listener.html Cheers, Leif On Tue, Mar 17, 2009 at 6:41 PM, ejml <eli...@gm...> wrote: > > Hello Folks!, > > I'm trying to use Java Service Wrapper to implement my java project like > windows service. My Project is made with Spring using Jetty. In other words, > I use spring to startup jetty. This setup in eclipse work fine but I try to > configure my application with Java Service Wrapper I get the next: > > DEBUG | wrapper | 2009/03/17 09:40:35 | Allocating a console for the > service. > DEBUG | wrapper | 2009/03/17 09:40:35 | Found console window. > STATUS | wrapper | 2009/03/17 09:40:35 | --> Wrapper Started as Service > STATUS | wrapper | 2009/03/17 09:40:35 | Java Service Wrapper Community > Edition 3.3.3 > STATUS | wrapper | 2009/03/17 09:40:35 | Copyright (C) 1999-2009 Tanuki > Software, Ltd. All Rights Reserved. > STATUS | wrapper | 2009/03/17 09:40:35 | > http://wrapper.tanukisoftware.org > STATUS | wrapper | 2009/03/17 09:40:35 | > DEBUG | wrapper | 2009/03/17 09:40:35 | Using tick timer. > DEBUG | wrapperp | 2009/03/17 09:40:35 | server listening on port 32000. > DEBUG | wrapper | 2009/03/17 09:40:35 | Ping settings: > wrapper.ping.interval=5, wrapper.ping.interval.logged=1, > wrapper.ping.timeout=30 > STATUS | wrapper | 2009/03/17 09:40:35 | Launching a JVM... > DEBUG | wrapper | 2009/03/17 09:40:35 | command: > "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath > "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" > -Dwrapper.key="fREO9IxlyMDSknzk" -Dwrapper.port=32000 > -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 > -Dwrapper.debug="TRUE" -Dwrapper.pid=4020 -Dwrapper.version="3.3.3" > -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" > -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 > com.gvs.AXConnectorServer.AXConnectorServiceWin32 > DEBUG | wrapper | 2009/03/17 09:40:35 | JVM started (PID=3756) > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > WrapperManager class initialized by thread: main Using classloader: > sun.misc.Launcher$AppClassLoader@11b86e7 > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager: Initializing... > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: JVM #1 > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Running a > 32-bit JVM. > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Registering > shutdown hook > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Using > wrapper > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Load native > library. One or more attempts may fail if platform specific libraries do > not exist. This is NORMAL and is only a problem if they all fail. > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Unable to > load native library: wrapper-windows-x86-32.dll Cause: no > wrapper-windows-x86-32 in java.library.path > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Loaded > native library: wrapper.dll > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Calling > native initialization method. > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Initializing > WrapperManager native library. > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Java Executable: > C:\WINNT\system32\java.exe > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Windows version: > 5.0.2195 > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java Version > : 1.6.0_11-b03 Java HotSpot(TM) Client VM > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java VM > Vendor : Sun Microsystems Inc. > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS Name > : Windows 2000 > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS Arch > : x86 > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9, > args[]) called by thread: main > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Startup > runner thread started. > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Control > event monitor thread started. > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > Communications runner thread started. > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Open socket > to wrapper...Wrapper-Connection > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Failed > attempt to bind using local port 31000 > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Opened > Socket from 31001 to 32000 > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a > packet KEY : fREO9IxlyMDSknzk > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001]) > DEBUG | wrapperp | 2009/03/17 09:40:35 | accepted a socket from 127.0.0.1 > on port 31001 > DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet KEY : > fREO9IxlyMDSknzk > DEBUG | wrapper | 2009/03/17 09:40:35 | Got key from JVM: fREO9IxlyMDSknzk > DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet LOW_LOG_LEVEL : 1 > DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PING_TIMEOUT : 30 > DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PROPERTIES : > (Property Values) > DEBUG | wrapper | 2009/03/17 09:40:35 | Start Application. > DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet START : start > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received a > packet LOW_LOG_LEVEL : 1 > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: LowLogLevel > from Wrapper is 1 > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received a > packet PING_TIMEOUT : 30 > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: PingTimeout > from Wrapper is 30000 > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received a > packet PROPERTIES : (Property Values) > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received a > packet START : start > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: calling > WrapperListener.start() > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > WrapperListener.start runner thread started. > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: returned > from WrapperListener.start() > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > WrapperListener.start() returned an exit code of 0. > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: > WrapperManager.stop(0) called by thread: WrapperListener_start_runner > INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a > packet STOP : 0 > DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet STOP : 0 > DEBUG | wrapper | 2009/03/17 09:40:35 | JVM requested a shutdown. (0) > DEBUG | wrapper | 2009/03/17 09:40:35 | wrapperStopProcess(0) called. > DEBUG | wrapper | 2009/03/17 09:40:35 | Sending stop signal to JVM > DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet STOP : NULL > INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Received a > packet STOP : > INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Thread, > WrapperListener_start_runner, handling the shutdown process. > INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: > shutdownJVM(0) Thread:WrapperListener_start_runner > INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: wait for 0 > shutdown locs to be released. > INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Send a > packet STOPPED : 0 > DEBUG | wrapperp | 2009/03/17 09:40:36 | read a packet STOPPED : 0 > DEBUG | wrapper | 2009/03/17 09:40:36 | JVM signalled that it was stopped. > INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Closing > socket. > DEBUG | wrapperp | 2009/03/17 09:40:37 | socket read no code (closed?). > INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: calling > System.exit(0) > INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Server > daemon shut down > DEBUG | wrapper | 2009/03/17 09:40:37 | JVM process exited with a code of > 0, leaving the wrapper exit code set to 0. > DEBUG | wrapper | 2009/03/17 09:40:37 | JVM exited normally. > STATUS | wrapper | 2009/03/17 09:40:37 | <-- Wrapper Stopped > > This log say us something. > > Thanks in advance!!. |
|
From: ejml <eli...@gm...> - 2009-03-17 09:41:52
|
Hello Folks!, I'm trying to use Java Service Wrapper to implement my java project like windows service. My Project is made with Spring using Jetty. In other words, I use spring to startup jetty. This setup in eclipse work fine but I try to configure my application with Java Service Wrapper I get the next: DEBUG | wrapper | 2009/03/17 09:40:35 | Allocating a console for the service. DEBUG | wrapper | 2009/03/17 09:40:35 | Found console window. STATUS | wrapper | 2009/03/17 09:40:35 | --> Wrapper Started as Service STATUS | wrapper | 2009/03/17 09:40:35 | Java Service Wrapper Community Edition 3.3.3 STATUS | wrapper | 2009/03/17 09:40:35 | Copyright (C) 1999-2009 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2009/03/17 09:40:35 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2009/03/17 09:40:35 | DEBUG | wrapper | 2009/03/17 09:40:35 | Using tick timer. DEBUG | wrapperp | 2009/03/17 09:40:35 | server listening on port 32000. DEBUG | wrapper | 2009/03/17 09:40:35 | Ping settings: wrapper.ping.interval=5, wrapper.ping.interval.logged=1, wrapper.ping.timeout=30 STATUS | wrapper | 2009/03/17 09:40:35 | Launching a JVM... DEBUG | wrapper | 2009/03/17 09:40:35 | command: "C:\WINNT\system32\java.exe" -Djava.library.path="../lib" -classpath "../bin/AXConnectorServer.jar;../lib/wrappertest.jar;../lib/wrapper.jar" -Dwrapper.key="fREO9IxlyMDSknzk" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=4020 -Dwrapper.version="3.3.3" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 com.gvs.AXConnectorServer.AXConnectorServiceWin32 DEBUG | wrapper | 2009/03/17 09:40:35 | JVM started (PID=3756) INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoader@11b86e7 INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager: Initializing... INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: JVM #1 INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Running a 32-bit JVM. INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Registering shutdown hook INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Using wrapper INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Load native library. One or more attempts may fail if platform specific libraries do not exist. This is NORMAL and is only a problem if they all fail. INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Unable to load native library: wrapper-windows-x86-32.dll Cause: no wrapper-windows-x86-32 in java.library.path INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Loaded native library: wrapper.dll INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Calling native initialization method. INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Initializing WrapperManager native library. INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Java Executable: C:\WINNT\system32\java.exe INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperJNI Debug: Windows version: 5.0.2195 INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java Version : 1.6.0_11-b03 Java HotSpot(TM) Client VM INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Java VM Vendor : Sun Microsystems Inc. INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS Name : Windows 2000 INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: OS Arch : x86 INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: WrapperManager.start(com.gvs.AXConnectorServer.AXConnectorServiceWin32@201f9, args[]) called by thread: main INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Startup runner thread started. INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Control event monitor thread started. INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Communications runner thread started. INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Open socket to wrapper...Wrapper-Connection INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Failed attempt to bind using local port 31000 INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Opened Socket from 31001 to 32000 INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a packet KEY : fREO9IxlyMDSknzk INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001]) DEBUG | wrapperp | 2009/03/17 09:40:35 | accepted a socket from 127.0.0.1 on port 31001 DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet KEY : fREO9IxlyMDSknzk DEBUG | wrapper | 2009/03/17 09:40:35 | Got key from JVM: fREO9IxlyMDSknzk DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet LOW_LOG_LEVEL : 1 DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PING_TIMEOUT : 30 DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet PROPERTIES : (Property Values) DEBUG | wrapper | 2009/03/17 09:40:35 | Start Application. DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet START : start INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received a packet LOW_LOG_LEVEL : 1 INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: LowLogLevel from Wrapper is 1 INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received a packet PING_TIMEOUT : 30 INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: PingTimeout from Wrapper is 30000 INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received a packet PROPERTIES : (Property Values) INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Received a packet START : start INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: calling WrapperListener.start() INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: WrapperListener.start runner thread started. INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: returned from WrapperListener.start() INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: WrapperListener.start() returned an exit code of 0. INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: WrapperManager.stop(0) called by thread: WrapperListener_start_runner INFO | jvm 1 | 2009/03/17 09:40:35 | WrapperManager Debug: Send a packet STOP : 0 DEBUG | wrapperp | 2009/03/17 09:40:35 | read a packet STOP : 0 DEBUG | wrapper | 2009/03/17 09:40:35 | JVM requested a shutdown. (0) DEBUG | wrapper | 2009/03/17 09:40:35 | wrapperStopProcess(0) called. DEBUG | wrapper | 2009/03/17 09:40:35 | Sending stop signal to JVM DEBUG | wrapperp | 2009/03/17 09:40:35 | send a packet STOP : NULL INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Received a packet STOP : INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Thread, WrapperListener_start_runner, handling the shutdown process. INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: shutdownJVM(0) Thread:WrapperListener_start_runner INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: wait for 0 shutdown locs to be released. INFO | jvm 1 | 2009/03/17 09:40:36 | WrapperManager Debug: Send a packet STOPPED : 0 DEBUG | wrapperp | 2009/03/17 09:40:36 | read a packet STOPPED : 0 DEBUG | wrapper | 2009/03/17 09:40:36 | JVM signalled that it was stopped. INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Closing socket. DEBUG | wrapperp | 2009/03/17 09:40:37 | socket read no code (closed?). INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: calling System.exit(0) INFO | jvm 1 | 2009/03/17 09:40:37 | WrapperManager Debug: Server daemon shut down DEBUG | wrapper | 2009/03/17 09:40:37 | JVM process exited with a code of 0, leaving the wrapper exit code set to 0. DEBUG | wrapper | 2009/03/17 09:40:37 | JVM exited normally. STATUS | wrapper | 2009/03/17 09:40:37 | <-- Wrapper Stopped This log say us something. Thanks in advance!!. -- View this message in context: http://www.nabble.com/Wrapper-stopped-after-startup-tp22554782p22554782.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
165 messages has been excluded from this view by a project administrator.
