Data Loss Prevention

INFO   | jvm 3    | 2017/09/17 19:01:48 | FR> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128M; support was removed in 8.0
INFO   | jvm 3    | 2017/09/17 19:01:48 | FR> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
INFO   | jvm 3    | 2017/09/17 19:01:53 | FR> Exception in thread "main" java.lang.NullPointerException
INFO   | jvm 3    | 2017/09/17 19:01:53 | FR>   at com.vontu.messaging.FileReader.stop(FileReader.java:620)
INFO   | jvm 3    | 2017/09/17 19:01:53 | FR>   at com.vontu.messaging.FileReaderSetup.initialize(FileReaderSetup.java:115)
INFO   | jvm 3    | 2017/09/17 19:01:53 | FR>   at com.vontu.messaging.FileReader.main(FileReader.java:270)
INFO   | jvm 3    | 2017/09/17 19:02:20 | FR> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128M; support was removed in 8.0
INFO   | jvm 3    | 2017/09/17 19:02:20 | FR> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
INFO   | jvm 3    | 2017/09/17 19:02:25 | FR> Exception in thread "main" java.lang.NullPointerException
INFO   | jvm 3    | 2017/09/17 19:02:25 | FR>   at com.vontu.messaging.FileReader.stop(FileReader.java:620)
INFO   | jvm 3    | 2017/09/17 19:02:25 | FR>   at com.vontu.messaging.FileReaderSetup.initialize(FileReaderSetup.java:115)
INFO   | jvm 3    | 2017/09/17 19:02:25 | FR>   at com.vontu.messaging.FileReader.main(FileReader.java:270)

Not sure what the question is..

The events you are seeing are INFORMATIONAL and nothing looks wrong with the system.

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0

The errors are about an older setting that is within the FileReader.properties file that sets the upper and lower limits of the JVM. This is not an issue, but you can change them so they are more up to date.

Edit the files so it is 512 and 1024 or higher.

Good Luck

Ronak

PLEASE MARKED SOLVED

Hi Ronak;

Thanks for the answer;

I try to configure Network prevent Email, but service is not Starting;

Name	Monitor 1
Host	127.0.0.1
Port	8100
Version	14.6.0.32030
Status	Starting[recycle]
CPU Usage	8%
Physical Memory	21%
Disk Usage	78%

You are running the DLP console and the Email Prevent on the same server? Is the DB on the same server too?

How much Total memory do you have?

Also have you changed the PORT settings for the email prevent server, by default they are 10026 and 10025 (See the Server Configuration page at the bottom), you should change them both to 25. Then recycle the service. 

Go to the General Settings page and check the Advance Control box, this will show you what service is failing.

Good Luck

Ronak

PLEASE MARKED SOLVED

Hi Ronak;

Yes, Same Server, DB and all, because i´m small;

Total Memory is 16GB, and 4 CPU;

License

Status

Name	Monitor 1
Host	127.0.0.1
Port	8100
Version	14.6.0.32030
Status	Starting[recycle]
DetectionServerDatabase Status	Running[stop]
FileReader Status	Starting[terminate]
RequestProcessor Status	Stopped[start]
CPU Usage	7%
Physical Memory	19%
Disk Usage	78%

Hi Ronak;

I use VM Server;

Best Regards

OK..

Did you change the settings? 

Also have you changed the PORT settings for the email prevent server, by default they are 10026 and 10025 (See the Server Configuration page at the bottom), you should change them both to 25. Then recycle the service. 

Since you have SO little memory, you may will have to edit the FileReader.properties file and reduce the setting. Look for the HEAP settings, play with those numbers.

Keep in ind that the VM is VERY UNDER POWERED... it will bairly run. 16GB is not enough to really have the DB and other services run well.

Good Luck

Ronak

PLEASE MARKED SOLVED

Hi;

Yes, I made changes and it is attached;
I have also changed memory for 32GB;

But problem continue;

Best Regards

Gaudencio Fernandes