-
Title
Persistent script [mergeAttributes] not found -
Description
After upgrading, customer is seeing these error messages for JMX cart. JMX is upgraded to 5.8.1 as well
2012-07-06 09:28:27.622 ERROR [main] com.quest.nitro.service.topology.TopologyAdjustmentService - Topology merge rule "foglight-5:NamedScriptMergeRule:bc847754-d2bf-4afa-81bd-ddbefb3fc4aa:1 datasource=foglight-5:foglight-5 (JMXMBeanTypeAttributes) " could not be loaded. This rule will be ignored.
java.lang.IllegalArgumentException: Invalid script in merge rule: foglight-5:NamedScriptMergeRule:bc847754-d2bf-4afa-81bd-ddbefb3fc4aa:1 datasource=foglight-5:foglight-5
at com.quest.nitro.service.topology.TopologyAdjustmentService$NamedScriptRuleFactory.buildRule(TopologyAdjustmentService.java:748)
at com.quest.nitro.service.topology.TopologyAdjustmentService.createMergeRule(TopologyAdjustmentService.java:441)
at com.quest.nitro.service.topology.TopologyAdjustmentService.loadRules(TopologyAdjustmentService.java:344)
at com.quest.nitro.service.topology.TopologyAdjustmentService.reloadRules(TopologyAdjustmentService.java:177)
at com.quest.nitro.service.topology.TopologyAdjustmentService.startService(TopologyAdjustmentService.java:159)
at com.quest.nitro.service.AbstractNitrogenService.start(AbstractNitrogenService.java:103)
at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
a.......
Caused by: com.quest.nitro.service.sl.interfaces.scripting.ScriptingException: Persistent script [mergeAttributes] not found
at com.quest.nitro.service.scripting.ScriptingService.prepareScript(ScriptingService.java:475)
at com.quest.nitro.service.topology.TopologyAdjustmentService$NamedScriptRuleFactory.buildRule(TopologyAdjustmentService.java:744)
... 231 more -
Cause
JMX-431. The root cause of the error is "Persistent script [mergeAttributes] not found".
And this particular persistable script was not found on the FMS, hence the error.
This particular FMS is a federation Master and no persistable scripts are available on the master. So this is actually a bug on the JMX-cart not to call the merge script rule specifically on a Federation Master.
-
Resolution
For JMX cartridge, federation isn't supported anyways...so they are not missing out on anything other than the couple of errors they see during their FMS startup...
Its a cartridge defect in 5.8.x. There is a workaround which we can try
1. Navigate to FMS_HOME\state\cartridge.exploded\\JMXCartridge-5_8_1\JMXCartridge-Scripts-5_8_1\scripts-monitoring-policy.xml and backup the scripts-monitoring-policy.xml file. (monpolicy_backup.xml)
2. Copy over the attached file to this location.
3. Navigate to the FMS jmx-console and import this xml:
a. In the jmx-console, search for "service=ImportExport"
b. Invoke "exportToFile" with a parameter say c:\monpolicy_beforeimport.xml
c. Invoke "importFromFile" with the parameter pointing to the location of the attached xml file
d. Invoke "exportToFile" with a parameter say c:\monpolicy_afterimport.xml
4. If this workaround corrected the problem, the error messages should now stop.
5. Generate a fresh support bundle. -
Attachments