[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1649) redesign management replication

Clebert Suconic (JIRA) jira-events at lists.jboss.org
Fri Jul 24 11:38:33 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clebert Suconic updated JBMESSAGING-1649:
-----------------------------------------

    Fix Version/s: 2.0.0
                       (was: 2.0.0.beta4)


> redesign management replication
> -------------------------------
>
>                 Key: JBMESSAGING-1649
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1649
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 2.0.0 Beta1
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>             Fix For: 2.0.0
>
>
> In order for management operation using JMX to be replicated, the MBeans are translating the management
> operation to a management messages which is sent to the management address using Core API. This allows
> for management messages to be properly replicated.
> However this allow forces the server to have an acceptor and a connector to talk to *itelsf* which is configusing
> and clutter the server configuration.
> The management code should be redesigned to be plugged directly on the server-side. The management 
> service'd no longer send a Core message using the Core API. Instead it'd call directly the ServerSessionPacketHandler
> (or equivalent) to handle a packet corresponding to the management message. It'll work since the handler will then
> replicate the packet correctly.

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

        



More information about the jboss-jira mailing list