MID Server not using remote.properties

[mlobonexthink]

Hi all,

I think I detected a bug in MID Server application (mid-jre.istanbul-09-23-2016__patch0-10-05-2016_11-18-2016_1553.linux.x86-64).

MID Server manages a file, inside "/work" directory, named "remote.properties". My undestanding is: MID Server ask ServiceNow instance about mid.* properties and download them to this remote.properties file. In fact, in the header of this file, you can see the timestamp of the last update. This file is properly updated with the data from ServiceNow instance. So far, so good.

However, the values stored in this remote.properties file are not used by MIDServer application in execution time.

For example, this is my remote.properties file in the MID Server machine:

#Remote properties loaded from https://devxxxxxx.service-now.com/
#Thu Mar 30 14:43:48 CEST 2017
mid.property.ssh.use_snc=true
mid.eccq.max_payload_size=80000000000
mid.property.powershell.command.script.parameter_passing=false
mid.discovery.max_payload_size=50000000000

Now, I restart the midserver.

Then, from ServiceNow, I create a new REST Message using a MIDServer for the communication. This REST Message just ask for BIG text file, like >20000000 bytes. If you execute this REST Message and you check the MIDServer log $MIDSERVERINSTALLATION/agent/logs/agent0.log.0 you will see an error message like:

ECCSender.1 SEVERE *** ERROR *** Payload size of 185790955 bytes exceeded maximum of 20000000 bytes.
Contents of the original payload were moved to /XXXXXXX/agent/work/monitors/ECCSender/output_oversize/ecc_queue.aa3588c60fb13200487065ba32050e1b.xml on the MID server.
Maximum payload size can be set with mid config parameter: mid.eccq.max_payload_size

In the error, you can see that "[...] 185790955 bytes exceeded maximum of 20000000 bytes [...]". So, instead to use value 80000000000, MIDServer is still using default value 20000000.

So, the value for mid.eccq.max_payload_size property stored in remote.properties file is not used, MIDServer does not care about the value in that field.

Any thoughts about how to fix this in the MIDServer?

Thank you for your help.

Cheers,

Marcos.

[mariochanes]

For each Midserver
Related Lists > Configuration Parameters

Create a new parameter
name:   mid.eccq.max_payload_size
value: 50000000

The value can be adjusted as need. Default was 20000000?

[Karthick Nagara]

Actually I added the property 'mid.eccq.max_payload_size' with value 50000000 in the MID server's agent\config.xml file and restarted the MID server.

It worked fine and also I can see the property under MID SERVERS --> Configuration Parameters after the restart of MID server. Moving forward I can edit the value from the UI itself