Installation and Upgrade Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Troubleshooting Lotus Notes Portlets

The table on the following page summarizes cases in which users encountered unexpected results with the Lotus Notes Portlets. Use this table as a reference for troubleshooting any similar problems you might encounter.

Application logs for Lotus Notes Portlets are located in the following folder: <PT_HOME>\PortletSuiteLotusNotes\3.4\settings\logs.

Error
Solution
Port conflict, port in use, BindException
Edit the HTTP and HTTPS settings in application.conf to set the value to an available port (<PT_HOME>/PortletSuiteLotusNotes/3.4/settings/ config/application.conf). The service must be restarted to pick up changes made in the configuration file. Note that changes to a service port number require corresponding changes to any Web service or remote server settings that reference that port number.
Memory consumption, Out of Memory Errors
The maximum amount of memory (MB) that the service JVM will be allowed to use is controlled by the wrapper.java.maxmemory property, configured in the file <PT_HOME>/PortletSuiteILotusNotes/3.4/settings/config/wrapper.conf. For example, the following line shows a maximum memory setting of 1 GB:
wrapper.java.maxmemory=1024
The setting corresponds directly to the -Xmx parameter used by the java executable. The default value of this setting in the config file is adequate for most configurations. For large production configurations, especially those in which the service is installed on a dedicated host machine, this value should be set as high as possible (for example, 1024 or 1536) but should always remain below the amount of physical RAM on the host machine.


  Back to Top       Previous  Next