-
Bug
-
Resolution: Done
-
Critical
-
7.0.0.GA
-
None
-
issue was analysed on OpenShift 3.6
EAP 7.1
-
RC1
-
-
-
-
-
-
-
CR3
-
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
- relates to
-
RHDM-400 Allow usage of different JMS brokers
- Closed