Via JBoss Operations Network 3.1.2 GUI I am adding a CLI-Notification to an alert template in JBossAS5.  The condition is a drift definition regex.

When populating the notification tab: Add, -> CLI, I select the Server-Side CLI script from the repo, I click okay(No issues), Then click save.  After I hit save an error at the top of the UI displays "Alert Definition failed to update".  Below is the stack trace.

I spot checked some of these resourceIds and they do come back as valid EAP instances.

Message :

Alert definition update failed

Severity :

Error

Time :

Thursday, September 12, 2013 6:15:16 PM UTC-4

Detail :

java.lang.RuntimeException:[1379024116794] org.rhq.enterprise.server.alert.AlertDefinitionUpdateException:Failed to re-create child AlertDefinition for Resources [10012, 10013, 10015, 10016, 10017, 13061, 10018, 10019, 10020, 10002, 10003, 10004, 10005, 10006, 10007, 10009, 10010, 13071, 13211, 12043, 12059, 12060, 12048, 12049, 13261, 12057, 12058, 12046, 12047, 12044, 12054, 12055, 12053, 11149, 11150, 11681, 12941, 12942, 11839, 11840, 11841, 13321];  -> javax.ejb.EJBTransactionRolledbackException:null -> java.lang.NullPointerException:null

--- STACK TRACE FOLLOWS ---

[1379024116794] org.rhq.enterprise.server.alert.AlertDefinitionUpdateException:Failed to re-create child AlertDefinition for Resources [10012, 10013, 10015, 10016, 10017, 13061, 10018, 10019, 10020, 10002, 10003, 10004, 10005, 10006, 10007, 10009, 10010, 13071, 13211, 12043, 12059, 12060, 12048, 12049, 13261, 12057, 12058, 12046, 12047, 12044, 12054, 12055, 12053, 11149, 11150, 11681, 12941, 12942, 11839, 11840, 11841, 13321];  -> javax.ejb.EJBTransactionRolledbackException:null -> java.lang.NullPointerException:null

   at Unknown.java_lang_Throwable_Throwable__V(http://rhq-server.example.com:7080/coregui/org.rhq.enterprise.gui.coregui.CoreGUI/9D91F7D263732396B464285EB27061C8.cache.html@3)

   at Unknown.java_lang_Exception_Exception__V(http://rhq-server.example.com:7080/coregui/org.rhq.enterprise.gui.coregui.CoreGUI/9D91F7D263732396B464285EB27061C8.cache.html@36)

   at Unknown.java_lang_RuntimeException_RuntimeException__V(http://rhq-server.example.com:7080/coregui/org.rhq.enterprise.gui.coregui.CoreGUI/9D91F7D263732396B464285EB27061C8.cache.html@36)

   at Unknown.com_google_gwt_user_client_rpc_core_java_lang_RuntimeException_1FieldSerializer_instantiate__Lcom_google_gwt_user_client_rpc_SerializationStreamReader_2Ljava_lang_RuntimeException_2(http://rhq-server.example.com:7080/coregui/org.rhq.enterprise.gui.coregui.CoreGUI/9D91F7D263732396B464285EB27061C8.cache.html@10)

   at Unknown.com_google_gwt_user_client_rpc_impl_SerializerBase$MethodMap_$instantiate__Lcom_google_gwt_user_client_rpc_impl_SerializerBase$MethodMap_2Lcom_google_gwt_user_client_rpc_SerializationStreamReader_2Ljava_lang_String_2Ljava_lang_Object_2(http://rhq-server.example.com:7080/coregui/org.rhq.enterprise.gui.coregui.CoreGUI/9D91F7D263732396B464285EB27061C8.cache.html@35)

...

...

...

...

Here is a snippet from where I believe the error originates.

137        for (Integer resourceId : resourceIdsForType) {

138            try {

139                // construct the child

140                AlertDefinition childAlertDefinition = new AlertDefinition(alertTemplate);

141                childAlertDefinition.setParentId(alertTemplate.getId());

142

143                // persist the child using overlord

144                alertDefinitionManager.createAlertDefinition(overlord, childAlertDefinition, resourceId);

It seems that it recreates the alert definitions for each instance with the new cli alert. Would it make sense to remove all alert definitions and try again?