Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-6537 Upgrade JBoss Cache to 3.2.8
  3. JBPAPP-6538

CacheJmxWrapper ignores ClusterConfig attribute

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.1.2 ER1
    • EAP_EWP 5.1.1
    • Clustering
    • None
    • Release Notes
    • Hide
      When creating a cache using the CacheJmxWrapper the ClusterConfig section was ignored, and a default JGroups configuration used. The cause of the problem was that the parser was ignoring the contents of the <ClusterConfig> section. This problem has been fixed and the whole of the cluster configuration file is read correctly.
      Show
      When creating a cache using the CacheJmxWrapper the ClusterConfig section was ignored, and a default JGroups configuration used. The cause of the problem was that the parser was ignoring the contents of the <ClusterConfig> section. This problem has been fixed and the whole of the cluster configuration file is read correctly.
    • Documented as Resolved Issue
    • NEW

      When creating a cache using the CacheJmxWrapper:

      <mbean code="org.jboss.cache.jmx.CacheJmxWrapper" name="test:service=TreeCache">
      <attribute name="CacheMode">REPL_SYNC</attribute>
      <attribute name="ClusterName">Test</attribute>
      <attribute name="ClusterConfig">
      <config>
      <TCP start_port="12345"

      the ClusterConfig section is ignored, and a default JGroups configuration is used.

      The root cause is CacheJmxWrapper#setClusterConfig parses the contents of <ClusterConfig>,
      but doesn't save it, and always sets the result to null.

              rhn-support-dereed Dennis Reed
              rhn-support-dereed Dennis Reed
              Russell Dickenson Russell Dickenson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: