Zitat von Martijn Brinkers <[email protected]>:
On 12/05/2012 10:11 AM, [email protected] wrote:today we discovered teh following error in the Djigzo logfile: JVM appears hung: Timed out waiting for signal from JVM. JVM did not exit on request, terminated JVM received a signal SIGKILL (9). Launching a JVM... java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.5) (6b24-1.11.5-0ubuntu1~10.04.2) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) WrapperManager: Initializing... Phoenix 4.2 configure DjigzoServiceImpl. Configuring Djigzo Service. **** Begin system properties **** -- listing properties -- java.runtime.name=OpenJDK Runtime Environment sun.boot.library.path=/usr/lib/jvm/java-6-openjdk/jre/lib/a... java.vm.version=20.0-b12 java.vm.vendor=Sun Microsystems Inc. java.vendor.url=http://java.sun.com/ path.separator=: java.vm.name=OpenJDK 64-Bit Server VM file.encoding.pkg=sun.io user.country=US sun.java.launcher=SUN_STANDARD sun.os.patch.level=unknown wrapper.key=4V2wL5mowdmofv_Z java.vm.specification.name=Java Virtual Machine Specification user.dir=/usr/share/djigzo wrapper.version=3.4.1 java.runtime.version=1.6.0_24-b24 java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment phoenix.home=/usr/share/djigzo/james-2.3.1 djigzo.charset-alias-provider.properties=conf/charset-aliases.properties java.endorsed.dirs=/usr/lib/jvm/java-6-openjdk/jre/lib/e... os.arch=amd64 java.io.tmpdir=/tmp line.separator= java.vm.specification.vendor=Sun Microsystems Inc. wrapper.cpu.timeout=10 os.name=Linux sun.jnu.encoding=UTF-8 java.library.path=./wrapper/ wrapper.jvm.port.max=31999 java.specification.name=Java Platform API Specification java.class.version=50.0 java.naming.provider.url=djigzo sun.management.compiler=HotSpot 64-Bit Tiered Compilers wrapper.pid=1939 os.version=2.6.32-45-server networkaddress.cache.ttl=300 wrapper.java.pid=6134 user.home=/usr/share/djigzo user.timezone=Europe/Berlin wrapper.jvmid=2 java.awt.printerjob=sun.print.PSPrinterJob java.specification.version=1.6 file.encoding=UTF-8 user.name=djigzo java.class.path=james-2.3.1/bin/phoenix-loader.jar:wr... mail.mime.decodetext.strict=false java.naming.factory.initial=tyrex.naming.MemoryContextFactory java.vm.specification.version=1.0 wrapper.port=15012 sun.arch.data.model=64 java.home=/usr/lib/jvm/java-6-openjdk/jre sun.java.command=org.apache.avalon.phoenix.launcher.Da... djigzo.smime.outlook2010skiworkaround.enable=false java.specification.vendor=Sun Microsystems Inc. user.language=en java.vm.info=mixed mode java.version=1.6.0_24 java.ext.dirs=james-2.3.1/lib:./james-2.3.1/tools/lib sun.boot.class.path=/usr/lib/jvm/java-6-openjdk/jre/lib/r... java.vendor=Sun Microsystems Inc. file.separator=/ java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport... sun.cpu.endian=little sun.io.unicode.encoding=UnicodeLittle mail.mime.parameters.strict=false wrapper.native_library=wrapper wrapper.jvm.port.min=31000 sun.cpu.isalist= **** End system properties **** spring config file: conf/spring/djigzo.xml additional spring config dir: conf/spring/spring.d/ log4j config file: conf/log4j.properties Obviously Djigzo decided to restart but the strange thing is that it was working normal at this point. I have checked the logfiles and it looks like happend some times already but with increasing frequency. Any idea what could be wrong?The djigzo backend is started by the Java wrapper process. The Java wrapper process monitors the JVM to see whether the JVM is still running and if not it will restart it. Somehow the JVM was hanging or the Java wrapper incorrectly assumed it was hanging and restarted the backend. I have seen this happen when the gateway runs under VMWare with overcommitted memory and not setting all memory of the virtual machine as reserved. If memory is overcommitted and the memory of the virtual machine is not fully reserved the virtual machine swaps the memory to disk which kill the Java performance. Are you running the gateway virtualized or on real hardware? Kind regards, Martijn
This is real Hardware and no memory shortage either. Djigzo was working as expected at the time it was killed. Today where it was noticed i was even working in the admin console, so it should be no stall of Djigzo but more of a false restart trigger.
Regards Andreas
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list [email protected] http://lists.djigzo.com/lists/listinfo/users
