Uploaded image for project: 'Red Hat Decision Manager'
  1. Red Hat Decision Manager
  2. RHDM-352

Artemis JMS client version mismatch

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.0.0, 7.0.0.GA
    • 7.0.0.GA
    • Decision Central
    • None

    • issue was analysed on OpenShift 3.6
      EAP 7.1

    • RC1
    • CR3
    • Hide

      Install clustered Workbench in OpenShift according to [1] - use available AMQ broker (for example jboss-amq-63:1.2) instead of custom OpenShift image used in the instructions.
      Start Workbench pod. Check pod log.
      =>
      There is shown error listed in attachment.

      [1] https://docs.google.com/document/d/1cpXtp6aQyMuC2jPUWUzHDUIsdARY4qc9fMQLCVsPeNk

      Show
      Install clustered Workbench in OpenShift according to [1] - use available AMQ broker (for example jboss-amq-63:1.2) instead of custom OpenShift image used in the instructions. Start Workbench pod. Check pod log. => There is shown error listed in attachment. [1] https://docs.google.com/document/d/1cpXtp6aQyMuC2jPUWUzHDUIsdARY4qc9fMQLCVsPeNk

    Description

      BPMSPL-744 brought a dependency on ActiveMQ Artemis JMS client to the Workbench [1]. However it also specifies Artemis version [2] which is different to EAP 7.1 alignment. The result is that the clustered Workbench isn't able to connect to JMS broker, see errors in attachment.

      EAP 7.1.0.GA uses Artemis version 1.5.5.008-redhat-1 .

      That leads me to another question, why do we have a specific JMS client in the Workbench? Why don't we use jms client bundled in EAP? Or cannot we use Initial context to retrieve a connection factory available in the application server instead of creating specific instance [3]?

      [1] https://github.com/kiegroup/appformer/commit/93e21c3a2c3bd1eaacb6a5591fd5e71bcd37be63#diff-600376dffeb79835ede4a0b285078036R955
      [2] https://github.com/kiegroup/appformer/blob/master/pom.xml#L88
      [3] https://github.com/kiegroup/appformer/blob/master/uberfire-commons/src/main/java/org/uberfire/commons/cluster/ClusterJMSService.java#L70

      Attachments

        Issue Links

          relates to

          Feature Request - Feature requests from customers and/or users RHDM-400 Allow usage of different JMS brokers

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              paulovmr Paulo Rego
              ksuta Karel Suta
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: