Details
-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
0
-
0%
Description
- 1. ChannelFactory (MBean)
- channel names associated with configuration
- getChannel(name) --> channel configured correctly
- Advantage: central configuration
Example:
<mbean ...>
<stack name="Clustering">
<config>
...
</config>
</stack>
<stack name="Tomcat-5 session clustering">
<config>
...
</config>
</stack>
</mbean>
In cluster-service.xml, or tc5-cluster-service.xml, we would simply refer to "Clustering" or "Tomcat-5 session clustering" to get the correct stack, but we would not explicitly configure the stack there.
- 2. Multiplexing
- Multiple threads using same channel
- Any thread can send
- All threads receive every message
- State transfer ?
Currently #2 needs more thought. The requirement is that all applications use their own configuration (channel). Even if they have the same protocol stack configuration, we cannot yet support multiplexing due to state transfer issues !
- 3. Expose JGroups via JMX
- This is done in
JGRP-84(see dependent JIRA link)
- 4. Expose JBossCache via JMX
- For this to work in standalone JDK 5, we will need to use a
similar strategy as proposed inJGRP-84
Requirements:
- The same code needs to work in JBoss AS and in the standalone JDK 5