Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1661

Business-central clustering doesn't work with RHDG

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.3.0.GA
    • None
    • None
    • Hide

      Setup business-central cluster as described in Clustering_setup_with_gluster_AMQ_RHDG
      Use productized RHDG instead of community Infinispan version.

      Show
      Setup business-central cluster as described in Clustering_setup_with_gluster_AMQ_RHDG Use productized RHDG instead of community Infinispan version.
    • 2019 Week 05-07

    Description

      So far QE was only able to test business-central clustering with Community version of infinispan (9.3.3).

      When instead of infinispan server I start the productized version RHDG 7.2.3

      I'm getting this on business-central side:

      12:56:14,439 ERROR [org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation] (HotRod-client-async-pool-6) ISPN004007: Exception encountered. Retry 10 out of 10: org.infinispan.client.hotrod.exceptions.TransportException:: ISPN004077: Closing channel [id: 0xc4f47639, L:/10.40.3.36:44486 - R:10.40.3.36/10.40.3.36:11372] due to error in unknown operation.
    at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.exceptionCaught(HeaderDecoder.java:206)

      And this from RHDG server side:

      12:56:14,254 ERROR [org.infinispan.server.hotrod.CacheDecodeContext] (HotRod-ServerWorker-7-1) ISPN005003: Exception reported: org.infinispan.server.hotrod.InvalidMagicIdException: Error reading magic byte or message id: 0
    at org.infinispan.server.hotrod.HotRodDecoder.readHeader(HotRodDecoder.java:184)

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. AF-1697 Business-central clustering doesn't work with RHDG

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Activity

            People

              aparedes@redhat.com Adriel Paredes
              jhrcek Jan Hrcek (Inactive)
              Jan Hrcek Jan Hrcek (Inactive)
              Jan Hrcek Jan Hrcek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: