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

[Brian Stansberry (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12362201 ] 
            
Brian Stansberry commented on JBMESSAGING-957:
----------------------------------------------

Sorry, took me a while to get to my 'JIRA' folder today.

I opened a forum thread for modifying run.sh -- see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=108609.  I think using run.sh is OK, but am interested in any other use cases.  I think having to set 2 properties, one an int for JBM and one a string for other uses would suck though.

You don't see the jvmRoute stuff anywhere because it has to be manually added; not there by default.  It's added to the Engine element in server.xml if mod_jk is used.  See step 8 of http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingMod_jk1.2WithJBoss.

It's not there by default because Tomcat will append the value to every session cookie, which is a waste if JK is not used.  That's why I'd like the system property substition logic to support a null default.

> 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