[JBoss JIRA] Created: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
11:45 a.m.
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
Affects Versions: 1.2.0.SP2
Reporter: Jay Howell
Assigned To: Tim Fox
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
11:45 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=all ]
Jay Howell reassigned JBMESSAGING-957:
--------------------------------------
Assignee: Clebert Suconic (was: Tim Fox)
Assigning this to Clebert since he is doing the install for Messaging in sp2
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
Affects Versions: 1.2.0.SP2
Reporter: Jay Howell
Assigned To: Clebert Suconic
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
6:49 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-957:
---------------------------------------------
but I can no longer get to jconsole
How do I do that?
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
Affects Versions: 1.2.0.SP2
Reporter: Jay Howell
Assigned To: Clebert Suconic
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
10:51 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=all ]
Tim Fox updated JBMESSAGING-957:
--------------------------------
Fix Version/s: 1.2.0.SP2
Affects Version/s: (was: 1.2.0.SP2)
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
5:07 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-957:
-------------------------------------
Yes, we only currently work with the non clustered (non all) configuration.
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
6:09 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12... ]
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
9:15 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12... ]
Brian Stansberry commented on JBMESSAGING-957:
----------------------------------------------
AS clustering does something in this area with a hack. You can see it in cluster module,
o.j.ha.framework.server.ClusterPartition.startService() and
o.j.ha.framework.server.HAPartitionImpl.startPartition(). JGroups API let's you pass a
CONFIG event down the channel; if the event argument is a map with key
'additional_data' the value under that key gets stored in the IpAddress object
identifying the channel.
The clustering code generates the additional data by combining the address and port JNDI
is running on. That should be unique, since if it wasn't you'd have a port
conflict for JNDI.
HAPartitionImpl.startPartition() calls a verifyNodeIsUnique() method to confirm that
there's no other member with the same additional_data. This is a guard against a
member restarting or rejoining the group before the rest of the group realizes the old
incarnation has left.
JGRP-129 will be a much better solution to this problem. I know Bela wants to get rid of
the additional_data 'feature' once JGRP-129 is done.
Note the above isn't persistent; i.e. if you restart a node but change the bind
address, you get a different id.
Web clustering with mod_jk also gives nodes an id in the Tomcat server.xml file. For that
I recommend in training that people use a system property in the XML and set the property
from an environment variable in the script that launches JBoss.
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
9:47 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-957:
-------------------------------------
A logical JMS quueue in JBoss Messaging is actually composed of a set of individual
queues, one for each node in the cluster that the logical queue is deployed on.
Each queue fragment is owned by that node and will contain a different set of messages
than other queue fragments.
This is why we need a persistent node id, so the node knows which queue fragments in the
database it owns so it can load the queue state on startup and add/remove messages.
I'm beginning to think the tomcat approach of specifying the node id in a system
property is the best. This allows the actual JBM config to remain the same across each
node.
Do you see any problems with this approach. In particular I'm thinking cluster
installation will become more complex since the user will have to manually specify the
unique node id on each run.sh - which they currently don't have to do with AS cluster
install.
Another possibilty would be for JBM to generate a unique id on startup if it can't
find one in some config file. Once it's generated it, it would save it locally. This
has the difficulty of guarantee uniqueness of the id across the cluster (the id is
currently an int, not a string for performance reasons).
Any comments?
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
10:29 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12... ]
Brian Stansberry commented on JBMESSAGING-957:
----------------------------------------------
Yeah, I think the system property approach sounds better; I certainly don't want to
encourage the spread of the 'additional_data' hack.
I just checked, and unfortunately the system property substitution logic doesn't
support null as a default value, i.e. something like
jvmRoute="${jboss.cluster.nodeid:}" for the mod_jk usage.
That would be nice for the jvmRoute case; maybe doesn't matter for your case if you
can write code to check for and ignore some known value, i.e.
${jboss.cluster.nodeid:unspecified} or something.
The int thing is more of a hassle both for the unique generation issue you mentioned and
since I'm sure people would prefer to configure a string.
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
10:04 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-957:
-------------------------------------
Brian -
I've been trying to find the place in the tomcat config (AS 4.0.5) that substitutes
the node id, but can't find it. Can you point me to the right file? (And place in the
file).
Thx
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
10:07 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-957:
-------------------------------------
So, just to clarify, you think is OK for the user to have to specify a system property
containing the node id in their run.sh, which is unique for each server.
At startup we can throw an exception if it detects two or more servers starting with the
same node id.
I just wanted to check is ok with you since there are useability impacts w.r.t th user
having to manually configure this ids after cluster install.
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
1:34 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12... ]
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
1:44 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-957:
-------------------------------------
Brian - why would need a int property *and* a string property?
JBM just needs an int property.
What are these "other uses"?
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
2:33 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=comments#action_12... ]
Brian Stansberry commented on JBMESSAGING-957:
----------------------------------------------
The jvmRoute for mod_jk. That's a string, and an int is not a good alternative.
Perhaps the JON people want node identity as well; that's why I asked on the forum.
Note that I'm thinking longer term here, i.e. AS 5 and beyond. If we're just
discussing some modification you guys will do to AS 4.2 when you install JBM, then I'm
less concerned. AS 4.2 is out; the AS side won't be adding anything that uses any
particular system property. Up to now, the use of a system property for jvmRoute is just
something I teach people how to do in training classes; it's not a standard feature of
the AS.
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
11:47 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-957?page=all ]
Clebert Suconic closed JBMESSAGING-957.
---------------------------------------
Resolution: Done
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
7030
days inactive
7039
days old
14 comments
4 participants
participants (4)
-
Brian Stansberry (JIRA) -
Clebert Suconic (JIRA)
-
Jay Howell (JIRA)
-
Tim Fox (JIRA)