ShowTable of Contents
This article is intended to act as a repository for guidance, best practices, known issues, and problems related to upgrading XPages applications to version 8.5.2.
If you have upgraded Domino Server to Release 8.5.2 and you seem to be get unextended errors when running XPages applications. If these errors seem to get resolved by a server restart and the log messages refer to memory problems (stack overflow errors, for example), then you may need to set HTTPJVMMaxHeapSize in notes.ini
See the following IBM Tech Note :- What is the HTTPJVMMaxHeapSize notes.ini parameter in Domino 8.5 and what should it be set to?
. In summary,
- Beginning in Domino 8.5, a new notes.ini file parameter, HTTPJVMMaxHeapSize=256M , was added to control memory allocation to allow the new XPages functionality to work correctly.
- In prior releases, the default memory allocation was 64MB
- 64MB will be the new default value for 8.5.2 and later.
By default, for releases 8.5 and 8.5.1, the default setting was 256. If Domino server is upgraded to 8.5.2, the default setting is reset back down to 64M. Therefore, the HTTPJVMMaxHeapSize parameter will have to be set manually to 256M in notes.ini.
Note(1): This advice only applies to 32-bit platforms.
Note(2): From Releases 8.5.1FP5 and 8.5.2 onwards, HTTPJVMMaxHeapSizeSet=1 will also have to be set to prevent Domino server from resetting the manually enteredHTTPJVMHeapSize setting in notes.ini back to 64M from 256M.
XPages 851 used to transparently handle an infinite loop of page reloads in your code
If your XPages code used to somehow trigger and infinite loop of page reloads, for example,Best Tax Attorneys in San Diego
XPages Release 8.5.1 used to handle it transparently. Now when you upgrade your application to release 8.5.2, you get:
HTTP Web Server: Command Not Handled Exception
See this lotusnotus.com blog entry
for more details