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: Gabriel J. <goj...@ya...> - 2007-11-23 14:53:39
|
I have developed an application with Java 1.4.2_08. I installed this application as a service and
it displays a control panel as soon as it is executed. I run the application fine on Windows XP,
but when i tryed to run it on Windows Vista, when the service is executed, i got a new window from
Vista, called "Interactive Services dialog detection".
I read that there is some bug on JRE 1.4.2, and 1.5 that crashes the JVM when trying to initiate a
Windows' Vista session 0 desktop, but i don't see the JVM crashed on my application.
Did anyone had this same problem with Windows Vista, do you know how can it be fixed?
Thanks,
G.J.
Los referentes más importantes en compra/ venta de autos se juntaron:
Demotores y Yahoo!
Ahora comprar o vender tu auto es más fácil. Vistá ar.autos.yahoo.com/
|
|
From: Tom S. <Tom...@Me...> - 2007-11-21 18:06:58
|
The previous version was 3.2.3. We are now using version 3.3.0-b Tom -----Original Message----- From: wra...@li... [mailto:wrapper-user-bounc= es...@li...] On Behalf Of Leif Mortenson Sent: Tuesday, November 20, 2007 7:26 PM To: wra...@li... Subject: Re: [Wrapper-user] ^^C not working sometimes Tom, I agree, that something is not working correctly. You said with the previous version "2.3" it was working. Do you mean "3.2.3"? What version are you using now? Cheers, Leif Tom Saulpaugh wrote: > Leif, > > Here is the log during the double ctl-c. > > It takes 6 seconds to shutdown the JVM starting at > > DEBUG | wrapper | main | 2007/11/20 13:58:36 | Signal trapped. Deta= ils: > DEBUG | wrapper | main | 2007/11/20 13:58:36 | signal number=3D2 (= SIGINT), source=3D"the kernel" > STATUS | wrapper | main | 2007/11/20 13:58:36 | INT trapped. Shuttin= g down. > DEBUG | wrapper | main | 2007/11/20 13:58:36 | wrapperStopProcess(0)= called. > DEBUG | wrapper | main | 2007/11/20 13:58:36 | Sending stop signal t= o JVM > DEBUG | wrapperp | main | 2007/11/20 13:58:36 | send a packet STOP : = NULL > DEBUG | wrapper | main | 2007/11/20 13:58:36 | Signal trapped. Deta= ils: > DEBUG | wrapper | main | 2007/11/20 13:58:36 | signal number=3D2 (= SIGINT), source=3D"the kernel" > STATUS | wrapper | main | 2007/11/20 13:58:36 | INT trapped. Forcing= immediate shutdown. > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug:= Received a packet STOP : > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug:= Thread, Wrapper-Connection, handling the shutdown process. > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug:= calling listener.stop() > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug:= Waiting for WrapperListener.stop runner thread to complete. > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug:= Processing control event(WRAPPER_CTRL_C_EVENT) > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug:= WrapperManager.stop(0) called by thread: Wrapper-Control-Event-Monitor > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug:= Thread, Wrapper-Control-Event-Monitor, waiting for the JVM to exit. > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug:= WrapperListener.stop runner thread started. > > > < OUR JVM SHUTDOWN PROCESSING HERE> > . > . > . > < OUR JVM SHUTDOWN PROCESSING HERE> > > > and ending at: > > INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug:= WrapperListener.stop runner thread stopped. > INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug:= returned from listener.stop() -> 0 > INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug:= shutdownJVM(0) Thread:Wrapper-Connection > INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug:= Send a packet STOPPED : 0 > INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug:= Closing socket. > INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug:= calling System.exit(0) > DEBUG | wrapper | main | 2007/11/20 13:58:42 | JVM exited normally. > DEBUG | wrapper | main | 2007/11/20 13:58:42 | Signal trapped. Deta= ils: > DEBUG | wrapper | main | 2007/11/20 13:58:42 | signal number=3D17 = (SIGCHLD), source=3D"unknown" > DEBUG | wrapper | main | 2007/11/20 13:58:42 | Received SIGCHLD, che= cking JVM process status. > DEBUG | wrapper | main | 2007/11/20 13:58:42 | JVM process exited wi= th a code of 0, leaving the wrapper exit code set to 0. > STATUS | wrapper | main | 2007/11/20 13:58:42 | <-- Wrapper Stopped > > It seems like that even when the wrapper says it is forcing an immediate = shutdown, it is waiting for the JVM to finish and during that time our code= is doing its shutdown processing, which takes 6 seconds in this case. > > I'm confused regarding the notion of "immediate". What is an immediate s= hutdown? How is it different than kill -9 JVM_PID? > > With the previous wrapper (2.3) this never happened. Did anything change= that would affect immediate shutdown? > > Thanks for your help, > > Tom > > > > -----Original Message----- > From: wra...@li... [mailto:wrapper-user-bou= nc...@li...] On Behalf Of Leif Mortenson > Sent: Monday, November 19, 2007 6:28 PM > To: wra...@li... > Subject: Re: [Wrapper-user] ^^C not working sometimes > > Tom, > There used to be a bug where the Wrapper would sometimes mistake > a single CTRL-C event as two and kill the JVM. But I have never seen > what you are seeing. > > Could you try to reproduce this with wrapper.debug=3Dtrue enabled? > > How long apart are the two CTRL-C events? Are you seeing > messages in the log for both of them? > > Cheers, > Leif > > Tom Saulpaugh wrote: > >> Has anyone noticed that double cntrl-c doesn't always kill the JVM? >> >> I have seen this on linux and windows. >> >> Is there a fix for this? >> >> It seems to happen when the JVM is under heavy load. >> >> >> >> Thanks, >> >> >> >> Tom >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------= - >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leif M. <le...@ta...> - 2007-11-21 03:26:23
|
Tom, I agree, that something is not working correctly. You said with the previous version "2.3" it was working. Do you mean "3.2.3"? What version are you using now? Cheers, Leif Tom Saulpaugh wrote: > Leif, > > Here is the log during the double ctl-c. > > It takes 6 seconds to shutdown the JVM starting at > > DEBUG | wrapper | main | 2007/11/20 13:58:36 | Signal trapped. Details: > DEBUG | wrapper | main | 2007/11/20 13:58:36 | signal number=2 (SIGINT), source="the kernel" > STATUS | wrapper | main | 2007/11/20 13:58:36 | INT trapped. Shutting down. > DEBUG | wrapper | main | 2007/11/20 13:58:36 | wrapperStopProcess(0) called. > DEBUG | wrapper | main | 2007/11/20 13:58:36 | Sending stop signal to JVM > DEBUG | wrapperp | main | 2007/11/20 13:58:36 | send a packet STOP : NULL > DEBUG | wrapper | main | 2007/11/20 13:58:36 | Signal trapped. Details: > DEBUG | wrapper | main | 2007/11/20 13:58:36 | signal number=2 (SIGINT), source="the kernel" > STATUS | wrapper | main | 2007/11/20 13:58:36 | INT trapped. Forcing immediate shutdown. > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: Received a packet STOP : > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: Thread, Wrapper-Connection, handling the shutdown process. > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: calling listener.stop() > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: Waiting for WrapperListener.stop runner thread to complete. > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: Processing control event(WRAPPER_CTRL_C_EVENT) > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: WrapperManager.stop(0) called by thread: Wrapper-Control-Event-Monitor > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: Thread, Wrapper-Control-Event-Monitor, waiting for the JVM to exit. > INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: WrapperListener.stop runner thread started. > > > < OUR JVM SHUTDOWN PROCESSING HERE> > . > . > . > < OUR JVM SHUTDOWN PROCESSING HERE> > > > and ending at: > > INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug: WrapperListener.stop runner thread stopped. > INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug: returned from listener.stop() -> 0 > INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug: shutdownJVM(0) Thread:Wrapper-Connection > INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug: Send a packet STOPPED : 0 > INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug: Closing socket. > INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug: calling System.exit(0) > DEBUG | wrapper | main | 2007/11/20 13:58:42 | JVM exited normally. > DEBUG | wrapper | main | 2007/11/20 13:58:42 | Signal trapped. Details: > DEBUG | wrapper | main | 2007/11/20 13:58:42 | signal number=17 (SIGCHLD), source="unknown" > DEBUG | wrapper | main | 2007/11/20 13:58:42 | Received SIGCHLD, checking JVM process status. > DEBUG | wrapper | main | 2007/11/20 13:58:42 | JVM process exited with a code of 0, leaving the wrapper exit code set to 0. > STATUS | wrapper | main | 2007/11/20 13:58:42 | <-- Wrapper Stopped > > It seems like that even when the wrapper says it is forcing an immediate shutdown, it is waiting for the JVM to finish and during that time our code is doing its shutdown processing, which takes 6 seconds in this case. > > I'm confused regarding the notion of "immediate". What is an immediate shutdown? How is it different than kill -9 JVM_PID? > > With the previous wrapper (2.3) this never happened. Did anything change that would affect immediate shutdown? > > Thanks for your help, > > Tom > > > > -----Original Message----- > From: wra...@li... [mailto:wra...@li...] On Behalf Of Leif Mortenson > Sent: Monday, November 19, 2007 6:28 PM > To: wra...@li... > Subject: Re: [Wrapper-user] ^^C not working sometimes > > Tom, > There used to be a bug where the Wrapper would sometimes mistake > a single CTRL-C event as two and kill the JVM. But I have never seen > what you are seeing. > > Could you try to reproduce this with wrapper.debug=true enabled? > > How long apart are the two CTRL-C events? Are you seeing > messages in the log for both of them? > > Cheers, > Leif > > Tom Saulpaugh wrote: > >> Has anyone noticed that double cntrl-c doesn't always kill the JVM? >> >> I have seen this on linux and windows. >> >> Is there a fix for this? >> >> It seems to happen when the JVM is under heavy load. >> >> >> >> Thanks, >> >> >> >> Tom >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: Tom S. <Tom...@Me...> - 2007-11-21 00:47:24
|
Leif, Here is the log during the double ctl-c. It takes 6 seconds to shutdown the JVM starting at DEBUG | wrapper | main | 2007/11/20 13:58:36 | Signal trapped. Detail= s: DEBUG | wrapper | main | 2007/11/20 13:58:36 | signal number=3D2 (SI= GINT), source=3D"the kernel" STATUS | wrapper | main | 2007/11/20 13:58:36 | INT trapped. Shutting = down. DEBUG | wrapper | main | 2007/11/20 13:58:36 | wrapperStopProcess(0) c= alled. DEBUG | wrapper | main | 2007/11/20 13:58:36 | Sending stop signal to = JVM DEBUG | wrapperp | main | 2007/11/20 13:58:36 | send a packet STOP : NU= LL DEBUG | wrapper | main | 2007/11/20 13:58:36 | Signal trapped. Detail= s: DEBUG | wrapper | main | 2007/11/20 13:58:36 | signal number=3D2 (SI= GINT), source=3D"the kernel" STATUS | wrapper | main | 2007/11/20 13:58:36 | INT trapped. Forcing i= mmediate shutdown. INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: R= eceived a packet STOP : INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: T= hread, Wrapper-Connection, handling the shutdown process. INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: c= alling listener.stop() INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: W= aiting for WrapperListener.stop runner thread to complete. INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: P= rocessing control event(WRAPPER_CTRL_C_EVENT) INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: W= rapperManager.stop(0) called by thread: Wrapper-Control-Event-Monitor INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: T= hread, Wrapper-Control-Event-Monitor, waiting for the JVM to exit. INFO | jvm 1 | main | 2007/11/20 13:58:36 | WrapperManager Debug: W= rapperListener.stop runner thread started. < OUR JVM SHUTDOWN PROCESSING HERE> . . . < OUR JVM SHUTDOWN PROCESSING HERE> and ending at: INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug: W= rapperListener.stop runner thread stopped. INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug: r= eturned from listener.stop() -> 0 INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug: s= hutdownJVM(0) Thread:Wrapper-Connection INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug: S= end a packet STOPPED : 0 INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug: C= losing socket. INFO | jvm 1 | main | 2007/11/20 13:58:42 | WrapperManager Debug: c= alling System.exit(0) DEBUG | wrapper | main | 2007/11/20 13:58:42 | JVM exited normally. DEBUG | wrapper | main | 2007/11/20 13:58:42 | Signal trapped. Detail= s: DEBUG | wrapper | main | 2007/11/20 13:58:42 | signal number=3D17 (S= IGCHLD), source=3D"unknown" DEBUG | wrapper | main | 2007/11/20 13:58:42 | Received SIGCHLD, check= ing JVM process status. DEBUG | wrapper | main | 2007/11/20 13:58:42 | JVM process exited with= a code of 0, leaving the wrapper exit code set to 0. STATUS | wrapper | main | 2007/11/20 13:58:42 | <-- Wrapper Stopped It seems like that even when the wrapper says it is forcing an immediate sh= utdown, it is waiting for the JVM to finish and during that time our code i= s doing its shutdown processing, which takes 6 seconds in this case. I'm confused regarding the notion of "immediate". What is an immediate shu= tdown? How is it different than kill -9 JVM_PID? With the previous wrapper (2.3) this never happened. Did anything change t= hat would affect immediate shutdown? Thanks for your help, Tom -----Original Message----- From: wra...@li... [mailto:wrapper-user-bounc= es...@li...] On Behalf Of Leif Mortenson Sent: Monday, November 19, 2007 6:28 PM To: wra...@li... Subject: Re: [Wrapper-user] ^^C not working sometimes Tom, There used to be a bug where the Wrapper would sometimes mistake a single CTRL-C event as two and kill the JVM. But I have never seen what you are seeing. Could you try to reproduce this with wrapper.debug=3Dtrue enabled? How long apart are the two CTRL-C events? Are you seeing messages in the log for both of them? Cheers, Leif Tom Saulpaugh wrote: > > Has anyone noticed that double cntrl-c doesn't always kill the JVM? > > I have seen this on linux and windows. > > Is there a fix for this? > > It seems to happen when the JVM is under heavy load. > > > > Thanks, > > > > Tom > > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Sandeep PS <san...@ya...> - 2007-11-20 11:17:23
|
Leif, I was able to compile it myself ... it is working fine :) Sandeep Sandeep PS wrote: > > Leif, > > Thanks for your reply. > > Is it possible for u to send me the 64-bit binaries that is working on ur > development machine ?? > > Regards, > Sandeep > > > > Leif Mortenson-2 wrote: >> >> Sandeep, >> Sorry for the delays. I am working to get version 3.3.0 which will >> include Win64, completed for a release by the end of the year. >> It is currently working on my development system. >> >> Cheers, >> Leif >> >> Sandeep PS wrote: >>> Hi, >>> >>> Does anyone have the 64 bit wrapper.exe and wrapper.dll that works on >>> win >>> server 2003 ?? >>> I am struggling to find one. It would be of gr8 help if you could >>> provide >>> it. >>> >>> Thanks, >>> Sandeep >>> >>> >>> >>> Tom Saulpaugh wrote: >>> >>>> I'm following instructions from Mattias on how to build 64-bit wrapper >>>> on >>>> Win64. >>>> >>>> >>>> 1) Checkout from SVN truck. >>>> >>>> 2) Copy Makefile-windows-x86-32.nmake to Makefile-windows-x86-64.nmake >>>> >>>> (located in ..\src\c\) >>>> >>>> 3) Edited Makefile-windows-x86-64.nmake >>>> >>>> 3.1) Remove -Zp4 from compile options (seams to cause 'Stdout pipe >>>> >>>> creation failed' ?!) >>>> >>>> 3.2) Changed /MACHINE:X86 to /MACHINE:X64 >>>> >>>> 3.3) EXE_OUTDIR = $(PROJ)32_VC8__Win32_Release to EXE_OUTDIR = >>>> >>>> $(PROJ)32_VC8__Win64_Release >>>> >>>> 3.4) DLL_OUTDIR = $(PROJ)JNI32_VC8__Win32_Release to DLL_OUTDIR = >>>> >>>> $(PROJ)JNI32_VC8__Win64_Release >>>> >>>> >>>> >>>> 4) Open a Visual Studio 2005 x64 command prompt (and I use java >>>> 1.6.0_02 >>>> >>>> 64-bit Server) >>>> >>>> 4.1) ant -Dbits=64 >>>> >>>> >>>> >>>> Regards, >>>> /Mattias >>>> >>>> This worked for me the first time I built, but now I get this error >>>> from >>>> the linker: >>>> >>>> [exec] link /NOLOGO /MANIFEST /DEBUG /MACHINE:X64 >>>> /ERRORREPORT:PROMPT D >>>> elayImp.lib /INCREMENTAL:NO /SUBSYSTEM:CONSOLE >>>> /MANIFESTFILE:"wrapper32_VC8__Win >>>> 64_Release\wrapper.exe.intermediate.manifest" >>>> /PDB:"wrapper32_VC8__Win64_Release >>>> \wrapper.pdb" /OPT:REF /OPT:ICF /OPT:WIN98 /LTCG >>>> wrapper32_VC8__Win64_Release\lo >>>> gger.obj wrapper32_VC8__Win64_Release\property.obj >>>> wrapper32_VC8__Win64_Release\ >>>> wrapper.obj wrapper32_VC8__Win64_Release\wrapper_win.obj >>>> wrapper32_VC8__Win64_Re >>>> lease\wrappereventloop.obj wrapper32_VC8__Win64_Release\wrapperinfo.obj >>>> wsock32. >>>> lib shlwapi.lib advapi32.lib user32.lib >>>> wrapper32_VC8__Win64_Release\wrapper.res >>>> /OUT:"..\..\bin\wrapper.exe" >>>> [exec] wrapper32_VC8__Win64_Release\logger.obj : fatal error >>>> LNK1112: >>>> modul >>>> e machine type 'X86' conflicts with target machine type 'x64' >>>> >>>> I think something in my Visual Studio 2005 environment has changed. >>>> >>>> Has anyone seen this? >>>> >>>> Thanks, >>>> >>>> Tom >>>> >>>> >>>> -- >>>> Notice: This email and any files transmitted with it are confidential >>>> and >>>> intended solely for the individual or entity to which they are >>>> addressed. >>>> If you have received this email in error please notify the sender and >>>> destroy any copies of this email and its attachments. You are hereby >>>> notified that any unauthorized review, use, disclosure, dissemination, >>>> distribution, or copying of this communication, or any of its contents, >>>> is >>>> strictly prohibited. Please note that any views or opinions presented >>>> in >>>> this email are solely those of the author and do not necessarily >>>> represent >>>> those of the company. The recipient should check this email and any >>>> attachments for the presence of viruses. The company accepts no >>>> liability >>>> for any damage caused by any virus transmitted by this email. >>>> >>>> ------------------------------------------------------------------------- >>>> This SF.net email is sponsored by: Microsoft >>>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>> _______________________________________________ >>>> Wrapper-user mailing list >>>> Wra...@li... >>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user >>>> >>>> >>>> >>> >>> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > > -- View this message in context: http://www.nabble.com/64-bit-Build-Error-on-Win64-tf4529456.html#a13855053 Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Sandeep PS <san...@ya...> - 2007-11-20 08:38:05
|
Leif, Thanks for your reply. Is it possible for u to send me the 64-bit binaries that is working on ur development machine ?? Regards, Sandeep Leif Mortenson-2 wrote: > > Sandeep, > Sorry for the delays. I am working to get version 3.3.0 which will > include Win64, completed for a release by the end of the year. > It is currently working on my development system. > > Cheers, > Leif > > Sandeep PS wrote: >> Hi, >> >> Does anyone have the 64 bit wrapper.exe and wrapper.dll that works on win >> server 2003 ?? >> I am struggling to find one. It would be of gr8 help if you could provide >> it. >> >> Thanks, >> Sandeep >> >> >> >> Tom Saulpaugh wrote: >> >>> I'm following instructions from Mattias on how to build 64-bit wrapper >>> on >>> Win64. >>> >>> >>> 1) Checkout from SVN truck. >>> >>> 2) Copy Makefile-windows-x86-32.nmake to Makefile-windows-x86-64.nmake >>> >>> (located in ..\src\c\) >>> >>> 3) Edited Makefile-windows-x86-64.nmake >>> >>> 3.1) Remove -Zp4 from compile options (seams to cause 'Stdout pipe >>> >>> creation failed' ?!) >>> >>> 3.2) Changed /MACHINE:X86 to /MACHINE:X64 >>> >>> 3.3) EXE_OUTDIR = $(PROJ)32_VC8__Win32_Release to EXE_OUTDIR = >>> >>> $(PROJ)32_VC8__Win64_Release >>> >>> 3.4) DLL_OUTDIR = $(PROJ)JNI32_VC8__Win32_Release to DLL_OUTDIR = >>> >>> $(PROJ)JNI32_VC8__Win64_Release >>> >>> >>> >>> 4) Open a Visual Studio 2005 x64 command prompt (and I use java 1.6.0_02 >>> >>> 64-bit Server) >>> >>> 4.1) ant -Dbits=64 >>> >>> >>> >>> Regards, >>> /Mattias >>> >>> This worked for me the first time I built, but now I get this error from >>> the linker: >>> >>> [exec] link /NOLOGO /MANIFEST /DEBUG /MACHINE:X64 >>> /ERRORREPORT:PROMPT D >>> elayImp.lib /INCREMENTAL:NO /SUBSYSTEM:CONSOLE >>> /MANIFESTFILE:"wrapper32_VC8__Win >>> 64_Release\wrapper.exe.intermediate.manifest" >>> /PDB:"wrapper32_VC8__Win64_Release >>> \wrapper.pdb" /OPT:REF /OPT:ICF /OPT:WIN98 /LTCG >>> wrapper32_VC8__Win64_Release\lo >>> gger.obj wrapper32_VC8__Win64_Release\property.obj >>> wrapper32_VC8__Win64_Release\ >>> wrapper.obj wrapper32_VC8__Win64_Release\wrapper_win.obj >>> wrapper32_VC8__Win64_Re >>> lease\wrappereventloop.obj wrapper32_VC8__Win64_Release\wrapperinfo.obj >>> wsock32. >>> lib shlwapi.lib advapi32.lib user32.lib >>> wrapper32_VC8__Win64_Release\wrapper.res >>> /OUT:"..\..\bin\wrapper.exe" >>> [exec] wrapper32_VC8__Win64_Release\logger.obj : fatal error >>> LNK1112: >>> modul >>> e machine type 'X86' conflicts with target machine type 'x64' >>> >>> I think something in my Visual Studio 2005 environment has changed. >>> >>> Has anyone seen this? >>> >>> Thanks, >>> >>> Tom >>> >>> >>> -- >>> Notice: This email and any files transmitted with it are confidential >>> and >>> intended solely for the individual or entity to which they are >>> addressed. >>> If you have received this email in error please notify the sender and >>> destroy any copies of this email and its attachments. You are hereby >>> notified that any unauthorized review, use, disclosure, dissemination, >>> distribution, or copying of this communication, or any of its contents, >>> is >>> strictly prohibited. Please note that any views or opinions presented >>> in >>> this email are solely those of the author and do not necessarily >>> represent >>> those of the company. The recipient should check this email and any >>> attachments for the presence of viruses. The company accepts no >>> liability >>> for any damage caused by any virus transmitted by this email. >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> Wrapper-user mailing list >>> Wra...@li... >>> https://lists.sourceforge.net/lists/listinfo/wrapper-user >>> >>> >>> >> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > -- View this message in context: http://www.nabble.com/64-bit-Build-Error-on-Win64-tf4529456.html#a13852782 Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Leif M. <le...@ta...> - 2007-11-20 08:26:49
|
Sandeep, Sorry for the delays. I am working to get version 3.3.0 which will include Win64, completed for a release by the end of the year. It is currently working on my development system. Cheers, Leif Sandeep PS wrote: > Hi, > > Does anyone have the 64 bit wrapper.exe and wrapper.dll that works on win > server 2003 ?? > I am struggling to find one. It would be of gr8 help if you could provide > it. > > Thanks, > Sandeep > > > > Tom Saulpaugh wrote: > >> I'm following instructions from Mattias on how to build 64-bit wrapper on >> Win64. >> >> >> 1) Checkout from SVN truck. >> >> 2) Copy Makefile-windows-x86-32.nmake to Makefile-windows-x86-64.nmake >> >> (located in ..\src\c\) >> >> 3) Edited Makefile-windows-x86-64.nmake >> >> 3.1) Remove -Zp4 from compile options (seams to cause 'Stdout pipe >> >> creation failed' ?!) >> >> 3.2) Changed /MACHINE:X86 to /MACHINE:X64 >> >> 3.3) EXE_OUTDIR = $(PROJ)32_VC8__Win32_Release to EXE_OUTDIR = >> >> $(PROJ)32_VC8__Win64_Release >> >> 3.4) DLL_OUTDIR = $(PROJ)JNI32_VC8__Win32_Release to DLL_OUTDIR = >> >> $(PROJ)JNI32_VC8__Win64_Release >> >> >> >> 4) Open a Visual Studio 2005 x64 command prompt (and I use java 1.6.0_02 >> >> 64-bit Server) >> >> 4.1) ant -Dbits=64 >> >> >> >> Regards, >> /Mattias >> >> This worked for me the first time I built, but now I get this error from >> the linker: >> >> [exec] link /NOLOGO /MANIFEST /DEBUG /MACHINE:X64 >> /ERRORREPORT:PROMPT D >> elayImp.lib /INCREMENTAL:NO /SUBSYSTEM:CONSOLE >> /MANIFESTFILE:"wrapper32_VC8__Win >> 64_Release\wrapper.exe.intermediate.manifest" >> /PDB:"wrapper32_VC8__Win64_Release >> \wrapper.pdb" /OPT:REF /OPT:ICF /OPT:WIN98 /LTCG >> wrapper32_VC8__Win64_Release\lo >> gger.obj wrapper32_VC8__Win64_Release\property.obj >> wrapper32_VC8__Win64_Release\ >> wrapper.obj wrapper32_VC8__Win64_Release\wrapper_win.obj >> wrapper32_VC8__Win64_Re >> lease\wrappereventloop.obj wrapper32_VC8__Win64_Release\wrapperinfo.obj >> wsock32. >> lib shlwapi.lib advapi32.lib user32.lib >> wrapper32_VC8__Win64_Release\wrapper.res >> /OUT:"..\..\bin\wrapper.exe" >> [exec] wrapper32_VC8__Win64_Release\logger.obj : fatal error LNK1112: >> modul >> e machine type 'X86' conflicts with target machine type 'x64' >> >> I think something in my Visual Studio 2005 environment has changed. >> >> Has anyone seen this? >> >> Thanks, >> >> Tom >> >> >> -- >> Notice: This email and any files transmitted with it are confidential and >> intended solely for the individual or entity to which they are addressed. >> If you have received this email in error please notify the sender and >> destroy any copies of this email and its attachments. You are hereby >> notified that any unauthorized review, use, disclosure, dissemination, >> distribution, or copying of this communication, or any of its contents, is >> strictly prohibited. Please note that any views or opinions presented in >> this email are solely those of the author and do not necessarily represent >> those of the company. The recipient should check this email and any >> attachments for the presence of viruses. The company accepts no liability >> for any damage caused by any virus transmitted by this email. >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> >> > > |
|
From: Sandeep PS <san...@ya...> - 2007-11-20 06:22:31
|
Hi, Does anyone have the 64 bit wrapper.exe and wrapper.dll that works on win server 2003 ?? I am struggling to find one. It would be of gr8 help if you could provide it. Thanks, Sandeep Tom Saulpaugh wrote: > > I'm following instructions from Mattias on how to build 64-bit wrapper on > Win64. > > > 1) Checkout from SVN truck. > > 2) Copy Makefile-windows-x86-32.nmake to Makefile-windows-x86-64.nmake > > (located in ..\src\c\) > > 3) Edited Makefile-windows-x86-64.nmake > > 3.1) Remove -Zp4 from compile options (seams to cause 'Stdout pipe > > creation failed' ?!) > > 3.2) Changed /MACHINE:X86 to /MACHINE:X64 > > 3.3) EXE_OUTDIR = $(PROJ)32_VC8__Win32_Release to EXE_OUTDIR = > > $(PROJ)32_VC8__Win64_Release > > 3.4) DLL_OUTDIR = $(PROJ)JNI32_VC8__Win32_Release to DLL_OUTDIR = > > $(PROJ)JNI32_VC8__Win64_Release > > > > 4) Open a Visual Studio 2005 x64 command prompt (and I use java 1.6.0_02 > > 64-bit Server) > > 4.1) ant -Dbits=64 > > > > Regards, > /Mattias > > This worked for me the first time I built, but now I get this error from > the linker: > > [exec] link /NOLOGO /MANIFEST /DEBUG /MACHINE:X64 > /ERRORREPORT:PROMPT D > elayImp.lib /INCREMENTAL:NO /SUBSYSTEM:CONSOLE > /MANIFESTFILE:"wrapper32_VC8__Win > 64_Release\wrapper.exe.intermediate.manifest" > /PDB:"wrapper32_VC8__Win64_Release > \wrapper.pdb" /OPT:REF /OPT:ICF /OPT:WIN98 /LTCG > wrapper32_VC8__Win64_Release\lo > gger.obj wrapper32_VC8__Win64_Release\property.obj > wrapper32_VC8__Win64_Release\ > wrapper.obj wrapper32_VC8__Win64_Release\wrapper_win.obj > wrapper32_VC8__Win64_Re > lease\wrappereventloop.obj wrapper32_VC8__Win64_Release\wrapperinfo.obj > wsock32. > lib shlwapi.lib advapi32.lib user32.lib > wrapper32_VC8__Win64_Release\wrapper.res > /OUT:"..\..\bin\wrapper.exe" > [exec] wrapper32_VC8__Win64_Release\logger.obj : fatal error LNK1112: > modul > e machine type 'X86' conflicts with target machine type 'x64' > > I think something in my Visual Studio 2005 environment has changed. > > Has anyone seen this? > > Thanks, > > Tom > > > -- > Notice: This email and any files transmitted with it are confidential and > intended solely for the individual or entity to which they are addressed. > If you have received this email in error please notify the sender and > destroy any copies of this email and its attachments. You are hereby > notified that any unauthorized review, use, disclosure, dissemination, > distribution, or copying of this communication, or any of its contents, is > strictly prohibited. Please note that any views or opinions presented in > this email are solely those of the author and do not necessarily represent > those of the company. The recipient should check this email and any > attachments for the presence of viruses. The company accepts no liability > for any damage caused by any virus transmitted by this email. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > -- View this message in context: http://www.nabble.com/64-bit-Build-Error-on-Win64-tf4529456.html#a13851596 Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Leif M. <le...@ta...> - 2007-11-20 02:28:14
|
Tom, There used to be a bug where the Wrapper would sometimes mistake a single CTRL-C event as two and kill the JVM. But I have never seen what you are seeing. Could you try to reproduce this with wrapper.debug=true enabled? How long apart are the two CTRL-C events? Are you seeing messages in the log for both of them? Cheers, Leif Tom Saulpaugh wrote: > > Has anyone noticed that double cntrl-c doesn't always kill the JVM? > > I have seen this on linux and windows. > > Is there a fix for this? > > It seems to happen when the JVM is under heavy load. > > > > Thanks, > > > > Tom > > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Tom S. <Tom...@Me...> - 2007-11-19 19:37:18
|
Has anyone noticed that double cntrl-c doesn't always kill the JVM? I have seen this on linux and windows. Is there a fix for this? It seems to happen when the JVM is under heavy load. Thanks, Tom |
|
From: Nathan W. <wr...@de...> - 2007-11-14 14:42:10
|
Again, I've never used parallelgc so I don't know what the tradeoffs are for you. If you can run without it, I would drop it. I would take steps to keep yourself from getting into swap though. Add more ram or find ways to trim the in memory image of your app. If it's growing without bound and you aren't sure why you need so much memory you should be hunting for a leak. I would start with anything declared static. On 11/14/07, no spam <mrs...@gm...> wrote: > > I switched to the 1.6.0_03-b05 JRE and we've been running great since > yesterday at 7pm. > This was also with our progam running standalone and not with JavaWrapper. > > I'm going to switch over to running with that as our next test. > > I am using ParallelGC, should I disable this? > > On 11/14/07, Leif Mortenson <le...@ta... > wrote: > > > > no spam wrote: > > > It appears that we're running out of physical memory. Would something > > > like this cause the JVM to just exit? > > Possibly. It does sound like the JVM is crashing for some reason. > > > I assume things can get strange when swapping starts. > > In my experience, Java behaves VERY poorly when its memory is swapped. > > Things can start running 100 to 1000 slower depending on how bad the > > swapping is. You want to be careful to make sure that there is always > > enough memory to keep the OS and JVM completely in memory. > > > > I have seen this lead to crashes with Java 1.3. But not with newer > > JVMs. > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > -- Nathan Wray nw...@de... -- |
|
From: no s. <mrs...@gm...> - 2007-11-14 14:27:09
|
I switched to the 1.6.0_03-b05 JRE and we've been running great since yesterday at 7pm. This was also with our progam running standalone and not with JavaWrapper. I'm going to switch over to running with that as our next test. I am using ParallelGC, should I disable this? On 11/14/07, Leif Mortenson <le...@ta...> wrote: > > no spam wrote: > > It appears that we're running out of physical memory. Would something > > like this cause the JVM to just exit? > Possibly. It does sound like the JVM is crashing for some reason. > > I assume things can get strange when swapping starts. > In my experience, Java behaves VERY poorly when its memory is swapped. > Things can start running 100 to 1000 slower depending on how bad the > swapping is. You want to be careful to make sure that there is always > enough memory to keep the OS and JVM completely in memory. > > I have seen this lead to crashes with Java 1.3. But not with newer JVMs. > > |
|
From: Nathan W. <wr...@de...> - 2007-11-14 14:00:01
|
On 11/14/07, Leif Mortenson <le...@ta...> wrote: > > > > I assume things can get strange when swapping starts. > In my experience, Java behaves VERY poorly when its memory is swapped. > Things can start running 100 to 1000 slower depending on how bad the > swapping is. You want to be careful to make sure that there is always > enough memory to keep the OS and JVM completely in memory. > > I have seen this lead to crashes with Java 1.3. But not with newer JVMs. UseParallelGC is documented to crash the JVM if the memory sweep takes too much time. I don't have any experience with the alternate collection behavior, just going from the docs: "The parallel garbage collector (UseParallelGC) throws an out-of-memory exception if an excessive amount of time is being spent collecting a small amount of the heap. http://java.sun.com/j2se/1.5.0/docs/guide/vm/gc-ergonomics.html |
|
From: Datacom - M. <ma...@da...> - 2007-11-14 13:21:03
|
Leif, The file you told-me to copy already exist in the last version of source code. I have some problems to build due to choose the right compiler and pointing libs, but the final build was done but it stills complain after running bash-3.00# file wrapper wrapper: ELF 64-bit LSB executable AMD64 Version 1, dynamically linked, not stripped, no debugging information available bash-3.00# file libwrapper.so libwrapper.so: ELF 64-bit LSB dynamic lib AMD64 Version 1, dynamically linked, not stripped, no debugging information available bash-3.00# ../java -version java version "1.6.0_03" Java(TM) SE Runtime Environment (build 1.6.0_03-b05) Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-b05, mixed mode) And yes, wrapper.conf calls ../java also Is there a problem witch version of jni.h I used to build ? I guess I pointed to jdk1.5's library to pick jni.h. Thanks in advance. Leif Mortenson escreveu: > Marcelo, > Sorry, that is not a platform that I was able to build myself. > If you download the source and copy the x86-32 bit makefile > to x86-64 in src/c, and then run ./build64.sh in the root, you > should be able to build it fairly easily. If you get any errors, > post back with them on this list an I should be able to give > you some hints as to how to get it working. > > Cheers, > Leif > > Datacom - Marcelo wrote: >> Hi, We are testing our application from Windows/Solaris 64-sparc in >> a Solaris AMD64 arch. we notice there is no build for such arch. Is >> there a way to use java wrapper in such arch ? >> >> > > -- MARCELO Ribeiro |
|
From: Leif M. <le...@ta...> - 2007-11-14 11:50:57
|
no spam wrote: > It appears that we're running out of physical memory. Would something > like this cause the JVM to just exit? Possibly. It does sound like the JVM is crashing for some reason. > I assume things can get strange when swapping starts. In my experience, Java behaves VERY poorly when its memory is swapped. Things can start running 100 to 1000 slower depending on how bad the swapping is. You want to be careful to make sure that there is always enough memory to keep the OS and JVM completely in memory. I have seen this lead to crashes with Java 1.3. But not with newer JVMs. Cheers, Leif > On 11/13/07, *no spam* <mrs...@gm... > <mailto:mrs...@gm...>> wrote: > > Wrapper (Version 3.2.3) > JRE 1.5.0_13-b05 > > I'm getting ready to run a test that's not using the wrapper to > see if I get the same results. Strange thing is that I don't see > a dump file and Dr Watson doesn't report anything. > > > On 11/13/07, *Leif Mortenson* < le...@ta... > <mailto:le...@ta...>> wrote: > > Hi, > The JVM process is either crashing or is exiting with a call to > Runtime.halt(128). I am not sure what that 128 exit code would > be. > > It is most likely a JVM crash. Looking at the log output the last > confirmation that the JVM is alive was at 09:15:06. After that > the Wrapper tried to ping the JVM several times but those pings > all went unanswered. The JVM appears to crash or otherwise > terminate before the Wrapper has a chance to request that it do > so. > > What version of the Wrapper and JVM are you using? > > Cheers, > Leif > > no spam wrote: > > I'm testing a system that's using JIntegra as a COM wrapper > > and using lots of COM objects at high load. I'm seeing the > wrapper restarting my jvm with this error: > > > > JVM process exited with a code of 128, setting the wrapper > exit code > > to 128. > > > > What is this telling me? > > > > DEBUG | wrapperp | 2007/11/12 09:15:06 | send a packet PING : > ping > > INFO | jvm 1 | 2007/11/12 09:15:06 | Received a packet PING : > ping > > INFO | jvm 1 | 2007/11/12 09:15:06 | Send a packet PING : ok > > DEBUG | wrapperp | 2007/11/12 09:15:06 | read a packet PING : ok > > DEBUG | wrapper | 2007/11/12 09:15:06 | Got ping response > from JVM > > DEBUG | wrapperp | 2007/11/12 09:15:10 | send a packet PING : > ping > > DEBUG | wrapperp | 2007/11/12 09:15:14 | send a packet PING : > ping > > DEBUG | wrapperp | 2007/11/12 09:15:18 | send a packet PING : > ping > > DEBUG | wrapper | 2007/11/12 09:15:18 | JVM process exited > with a code > > of 128, setting the wrapper exit code to 128. > > ERROR | wrapper | 2007/11/12 09:15:18 | JVM exited unexpectedly. > > DEBUG | wrapperp | 2007/11/12 09:15:18 | server listening on > port 32001. > > DEBUG | wrapper | 2007/11/12 09:15:18 | Waiting 5 seconds before > > launching another JVM. > > DEBUG | wrapper | 2007/11/12 09:15:23 | Classpath element, > > wrapper.java.classpath.27, does not exist: > lib/proxybrowse-1.0.0.4.jar > > STATUS | wrapper | 2007/11/12 09:15:23 | Launching a JVM... > <snip:restarted normally> > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > <mailto:Wra...@li...> > https://lists.sourceforge.net/lists/listinfo/wrapper-user > <https://lists.sourceforge.net/lists/listinfo/wrapper-user> > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: no s. <mrs...@gm...> - 2007-11-13 23:16:57
|
It appears that we're running out of physical memory. Would something like this cause the JVM to just exit? I assume things can get strange when swapping starts. On 11/13/07, no spam <mrs...@gm...> wrote: > > Wrapper (Version 3.2.3) > JRE 1.5.0_13-b05 > > I'm getting ready to run a test that's not using the wrapper to see if I > get the same results. Strange thing is that I don't see a dump file and Dr > Watson doesn't report anything. > > On 11/13/07, Leif Mortenson <le...@ta...> wrote: > > > > Hi, > > The JVM process is either crashing or is exiting with a call to > > Runtime.halt(128). I am not sure what that 128 exit code would > > be. > > > > It is most likely a JVM crash. Looking at the log output the last > > confirmation that the JVM is alive was at 09:15:06. After that > > the Wrapper tried to ping the JVM several times but those pings > > all went unanswered. The JVM appears to crash or otherwise > > terminate before the Wrapper has a chance to request that it do > > so. > > > > What version of the Wrapper and JVM are you using? > > > > Cheers, > > Leif > > > > no spam wrote: > > > I'm testing a system that's using JIntegra as a COM wrapper > > > and using lots of COM objects at high load. I'm seeing the wrapper > > restarting my jvm with this error: > > > > > > JVM process exited with a code of 128, setting the wrapper exit code > > > to 128. > > > > > > What is this telling me? > > > > > > DEBUG | wrapperp | 2007/11/12 09:15:06 | send a packet PING : ping > > > INFO | jvm 1 | 2007/11/12 09:15:06 | Received a packet PING : ping > > > INFO | jvm 1 | 2007/11/12 09:15:06 | Send a packet PING : ok > > > DEBUG | wrapperp | 2007/11/12 09:15:06 | read a packet PING : ok > > > DEBUG | wrapper | 2007/11/12 09:15:06 | Got ping response from JVM > > > DEBUG | wrapperp | 2007/11/12 09:15:10 | send a packet PING : ping > > > DEBUG | wrapperp | 2007/11/12 09:15:14 | send a packet PING : ping > > > DEBUG | wrapperp | 2007/11/12 09:15:18 | send a packet PING : ping > > > DEBUG | wrapper | 2007/11/12 09:15:18 | JVM process exited with a code > > > of 128, setting the wrapper exit code to 128. > > > ERROR | wrapper | 2007/11/12 09:15:18 | JVM exited unexpectedly. > > > DEBUG | wrapperp | 2007/11/12 09:15:18 | server listening on port > > 32001. > > > DEBUG | wrapper | 2007/11/12 09:15:18 | Waiting 5 seconds before > > > launching another JVM. > > > DEBUG | wrapper | 2007/11/12 09:15:23 | Classpath element, > > > wrapper.java.classpath.27, does not exist: lib/proxybrowse-1.0.0.4.jar > > > STATUS | wrapper | 2007/11/12 09:15:23 | Launching a JVM... > > <snip:restarted normally> > > > > > > ------------------------------------------------------------------------- > > > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > |
|
From: no s. <mrs...@gm...> - 2007-11-13 18:46:55
|
Wrapper (Version 3.2.3) JRE 1.5.0_13-b05 I'm getting ready to run a test that's not using the wrapper to see if I get the same results. Strange thing is that I don't see a dump file and Dr Watson doesn't report anything. On 11/13/07, Leif Mortenson <le...@ta...> wrote: > > Hi, > The JVM process is either crashing or is exiting with a call to > Runtime.halt(128). I am not sure what that 128 exit code would > be. > > It is most likely a JVM crash. Looking at the log output the last > confirmation that the JVM is alive was at 09:15:06. After that > the Wrapper tried to ping the JVM several times but those pings > all went unanswered. The JVM appears to crash or otherwise > terminate before the Wrapper has a chance to request that it do > so. > > What version of the Wrapper and JVM are you using? > > Cheers, > Leif > > no spam wrote: > > I'm testing a system that's using JIntegra as a COM wrapper > > and using lots of COM objects at high load. I'm seeing the wrapper > restarting my jvm with this error: > > > > JVM process exited with a code of 128, setting the wrapper exit code > > to 128. > > > > What is this telling me? > > > > DEBUG | wrapperp | 2007/11/12 09:15:06 | send a packet PING : ping > > INFO | jvm 1 | 2007/11/12 09:15:06 | Received a packet PING : ping > > INFO | jvm 1 | 2007/11/12 09:15:06 | Send a packet PING : ok > > DEBUG | wrapperp | 2007/11/12 09:15:06 | read a packet PING : ok > > DEBUG | wrapper | 2007/11/12 09:15:06 | Got ping response from JVM > > DEBUG | wrapperp | 2007/11/12 09:15:10 | send a packet PING : ping > > DEBUG | wrapperp | 2007/11/12 09:15:14 | send a packet PING : ping > > DEBUG | wrapperp | 2007/11/12 09:15:18 | send a packet PING : ping > > DEBUG | wrapper | 2007/11/12 09:15:18 | JVM process exited with a code > > of 128, setting the wrapper exit code to 128. > > ERROR | wrapper | 2007/11/12 09:15:18 | JVM exited unexpectedly. > > DEBUG | wrapperp | 2007/11/12 09:15:18 | server listening on port 32001. > > DEBUG | wrapper | 2007/11/12 09:15:18 | Waiting 5 seconds before > > launching another JVM. > > DEBUG | wrapper | 2007/11/12 09:15:23 | Classpath element, > > wrapper.java.classpath.27, does not exist: lib/proxybrowse-1.0.0.4.jar > > STATUS | wrapper | 2007/11/12 09:15:23 | Launching a JVM... > <snip:restarted normally> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2007-11-13 18:37:05
|
Marcelo, Sorry, that is not a platform that I was able to build myself. If you download the source and copy the x86-32 bit makefile to x86-64 in src/c, and then run ./build64.sh in the root, you should be able to build it fairly easily. If you get any errors, post back with them on this list an I should be able to give you some hints as to how to get it working. Cheers, Leif Datacom - Marcelo wrote: > Hi, We are testing our application from Windows/Solaris 64-sparc in a > Solaris AMD64 arch. we notice there is no build for such arch. Is there > a way to use java wrapper in such arch ? > > |
|
From: Leif M. <le...@ta...> - 2007-11-13 18:32:25
|
This looks like the same problem as the thread titled "JVM Exit Code 128". See my comments there. Cheers, Leif no spam wrote: > I turned on debug and it has again terminated the JVM, this time using > 1.5 and the UseParallelGC setting. > > DEBUG | wrapperp | 2007/11/09 13:21:48 | send a packet PING : ping > INFO | jvm 1 | 2007/11/09 13:21:48 | Received a packet PING : ping > INFO | jvm 1 | 2007/11/09 13:21:48 | Send a packet PING : ok > DEBUG | wrapperp | 2007/11/09 13:21:48 | read a packet PING : ok > DEBUG | wrapper | 2007/11/09 13:21:48 | Got ping response from JVM > DEBUG | wrapperp | 2007/11/09 13:21:53 | send a packet PING : ping > INFO | jvm 1 | 2007/11/09 13:21:53 | Received a packet PING : ping > INFO | jvm 1 | 2007/11/09 13:21:53 | Send a packet PING : ok > DEBUG | wrapperp | 2007/11/09 13:21:53 | read a packet PING : ok > DEBUG | wrapper | 2007/11/09 13:21:53 | Got ping response from JVM > DEBUG | wrapperp | 2007/11/09 13:21:57 | send a packet PING : ping > INFO | jvm 1 | 2007/11/09 13:21:57 | Received a packet PING : ping > INFO | jvm 1 | 2007/11/09 13:21:57 | Send a packet PING : ok > DEBUG | wrapperp | 2007/11/09 13:21:57 | read a packet PING : ok > DEBUG | wrapper | 2007/11/09 13:21:57 | Got ping response from JVM > DEBUG | wrapperp | 2007/11/09 13:22:02 | send a packet PING : ping > INFO | jvm 1 | 2007/11/09 13:22:02 | Received a packet PING : ping > INFO | jvm 1 | 2007/11/09 13:22:02 | Send a packet PING : ok > DEBUG | wrapperp | 2007/11/09 13:22:02 | read a packet PING : ok > DEBUG | wrapper | 2007/11/09 13:22:02 | Got ping response from JVM > DEBUG | wrapperp | 2007/11/09 13:22:07 | send a packet PING : ping > INFO | jvm 1 | 2007/11/09 13:22:07 | Received a packet PING : ping > INFO | jvm 1 | 2007/11/09 13:22:07 | Send a packet PING : ok > DEBUG | wrapperp | 2007/11/09 13:22:07 | read a packet PING : ok > DEBUG | wrapper | 2007/11/09 13:22:07 | Got ping response from JVM > DEBUG | wrapper | 2007/11/09 13:22:07 | JVM process exited with a code > of 128, setting the wrapper exit code to 128. > ERROR | wrapper | 2007/11/09 13:22:07 | JVM exited unexpectedly. > DEBUG | wrapperp | 2007/11/09 13:22:07 | server listening on port 32001. > DEBUG | wrapper | 2007/11/09 13:22:07 | Waiting 5 seconds before > launching another JVM. > DEBUG | wrapper | 2007/11/09 13:22:12 | Classpath element, > wrapper.java.classpath.27, does not exist: lib/proxybrowse-1.0.0.4.jar > STATUS | wrapper | 2007/11/09 13:22:12 | Launching a JVM... > DEBUG | wrapper | 2007/11/09 13:22:12 | command: "C:\Program > Files\Java\jre1.5.0_13\bin\java" -XX:+UseParallelGC -Xmx500m > -Djava.library.p > ath="../javawrapper/lib;lib/jintegra;lib/jintegra/international" > -classpath > "../javawrapper/lib/wrapper.jar;classes;lib/antlr-2.7.6.jar;lib/ > asm-1.5.3.jar;lib/asm-attrs-1.5.3.jar;lib/cglib-2.1.3.jar;lib/commons- > beanutils-1.7.0.jar;lib/commons-codec-1.3.jar;lib/commons-collections- > 3.2.jar;lib/commons-dbcp-1.2.1.jar;lib/commons-httpclient-3.0.1.jar;lib/commons-lang-2.1.jar;lib/commons-logging-1.0.4.jar;lib/commons-net-1 > .2.2.jar;lib/commons- > pool-1.3.jar;lib/dom4j-1.6.1.jar;lib/ehcache-1.2.3.jar;lib/hibernate-3.2.1.ga.jar;lib/jdom-1.0.jar;lib/jta-1.0.1B.jar;l > ib/kfservice-1.0.0.16.jar;lib/log4j-1.2.13.jar;lib/mam_fwk-1.0.0.12.jar;lib/mam_shared-1.0.0.97.jar > ;lib/mam_shared_testing-1.0.0.42.jar;lib/ > ojdbc-9.0.2.0.0.jar;lib/proxybrowse-1.0.0.4.jar;lib/spring-2.0.1.jar;lib/xpp3_min-1.1.3.4.O.jar;lib/xstream-1.2.1.jar;lib/ifxjdbc_3_0_jc3.ja > r;lib/jintegra.jar" -Dwrapper.key= "KWkoCHr3L_5AnUf8" > -Dwrapper.port=32001 -Dwrapper.jvm.port.min=31000 > -Dwrapper.jvm.port.max=31999 -Dwrappe > r.debug="TRUE" -Dwrapper.pid=10960 -Dwrapper.version="3.2.3" > -Dwrapper.native_library= "wrapper" -Dwrapper.service="TRUE" > -Dwrapper.cpu.timeo > ut="10" -Dwrapper.jvmid=2 org.tanukisoftware.wrapper.WrapperSimpleApp > com.cnn.proxygen.treatment.TreatmentDaemon > DEBUG | wrapper | 2007/11/09 13:22:12 | JVM started (PID=8892) > INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperManager class initialized > by thread: main Using classloader: sun.misc.Launcher$AppClassLoa > der@92e78c > INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper (Version 3.2.3) > http://wrapper.tanukisoftware.org > INFO | jvm 2 | 2007/11/09 13:22:12 | Copyright 1999-2006 Tanuki > Software, Inc. All Rights Reserved. > INFO | jvm 2 | 2007/11/09 13:22:12 | > INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper Manager: JVM #2 > INFO | jvm 2 | 2007/11/09 13:22:12 | Running a 32-bit JVM. > INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper Manager: Registering > shutdown hook > INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper Manager: Using wrapper > INFO | jvm 2 | 2007/11/09 13:22:12 | Load native library. One or more > attempts may fail if platform specific libraries do not exist. > INFO | jvm 2 | 2007/11/09 13:22:12 | Loading native library failed: > wrapper-windows-x86-32.dll Cause: java.lang.UnsatisfiedLinkError: > no wrapper-windows-x86-32 in java.library.path > INFO | jvm 2 | 2007/11/09 13:22:12 | Loaded native library: wrapper.dll > INFO | jvm 2 | 2007/11/09 13:22:12 | Calling native initialization method. > INFO | jvm 2 | 2007/11/09 13:22:12 | Initializing WrapperManager > native library. > INFO | jvm 2 | 2007/11/09 13:22:12 | Java Executable: C:\Program > Files\Java\jre1.5.0_13\bin\java.exe > INFO | jvm 2 | 2007/11/09 13:22:12 | Windows version: 5.2.3790 > INFO | jvm 2 | 2007/11/09 13:22:12 | Java Version : 1.5.0_13-b05 Java > HotSpot(TM) Client VM > INFO | jvm 2 | 2007/11/09 13:22:12 | Java VM Vendor : Sun Microsystems > Inc. > INFO | jvm 2 | 2007/11/09 13:22:12 | > INFO | jvm 2 | 2007/11/09 13:22:12 | Control event monitor thread started. > INFO | jvm 2 | 2007/11/09 13:22:12 | Startup runner thread started. > INFO | jvm 2 | 2007/11/09 13:22:12 | > WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@fd54d6, > args[]) called by thread: > main > INFO | jvm 2 | 2007/11/09 13:22:12 | Communications runner thread started. > INFO | jvm 2 | 2007/11/09 13:22:12 | Open socket to > wrapper...Wrapper-Connection > INFO | jvm 2 | 2007/11/09 13:22:12 | Opened Socket from 31000 to 32001 > INFO | jvm 2 | 2007/11/09 13:22:12 | Send a packet KEY : KWkoCHr3L_5AnUf8 > INFO | jvm 2 | 2007/11/09 13:22:12 | > handleSocket(Socket[addr=/127.0.0.1,port=32001,localport=31000]) > DEBUG | wrapperp | 2007/11/09 13:22:12 | accepted a socket from > 127.0.0.1 <http://127.0.0.1> on port 31000 > DEBUG | wrapperp | 2007/11/09 13:22:12 | read a packet KEY : > KWkoCHr3L_5AnUf8 > DEBUG | wrapper | 2007/11/09 13:22:12 | Got key from JVM: > KWkoCHr3L_5AnUf8 > DEBUG | wrapperp | 2007/11/09 13:22:12 | send a packet LOW_LOG_LEVEL : 1 > DEBUG | wrapperp | 2007/11/09 13:22:12 | send a packet PING_TIMEOUT : 1200 > DEBUG | wrapperp | 2007/11/09 13:22:12 | send a packet PROPERTIES : > (Property Values) > DEBUG | wrapper | 2007/11/09 13:22:12 | Start Application. > DEBUG | wrapperp | 2007/11/09 13:22:12 | send a packet START : start > INFO | jvm 2 | 2007/11/09 13:22:12 | Received a packet LOW_LOG_LEVEL : 1 > INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper Manager: LowLogLevel from > Wrapper is 1 > INFO | jvm 2 | 2007/11/09 13:22:12 | Received a packet PING_TIMEOUT : 1200 > INFO | jvm 2 | 2007/11/09 13:22:12 | PingTimeout from Wrapper is 1200000 > INFO | jvm 2 | 2007/11/09 13:22:12 | Received a packet PROPERTIES : > (Property Values) > INFO | jvm 2 | 2007/11/09 13:22:12 | Received a packet START : start > INFO | jvm 2 | 2007/11/09 13:22:12 | calling WrapperListener.start() > INFO | jvm 2 | 2007/11/09 13:22:12 | Waiting for WrapperListener.start > runner thread to complete. > INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperListener.start runner > thread started. > INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperSimpleApp: start(args) > Will wait up to 2 seconds for the main method to complete. > INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperSimpleApp: invoking main > method > INFO | jvm 2 | 2007/11/09 13:22:12 | log4j:WARN No appenders could be > found for logger ( com.cnn.mam.soa.client.SecureClientImpl). > INFO | jvm 2 | 2007/11/09 13:22:12 | log4j:WARN Please initialize the > log4j system properly. > INFO | jvm 2 | 2007/11/09 13:22:13 | WrapperSimpleApp: main method > completed > INFO | jvm 2 | 2007/11/09 13:22:13 | WrapperSimpleApp: start(args) > end. Main Completed=true, exitCode=null > INFO | jvm 2 | 2007/11/09 13:22:13 | WrapperListener.start runner > thread stopped. > INFO | jvm 2 | 2007/11/09 13:22:13 | returned from WrapperListener.start() > INFO | jvm 2 | 2007/11/09 13:22:13 | Send a packet STARTED : > DEBUG | wrapperp | 2007/11/09 13:22:13 | read a packet STARTED : > DEBUG | wrapper | 2007/11/09 13:22:13 | JVM signalled that it was > started. > DEBUG | wrapperp | 2007/11/09 13:22:13 | send a packet PING : ping > INFO | jvm 2 | 2007/11/09 13:22:13 | Received a packet PING : ping > INFO | jvm 2 | 2007/11/09 13:22:13 | Send a packet PING : ok > INFO | jvm 2 | 2007/11/09 13:22:13 | Startup runner thread stopped. > DEBUG | wrapperp | 2007/11/09 13:22:13 | read a packet PING : ok > DEBUG | wrapper | 2007/11/09 13:22:13 | Got ping response from JVM > DEBUG | wrapperp | 2007/11/09 13:22:17 | send a packet PING : ping > INFO | jvm 2 | 2007/11/09 13:22:17 | Received a packet PING : ping > INFO | jvm 2 | 2007/11/09 13:22:17 | Send a packet PING : ok > DEBUG | wrapperp | 2007/11/09 13:22:17 | read a packet PING : ok > DEBUG | wrapper | 2007/11/09 13:22:17 | Got ping response from JVM > DEBUG | wrapperp | 2007/11/09 13:22:21 | send a packet PING : ping > INFO | jvm 2 | 2007/11/09 13:22:21 | Received a packet PING : ping > INFO | jvm 2 | 2007/11/09 13:22:21 | Send a packet PING : ok > DEBUG | wrapperp | 2007/11/09 13:22:21 | read a packet PING : ok > DEBUG | wrapper | 2007/11/09 13:22:21 | Got ping response from JVM > DEBUG | wrapperp | 2007/11/09 13:22:25 | send a packet PING : ping > > > On 11/9/07, *no spam* <mrs...@gm... > <mailto:mrs...@gm...>> wrote: > > The strange thing is that I ran this on our reference servers for > a week straight with no issues. But that was all 1.5 JRE. The > only other difference I noticed is that on these current tests I > wasn't using the wrapper.java.additional.1=-XX:+UseParallelGC > setting. > > I've kicked off a new test all 1.5 with this additional setting. > > Mark > > > On 11/9/07, * Nathan Wray* <wr...@de... > <mailto:wr...@de...>> wrote: > > > Not necessarily, you should be able to run under a newer JVM. > Does the application run successfully for long periods when > it's not running under wrapper? I would be looking for a > resource leak, and trying to gather additional debug info. > Try running without wrapper under the same conditions. Also > take a look at jhat and jmap, you could probably run for 24 > hours and take a look at the heap for anything suspicious. > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2007-11-13 18:29:34
|
Hi, The JVM process is either crashing or is exiting with a call to Runtime.halt(128). I am not sure what that 128 exit code would be. It is most likely a JVM crash. Looking at the log output the last confirmation that the JVM is alive was at 09:15:06. After that the Wrapper tried to ping the JVM several times but those pings all went unanswered. The JVM appears to crash or otherwise terminate before the Wrapper has a chance to request that it do so. What version of the Wrapper and JVM are you using? Cheers, Leif no spam wrote: > I'm testing a system that's using JIntegra as a COM wrapper > and using lots of COM objects at high load. I'm seeing the wrapper restarting my jvm with this error: > > JVM process exited with a code of 128, setting the wrapper exit code > to 128. > > What is this telling me? > > DEBUG | wrapperp | 2007/11/12 09:15:06 | send a packet PING : ping > INFO | jvm 1 | 2007/11/12 09:15:06 | Received a packet PING : ping > INFO | jvm 1 | 2007/11/12 09:15:06 | Send a packet PING : ok > DEBUG | wrapperp | 2007/11/12 09:15:06 | read a packet PING : ok > DEBUG | wrapper | 2007/11/12 09:15:06 | Got ping response from JVM > DEBUG | wrapperp | 2007/11/12 09:15:10 | send a packet PING : ping > DEBUG | wrapperp | 2007/11/12 09:15:14 | send a packet PING : ping > DEBUG | wrapperp | 2007/11/12 09:15:18 | send a packet PING : ping > DEBUG | wrapper | 2007/11/12 09:15:18 | JVM process exited with a code > of 128, setting the wrapper exit code to 128. > ERROR | wrapper | 2007/11/12 09:15:18 | JVM exited unexpectedly. > DEBUG | wrapperp | 2007/11/12 09:15:18 | server listening on port 32001. > DEBUG | wrapper | 2007/11/12 09:15:18 | Waiting 5 seconds before > launching another JVM. > DEBUG | wrapper | 2007/11/12 09:15:23 | Classpath element, > wrapper.java.classpath.27, does not exist: lib/proxybrowse-1.0.0.4.jar > STATUS | wrapper | 2007/11/12 09:15:23 | Launching a JVM... <snip:restarted normally> |
|
From: no s. <mrs...@gm...> - 2007-11-13 16:20:49
|
I'm testing a system that's using JIntegra as a COM wrapper and using lots of COM objects at high load. I'm seeing the wrapper restarting my jvm with this error: JVM process exited with a code of 128, setting the wrapper exit code to 128. What is this telling me? DEBUG | wrapperp | 2007/11/12 09:15:06 | send a packet PING : ping INFO | jvm 1 | 2007/11/12 09:15:06 | Received a packet PING : ping INFO | jvm 1 | 2007/11/12 09:15:06 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/12 09:15:06 | read a packet PING : ok DEBUG | wrapper | 2007/11/12 09:15:06 | Got ping response from JVM DEBUG | wrapperp | 2007/11/12 09:15:10 | send a packet PING : ping DEBUG | wrapperp | 2007/11/12 09:15:14 | send a packet PING : ping DEBUG | wrapperp | 2007/11/12 09:15:18 | send a packet PING : ping DEBUG | wrapper | 2007/11/12 09:15:18 | JVM process exited with a code of 128, setting the wrapper exit code to 128. ERROR | wrapper | 2007/11/12 09:15:18 | JVM exited unexpectedly. DEBUG | wrapperp | 2007/11/12 09:15:18 | server listening on port 32001. DEBUG | wrapper | 2007/11/12 09:15:18 | Waiting 5 seconds before launching another JVM. DEBUG | wrapper | 2007/11/12 09:15:23 | Classpath element, wrapper.java.classpath.27, does not exist: lib/proxybrowse-1.0.0.4.jar STATUS | wrapper | 2007/11/12 09:15:23 | Launching a JVM... DEBUG | wrapper | 2007/11/12 09:15:23 | command: "C:\Program Files\Java\jre1.5.0_13\bin\java" -XX:+UseParallelGC -Xmx500m - Djava.library.p ath="../javawrapper/lib;lib/jintegra;lib/jintegra/international" -classpath "../javawrapper/lib/wrapper.jar;classes;lib/antlr-2.7.6.jar;lib/ asm-1.5.3.jar;lib/asm-attrs-1.5.3.jar;lib/cglib-2.1.3.jar;lib/commons- beanutils-1.7.0.jar;lib/commons-codec-1.3.jar;lib/commons-collections- 3.2.jar;lib/commons-dbcp-1.2.1.jar;lib/commons-httpclient-3.0.1.jar ;lib/commons-lang-2.1.jar;lib/commons-logging-1.0.4.jar;lib/commons-net-1 .2.2.jar;lib/commons-pool-1.3.jar;lib/dom4j-1.6.1.jar;lib/ehcache-1.2.3.jar ;lib/hibernate-3.2.1.ga.jar;lib/jdom-1.0.jar;lib/jta-1.0.1B.jar;l ib/kfservice-1.0.0.16.jar;lib/log4j-1.2.13.jar;lib/mam_fwk-1.0.0.12.jar ;lib/mam_shared-1.0.0.97.jar;lib/mam_shared_testing-1.0.0.42.jar;lib/ ojdbc-9.0.2.0.0.jar;lib/proxybrowse-1.0.0.4.jar;lib/spring-2.0.1.jar ;lib/xpp3_min-1.1.3.4.O.jar;lib/xstream-1.2.1.jar;lib/ifxjdbc_3_0_jc3.ja r;lib/jintegra.jar" -Dwrapper.key="snp2ssxbuqWEE4Gd" -Dwrapper.port=32001 - Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrappe r.debug="TRUE" -Dwrapper.pid=4444 -Dwrapper.version="3.2.3" - Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" - Dwrapper.cpu.timeou t="10" -Dwrapper.jvmid=2 org.tanukisoftware.wrapper.WrapperSimpleApp com.cnn.proxygen.treatment.TreatmentDaemon DEBUG | wrapper | 2007/11/12 09:15:23 | JVM started (PID=5340) INFO | jvm 2 | 2007/11/12 09:15:23 | WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoa der@92e78c INFO | jvm 2 | 2007/11/12 09:15:23 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 2 | 2007/11/12 09:15:23 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 2 | 2007/11/12 09:15:23 | INFO | jvm 2 | 2007/11/12 09:15:23 | Wrapper Manager: JVM #2 INFO | jvm 2 | 2007/11/12 09:15:23 | Running a 32-bit JVM. INFO | jvm 2 | 2007/11/12 09:15:23 | Wrapper Manager: Registering shutdown hook INFO | jvm 2 | 2007/11/12 09:15:23 | Wrapper Manager: Using wrapper INFO | jvm 2 | 2007/11/12 09:15:23 | Load native library. One or more attempts may fail if platform specific libraries do not exist. INFO | jvm 2 | 2007/11/12 09:15:23 | Loading native library failed: wrapper-windows-x86-32.dll Cause: java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-32 in java.library.path INFO | jvm 2 | 2007/11/12 09:15:23 | Loaded native library: wrapper.dll INFO | jvm 2 | 2007/11/12 09:15:23 | Calling native initialization method. INFO | jvm 2 | 2007/11/12 09:15:23 | Initializing WrapperManager native library. INFO | jvm 2 | 2007/11/12 09:15:23 | Java Executable: C:\Program Files\Java\jre1.5.0_13\bin\java.exe INFO | jvm 2 | 2007/11/12 09:15:23 | Windows version: 5.2.3790 INFO | jvm 2 | 2007/11/12 09:15:23 | Java Version : 1.5.0_13-b05 Java HotSpot(TM) Client VM INFO | jvm 2 | 2007/11/12 09:15:23 | Java VM Vendor : Sun Microsystems Inc. INFO | jvm 2 | 2007/11/12 09:15:23 | INFO | jvm 2 | 2007/11/12 09:15:23 | Control event monitor thread started. INFO | jvm 2 | 2007/11/12 09:15:23 | Startup runner thread started. INFO | jvm 2 | 2007/11/12 09:15:23 | WrapperManager.start( org.tanukisoftware.wrapper.WrapperSimpleApp@fd54d6, args[]) called by thread: main INFO | jvm 2 | 2007/11/12 09:15:23 | Communications runner thread started. INFO | jvm 2 | 2007/11/12 09:15:23 | Open socket to wrapper...Wrapper-Connection INFO | jvm 2 | 2007/11/12 09:15:23 | Opened Socket from 31000 to 32001 INFO | jvm 2 | 2007/11/12 09:15:23 | Send a packet KEY : snp2ssxbuqWEE4Gd INFO | jvm 2 | 2007/11/12 09:15:23 | handleSocket(Socket[addr=/127.0.0.1,port=32001,localport=31000]) DEBUG | wrapperp | 2007/11/12 09:15:23 | accepted a socket from 127.0.0.1 on port 31000 DEBUG | wrapperp | 2007/11/12 09:15:23 | read a packet KEY : snp2ssxbuqWEE4Gd DEBUG | wrapper | 2007/11/12 09:15:23 | Got key from JVM: snp2ssxbuqWEE4Gd DEBUG | wrapperp | 2007/11/12 09:15:23 | send a packet LOW_LOG_LEVEL : 1 DEBUG | wrapperp | 2007/11/12 09:15:23 | send a packet PING_TIMEOUT : 600 DEBUG | wrapperp | 2007/11/12 09:15:23 | send a packet PROPERTIES : (Property Values) DEBUG | wrapper | 2007/11/12 09:15:23 | Start Application. DEBUG | wrapperp | 2007/11/12 09:15:23 | send a packet START : start INFO | jvm 2 | 2007/11/12 09:15:23 | Received a packet LOW_LOG_LEVEL : 1 INFO | jvm 2 | 2007/11/12 09:15:23 | Wrapper Manager: LowLogLevel from Wrapper is 1 INFO | jvm 2 | 2007/11/12 09:15:23 | Received a packet PING_TIMEOUT : 600 INFO | jvm 2 | 2007/11/12 09:15:23 | PingTimeout from Wrapper is 600000 INFO | jvm 2 | 2007/11/12 09:15:23 | Received a packet PROPERTIES : (Property Values) INFO | jvm 2 | 2007/11/12 09:15:23 | Received a packet START : start INFO | jvm 2 | 2007/11/12 09:15:23 | calling WrapperListener.start() INFO | jvm 2 | 2007/11/12 09:15:23 | Waiting for WrapperListener.startrunner thread to complete. INFO | jvm 2 | 2007/11/12 09:15:23 | WrapperListener.start runner thread started. INFO | jvm 2 | 2007/11/12 09:15:23 | WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete. INFO | jvm 2 | 2007/11/12 09:15:23 | WrapperSimpleApp: invoking main method INFO | jvm 2 | 2007/11/12 09:15:23 | log4j:WARN No appenders could be found for logger (com.cnn.mam.soa.client.SecureClientImpl). INFO | jvm 2 | 2007/11/12 09:15:23 | log4j:WARN Please initialize the log4j system properly. INFO | jvm 2 | 2007/11/12 09:15:24 | WrapperSimpleApp: main method completed INFO | jvm 2 | 2007/11/12 09:15:24 | WrapperSimpleApp: start(args) end. Main Completed=true, exitCode=null INFO | jvm 2 | 2007/11/12 09:15:24 | WrapperListener.start runner thread stopped. INFO | jvm 2 | 2007/11/12 09:15:24 | returned from WrapperListener.start() INFO | jvm 2 | 2007/11/12 09:15:24 | Send a packet STARTED : INFO | jvm 2 | 2007/11/12 09:15:24 | Startup runner thread stopped. DEBUG | wrapperp | 2007/11/12 09:15:24 | read a packet STARTED : DEBUG | wrapper | 2007/11/12 09:15:24 | JVM signalled that it was started. DEBUG | wrapperp | 2007/11/12 09:15:24 | send a packet PING : ping |
|
From: Datacom - M. <ma...@da...> - 2007-11-13 10:43:13
|
Hi, We are testing our application from Windows/Solaris 64-sparc in a Solaris AMD64 arch. we notice there is no build for such arch. Is there a way to use java wrapper in such arch ? -- MARCELO Ribeiro |
|
From: no s. <mrs...@gm...> - 2007-11-09 18:48:07
|
I turned on debug and it has again terminated the JVM, this time using 1.5and the UseParallelGC setting. DEBUG | wrapperp | 2007/11/09 13:21:48 | send a packet PING : ping INFO | jvm 1 | 2007/11/09 13:21:48 | Received a packet PING : ping INFO | jvm 1 | 2007/11/09 13:21:48 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:21:48 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:21:48 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:21:53 | send a packet PING : ping INFO | jvm 1 | 2007/11/09 13:21:53 | Received a packet PING : ping INFO | jvm 1 | 2007/11/09 13:21:53 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:21:53 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:21:53 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:21:57 | send a packet PING : ping INFO | jvm 1 | 2007/11/09 13:21:57 | Received a packet PING : ping INFO | jvm 1 | 2007/11/09 13:21:57 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:21:57 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:21:57 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:22:02 | send a packet PING : ping INFO | jvm 1 | 2007/11/09 13:22:02 | Received a packet PING : ping INFO | jvm 1 | 2007/11/09 13:22:02 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:22:02 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:22:02 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:22:07 | send a packet PING : ping INFO | jvm 1 | 2007/11/09 13:22:07 | Received a packet PING : ping INFO | jvm 1 | 2007/11/09 13:22:07 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:22:07 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:22:07 | Got ping response from JVM DEBUG | wrapper | 2007/11/09 13:22:07 | JVM process exited with a code of 128, setting the wrapper exit code to 128. ERROR | wrapper | 2007/11/09 13:22:07 | JVM exited unexpectedly. DEBUG | wrapperp | 2007/11/09 13:22:07 | server listening on port 32001. DEBUG | wrapper | 2007/11/09 13:22:07 | Waiting 5 seconds before launching another JVM. DEBUG | wrapper | 2007/11/09 13:22:12 | Classpath element, wrapper.java.classpath.27, does not exist: lib/proxybrowse-1.0.0.4.jar STATUS | wrapper | 2007/11/09 13:22:12 | Launching a JVM... DEBUG | wrapper | 2007/11/09 13:22:12 | command: "C:\Program Files\Java\jre1.5.0_13\bin\java" -XX:+UseParallelGC -Xmx500m - Djava.library.p ath="../javawrapper/lib;lib/jintegra;lib/jintegra/international" -classpath "../javawrapper/lib/wrapper.jar;classes;lib/antlr-2.7.6.jar;lib/ asm-1.5.3.jar;lib/asm-attrs-1.5.3.jar;lib/cglib-2.1.3.jar;lib/commons- beanutils-1.7.0.jar;lib/commons-codec-1.3.jar;lib/commons-collections- 3.2.jar;lib/commons-dbcp-1.2.1.jar;lib/commons-httpclient-3.0.1.jar ;lib/commons-lang-2.1.jar;lib/commons-logging-1.0.4.jar;lib/commons-net-1 .2.2.jar;lib/commons-pool-1.3.jar;lib/dom4j-1.6.1.jar;lib/ehcache-1.2.3.jar ;lib/hibernate-3.2.1.ga.jar;lib/jdom-1.0.jar;lib/jta-1.0.1B.jar;l ib/kfservice-1.0.0.16.jar;lib/log4j-1.2.13.jar;lib/mam_fwk-1.0.0.12.jar ;lib/mam_shared-1.0.0.97.jar;lib/mam_shared_testing-1.0.0.42.jar;lib/ ojdbc-9.0.2.0.0.jar;lib/proxybrowse-1.0.0.4.jar;lib/spring-2.0.1.jar ;lib/xpp3_min-1.1.3.4.O.jar;lib/xstream-1.2.1.jar;lib/ifxjdbc_3_0_jc3.ja r;lib/jintegra.jar" -Dwrapper.key="KWkoCHr3L_5AnUf8" -Dwrapper.port=32001 - Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrappe r.debug="TRUE" -Dwrapper.pid=10960 -Dwrapper.version="3.2.3" - Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" - Dwrapper.cpu.timeo ut="10" -Dwrapper.jvmid=2 org.tanukisoftware.wrapper.WrapperSimpleApp com.cnn.proxygen.treatment.TreatmentDaemon DEBUG | wrapper | 2007/11/09 13:22:12 | JVM started (PID=8892) INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoa der@92e78c INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 2 | 2007/11/09 13:22:12 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 2 | 2007/11/09 13:22:12 | INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper Manager: JVM #2 INFO | jvm 2 | 2007/11/09 13:22:12 | Running a 32-bit JVM. INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper Manager: Registering shutdown hook INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper Manager: Using wrapper INFO | jvm 2 | 2007/11/09 13:22:12 | Load native library. One or more attempts may fail if platform specific libraries do not exist. INFO | jvm 2 | 2007/11/09 13:22:12 | Loading native library failed: wrapper-windows-x86-32.dll Cause: java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-32 in java.library.path INFO | jvm 2 | 2007/11/09 13:22:12 | Loaded native library: wrapper.dll INFO | jvm 2 | 2007/11/09 13:22:12 | Calling native initialization method. INFO | jvm 2 | 2007/11/09 13:22:12 | Initializing WrapperManager native library. INFO | jvm 2 | 2007/11/09 13:22:12 | Java Executable: C:\Program Files\Java\jre1.5.0_13\bin\java.exe INFO | jvm 2 | 2007/11/09 13:22:12 | Windows version: 5.2.3790 INFO | jvm 2 | 2007/11/09 13:22:12 | Java Version : 1.5.0_13-b05 Java HotSpot(TM) Client VM INFO | jvm 2 | 2007/11/09 13:22:12 | Java VM Vendor : Sun Microsystems Inc. INFO | jvm 2 | 2007/11/09 13:22:12 | INFO | jvm 2 | 2007/11/09 13:22:12 | Control event monitor thread started. INFO | jvm 2 | 2007/11/09 13:22:12 | Startup runner thread started. INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperManager.start( org.tanukisoftware.wrapper.WrapperSimpleApp@fd54d6, args[]) called by thread: main INFO | jvm 2 | 2007/11/09 13:22:12 | Communications runner thread started. INFO | jvm 2 | 2007/11/09 13:22:12 | Open socket to wrapper...Wrapper-Connection INFO | jvm 2 | 2007/11/09 13:22:12 | Opened Socket from 31000 to 32001 INFO | jvm 2 | 2007/11/09 13:22:12 | Send a packet KEY : KWkoCHr3L_5AnUf8 INFO | jvm 2 | 2007/11/09 13:22:12 | handleSocket(Socket[addr=/127.0.0.1,port=32001,localport=31000]) DEBUG | wrapperp | 2007/11/09 13:22:12 | accepted a socket from 127.0.0.1 on port 31000 DEBUG | wrapperp | 2007/11/09 13:22:12 | read a packet KEY : KWkoCHr3L_5AnUf8 DEBUG | wrapper | 2007/11/09 13:22:12 | Got key from JVM: KWkoCHr3L_5AnUf8 DEBUG | wrapperp | 2007/11/09 13:22:12 | send a packet LOW_LOG_LEVEL : 1 DEBUG | wrapperp | 2007/11/09 13:22:12 | send a packet PING_TIMEOUT : 1200 DEBUG | wrapperp | 2007/11/09 13:22:12 | send a packet PROPERTIES : (Property Values) DEBUG | wrapper | 2007/11/09 13:22:12 | Start Application. DEBUG | wrapperp | 2007/11/09 13:22:12 | send a packet START : start INFO | jvm 2 | 2007/11/09 13:22:12 | Received a packet LOW_LOG_LEVEL : 1 INFO | jvm 2 | 2007/11/09 13:22:12 | Wrapper Manager: LowLogLevel from Wrapper is 1 INFO | jvm 2 | 2007/11/09 13:22:12 | Received a packet PING_TIMEOUT : 1200 INFO | jvm 2 | 2007/11/09 13:22:12 | PingTimeout from Wrapper is 1200000 INFO | jvm 2 | 2007/11/09 13:22:12 | Received a packet PROPERTIES : (Property Values) INFO | jvm 2 | 2007/11/09 13:22:12 | Received a packet START : start INFO | jvm 2 | 2007/11/09 13:22:12 | calling WrapperListener.start() INFO | jvm 2 | 2007/11/09 13:22:12 | Waiting for WrapperListener.startrunner thread to complete. INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperListener.start runner thread started. INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete. INFO | jvm 2 | 2007/11/09 13:22:12 | WrapperSimpleApp: invoking main method INFO | jvm 2 | 2007/11/09 13:22:12 | log4j:WARN No appenders could be found for logger (com.cnn.mam.soa.client.SecureClientImpl). INFO | jvm 2 | 2007/11/09 13:22:12 | log4j:WARN Please initialize the log4j system properly. INFO | jvm 2 | 2007/11/09 13:22:13 | WrapperSimpleApp: main method completed INFO | jvm 2 | 2007/11/09 13:22:13 | WrapperSimpleApp: start(args) end. Main Completed=true, exitCode=null INFO | jvm 2 | 2007/11/09 13:22:13 | WrapperListener.start runner thread stopped. INFO | jvm 2 | 2007/11/09 13:22:13 | returned from WrapperListener.start() INFO | jvm 2 | 2007/11/09 13:22:13 | Send a packet STARTED : DEBUG | wrapperp | 2007/11/09 13:22:13 | read a packet STARTED : DEBUG | wrapper | 2007/11/09 13:22:13 | JVM signalled that it was started. DEBUG | wrapperp | 2007/11/09 13:22:13 | send a packet PING : ping INFO | jvm 2 | 2007/11/09 13:22:13 | Received a packet PING : ping INFO | jvm 2 | 2007/11/09 13:22:13 | Send a packet PING : ok INFO | jvm 2 | 2007/11/09 13:22:13 | Startup runner thread stopped. DEBUG | wrapperp | 2007/11/09 13:22:13 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:22:13 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:22:17 | send a packet PING : ping INFO | jvm 2 | 2007/11/09 13:22:17 | Received a packet PING : ping INFO | jvm 2 | 2007/11/09 13:22:17 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:22:17 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:22:17 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:22:21 | send a packet PING : ping INFO | jvm 2 | 2007/11/09 13:22:21 | Received a packet PING : ping INFO | jvm 2 | 2007/11/09 13:22:21 | Send a packet PING : ok DEBUG | wrapperp | 2007/11/09 13:22:21 | read a packet PING : ok DEBUG | wrapper | 2007/11/09 13:22:21 | Got ping response from JVM DEBUG | wrapperp | 2007/11/09 13:22:25 | send a packet PING : ping On 11/9/07, no spam <mrs...@gm...> wrote: > > The strange thing is that I ran this on our reference servers for a week > straight with no issues. But that was all 1.5 JRE. The only other > difference I noticed is that on these current tests I wasn't using the > wrapper.java.additional.1=-XX:+UseParallelGC setting. > > I've kicked off a new test all 1.5 with this additional setting. > > Mark > > On 11/9/07, Nathan Wray <wr...@de...> wrote: > > > > > > Not necessarily, you should be able to run under a newer JVM. Does the > > application run successfully for long periods when it's not running under > > wrapper? I would be looking for a resource leak, and trying to gather > > additional debug info. Try running without wrapper under the same > > conditions. Also take a look at jhat and jmap, you could probably run for > > 24 hours and take a look at the heap for anything suspicious. > > > > |
|
From: no s. <mrs...@gm...> - 2007-11-09 17:51:45
|
The strange thing is that I ran this on our reference servers for a week straight with no issues. But that was all 1.5 JRE. The only other difference I noticed is that on these current tests I wasn't using the wrapper.java.additional.1=-XX:+UseParallelGC setting. I've kicked off a new test all 1.5 with this additional setting. Mark On 11/9/07, Nathan Wray <wr...@de...> wrote: > > > Not necessarily, you should be able to run under a newer JVM. Does the > application run successfully for long periods when it's not running under > wrapper? I would be looking for a resource leak, and trying to gather > additional debug info. Try running without wrapper under the same > conditions. Also take a look at jhat and jmap, you could probably run for > 24 hours and take a look at the heap for anything suspicious. > |
|
From: Nathan W. <wr...@de...> - 2007-11-09 17:26:28
|
Not necessarily, you should be able to run under a newer JVM. Does the application run successfully for long periods when it's not running under wrapper? I would be looking for a resource leak, and trying to gather additional debug info. Try running without wrapper under the same conditions. Also take a look at jhat and jmap, you could probably run for 24 hours and take a look at the heap for anything suspicious. On 11/9/07, no spam <mrs...@gm...> wrote: > > hmmm ... i just figured out that compiled with JRE 1.5.0_06 and was > interpreting with 1.6.0_03-b05. Would this cause issues like this? > > On 11/9/07, no spam <mrs...@gm...> wrote: > > > > I forgot to include my platform information > > > > Windows Server 2003 Standard, Version 5.2.3790 Service Pack 2 Build 3790 > > JRE 1.6.0_03-b05 > > > > Mark > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > -- Nathan Wray nw...@de... -- |
165 messages has been excluded from this view by a project administrator.
