FileReader Won't Restart on Detection Servers After 64bit Tuning

Products

• Data Loss Prevention Network Monitor

Issue/Introduction

Scenario: Customer has just made adjustments to their Detection Servers memory settings copied directly from the 64bit Tuning Guide.

 

In the console you will see Error Code 1008 once these memory changes have been made under the Server Settings>BoxMonitor.FileReaderMemory setting.

Also, if you see the following log snippet in the VontuMonitor.log file, you will know by the invalid ascii characters(–), that they have copied the memory settings out of the 64bit Tuning Guide directly.

INFO   | jvm 5    | 2013/02/19 08:53:41 | FR> Could not find the main class: –Xms2048M.  Program will exit.
INFO   | jvm 5    | 2013/02/19 08:54:03 | FR> Exception in thread "main" java.lang.NoClassDefFoundError: –Xms2048M
INFO   | jvm 5    | 2013/02/19 08:54:03 | FR> Caused by: java.lang.ClassNotFoundException: –Xms2048M

Resolution

Notice the longer dashes on the 64bit Tuning Guides Memory Configuration.

example:
correct:
-Xrs -Xms2048M -Xmx16384M

incorrect:

-Xrs –Xms2048M –Xmx16384M
(Notice the longer 2nd and 3rd dashes)

 

In order to fully resolve this you will need to change the long dash(–) to the proper short ascii dash(-).

 

Related KB Article#55422