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: Tasso A. <ta...@rb...> - 2010-08-20 19:46:13
|
Using Windows 2003 SP2 Yes this would be useful, especially for monitoring/troubleshooting live applications without the need of JMX. -----Original Message----- From: Christian Mueller [mailto:chr...@ta...] Sent: Thursday, August 19, 2010 12:00 AM To: wra...@li... Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detectappsrunning in service mode. Tasso, I'm sorry for the delay. I was digging around a bit more and could finally reproduce your problem on Windows 7. Are you running a Windows 7? On this platform it seems that sth. has changed about accessing the data from a different user. I couldn't find a way of how to monitor the java application directly, yet. However, you can also try enabling jmx: wrapper.java.additional.x=-Dcom.sun.management.jmxremote.port=XXXX wrapper.java.additional.x=-Dcom.sun.management.jmxremote.ssl=false wrapper.java.additional.x=-Dcom.sun.management.jmxremote.authenticate=false When you start VisualVM and select File->Add JMX Connection. Input in the Connection field "localhost:XXXX" and you should be able to monitor the app via jmx. I will keep my eyes open in order to find out if there is another solution. Cheers, Christian On Thu, Aug 19, 2010 at 12:50 AM, Tasso Angelidis <ta...@rb...> wrote: > Any ideas? > > -----Original Message----- > From: Tasso Angelidis [mailto:ta...@rb...] > Sent: Friday, August 13, 2010 2:45 PM > To: wra...@li... > Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detectappsrunning in service mode. > > It looks like the same path. I even put DEBUG on to see what PATH variables are being used. > > This is what I get... > > INFO | wrapper | 2010/08/13 14:27:47 | PS--- | JAVA_HOME=C:\jdk1.6.0_21 > ... > INFO | wrapper | 2010/08/13 14:27:47 | PS--- | TEMP=C:\WINDOWS\TEMP > INFO | wrapper | 2010/08/13 14:27:47 | PS--- | TMP=C:\WINDOWS\TEMP > ... > INFO | wrapper | 2010/08/13 14:27:48 | Command: "C:\jdk1.6.0_21\bin\java" -server ...... > > So then, I open a command window and run... > > C:\>SET TMP=C:\WINDOWS\TEMP > C:\>C:\jdk1.6.0_21\bin\jvisualvm.exe > > The wrapper shows up as <unknown application> (pid 1234) > > And the main window where the telemetry is supposed to be, indicates "Not supported for this JVM" > > > > -----Original Message----- > From: Christian Mueller [mailto:chr...@ta...] > Sent: Thursday, August 12, 2010 10:25 PM > To: wra...@li... > Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detect appsrunning in service mode. > > Tasso, > > It seems the jvm version of the application running as service and the > version of VisualVM is different. > > I assume that you have specified in your conf file "wrapper.java.command=java" > This will tell the wrapper to look up the java command from the PATH > Variable. However when running as service it is most likely that the > PATH variable is not the same as the one for your user account. This > most likely leads to a different jvm version being used rather than > the one you maybe are intending to use. > > Please set this parameter in your conf file to verify this: > wrapper.java.command.loglevel=INFO > > This will print out the command line of the java process immediately > before creating the java process. > > The first token is the path to the jvm. > > Hope this helps you out. > > Cheers, > Christian > > > > On Fri, Aug 13, 2010 at 2:51 AM, Tasso Angelidis <ta...@rb...> wrote: >> I tried. Now it seems to detect the app but I get no telemetry data. >> This is my conf... >> >> #******************************************************************** >> # Wrapper License Properties (Ignored by Community Edition) >> #******************************************************************** >> # Include file problems can be debugged by removing the first '#' >> # from the following line: >> ##include.debug >> #include ../conf/wrapper-license.conf >> ##include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf >> set.TMP=../TMP >> >> Do I have to explicitly set the path? It seems to work the temp data got >> created and jvisualvm finds the application PID, but it's not displaying >> any telemetry. It says "not supported for this vm" >> >> >> -----Original Message----- >> From: Christian Mueller [mailto:chr...@ta...] >> Sent: Tuesday, August 10, 2010 4:14 AM >> To: wra...@li... >> Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detect >> appsrunning in service mode. >> >> Tasso, >> >> The temp directory of Visual VM and the java application run as >> service is different, so they can not find each other instantly. >> >> However there is a workaround to achieve what you are trying to do. >> >> Please set the environment variable TMP for the wrapper process in >> your conf file: >> >> set.TMP=C:\tmp >> >> and start the wrapper as service. >> >> Now start a console and set the TMP environment variable to the same >> value you specified in the conf file: >> >> set TMP=C:\tmp >> >> after that start jvisualvm >> >> C:\Program Files\...\jvisualvm.exe >> >> Visual VM should now be able to list the java process. >> >> Hope this works out for you. >> >> Cheers, >> Christian >> >> >> >> >> On Mon, Aug 9, 2010 at 10:24 PM, Tasso Angelidis <ta...@rb...> >> wrote: >>> If I run my application with the wrapper as Windows service Java >> Visual VM >>> doesn't detect it. But if I run the application using console mode of >> the >>> wrapper it gets detected. >>> >>> >> ------------------------------------------------------------------------ >> ------ >>> This SF.net email is sponsored by >>> >>> Make an app they can't live without >>> Enter the BlackBerry Developer Challenge >>> http://p.sf.net/sfu/RIM-dev2dev >>> _______________________________________________ >>> Wrapper-user mailing list >>> Wra...@li... >>> https://lists.sourceforge.net/lists/listinfo/wrapper-user >>> >>> >> >> ------------------------------------------------------------------------ >> ------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Christian M. <chr...@ta...> - 2010-08-19 04:00:32
|
Tasso, I'm sorry for the delay. I was digging around a bit more and could finally reproduce your problem on Windows 7. Are you running a Windows 7? On this platform it seems that sth. has changed about accessing the data from a different user. I couldn't find a way of how to monitor the java application directly, yet. However, you can also try enabling jmx: wrapper.java.additional.x=-Dcom.sun.management.jmxremote.port=XXXX wrapper.java.additional.x=-Dcom.sun.management.jmxremote.ssl=false wrapper.java.additional.x=-Dcom.sun.management.jmxremote.authenticate=false When you start VisualVM and select File->Add JMX Connection. Input in the Connection field "localhost:XXXX" and you should be able to monitor the app via jmx. I will keep my eyes open in order to find out if there is another solution. Cheers, Christian On Thu, Aug 19, 2010 at 12:50 AM, Tasso Angelidis <ta...@rb...> wrote: > Any ideas? > > -----Original Message----- > From: Tasso Angelidis [mailto:ta...@rb...] > Sent: Friday, August 13, 2010 2:45 PM > To: wra...@li... > Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detectappsrunning in service mode. > > It looks like the same path. I even put DEBUG on to see what PATH variables are being used. > > This is what I get... > > INFO | wrapper | 2010/08/13 14:27:47 | PS--- | JAVA_HOME=C:\jdk1.6.0_21 > ... > INFO | wrapper | 2010/08/13 14:27:47 | PS--- | TEMP=C:\WINDOWS\TEMP > INFO | wrapper | 2010/08/13 14:27:47 | PS--- | TMP=C:\WINDOWS\TEMP > ... > INFO | wrapper | 2010/08/13 14:27:48 | Command: "C:\jdk1.6.0_21\bin\java" -server ...... > > So then, I open a command window and run... > > C:\>SET TMP=C:\WINDOWS\TEMP > C:\>C:\jdk1.6.0_21\bin\jvisualvm.exe > > The wrapper shows up as <unknown application> (pid 1234) > > And the main window where the telemetry is supposed to be, indicates "Not supported for this JVM" > > > > -----Original Message----- > From: Christian Mueller [mailto:chr...@ta...] > Sent: Thursday, August 12, 2010 10:25 PM > To: wra...@li... > Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detect appsrunning in service mode. > > Tasso, > > It seems the jvm version of the application running as service and the > version of VisualVM is different. > > I assume that you have specified in your conf file "wrapper.java.command=java" > This will tell the wrapper to look up the java command from the PATH > Variable. However when running as service it is most likely that the > PATH variable is not the same as the one for your user account. This > most likely leads to a different jvm version being used rather than > the one you maybe are intending to use. > > Please set this parameter in your conf file to verify this: > wrapper.java.command.loglevel=INFO > > This will print out the command line of the java process immediately > before creating the java process. > > The first token is the path to the jvm. > > Hope this helps you out. > > Cheers, > Christian > > > > On Fri, Aug 13, 2010 at 2:51 AM, Tasso Angelidis <ta...@rb...> wrote: >> I tried. Now it seems to detect the app but I get no telemetry data. >> This is my conf... >> >> #******************************************************************** >> # Wrapper License Properties (Ignored by Community Edition) >> #******************************************************************** >> # Include file problems can be debugged by removing the first '#' >> # from the following line: >> ##include.debug >> #include ../conf/wrapper-license.conf >> ##include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf >> set.TMP=../TMP >> >> Do I have to explicitly set the path? It seems to work the temp data got >> created and jvisualvm finds the application PID, but it's not displaying >> any telemetry. It says "not supported for this vm" >> >> >> -----Original Message----- >> From: Christian Mueller [mailto:chr...@ta...] >> Sent: Tuesday, August 10, 2010 4:14 AM >> To: wra...@li... >> Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detect >> appsrunning in service mode. >> >> Tasso, >> >> The temp directory of Visual VM and the java application run as >> service is different, so they can not find each other instantly. >> >> However there is a workaround to achieve what you are trying to do. >> >> Please set the environment variable TMP for the wrapper process in >> your conf file: >> >> set.TMP=C:\tmp >> >> and start the wrapper as service. >> >> Now start a console and set the TMP environment variable to the same >> value you specified in the conf file: >> >> set TMP=C:\tmp >> >> after that start jvisualvm >> >> C:\Program Files\...\jvisualvm.exe >> >> Visual VM should now be able to list the java process. >> >> Hope this works out for you. >> >> Cheers, >> Christian >> >> >> >> >> On Mon, Aug 9, 2010 at 10:24 PM, Tasso Angelidis <ta...@rb...> >> wrote: >>> If I run my application with the wrapper as Windows service Java >> Visual VM >>> doesn't detect it. But if I run the application using console mode of >> the >>> wrapper it gets detected. >>> >>> >> ------------------------------------------------------------------------ >> ------ >>> This SF.net email is sponsored by >>> >>> Make an app they can't live without >>> Enter the BlackBerry Developer Challenge >>> http://p.sf.net/sfu/RIM-dev2dev >>> _______________________________________________ >>> Wrapper-user mailing list >>> Wra...@li... >>> https://lists.sourceforge.net/lists/listinfo/wrapper-user >>> >>> >> >> ------------------------------------------------------------------------ >> ------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Tasso A. <ta...@rb...> - 2010-08-18 15:51:03
|
Any ideas? -----Original Message----- From: Tasso Angelidis [mailto:ta...@rb...] Sent: Friday, August 13, 2010 2:45 PM To: wra...@li... Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detectappsrunning in service mode. It looks like the same path. I even put DEBUG on to see what PATH variables are being used. This is what I get... INFO | wrapper | 2010/08/13 14:27:47 | PS--- | JAVA_HOME=C:\jdk1.6.0_21 ... INFO | wrapper | 2010/08/13 14:27:47 | PS--- | TEMP=C:\WINDOWS\TEMP INFO | wrapper | 2010/08/13 14:27:47 | PS--- | TMP=C:\WINDOWS\TEMP ... INFO | wrapper | 2010/08/13 14:27:48 | Command: "C:\jdk1.6.0_21\bin\java" -server ...... So then, I open a command window and run... C:\>SET TMP=C:\WINDOWS\TEMP C:\>C:\jdk1.6.0_21\bin\jvisualvm.exe The wrapper shows up as <unknown application> (pid 1234) And the main window where the telemetry is supposed to be, indicates "Not supported for this JVM" -----Original Message----- From: Christian Mueller [mailto:chr...@ta...] Sent: Thursday, August 12, 2010 10:25 PM To: wra...@li... Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detect appsrunning in service mode. Tasso, It seems the jvm version of the application running as service and the version of VisualVM is different. I assume that you have specified in your conf file "wrapper.java.command=java" This will tell the wrapper to look up the java command from the PATH Variable. However when running as service it is most likely that the PATH variable is not the same as the one for your user account. This most likely leads to a different jvm version being used rather than the one you maybe are intending to use. Please set this parameter in your conf file to verify this: wrapper.java.command.loglevel=INFO This will print out the command line of the java process immediately before creating the java process. The first token is the path to the jvm. Hope this helps you out. Cheers, Christian On Fri, Aug 13, 2010 at 2:51 AM, Tasso Angelidis <ta...@rb...> wrote: > I tried. Now it seems to detect the app but I get no telemetry data. > This is my conf... > > #******************************************************************** > # Wrapper License Properties (Ignored by Community Edition) > #******************************************************************** > # Include file problems can be debugged by removing the first '#' > # from the following line: > ##include.debug > #include ../conf/wrapper-license.conf > ##include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf > set.TMP=../TMP > > Do I have to explicitly set the path? It seems to work the temp data got > created and jvisualvm finds the application PID, but it's not displaying > any telemetry. It says "not supported for this vm" > > > -----Original Message----- > From: Christian Mueller [mailto:chr...@ta...] > Sent: Tuesday, August 10, 2010 4:14 AM > To: wra...@li... > Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detect > appsrunning in service mode. > > Tasso, > > The temp directory of Visual VM and the java application run as > service is different, so they can not find each other instantly. > > However there is a workaround to achieve what you are trying to do. > > Please set the environment variable TMP for the wrapper process in > your conf file: > > set.TMP=C:\tmp > > and start the wrapper as service. > > Now start a console and set the TMP environment variable to the same > value you specified in the conf file: > > set TMP=C:\tmp > > after that start jvisualvm > > C:\Program Files\...\jvisualvm.exe > > Visual VM should now be able to list the java process. > > Hope this works out for you. > > Cheers, > Christian > > > > > On Mon, Aug 9, 2010 at 10:24 PM, Tasso Angelidis <ta...@rb...> > wrote: >> If I run my application with the wrapper as Windows service Java > Visual VM >> doesn't detect it. But if I run the application using console mode of > the >> wrapper it gets detected. >> >> > ------------------------------------------------------------------------ > ------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > > ------------------------------------------------------------------------ > ------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leif M. <lei...@ta...> - 2010-08-16 14:41:43
|
Peter, I am not aware of any issues that would directly cause such a change. What was the version that worked before, and what is the new version which is no longer working? Once I know the versions I can look into this more carefully. Could you please set the wrapper.java.command.loglevel=INFO property in both versions and try running the Wrapper. This will cause the full generated Java command line in both cases to be output to the log file. My guess is that something is different between the two. Please send me your wrapper.conf file as well so I can take a look at that. Cheers, Leif On Mon, Aug 16, 2010 at 10:59 PM, Peter Dahm <pd...@it...> wrote: > Hi, > > > > I changed from an evaluation version of the wrapper to a newer one, because > I bought a developer license and now the application doesn’t work any more. > > > > Now I got the following exception: > > > > 0/08/16 15:53:04 | SCHWERWIEGEND: Fehler beim Start der Application. > Neustart: > > INFO | jvm 2 | 2010/08/16 15:53:04 | > org.springframework.beans.factory.BeanInitializationException: Could not > load properties; nested exception is java.io.FileNotFoundException: class > path resource [application.properties] cannot be opened because it does not > exist > > INFO | jvm 2 | 2010/08/16 15:53:04 | at > org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:78) > > INFO | jvm 2 | 2010/08/16 15:53:04 | at > org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:554) > > INFO | jvm 2 | 2010/08/16 15:53:04 | at > org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:528) > > INFO | jvm 2 | 2010/08/16 15:53:04 | at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:363) > > INFO | jvm 2 | 2010/08/16 15:53:04 | at > org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139) > > INFO | jvm 2 | 2010/08/16 15:53:04 | at > org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:83) > > INFO | jvm 2 | 2010/08/16 15:53:04 | at > com.dpd.delisprint.environment.Environmen > > > > The Resource application.properties can’t be found any more. It must be in > the classpath. I got the following debug information concerning this class > path entry. > > > > INFO | jvm 1 | 2010/08/16 15:33:48 | INFO: > URLSfile:/C:/Program%20Files/DPD/DELISprint%206%20s/Resources/config/application.properties > > > > Is something changed to the class path behavior ? > > > > Peter |
|
From: Peter D. <pd...@it...> - 2010-08-16 14:24:18
|
Hi, I changed from an evaluation version of the wrapper to a newer one, because I bought a developer license and now the application doesn't work any more. Now I got the following exception: 0/08/16 15:53:04 | SCHWERWIEGEND: Fehler beim Start der Application. Neustart: INFO | jvm 2 | 2010/08/16 15:53:04 | org.springframework.beans.factory.BeanInitializationException: Could not load properties; nested exception is java.io.FileNotFoundException: class path resource [application.properties] cannot be opened because it does not exist INFO | jvm 2 | 2010/08/16 15:53:04 | at org.springframework.beans.factory.config.PropertyResourceConfigurer.postProc essBeanFactory(PropertyResourceConfigurer.java:78) INFO | jvm 2 | 2010/08/16 15:53:04 | at org.springframework.context.support.AbstractApplicationContext.invokeBeanFac toryPostProcessors(AbstractApplicationContext.java:554) INFO | jvm 2 | 2010/08/16 15:53:04 | at org.springframework.context.support.AbstractApplicationContext.invokeBeanFac toryPostProcessors(AbstractApplicationContext.java:528) INFO | jvm 2 | 2010/08/16 15:53:04 | at org.springframework.context.support.AbstractApplicationContext.refresh(Abstr actApplicationContext.java:363) INFO | jvm 2 | 2010/08/16 15:53:04 | at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(Cl assPathXmlApplicationContext.java:139) INFO | jvm 2 | 2010/08/16 15:53:04 | at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(Cl assPathXmlApplicationContext.java:83) INFO | jvm 2 | 2010/08/16 15:53:04 | at com.dpd.delisprint.environment.Environmen The Resource application.properties can't be found any more. It must be in the classpath. I got the following debug information concerning this class path entry. INFO | jvm 1 | 2010/08/16 15:33:48 | INFO: URLSfile:/C:/Program%20Files/DPD/DELISprint%206%20s/Resources/config/applica tion.properties Is something changed to the class path behavior ? Peter |
|
From: Leif M. <lei...@ta...> - 2010-08-16 07:51:33
|
Osiris, Could you please send me your wrapper.conf, and the full wrapper.log file so I can review this in context. Initially I am interested in what the various timeout values in your wrapper.conf are set to. I would also like to see in more detail exactly what is and isn't happening, and when. The first message is normal line of output when wrapper.state_output=TRUE is set. The second line you sent is a message from the JVM that is logged when it has not received any pings from the Wrapper process for a long period of time. The fact that you are seeing the message however shows that the Wrapper process is alive to log it. As your CPU is low, one possible cause is when the system is undergoing heavy swapping. Your iowait is low however. Is this a physical server or a virtual machine? Please feel free to contact su...@ta... directly with your reply so we don't hit the list with the large log files. I will update the thread when we figure out what is happening. Cheers, Leif On Mon, Aug 16, 2010 at 4:34 PM, Osiris <os...@ia...> wrote: > I am running the Linux Java Service Wrapper (3.5.3) and have been having the > following problem for months: every few hours (randomly it seems), the > wrapper does not ping the JVM for about 5 minutes: > > > > STATUS | wrapper | 2010/08/15 18:47:08 | Ticks=0001c8b5, > WrapperState=STARTED, JVMState=STARTED JVMStateTimeoutTicks=0001c9ed (31s), > Exit=false, RestartMode=0, Orphan=false > > INFO | jvm 1 | 2010/08/15 18:52:08 | WrapperManager Debug: Read > Timed out. (Last Ping was 303,200 milliseconds ago) > > > > CPU usage is minimal during this time, and the server was given a hardware > swap to rule out faulty hardware and there is no power management on the > server. Has anyone seen this behaviour before? > > > > In the following sar output (logs every minute), there are some missing > entries (18:49, 18:51), which might indicate CPU suspension for some reason: > > sar -s 18:48:00 -e 18:52:00 -f /var/log/sysstat/sa15 -u -d -r -n ALL > > > > 18:48:01 CPU %user %nice %system %iowait %steal > %idle > > 18:50:01 all 0.10 0.00 0.16 0.01 0.00 > 99.74 > > Average: all 0.10 0.00 0.16 0.01 0.00 > 99.74 > > > > 18:48:01 kbmemfree kbmemused %memused kbbuffers kbcached kbcommit > %commit > > 18:50:01 3078524 1033780 25.14 144144 487128 665964 > 3.19 > > Average: 3078524 1033780 25.14 144144 487128 665964 > 3.19 > > > > 18:48:01 DEV tps rd_sec/s wr_sec/s avgrq-sz avgqu-sz > await svctm %util > > 18:50:01 dev8-0 22.40 0.00 307.20 13.71 0.14 > 6.43 5.93 13.28 > > 18:50:01 dev8-16 22.40 0.00 307.20 13.71 0.14 > 6.07 5.57 12.48 > > 18:50:01 dev9-0 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 > > 18:50:01 dev9-1 25.60 0.00 204.80 8.00 0.00 > 0.00 0.00 0.00 > > Average: dev8-0 22.40 0.00 307.20 13.71 0.14 > 6.43 5.93 13.28 > > Average: dev8-16 22.40 0.00 307.20 13.71 0.14 > 6.07 5.57 12.48 > > Average: dev9-0 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 > > Average: dev9-1 25.60 0.00 204.80 8.00 0.00 > 0.00 0.00 0.00 > > > > 18:48:01 IFACE rxpck/s txpck/s rxkB/s txkB/s rxcmp/s > txcmp/s rxmcst/s > > 18:50:01 lo 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 > > 18:50:01 eth0 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 > > Average: lo 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 > > Average: eth0 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 > > > > 18:48:01 IFACE rxerr/s txerr/s coll/s rxdrop/s txdrop/s > txcarr/s rxfram/s rxfifo/s txfifo/s > > 18:50:01 lo 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 > > 18:50:01 eth0 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 > > Average: lo 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 > > Average: eth0 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 > > > > 18:48:01 call/s retrans/s read/s write/s access/s getatt/s > > 18:50:01 0.00 0.00 0.00 0.00 0.00 0.00 > > Average: 0.00 0.00 0.00 0.00 0.00 0.00 > > > > 18:48:01 scall/s badcall/s packet/s udp/s tcp/s hit/s > miss/s sread/s swrite/s saccess/s sgetatt/s > > 18:50:01 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 > > Average: 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 > > > > 18:48:01 totsck tcpsck udpsck rawsck ip-frag tcp-tw > > 18:50:01 105 12 2 0 0 0 > > Average: 105 12 2 0 0 0 |
|
From: Osiris <os...@ia...> - 2010-08-16 07:34:32
|
I am running the Linux Java Service Wrapper (3.5.3) and have been having the
following problem for months: every few hours (randomly it seems), the
wrapper does not ping the JVM for about 5 minutes:
STATUS | wrapper | 2010/08/15 18:47:08 | Ticks=0001c8b5,
WrapperState=STARTED, JVMState=STARTED JVMStateTimeoutTicks=0001c9ed (31s),
Exit=false, RestartMode=0, Orphan=false
INFO | jvm 1 | 2010/08/15 18:52:08 | WrapperManager Debug: Read
Timed out. (Last Ping was 303,200 milliseconds ago)
CPU usage is minimal during this time, and the server was given a hardware
swap to rule out faulty hardware and there is no power management on the
server. Has anyone seen this behaviour before?
In the following sar output (logs every minute), there are some missing
entries (18:49, 18:51), which might indicate CPU suspension for some reason:
sar -s 18:48:00 -e 18:52:00 -f /var/log/sysstat/sa15 -u -d -r -n ALL
18:48:01 CPU %user %nice %system %iowait %steal
%idle
18:50:01 all 0.10 0.00 0.16 0.01 0.00
99.74
Average: all 0.10 0.00 0.16 0.01 0.00
99.74
18:48:01 kbmemfree kbmemused %memused kbbuffers kbcached kbcommit
%commit
18:50:01 3078524 1033780 25.14 144144 487128 665964
3.19
Average: 3078524 1033780 25.14 144144 487128 665964
3.19
18:48:01 DEV tps rd_sec/s wr_sec/s avgrq-sz avgqu-sz
await svctm %util
18:50:01 dev8-0 22.40 0.00 307.20 13.71 0.14
6.43 5.93 13.28
18:50:01 dev8-16 22.40 0.00 307.20 13.71 0.14
6.07 5.57 12.48
18:50:01 dev9-0 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00
18:50:01 dev9-1 25.60 0.00 204.80 8.00 0.00
0.00 0.00 0.00
Average: dev8-0 22.40 0.00 307.20 13.71 0.14
6.43 5.93 13.28
Average: dev8-16 22.40 0.00 307.20 13.71 0.14
6.07 5.57 12.48
Average: dev9-0 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00
Average: dev9-1 25.60 0.00 204.80 8.00 0.00
0.00 0.00 0.00
18:48:01 IFACE rxpck/s txpck/s rxkB/s txkB/s rxcmp/s
txcmp/s rxmcst/s
18:50:01 lo 0.00 0.00 0.00 0.00 0.00
0.00 0.00
18:50:01 eth0 0.00 0.00 0.00 0.00 0.00
0.00 0.00
Average: lo 0.00 0.00 0.00 0.00 0.00
0.00 0.00
Average: eth0 0.00 0.00 0.00 0.00 0.00
0.00 0.00
18:48:01 IFACE rxerr/s txerr/s coll/s rxdrop/s txdrop/s
txcarr/s rxfram/s rxfifo/s txfifo/s
18:50:01 lo 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
18:50:01 eth0 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
Average: lo 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
Average: eth0 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
18:48:01 call/s retrans/s read/s write/s access/s getatt/s
18:50:01 0.00 0.00 0.00 0.00 0.00 0.00
Average: 0.00 0.00 0.00 0.00 0.00 0.00
18:48:01 scall/s badcall/s packet/s udp/s tcp/s hit/s
miss/s sread/s swrite/s saccess/s sgetatt/s
18:50:01 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00 0.00
Average: 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00 0.00
18:48:01 totsck tcpsck udpsck rawsck ip-frag tcp-tw
18:50:01 105 12 2 0 0 0
Average: 105 12 2 0 0 0
|
|
From: Tasso A. <ta...@rb...> - 2010-08-13 18:44:23
|
It looks like the same path. I even put DEBUG on to see what PATH variables are being used. This is what I get... INFO | wrapper | 2010/08/13 14:27:47 | PS--- | JAVA_HOME=C:\jdk1.6.0_21 ... INFO | wrapper | 2010/08/13 14:27:47 | PS--- | TEMP=C:\WINDOWS\TEMP INFO | wrapper | 2010/08/13 14:27:47 | PS--- | TMP=C:\WINDOWS\TEMP ... INFO | wrapper | 2010/08/13 14:27:48 | Command: "C:\jdk1.6.0_21\bin\java" -server ...... So then, I open a command window and run... C:\>SET TMP=C:\WINDOWS\TEMP C:\>C:\jdk1.6.0_21\bin\jvisualvm.exe The wrapper shows up as <unknown application> (pid 1234) And the main window where the telemetry is supposed to be, indicates "Not supported for this JVM" -----Original Message----- From: Christian Mueller [mailto:chr...@ta...] Sent: Thursday, August 12, 2010 10:25 PM To: wra...@li... Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detect appsrunning in service mode. Tasso, It seems the jvm version of the application running as service and the version of VisualVM is different. I assume that you have specified in your conf file "wrapper.java.command=java" This will tell the wrapper to look up the java command from the PATH Variable. However when running as service it is most likely that the PATH variable is not the same as the one for your user account. This most likely leads to a different jvm version being used rather than the one you maybe are intending to use. Please set this parameter in your conf file to verify this: wrapper.java.command.loglevel=INFO This will print out the command line of the java process immediately before creating the java process. The first token is the path to the jvm. Hope this helps you out. Cheers, Christian On Fri, Aug 13, 2010 at 2:51 AM, Tasso Angelidis <ta...@rb...> wrote: > I tried. Now it seems to detect the app but I get no telemetry data. > This is my conf... > > #******************************************************************** > # Wrapper License Properties (Ignored by Community Edition) > #******************************************************************** > # Include file problems can be debugged by removing the first '#' > # from the following line: > ##include.debug > #include ../conf/wrapper-license.conf > ##include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf > set.TMP=../TMP > > Do I have to explicitly set the path? It seems to work the temp data got > created and jvisualvm finds the application PID, but it's not displaying > any telemetry. It says "not supported for this vm" > > > -----Original Message----- > From: Christian Mueller [mailto:chr...@ta...] > Sent: Tuesday, August 10, 2010 4:14 AM > To: wra...@li... > Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detect > appsrunning in service mode. > > Tasso, > > The temp directory of Visual VM and the java application run as > service is different, so they can not find each other instantly. > > However there is a workaround to achieve what you are trying to do. > > Please set the environment variable TMP for the wrapper process in > your conf file: > > set.TMP=C:\tmp > > and start the wrapper as service. > > Now start a console and set the TMP environment variable to the same > value you specified in the conf file: > > set TMP=C:\tmp > > after that start jvisualvm > > C:\Program Files\...\jvisualvm.exe > > Visual VM should now be able to list the java process. > > Hope this works out for you. > > Cheers, > Christian > > > > > On Mon, Aug 9, 2010 at 10:24 PM, Tasso Angelidis <ta...@rb...> > wrote: >> If I run my application with the wrapper as Windows service Java > Visual VM >> doesn't detect it. But if I run the application using console mode of > the >> wrapper it gets detected. >> >> > ------------------------------------------------------------------------ > ------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > > ------------------------------------------------------------------------ > ------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Christian M. <chr...@ta...> - 2010-08-13 02:25:21
|
Tasso, It seems the jvm version of the application running as service and the version of VisualVM is different. I assume that you have specified in your conf file "wrapper.java.command=java" This will tell the wrapper to look up the java command from the PATH Variable. However when running as service it is most likely that the PATH variable is not the same as the one for your user account. This most likely leads to a different jvm version being used rather than the one you maybe are intending to use. Please set this parameter in your conf file to verify this: wrapper.java.command.loglevel=INFO This will print out the command line of the java process immediately before creating the java process. The first token is the path to the jvm. Hope this helps you out. Cheers, Christian On Fri, Aug 13, 2010 at 2:51 AM, Tasso Angelidis <ta...@rb...> wrote: > I tried. Now it seems to detect the app but I get no telemetry data. > This is my conf... > > #******************************************************************** > # Wrapper License Properties (Ignored by Community Edition) > #******************************************************************** > # Include file problems can be debugged by removing the first '#' > # from the following line: > ##include.debug > #include ../conf/wrapper-license.conf > ##include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf > set.TMP=../TMP > > Do I have to explicitly set the path? It seems to work the temp data got > created and jvisualvm finds the application PID, but it's not displaying > any telemetry. It says "not supported for this vm" > > > -----Original Message----- > From: Christian Mueller [mailto:chr...@ta...] > Sent: Tuesday, August 10, 2010 4:14 AM > To: wra...@li... > Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detect > appsrunning in service mode. > > Tasso, > > The temp directory of Visual VM and the java application run as > service is different, so they can not find each other instantly. > > However there is a workaround to achieve what you are trying to do. > > Please set the environment variable TMP for the wrapper process in > your conf file: > > set.TMP=C:\tmp > > and start the wrapper as service. > > Now start a console and set the TMP environment variable to the same > value you specified in the conf file: > > set TMP=C:\tmp > > after that start jvisualvm > > C:\Program Files\...\jvisualvm.exe > > Visual VM should now be able to list the java process. > > Hope this works out for you. > > Cheers, > Christian > > > > > On Mon, Aug 9, 2010 at 10:24 PM, Tasso Angelidis <ta...@rb...> > wrote: >> If I run my application with the wrapper as Windows service Java > Visual VM >> doesn't detect it. But if I run the application using console mode of > the >> wrapper it gets detected. >> >> > ------------------------------------------------------------------------ > ------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > > ------------------------------------------------------------------------ > ------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Tasso A. <ta...@rb...> - 2010-08-12 17:51:15
|
I tried. Now it seems to detect the app but I get no telemetry data. This is my conf... #******************************************************************** # Wrapper License Properties (Ignored by Community Edition) #******************************************************************** # Include file problems can be debugged by removing the first '#' # from the following line: ##include.debug #include ../conf/wrapper-license.conf ##include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf set.TMP=../TMP Do I have to explicitly set the path? It seems to work the temp data got created and jvisualvm finds the application PID, but it's not displaying any telemetry. It says "not supported for this vm" -----Original Message----- From: Christian Mueller [mailto:chr...@ta...] Sent: Tuesday, August 10, 2010 4:14 AM To: wra...@li... Subject: Re: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detect appsrunning in service mode. Tasso, The temp directory of Visual VM and the java application run as service is different, so they can not find each other instantly. However there is a workaround to achieve what you are trying to do. Please set the environment variable TMP for the wrapper process in your conf file: set.TMP=C:\tmp and start the wrapper as service. Now start a console and set the TMP environment variable to the same value you specified in the conf file: set TMP=C:\tmp after that start jvisualvm C:\Program Files\...\jvisualvm.exe Visual VM should now be able to list the java process. Hope this works out for you. Cheers, Christian On Mon, Aug 9, 2010 at 10:24 PM, Tasso Angelidis <ta...@rb...> wrote: > If I run my application with the wrapper as Windows service Java Visual VM > doesn't detect it. But if I run the application using console mode of the > wrapper it gets detected. > > ------------------------------------------------------------------------ ------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------ ------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: 波波 . <gw...@ho...> - 2010-08-12 14:25:09
|
Christian, Thanks for your reply. I rechecked the log, the problem is about my application, not the wrapper. My application creates a working thread after it started and tries to connect to the database. If it fails to do so, the working thread quits but the main thread keeps running. Then the service still runs but does not output anything. After I restart it, it connects to the database successfully and works correctly. George > Date: Thu, 12 Aug 2010 12:59:06 +0900 > From: chr...@ta... > To: wra...@li... > Subject: Re: [Wrapper-user] Service started by Windows cluster does not work properly > > George, > > I'm sorry for the delay. > I unfortunately couldn't reproduce the problem you were seeing. > > However when the Cluster Management Tool as well as the Windows > Service say that the service is started then I assume that the wrapper > wasn't been able to write the log file has for some reason to the > location you expected. > In this case the Wrapper will log output to a file called wrapper.log > in the current working directory. The current working directory will > most likely be the directory containing the binary. However, in some > cases, when running as a Windows Service, the wrapper.log file may be > placed in your system directory (WinNT\System32). > > Are you having any storage dependencies for the service? > > Sincerely, > Christian > > > 2010/8/9 波波 . <gw...@ho...>: > > Dear all, > > > > I've used Java Serivce Wrapper 3.3.6 to wrap my application as a service, > > and I installed my service on 2 machines which are nodes of a Windows > > cluster.Then I configured my service as a resource in Windows cluster > > manager, so if one node fails, the cluster service can start my service on > > another node automatically. > > > > My service worked properly until the last system rebooting. After the system > > rebooted, I saw the resource of my service was online in cluster manager, > > and I also saw my service started in Windows' Services. But my service did > > not functioning - there were no output of it. I checked the log of my > > service (wrapper.log), it is strange that the log was not updated since the > > system shut down - neither the wrapper itself nor my application wrote any > > messages into the log file. > > > > To resume the production ASAP, I stopped my service and the cluster service > > detected this action and started my service automatically. After that, I > > could saw the output of my service. > > > > I'm confused that why my service did not work after system reboot - it was > > started by Windows cluster service, but it worked after restarting - it was > > also started by cluster service. And why was the log file not updated while > > the service was running after system reboot? Thanks for any clues. > > > > The configuration of my service is attached. > > > > Regards, > > George > > ------------------------------------------------------------------------------ > > This SF.net email is sponsored by > > > > Make an app they can't live without > > Enter the BlackBerry Developer Challenge > > http://p.sf.net/sfu/RIM-dev2dev > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Neeraja K. <nee...@in...> - 2010-08-12 06:32:52
|
I will be out of the office starting 08/12/2010 and will not return until 08/15/2010. Please call me in case of any urgent issues @ 9866662965 |
|
From: Christian M. <chr...@ta...> - 2010-08-12 05:13:46
|
George, could you try to activate the syslog and re-run the situation you explained in your first mail? Activating the syslog will result in the wrapper sending the output to the syslog as well. Just put this line into your conf file(s): wrapper.syslog.loglevel=WARN This should display at least all warnings (for instance the log file was not accessible). For diagnostics you can also try setting the loglevel to INFO which will send all outputs (except DEBUG) to the syslog. Cheers, Christian 2010/8/12 Christian Mueller <chr...@ta...>: > George, > > I'm sorry for the delay. > I unfortunately couldn't reproduce the problem you were seeing. > > However when the Cluster Management Tool as well as the Windows > Service say that the service is started then I assume that the wrapper > wasn't been able to write the log file has for some reason to the > location you expected. > In this case the Wrapper will log output to a file called wrapper.log > in the current working directory. The current working directory will > most likely be the directory containing the binary. However, in some > cases, when running as a Windows Service, the wrapper.log file may be > placed in your system directory (WinNT\System32). > > Are you having any storage dependencies for the service? > > Sincerely, > Christian > > > 2010/8/9 波波 . <gw...@ho...>: >> Dear all, >> >> I've used Java Serivce Wrapper 3.3.6 to wrap my application as a service, >> and I installed my service on 2 machines which are nodes of a Windows >> cluster.Then I configured my service as a resource in Windows cluster >> manager, so if one node fails, the cluster service can start my service on >> another node automatically. >> >> My service worked properly until the last system rebooting. After the system >> rebooted, I saw the resource of my service was online in cluster manager, >> and I also saw my service started in Windows' Services. But my service did >> not functioning - there were no output of it. I checked the log of my >> service (wrapper.log), it is strange that the log was not updated since the >> system shut down - neither the wrapper itself nor my application wrote any >> messages into the log file. >> >> To resume the production ASAP, I stopped my service and the cluster service >> detected this action and started my service automatically. After that, I >> could saw the output of my service. >> >> I'm confused that why my service did not work after system reboot - it was >> started by Windows cluster service, but it worked after restarting - it was >> also started by cluster service. And why was the log file not updated while >> the service was running after system reboot? Thanks for any clues. >> >> The configuration of my service is attached. >> >> Regards, >> George >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > |
|
From: Christian M. <chr...@ta...> - 2010-08-12 03:59:13
|
George, I'm sorry for the delay. I unfortunately couldn't reproduce the problem you were seeing. However when the Cluster Management Tool as well as the Windows Service say that the service is started then I assume that the wrapper wasn't been able to write the log file has for some reason to the location you expected. In this case the Wrapper will log output to a file called wrapper.log in the current working directory. The current working directory will most likely be the directory containing the binary. However, in some cases, when running as a Windows Service, the wrapper.log file may be placed in your system directory (WinNT\System32). Are you having any storage dependencies for the service? Sincerely, Christian 2010/8/9 波波 . <gw...@ho...>: > Dear all, > > I've used Java Serivce Wrapper 3.3.6 to wrap my application as a service, > and I installed my service on 2 machines which are nodes of a Windows > cluster.Then I configured my service as a resource in Windows cluster > manager, so if one node fails, the cluster service can start my service on > another node automatically. > > My service worked properly until the last system rebooting. After the system > rebooted, I saw the resource of my service was online in cluster manager, > and I also saw my service started in Windows' Services. But my service did > not functioning - there were no output of it. I checked the log of my > service (wrapper.log), it is strange that the log was not updated since the > system shut down - neither the wrapper itself nor my application wrote any > messages into the log file. > > To resume the production ASAP, I stopped my service and the cluster service > detected this action and started my service automatically. After that, I > could saw the output of my service. > > I'm confused that why my service did not work after system reboot - it was > started by Windows cluster service, but it worked after restarting - it was > also started by cluster service. And why was the log file not updated while > the service was running after system reboot? Thanks for any clues. > > The configuration of my service is attached. > > Regards, > George > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: Tasso A. <ta...@rb...> - 2010-08-10 13:56:28
|
Hi Leif, I was wondering if you would know anything about this? For some reason when running in Windows service the VISUAL VM can't see the process, but when running the wrapper in console mode. The application shows up as org.tanukisoftware.wrapper.WrapperSimpleAppand then you can profile live. ________________________________ From: Tasso Angelidis [mailto:ta...@rb...] Sent: Monday, August 09, 2010 9:25 AM To: wra...@li... Subject: [Wrapper-user] JAVA Visual VM (Profiler) doesn't detect appsrunning in service mode. If I run my application with the wrapper as Windows service Java Visual VM doesn't detect it. But if I run the application using console mode of the wrapper it gets detected. |
|
From: Gerry S. <smi...@gm...> - 2010-08-10 13:54:05
|
Ok great, I'd assumed it was using a working dir under jboss somewhere. Thanks all for the help. Gerry On Tue, Aug 10, 2010 at 3:00 AM, Christian Mueller < chr...@ta...> wrote: > Garry, > > What is the value for java.io.tmpdir when you run as service? > I guess that you are using the default value, which means that in case > when running the service under the Local User account the temp dir > will be %WINDOWS%\system32. However because of stricter access rules > introduced in Windows 7 the Local User can not write to there. > > In 3.5.0 we have added a workaround for this issue with the > wrapper.java.tmpdir.* properties: > http://wrapper.tanukisoftware.com/doc/english/prop-java-tmpdir-x.html > > In order to print out the temp dir in the log file please set: > wrapper.java.tmpdir.warn_silently=FALSE > > Hope this helps you. > > Cheers, > Christian > > > On Tue, Aug 10, 2010 at 2:31 AM, Gerry Smith <smi...@gm...> > wrote: > > I think the exception is being thrown when the static class > > org.apache.axis2.deployment.util.TempFileManager > > is trying to initialize and clean up old or create a new tempfile. > > Any ideas why this would only happen when running as a service, and how > to > > fix it ? > > I am running it using local system account, Win 7. > > > > Thanks, > > > > Gerry > > > > On Mon, Aug 9, 2010 at 9:00 AM, Gerry Smith <smi...@gm...> > wrote: > >> > >> Hi, > >> > >> We are testing using the wrapper with jboss 421. > >> We have an ear file which contains among other things an Axis2 1.5.1 web > >> app in a war file to provide soap services. > >> This works fine when we run the wrapper from the console, but when we > run > >> it as a windows service, Axis2 fails to run. > >> I've pasted the stack trace of the error, which occurs when jboss is > >> starting and also when you try to access an axis2 web service. > >> Anyone have any ideas ? > >> > >> Many thanks, > >> > >> Gerry > >> > >> 2010-08-09 08:40:25,049 ERROR > >> [org.apache.axis2.deployment.ModuleDeployer] The addressing-1.5.mar > module, > >> which is not valid, caused Could not initialize class > >> org.apache.axis2.deployment.util.TempFileManager > >> java.lang.NoClassDefFoundError: Could not initialize class > >> org.apache.axis2.deployment.util.TempFileManager > >> at > >> org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224) > >> at > >> org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165) > >> at > >> org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899) > >> at > >> > org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115) > >> at > >> > org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65) > >> at > >> > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) > >> at > >> > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659) > >> at > >> > org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251) > >> at > >> > org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68) > >> at > >> > org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63) > >> at > >> > org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147) > >> at > >> > org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229) > >> at > >> > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) > >> at > >> > org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525) > >> at > >> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443) > >> at > >> > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) > >> at > >> > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806) > >> at > >> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) > >> at > >> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > >> at > >> > org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) > >> at > >> > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > >> at > >> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > >> at > >> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > >> at > >> > org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) > >> at > >> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > >> at > >> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) > >> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) > >> at > >> > org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381) > >> at > >> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > >> at java.lang.Thread.run(Thread.java:619) > >> 2010-08-09 08:40:25,073 ERROR > [org.apache.axis2.deployment.ModuleDeployer] > >> The axis2-jaxws-mar-1.5.mar module, which is not valid, caused Could not > >> initialize class org.apache.axis2.deployment.util.TempFileManager > >> java.lang.NoClassDefFoundError: Could not initialize class > >> org.apache.axis2.deployment.util.TempFileManager > >> at > >> org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224) > >> at > >> org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165) > >> at > >> org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899) > >> at > >> > org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115) > >> at > >> > org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65) > >> at > >> > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) > >> at > >> > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659) > >> at > >> > org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251) > >> at > >> > org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68) > >> at > >> > org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63) > >> at > >> > org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147) > >> at > >> > org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229) > >> at > >> > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) > >> at > >> > org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525) > >> at > >> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443) > >> at > >> > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) > >> at > >> > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806) > >> at > >> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) > >> at > >> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > >> at > >> > org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) > >> at > >> > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > >> at > >> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > >> at > >> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > >> at > >> > org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) > >> at > >> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > >> at > >> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) > >> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) > >> at > >> > org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381) > >> at > >> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > >> at java.lang.Thread.run(Thread.java:619) > >> 2010-08-09 08:40:25,158 ERROR > [org.apache.axis2.deployment.ModuleDeployer] > >> The axis2-scripting-1.5.mar module, which is not valid, caused Could not > >> initialize class org.apache.axis2.deployment.util.TempFileManager > >> java.lang.NoClassDefFoundError: Could not initialize class > >> org.apache.axis2.deployment.util.TempFileManager > >> at > >> org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224) > >> at > >> org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165) > >> at > >> org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899) > >> at > >> > org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115) > >> at > >> > org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65) > >> at > >> > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) > >> at > >> > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659) > >> at > >> > org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251) > >> at > >> > org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68) > >> at > >> > org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63) > >> at > >> > org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147) > >> at > >> > org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229) > >> at > >> > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) > >> at > >> > org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525) > >> at > >> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443) > >> at > >> > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) > >> at > >> > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806) > >> at > >> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) > >> at > >> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > >> at > >> > org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) > >> at > >> > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > >> at > >> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > >> at > >> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > >> at > >> > org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) > >> at > >> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > >> at > >> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) > >> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) > >> at > >> > org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381) > >> at > >> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > >> at java.lang.Thread.run(Thread.java:619) > >> > > > > > > > ------------------------------------------------------------------------------ > > This SF.net email is sponsored by > > > > Make an app they can't live without > > Enter the BlackBerry Developer Challenge > > http://p.sf.net/sfu/RIM-dev2dev > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <lei...@ta...> - 2010-08-10 08:46:28
|
Mark, Thank you for the update on that issue. Please let me know we can help out with anything else. Cheers, Leif On Sat, Aug 7, 2010 at 2:37 AM, Ludwig, Mark <mar...@us...> wrote: > Back in April I reported some problems I was having with the wrapper > services shutting down that I had set up for some Eclipse infocenters. I > tried various things, but nothing worked. I knew the problem was related to > McAfee hogging too much CPU for too long, and to make a long story short, a > recent McAfee patch seems to have solved the problem. Services have been > running 10 days now without failure. So, for anyone with a similar issue who > also has McAfee 8.7.0, try getting the third patch (HotFix 3, and possibly > also Patch/HotFix 538488, which came out just before #3, but maybe that’s > bundled in #3 anyway). |
|
From: Leif M. <lei...@ta...> - 2010-08-10 08:42:01
|
Tasso, The Wrapper is a different process than the JVM, so it is possible to launch a 32-bit JVM from the 64-bit Wrapper, but the Wrapper's native library will fail to link with the JVM. The Wrapper is designed to be resilient so it will try to work as well as possible without the DLL, but several very important functions will not work correctly. These include the Wrapper's ability to protect the JVM against unwanted system signals like logout events, etc. Many new features also make use of the DLL. Cheers, Leif On Thu, Jul 15, 2010 at 10:15 PM, Tasso Angelidis <ta...@rb...> wrote: > If you are running 64 bit JAVA with 32 bit wrapper you get an error that > the wrapper.dll cannot be loaded. But does it really matter or affect > anything? It seems to work anyways... |
|
From: Christian M. <chr...@ta...> - 2010-08-10 08:13:48
|
Tasso, The temp directory of Visual VM and the java application run as service is different, so they can not find each other instantly. However there is a workaround to achieve what you are trying to do. Please set the environment variable TMP for the wrapper process in your conf file: set.TMP=C:\tmp and start the wrapper as service. Now start a console and set the TMP environment variable to the same value you specified in the conf file: set TMP=C:\tmp after that start jvisualvm C:\Program Files\...\jvisualvm.exe Visual VM should now be able to list the java process. Hope this works out for you. Cheers, Christian On Mon, Aug 9, 2010 at 10:24 PM, Tasso Angelidis <ta...@rb...> wrote: > If I run my application with the wrapper as Windows service Java Visual VM > doesn’t detect it. But if I run the application using console mode of the > wrapper it gets detected. > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: Christian M. <chr...@ta...> - 2010-08-10 07:24:42
|
Garry, What is the value for java.io.tmpdir when you run as service? I guess that you are using the default value, which means that in case when running the service under the Local User account the temp dir will be %WINDOWS%\system32. However because of stricter access rules introduced in Windows 7 the Local User can not write to there. In 3.5.0 we have added a workaround for this issue with the wrapper.java.tmpdir.* properties: http://wrapper.tanukisoftware.com/doc/english/prop-java-tmpdir-x.html In order to print out the temp dir in the log file please set: wrapper.java.tmpdir.warn_silently=FALSE Hope this helps you. Cheers, Christian On Tue, Aug 10, 2010 at 2:31 AM, Gerry Smith <smi...@gm...> wrote: > I think the exception is being thrown when the static class > org.apache.axis2.deployment.util.TempFileManager > is trying to initialize and clean up old or create a new tempfile. > Any ideas why this would only happen when running as a service, and how to > fix it ? > I am running it using local system account, Win 7. > > Thanks, > > Gerry > > On Mon, Aug 9, 2010 at 9:00 AM, Gerry Smith <smi...@gm...> wrote: >> >> Hi, >> >> We are testing using the wrapper with jboss 421. >> We have an ear file which contains among other things an Axis2 1.5.1 web >> app in a war file to provide soap services. >> This works fine when we run the wrapper from the console, but when we run >> it as a windows service, Axis2 fails to run. >> I've pasted the stack trace of the error, which occurs when jboss is >> starting and also when you try to access an axis2 web service. >> Anyone have any ideas ? >> >> Many thanks, >> >> Gerry >> >> 2010-08-09 08:40:25,049 ERROR >> [org.apache.axis2.deployment.ModuleDeployer] The addressing-1.5.mar module, >> which is not valid, caused Could not initialize class >> org.apache.axis2.deployment.util.TempFileManager >> java.lang.NoClassDefFoundError: Could not initialize class >> org.apache.axis2.deployment.util.TempFileManager >> at >> org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224) >> at >> org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165) >> at >> org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899) >> at >> org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115) >> at >> org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65) >> at >> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) >> at >> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659) >> at >> org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251) >> at >> org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68) >> at >> org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63) >> at >> org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147) >> at >> org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229) >> at >> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) >> at >> org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525) >> at >> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443) >> at >> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) >> at >> org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806) >> at >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) >> at >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) >> at >> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) >> at >> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) >> at >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) >> at >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) >> at >> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) >> at >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) >> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) >> at >> org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381) >> at >> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) >> at java.lang.Thread.run(Thread.java:619) >> 2010-08-09 08:40:25,073 ERROR [org.apache.axis2.deployment.ModuleDeployer] >> The axis2-jaxws-mar-1.5.mar module, which is not valid, caused Could not >> initialize class org.apache.axis2.deployment.util.TempFileManager >> java.lang.NoClassDefFoundError: Could not initialize class >> org.apache.axis2.deployment.util.TempFileManager >> at >> org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224) >> at >> org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165) >> at >> org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899) >> at >> org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115) >> at >> org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65) >> at >> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) >> at >> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659) >> at >> org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251) >> at >> org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68) >> at >> org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63) >> at >> org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147) >> at >> org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229) >> at >> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) >> at >> org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525) >> at >> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443) >> at >> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) >> at >> org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806) >> at >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) >> at >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) >> at >> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) >> at >> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) >> at >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) >> at >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) >> at >> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) >> at >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) >> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) >> at >> org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381) >> at >> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) >> at java.lang.Thread.run(Thread.java:619) >> 2010-08-09 08:40:25,158 ERROR [org.apache.axis2.deployment.ModuleDeployer] >> The axis2-scripting-1.5.mar module, which is not valid, caused Could not >> initialize class org.apache.axis2.deployment.util.TempFileManager >> java.lang.NoClassDefFoundError: Could not initialize class >> org.apache.axis2.deployment.util.TempFileManager >> at >> org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224) >> at >> org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165) >> at >> org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899) >> at >> org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115) >> at >> org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65) >> at >> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) >> at >> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659) >> at >> org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251) >> at >> org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68) >> at >> org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63) >> at >> org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147) >> at >> org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229) >> at >> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) >> at >> org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525) >> at >> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443) >> at >> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) >> at >> org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806) >> at >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) >> at >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) >> at >> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) >> at >> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) >> at >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) >> at >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) >> at >> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) >> at >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) >> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) >> at >> org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381) >> at >> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) >> at java.lang.Thread.run(Thread.java:619) >> > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: Hubert F. <Hub...@ab...> - 2010-08-10 07:17:21
|
Hi,
Is it windows? If yes, check if your system environment (used for
services) contains a setting for TEMP. In a console, running in user
environment, you probably have this set, but not under system
environment.
Additionally check your "java.io.tmpdir".
-Djava.io.tmpdir=C:\some\default\directory
Regards
hub
>>> Gerry Smith <smi...@gm...> 09.08.2010 15:00 >>>
Hi,
We are testing using the wrapper with jboss 421.
We have an ear file which contains among other things an Axis2 1.5.1
web app
in a war file to provide soap services.
This works fine when we run the wrapper from the console, but when we
run it
as a windows service, Axis2 fails to run.
I've pasted the stack trace of the error, which occurs when jboss is
starting and also when you try to access an axis2 web service.
Anyone have any ideas ?
Many thanks,
Gerry
2010-08-09 08:40:25,049 ERROR
[org.apache.axis2.deployment.ModuleDeployer]
The addressing-1.5.mar module, which is not valid, caused Could not
initialize class org.apache.axis2.deployment.util.TempFileManager
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.axis2.deployment.util.TempFileManager
at
org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224)
at
org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165)
at
org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115)
at
org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659)
at
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251)
at
org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68)
at
org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63)
at
org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at
org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
at
org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
2010-08-09 08:40:25,073 ERROR
[org.apache.axis2.deployment.ModuleDeployer]
The axis2-jaxws-mar-1.5.mar module, which is not valid, caused Could
not
initialize class org.apache.axis2.deployment.util.TempFileManager
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.axis2.deployment.util.TempFileManager
at
org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224)
at
org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165)
at
org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115)
at
org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659)
at
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251)
at
org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68)
at
org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63)
at
org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at
org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
at
org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
2010-08-09 08:40:25,158 ERROR
[org.apache.axis2.deployment.ModuleDeployer]
The axis2-scripting-1.5.mar module, which is not valid, caused Could
not
initialize class org.apache.axis2.deployment.util.TempFileManager
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.axis2.deployment.util.TempFileManager
at
org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224)
at
org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165)
at
org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115)
at
org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659)
at
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251)
at
org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68)
at
org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63)
at
org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at
org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
at
org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
|
|
From: Gerry S. <smi...@gm...> - 2010-08-09 17:31:37
|
I think the exception is being thrown when the static class org.apache.axis2.deployment.util.TempFileManager is trying to initialize and clean up old or create a new tempfile. Any ideas why this would only happen when running as a service, and how to fix it ? I am running it using local system account, Win 7. Thanks, Gerry On Mon, Aug 9, 2010 at 9:00 AM, Gerry Smith <smi...@gm...> wrote: > Hi, > > We are testing using the wrapper with jboss 421. > We have an ear file which contains among other things an Axis2 1.5.1 web > app in a war file to provide soap services. > This works fine when we run the wrapper from the console, but when we run > it as a windows service, Axis2 fails to run. > I've pasted the stack trace of the error, which occurs when jboss is > starting and also when you try to access an axis2 web service. > Anyone have any ideas ? > > Many thanks, > > Gerry > > 2010-08-09 08:40:25,049 ERROR [org.apache.axis2.deployment.ModuleDeployer] > The addressing-1.5.mar module, which is not valid, caused Could not > initialize class org.apache.axis2.deployment.util.TempFileManager > java.lang.NoClassDefFoundError: Could not initialize class > org.apache.axis2.deployment.util.TempFileManager > at > org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224) > at > org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165) > at > org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115) > at > org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) > at > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659) > at > org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251) > at > org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68) > at > org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63) > at > org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147) > at > org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) > at > org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525) > at > org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443) > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) > at > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at > org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) > at > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > at > org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) > at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) > at > org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381) > at > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > 2010-08-09 08:40:25,073 ERROR [org.apache.axis2.deployment.ModuleDeployer] > The axis2-jaxws-mar-1.5.mar module, which is not valid, caused Could not > initialize class org.apache.axis2.deployment.util.TempFileManager > java.lang.NoClassDefFoundError: Could not initialize class > org.apache.axis2.deployment.util.TempFileManager > at > org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224) > at > org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165) > at > org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115) > at > org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) > at > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659) > at > org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251) > at > org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68) > at > org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63) > at > org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147) > at > org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) > at > org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525) > at > org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443) > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) > at > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at > org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) > at > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > at > org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) > at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) > at > org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381) > at > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > 2010-08-09 08:40:25,158 ERROR [org.apache.axis2.deployment.ModuleDeployer] > The axis2-scripting-1.5.mar module, which is not valid, caused Could not > initialize class org.apache.axis2.deployment.util.TempFileManager > java.lang.NoClassDefFoundError: Could not initialize class > org.apache.axis2.deployment.util.TempFileManager > at > org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224) > at > org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165) > at > org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115) > at > org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) > at > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659) > at > org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251) > at > org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68) > at > org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63) > at > org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147) > at > org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) > at > org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525) > at > org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443) > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) > at > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at > org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) > at > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > at > org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) > at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) > at > org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381) > at > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > > |
|
From: Tasso A. <ta...@rb...> - 2010-08-09 13:25:06
|
If I run my application with the wrapper as Windows service Java Visual VM doesn't detect it. But if I run the application using console mode of the wrapper it gets detected. |
|
From: Gerry S. <smi...@gm...> - 2010-08-09 13:01:00
|
Hi,
We are testing using the wrapper with jboss 421.
We have an ear file which contains among other things an Axis2 1.5.1 web app
in a war file to provide soap services.
This works fine when we run the wrapper from the console, but when we run it
as a windows service, Axis2 fails to run.
I've pasted the stack trace of the error, which occurs when jboss is
starting and also when you try to access an axis2 web service.
Anyone have any ideas ?
Many thanks,
Gerry
2010-08-09 08:40:25,049 ERROR [org.apache.axis2.deployment.ModuleDeployer]
The addressing-1.5.mar module, which is not valid, caused Could not
initialize class org.apache.axis2.deployment.util.TempFileManager
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.axis2.deployment.util.TempFileManager
at org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224)
at
org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165)
at
org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115)
at
org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659)
at
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251)
at
org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68)
at
org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63)
at
org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
at
org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
2010-08-09 08:40:25,073 ERROR [org.apache.axis2.deployment.ModuleDeployer]
The axis2-jaxws-mar-1.5.mar module, which is not valid, caused Could not
initialize class org.apache.axis2.deployment.util.TempFileManager
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.axis2.deployment.util.TempFileManager
at org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224)
at
org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165)
at
org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115)
at
org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659)
at
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251)
at
org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68)
at
org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63)
at
org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
at
org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
2010-08-09 08:40:25,158 ERROR [org.apache.axis2.deployment.ModuleDeployer]
The axis2-scripting-1.5.mar module, which is not valid, caused Could not
initialize class org.apache.axis2.deployment.util.TempFileManager
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.axis2.deployment.util.TempFileManager
at org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:224)
at
org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:165)
at
org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:899)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115)
at
org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:65)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659)
at
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:251)
at
org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:68)
at
org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:63)
at
org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:147)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:229)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
at
org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
|
|
From: Ludwig, M. <mar...@us...> - 2010-08-06 17:52:33
|
Back in April I reported some problems I was having with the wrapper services shutting down that I had set up for some Eclipse infocenters. I tried various things, but nothing worked. I knew the problem was related to McAfee hogging too much CPU for too long, and to make a long story short, a recent McAfee patch seems to have solved the problem. Services have been running 10 days now without failure. So, for anyone with a similar issue who also has McAfee 8.7.0, try getting the third patch (HotFix 3, and possibly also Patch/HotFix 538488, which came out just before #3, but maybe that's bundled in #3 anyway). |
165 messages has been excluded from this view by a project administrator.
