Menu
▾
▴
wrapper-user
|
From: Vadim P. <va...@2t...> - 2004-09-22 16:50:50
|
Hi!
I've found a lot of posts started with " JVM process exited with a
code", but no one with such a strange exit code.
This could be reproduced by clicking 10-20 times on some button of the
application in the browser.
During button pressing the system not overloaded at all.
The same thing works perfect during simple jvm execution w/o java wrapper.
All timings and timeouts were extended up to 3-4 minutes, and pinging
works perfect.
wrapper.conf configuration added after log messages.
Any ideas ?!
Best Regards,
Vadim
DEBUG | wrapper | 2004/09/22 18:22:40 | JVM process exited with a code
of -1073741571, setting the wrapper exit code to -1073741571.
ERROR | wrapper | 2004/09/22 18:22:40 | JVM exited unexpectedly.
DEBUG | wrapper | 2004/09/22 18:22:41 | Waiting 5 seconds before
launching another JVM.
STATUS | wrapper | 2004/09/22 18:22:45 | Launching a JVM...
DEBUG | wrapper | 2004/09/22 18:22:45 | command:
"c:\j2sdk1.4.2_02\bin\java" -server -XX:NewSize=400m -XX:PermSize=40m
-Xms512m -Xmx512m -Xloggc:C:\jboss-3.2.2\server\default\log\GC.log
-Dprogram.name=Wrapper -Xms512m -Xmx512m
-Djava.library.path="C:/jboss-3.2.2/lib;;C:/Eldat Common Path;"
-classpath
"C:/jboss-3.2.2/lib/wrapper.jar;C:/j2sdk1.4.2_02/lib/tools.jar;C:/jboss-3.2.2/bin/run.jar"
-Dwrapper.key="rZuk3O5PJPe7hdQ1" -Dwrapper.port=32000
-Dwrapper.debug="TRUE" -Dwrapper.use_system_time="TRUE"
-Dwrapper.version="3.1.1" -Dwrapper.native_library="wrapper"
-Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="50" -Dwrapper.jvmid=2
org.tanukisoftware.wrapper.WrapperSimpleApp org.jboss.Main -c default
DEBUG | wrapper | 2004/09/22 18:22:45 | JVM started (PID=16856)
INFO | jvm 2 | 2004/09/22 18:22:48 | WrapperManager class
initialized by thread: main Using classloader:
sun.misc.Launcher$AppClassLoader@1ff5ea7
INFO | jvm 2 | 2004/09/22 18:22:48 | Wrapper Manager: JVM #2
INFO | jvm 2 | 2004/09/22 18:22:48 | Wrapper Manager: Registering
shutdown hook
INFO | jvm 2 | 2004/09/22 18:22:48 | Wrapper Manager: Using wrapper
INFO | jvm 2 | 2004/09/22 18:22:48 | Loaded native library: wrapper.dll
INFO | jvm 2 | 2004/09/22 18:22:48 | Calling native initialization
method.
INFO | jvm 2 | 2004/09/22 18:22:48 | Initializing WrapperManager
native library.
INFO | jvm 2 | 2004/09/22 18:22:48 | Java Executable:
c:\j2sdk1.4.2_02\bin\java.exe
INFO | jvm 2 | 2004/09/22 18:22:48 | Windows version: 5.0.2195
INFO | jvm 2 | 2004/09/22 18:22:48 | Java Version : 1.4.2_02-b03
Java HotSpot(TM) Server VM
INFO | jvm 2 | 2004/09/22 18:22:48 | Java VM Vendor : Sun
Microsystems Inc.
INFO | jvm 2 | 2004/09/22 18:22:48 |
INFO | jvm 2 | 2004/09/22 18:22:48 | Wrapper (Version 3.1.1)
http://wrapper.tanukisoftware.org
INFO | jvm 2 | 2004/09/22 18:22:48 |
INFO | jvm 2 | 2004/09/22 18:22:48 |
WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@1fae3c6,
args["-c", "default"]) called by thread: main
INFO | jvm 2 | 2004/09/22 18:22:48 | Open socket to wrapper...
INFO | jvm 2 | 2004/09/22 18:22:48 | Opened Socket
INFO | jvm 2 | 2004/09/22 18:22:48 | Send a packet KEY :
rZuk3O5PJPe7hdQ1
INFO | jvm 2 | 2004/09/22 18:22:48 |
handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=1143])
DEBUG | wrapperp | 2004/09/22 18:22:48 | accepted a socket from
127.0.0.1 on port 1143
DEBUG | wrapperp | 2004/09/22 18:22:48 | read a packet KEY :
rZuk3O5PJPe7hdQ1
DEBUG | wrapper | 2004/09/22 18:22:48 | Got key from JVM: rZuk3O5PJPe7hdQ1
DEBUG | wrapperp | 2004/09/22 18:22:48 | send a packet LOW_LOG_LEVEL : 1
DEBUG | wrapperp | 2004/09/22 18:22:48 | send a packet PING_TIMEOUT : 300
DEBUG | wrapper | 2004/09/22 18:22:48 | Start Application.
DEBUG | wrapperp | 2004/09/22 18:22:48 | send a packet START : start
INFO | jvm 2 | 2004/09/22 18:22:48 | Received a packet
LOW_LOG_LEVEL : 1
INFO | jvm 2 | 2004/09/22 18:22:48 | Wrapper Manager: LowLogLevel
from Wrapper is 1
INFO | jvm 2 | 2004/09/22 18:22:48 | Received a packet PING_TIMEOUT
: 300
INFO | jvm 2 | 2004/09/22 18:22:48 | Wrapper Manager: PingTimeout
from Wrapper is 300000
INFO | jvm 2 | 2004/09/22 18:22:48 | Received a packet START : start
INFO | jvm 2 | 2004/09/22 18:22:48 | calling listener.start()
INFO | jvm 2 | 2004/09/22 18:22:48 | WrapperSimpleApp: start(args)
INFO | jvm 2 | 2004/09/22 18:22:48 | WrapperSimpleApp: invoking
main method
INFO | jvm 2 | 2004/09/22 18:22:48 | WrapperSimpleApp: main method
completed
INFO | jvm 2 | 2004/09/22 18:22:48 | WrapperSimpleApp: start(args)
end. Main Completed=true, exitCode=null
INFO | jvm 2 | 2004/09/22 18:22:48 | returned from listener.start()
INFO | jvm 2 | 2004/09/22 18:22:48 | Send a packet STARTED :
DEBUG | wrapperp | 2004/09/22 18:22:48 | read a packet STARTED :
DEBUG | wrapper | 2004/09/22 18:22:48 | JVM signalled that it was started.
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,343 INFO [Server]
Starting JBoss (MX MicroKernel)...
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Release ID: JBoss [WonderLand] 3.2.2 (build: CVSTag=JBoss_3_2_2
date=200310182216)
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Home Dir: C:\jboss-3.2.2
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Home URL: file:/C:/jboss-3.2.2/
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Library URL: file:/C:/jboss-3.2.2/lib/
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Patch URL: null
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Server Name: default
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Server Home Dir: C:\jboss-3.2.2\server\default
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Server Home URL: file:/C:/jboss-3.2.2/server/default/
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Server Data Dir: C:\jboss-3.2.2\server\default\data
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Server Temp Dir: C:\jboss-3.2.2\server\default\tmp
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Server Config URL: file:/C:/jboss-3.2.2/server/default/conf/
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Server Library URL: file:/C:/jboss-3.2.2/server/default/lib/
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,359 INFO [Server]
Root Deployemnt Filename: jboss-service.xml
INFO | jvm 2 | 2004/09/22 18:22:49 | 18:22:49,375 INFO [Server]
Starting General Purpose Architecture (GPA)...
INFO | jvm 2 | 2004/09/22 18:22:50 | 18:22:50,625 INFO
[ServerInfo] Java version: 1.4.2_02,Sun Microsystems Inc.
INFO | jvm 2 | 2004/09/22 18:22:50 | 18:22:50,625 INFO
[ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.4.2_02-b03,Sun
Microsystems Inc.
INFO | jvm 2 | 2004/09/22 18:22:50 | 18:22:50,625 INFO
[ServerInfo] OS-System: Windows 2000 5.0,x86
.... Jboss loading, deployment .... etc...
***************************************************
wrapper.conf :
###
#
###
#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=c:/j2sdk1.4.2_02/bin/java
# Java Main class. This class must implement the WrapperListener interface
# or guarantee that the WrapperManager class is initialized. Helper
# classes are provided to do this for you. See the Integration section
# of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=C:/jboss-3.2.2/lib/wrapper.jar
wrapper.java.classpath.2=C:/j2sdk1.4.2_02/lib/tools.jar
wrapper.java.classpath.3=C:/jboss-3.2.2/bin/run.jar
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=C:/jboss-3.2.2/lib;
wrapper.java.library.path.2=C:/Eldat Common Path;
# Java Additional Parameters
wrapper.java.additional.1=-server
wrapper.java.additional.2=-XX:NewSize=400m
wrapper.java.additional.3=-XX:PermSize=40m
wrapper.java.additional.4=-Xms512m
wrapper.java.additional.5=-Xmx512m
wrapper.java.additional.6=-Xloggc:C:\jboss-3.2.2\server\default\log\GC.log
wrapper.java.additional.7=-Dprogram.name=Wrapper
#wrapper.java.additional.6=-Xdebug
#wrapper.java.additional.7=-Xnoagent
#wrapper.java.additional.8=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8787
#wrapper.java.additional.9=-Djava.compiler=NONE
#wrapper.java.additional.10=-XX:+PrintGCTimeStamps
#wrapper.java.additional.11=-verbosegc
#wrapper.java.additional.12=-XX:+PrintGCDetails
#wrapper.java.additional.13=-XX:+PrintHeapAtGC
wrapper.debug=true
wrapper.startup.timeout=60
wrapper.shutdown.timeout=60
wrapper.jvm_exit.timeout=60
wrapper.ping.timeout=300
wrapper.ping.interval=240
wrapper.cpu.timeout=50
# Initial Java Heap Size (in MB)
wrapper.java.initmemory=512
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=512
# Application parameters. Add parameters as needed starting from 1
wrapper.app.parameter.1=org.jboss.Main
wrapper.app.parameter.2=-c
wrapper.app.parameter.3=default
#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console. (See docs for formats)
wrapper.console.format=PM
# Log Level for console output. (See docs for log levels)
wrapper.console.loglevel=DEBUG
# Log file to use for wrapper output logging.
wrapper.logfile=../server/default/log/wrapper.log
# Format of output for the log file. (See docs for formats)
wrapper.logfile.format=LPTM
# Log Level for log file output. (See docs for log levels)
wrapper.logfile.loglevel=DEBUG
# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix. For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=10m
# Maximum number of rolled log files which will be allowed before old
# files are deleted. The default value of 0 implies no limit.
wrapper.logfile.maxfiles=10
# Log Level for sys/event log output. (See docs for log levels)
wrapper.syslog.loglevel=NONE
#********************************************************************
# Wrapper NT Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.
# Name of the service
wrapper.ntservice.name=JBoss322
# Display name of the service
wrapper.ntservice.displayname=JBoss Application Server Service
# Description of the service
wrapper.ntservice.description=JBoss Application Server Service
# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=MySQL
# Mode in which the service is installed. AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START
# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false
|
|
From: Leif M. <le...@ta...> - 2004-09-24 04:45:24
|
Vadim,
Doing some research, I figured out that the function call I am
making to get the process exit
code is capable of returning the value of an uncaught exception that
killed the process. I will
modify the Wrapper for the 3.1.2 release to display more useful
information in this case.
In your case, the exception being thrown was
STATUS_STACK_OVERFLOW. This is
a low level error in the JVM implementation and not a Java level stack
overflow. Try looking
through the Sun bug database, or trying a newer JVM version. It may
have been fixed.
This was the kind of thing that the Wrapper was originally built for. :-)
Cheers,
Leif
Vadim Punski wrote:
> Hi!
> I've found a lot of posts started with " JVM process exited with a
> code", but no one with such a strange exit code.
> This could be reproduced by clicking 10-20 times on some button of the
> application in the browser.
> During button pressing the system not overloaded at all.
> The same thing works perfect during simple jvm execution w/o java
> wrapper.
> All timings and timeouts were extended up to 3-4 minutes, and pinging
> works perfect.
> wrapper.conf configuration added after log messages.
>
> Any ideas ?!
>
> Best Regards,
> Vadim
>
> DEBUG | wrapper | 2004/09/22 18:22:40 | JVM process exited with a
> code of -1073741571, setting the wrapper exit code to -1073741571.
> ERROR | wrapper | 2004/09/22 18:22:40 | JVM exited unexpectedly.
|
|
From: Leif M. <le...@ta...> - 2004-09-24 05:18:28
|
Vadim,
Also, if it is fairly easy for you to reproduce this problem, I
would appreciate it if you could
try out this new candidate for the 3.1.2 release. When the JVM
crashes, it should now display
an error message with the exception name even if debug output is disabled.
http://wrapper.tanukisoftware.org/tmp/3.1.2-e/wrapper_win32_3.1.2-e.zip
Cheers,
Leif
Leif Mortenson wrote:
> Vadim,
> Doing some research, I figured out that the function call I am
> making to get the process exit
> code is capable of returning the value of an uncaught exception that
> killed the process. I will
> modify the Wrapper for the 3.1.2 release to display more useful
> information in this case.
>
> In your case, the exception being thrown was
> STATUS_STACK_OVERFLOW. This is
> a low level error in the JVM implementation and not a Java level stack
> overflow. Try looking
> through the Sun bug database, or trying a newer JVM version. It may
> have been fixed.
> This was the kind of thing that the Wrapper was originally built for. :-)
>
> Cheers,
> Leif
>
> Vadim Punski wrote:
>
>> Hi!
>> I've found a lot of posts started with " JVM process exited with a
>> code", but no one with such a strange exit code.
>> This could be reproduced by clicking 10-20 times on some button of
>> the application in the browser.
>> During button pressing the system not overloaded at all.
>> The same thing works perfect during simple jvm execution w/o java
>> wrapper.
>> All timings and timeouts were extended up to 3-4 minutes, and pinging
>> works perfect.
>> wrapper.conf configuration added after log messages.
>>
>> Any ideas ?!
>>
>> Best Regards,
>> Vadim
>>
>> DEBUG | wrapper | 2004/09/22 18:22:40 | JVM process exited with a
>> code of -1073741571, setting the wrapper exit code to -1073741571.
>> ERROR | wrapper | 2004/09/22 18:22:40 | JVM exited unexpectedly.
>
|
