Knowledgebase: Meeting Maker
HTTP status 539 or 500 in the PIM Log
Posted by - NA - on 29 June 2009 03:29 PM

One or more users are not able to sync PIM on their device to and or from Meeting Maker.

The NL PIM log shows the following error:

GetEventVCard: GetPimRequest failed, Http status = 539


GetEventVCard: GetPimRequest failed, Http status = 500

The Notifylink.log on Tomcat directory shows the following error:
Unable to parse sync anchor data: null


This error may be related to a memory issue on tomcat.

Tomcat by default uses a specific amount of memory.

To solve this issue:

Adding memory to Tomcat to handle the increased load will increase

performance and decrease problems.

From the Tomcat site at:

For Linux, Solaris and Mac OS X, add this line to your after the

comments section:

JAVA_OPTS="-Xms128m -Xmx512m -server"

Though many of the new Tomcat versions use single quotes instead:

JAVA_OPTS='-Xms128m -Xmx512m -server'

-Xms128m means that the minimum memory allocation will be 128 megs.

-Xmx512m means that the maximum memory allocation will not exceed 512 megs.

You may adjust either of these values for your environment.

If this is not enough memory then you may also try

JAVA_OPTS="-Xms512m -Xmx1024m -server"

Windows users may do the same if using the scripts to start the server but

add it the catalina.bat file

Otherwise Windows users running the executable may select the service from

the system tray and select the Java tab and enter the memory limits you

would prefer and select Apply.

You will need to restart Tomcat for the settings to take effect.