[jboss-jira] [JBoss JIRA] Updated: (JBAS-4718) Handle or prevent duplicate invocation of lifecycle callbacks

[Brian Stansberry (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4718?page=all ]

Brian Stansberry updated JBAS-4718:
-----------------------------------

    Description: The JMX interfaces for a number of clustering beans expose the old ServiceMBean lifecycle methods.  Effect of that is that the lifecycle methods get invoked twice -- once by the MC for the pojo service, and once by the ServiceController for the proxy created via the @JMX annotation on the bean.  This duplicate invocation leads to errors as shown in the forum.  (was: The JMX interfaces for a number of clustering beans expose the old ServiceMBean lifecycle methods.  Effect of that is that the lifecycle methods get invoked twice -- once by the MC for the pojo service, and once by the ServiceController for the proxy created via the @JMX annotation on the bean.  This duplicate invocation leads to errors as shown in the forum.

Likely solution is to change the various services so they don't implement ServiceMBean.  Then change the name of the lifecycle methods to something the ServiceController doesn't recognize.  Annotate the methods so the microcontainer recognizes them.

Another solution is to have the services be aware of their current lifecycle state and ignore meaningless lifecycle callbacks.  The JBoss Cache JMX wrappers do that.)

> Handle or prevent duplicate invocation of lifecycle callbacks
> -------------------------------------------------------------
>
>                 Key: JBAS-4718
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4718
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-5.0.0.Beta2
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The JMX interfaces for a number of clustering beans expose the old ServiceMBean lifecycle methods.  Effect of that is that the lifecycle methods get invoked twice -- once by the MC for the pojo service, and once by the ServiceController for the proxy created via the @JMX annotation on the bean.  This duplicate invocation leads to errors as shown in the forum.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira