Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-775

jgroups configuration files in the AMQ7 clustered-jgroups example are disproportionately old

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • A-MQ 7.0.0.CR1
    • None
    • Release Notes
    • Not Yet Documented
    • AMQ Broker 7.1 Sprint 1

      AMQ7 uses jgroups 3.6. But the jgroups configuration files in the `clustered-jgroups` example are `JGroups-2.8.xsd` as below. One of the jgroups experts in Japan points out that it is disproportionately old and it uses some deprecated setting such as <MEARGE2> and <FC>.

      <config xmlns="urn:org:jgroups"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
              xsi:schemaLocation="urn:org:jgroups file:schema/JGroups-2.8.xsd">
      

      Could you please replace it with a new version one?
      I think almost AMQ7's jgroups users hope to use TCPPING instead of current FILE_PING because a reason of using jgroups instead of clustering with UDP is to want to use AMQ7 in a cloud platform that cannot use IP multicast/broadcast. I think replacing current FILE_PING with TCPPING should please our AMQ7 users.

      FYI, EAP 7 use jgroups 3.6 same as AMQ 7. You may be able to refer to those examples(, although it is different schema).

              rhn-support-jbertram Justin Bertram
              rhn-support-tyamashi Tomonari Yamashita
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: