[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.

[Tim Fox (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12362036 ] 
            
Tim Fox commented on JBMESSAGING-957:
-------------------------------------

We will only be able to support the all configuration from 4.2 onwards.

Also we we will need some way of handling server identity without each node maintaining it's own id. 

Currently each node maintains its own id in messaging-service.xml.

For integration with AS clustering, we need the JBM config to be identical on each node.

So we need some way of persistently determining server identity from inside the code. I'd like to understand how AS clustering does this (if they do it at all).

> Provide a configuration(installation) that will work in the All configuration.
> ------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-957
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-957
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Configuration and Management
>            Reporter: Jay Howell
>         Assigned To: Clebert Suconic
>             Fix For: 1.2.0.SP2
>
>
> When using the installation process for messaging, you install and it creates a new container based on the Default container.  We need to also be able to have one for the All container also.  Many customers want to run Messaging in clustered mode as well as everything else.  The all configuration is the current way to do this. 
> Note: Here's some background and some problems you may run into with the install of messaging 1.2.0 sp2 on 4.0.5 using an all configuration.  Had an instance yesterday, where the customer moved thier clusterd post office configuration to all.  This works as long as messaging is deployed in a scoped classloader.  I know that sp2 will copy the remoting and aop libs into the main lib directory for the container in order to avoid the scoped classloader.  So I had the customer do what sp 2 will do, copy over the old remoting and aop jars.  Becasue messaging is using an updated version of jgroups also, and jgroups is in the lib directory of the container, it picks that one up first before the one in messaging.  We copied over the jgroups jar just as we did for remoting and aop. I found that the container comes up with no problem, but I can no longer get to jconsole and things don't work correctly(no errors, but it won't work either).  I don't know what the problem is, but running the all configuration with the clustered post office without a scoped classloader seems to have problems.
> Jay:)

-- 
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