1 Reply Latest reply on Jan 23, 2014 1:45 PM by tcunning

I did a esb service and publish it as a web service, the problem is that when I alert monitors for the service I did, the first time it works, if I turn off the jboss server and turn on the alert again no longer works and tells me the esb service is not r

mariaerdguez Jan 23, 2014 1:23 PM

--- MBeans waiting for other MBeans ---

ObjectName: jboss.monitor:service=ServiceInvoker_messages_failed_count

State: FAILED

Reason: javax.management.InstanceNotFoundException: jboss.esb:category=MessageCounter,deployment=Rosaly_Prueba.esb,uid=13642944,service-category=invocacion,service-name=ServiceInvoker is not registered.

I Depend On:

jboss.alerts:service=ConsoleAlertListener

ObjectName: jboss.monitor:service=ESBActionListarEstudiantesMessagesMonitor

State: FAILED

Reason: javax.management.InstanceNotFoundException: jboss.esb:category=MessageCounter,deployment=Rosaly_Prueba.esb,service-category=central,service-name=Servicio is not registered.

I Depend On:

jboss.alerts:service=ConsoleAlertListener

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---

ObjectName: jboss.monitor:service=ESBActionListarEstudiantesMessagesMonitor

State: FAILED

Reason: javax.management.InstanceNotFoundException: jboss.esb:category=MessageCounter,deployment=Rosaly_Prueba.esb,service-category=central,service-name=Servicio is not registered.

I Depend On:

jboss.alerts:service=ConsoleAlertListener

ObjectName: jboss.monitor:service=ServiceInvoker_messages_failed_count

State: FAILED

I Depend On:

jboss.alerts:service=ConsoleAlertListener

1. Re: I did a esb service and publish it as a web service, the problem is that when I alert monitors for the service I did, the first time it works, if I turn off the jboss server and turn on the alert again no longer works and tells me the esb service is n

tcunning Jan 23, 2014 1:45 PM (in response to mariaerdguez)

I'm confused what's happening here - are you doing email alerts based on JMX properties? And you rebooted, and alerts wouldn't start?

If that's the case, I think you just have a dependency issue here. Your alert depends on the ESB being deployed, and the server may be trying to deploy the alert first. Can you paste your alert mbean XML? If you add the ESB deployment to the deployment-list, that should solve the problem.
Actions