Lase_server indicates a message is too large

The message “lase_server logging issue – Invalid message is received and size” indicates that an error message that is too large has been sent from the security server.

Example full message text

default.SEVERE server.SecurityEventHandler.run(): SecurityEventHandler #816 got exception. com.lawson.security.server.LawsonNetException: Got exception while reading from connection Socket[addr=/127.0.0.1,port=64706,localport=450000].

Stack Trace : com.lawson.security.server.LawsonNetException: Got exception while reading from connection Socket[addr=/127.0.0.1,port=6406,localport=50000].

at com.lawson.security.server.AbstractDefaultEventSource.read(AbstractDefaultEventSource.java:339)

at com.lawson.lawsec.server.SecurityEventHandler.run(SecurityEventHandler.java:151)

Caused by: java.io.IOException: Invalid message is received and size:300095616

at com.lawson.security.server.AbstractDefaultEventSource.readMsg(AbstractDefaultEventSource.java:351)

at com.lawson.security.server.AbstractDefaultEventSource.read(AbstractDefaultEventSource.java:352)

Resolution

The parameter server.readMsgMaxSize must be added to lsservice.properties.

The MsgMaxSize parameter ensures that a logging message that occurs when a vulnerability scan is run does not become so large that it causes the system to hang. The parameter catches very large messages and replaces them with shorter sample messages.

Perform these steps to add the parameter.

1. Stop the Infor environment and the application server.
2. Open the lsservice.properties file for editing.
   On Landmark, the location is: LASYSDIR/lsservice.properties
   On LSF, the location is: LAWDIR/system/lsservice.properties
3. Add the parameter server.readMsgMaxSize=[size number in Bytes] to the end of the file. The default size is 20MB. Infor recommends not setting the size larger than 40MB.
   Example: server.readMsgMaxSize=20
4. Restart the Infor environment and the application server.