Domino HTTP Error Loading Java Virtual Machine
The error usually occurs because of a conflict with the Java heap size setting in the notes.ini file. Lowering value or completely removing JavaMinHeapSize entry should resolve the issue
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 the notes.ini file prevented the Java Virtual Machine (JVM) from loading.
Diagnosing the problem
Domino Server console reported the following messages:
The 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:
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 HCL support resources.
Learn more: HTTP/JVM Out of memory https://ds_infolib.hcltechsw.com/ldd/dominowiki.nsf/dx/HTTPJVM_Out_of_memory
Lotus Notes’ life support is over – what now?
End of support means end of life for old IBM-branded versions of Lotus Notes and Domino. It’s time to commit. Decide what to do with your existing IBM Domino infrastructure and databases: upgrade or finally retire your IBM Domino environment. Just don’t stay in a half-migrated deadlock.
Lotus Notes Data Migration and Archiving: Seascape for Notes
Seascape for Notes helps you preserve historical data outside of HCL Notes and Domino. It exports Lotus Notes databases as stand-alone PDF/XML/JSON archives, retaining documents, views, links, and metadata. Plus, Seascape enables the easy uploading of archived documents to Microsoft SharePoint or Office 365.
Last updated