Guidance for updating agent or logger JVM options

If we use the -serviceJVMOptions parameter of the fteModifyAgent or fteModifyLogger command to modify an existing Windows Service definition for an agent or logger by updating, adding, or removing Java system properties, the existing Windows Service is first deleted before a new one is created in its place, and the agent or logger properties file is updated with the properties for the new Windows Service. The new Windows Service definition must be consistent with the updated Windows Service properties that are defined in the agent or logger properties file.

From IBM MQ Version 9.0.0, Fix Pack 4, additional checks are added under APAR IT22423 such that any updates that are made to the JVM options for an agent or logger with the -serviceJVMOptions parameter of the fteModifyAgent or fteModifyLogger command are verified to make sure that the options have been correctly specified. If the properties are found to be invalid, or otherwise could not be validated, the fteModifyAgent or fteModifyLogger command fails and an appropriate error message is displayed.

If the JVM properties are valid and the deletion of the existing Windows Service is successful, but a failure then arises when the fteModifyAgent or fteModifyLogger command is creating the new Windows Service, the command attempts to remove the properties that define the replacement Windows Service from the agent or logger properties file. In this case, error messages are returned to explain that the agent or logger could not be modified, the old Windows Service was deleted but a new Windows Service could not be created and the agent or logger will therefore not run as a Windows Service. We must then manually verify that the state of the Windows Service definition is consistent with the Windows Service properties that are defined in the agent or logger properties file, and take the appropriate action to correct any inconsistencies.

Parent topic: MFT general troubleshooting


Related information