Problem Domino HTTP fails to load Java Virtual Machine. As result, the HTTP task fails to start. Cause Conflict with Java heap size settings in notes.ini file prevented the Java Virtual Machine (JVM) from loading. Diagnosing the problem Domino Server console reported following messages: 03/29/2011 08:39:58 AM HTTP JVM: JVMJ9GC019E -Xms too large for -Xmx 03/29/2011 08:39:58 AM HTTP JVM: JVMJ9VM015W Initialization error for library j9gc24(2): Failed to initialize 03/29/2011 08:39:58 AM JVM: The Java Virtual Machine creation returned an invalid JVM machine pointer. 03/29/2011 08:39:58 AM JVM: Java Virtual Machine failed to start 03/29/2011 08:39:58 AM HTTP Server: Error Loading Java Virtual Machine 03/29/2011 08:39:58 AM HTTP Server: JVM: Missing entrypoint in JVM runtime library. 03/29/2011 08:39:58 AM HTTP Server: Shutdown Message "-Xms too large for -Xmx" indicates that the initial Java heap size is larger than the maximum Java heap size. In one case, the Notes.ini file had the following parameters: HTTPJVMMaxHeapSize=64M HTTPJVMMaxHeapSizeSet=1 JavaMaxHeapSize=268435456 JavaMinHeapSize=134217728 The JavaMinHeapSize of 128MB is set higher than the HTTP's JVM heap size 64MB. Resolving the problem The solution is to remove or lower JavaMinHeapSize (JavaMinHeapSize=67108864) or alternatively, increase HTTPJVMMaxHeapSize to 128M (HTTPJVMMaxHeapSize=128M). Note: This article is copied from IBM support resources. Original article is here. |
|
|