It is our intent to remove support for using an internal messaging broker in our OpenShift images for EAP 7.3. In 7.2 if your config includes the internal broker at container start we log a WARN message, so users get some info on this, if they happen to notice. But the 7.2 docs don't mention this, and it would be better if they did.
maschmid@redhat.com from QE noticed this.
[2:15pm] maschmid: bstansberry, hi Brian, I was wondering if we need to update the text regarding the "remote messaging" feature in https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.2/html/getting_started_with_jboss_eap_for_openshift_container_platform/introduction#comparison_eap_and_xpaas_eap_image (to state the deprecation of the internal artemis prehaps)
[2:19pm] maschmid: (I do remember that the existing text was a result of quite a long email thread, so I guess it is important to be precise with whatever we need it to say... )
[2:23pm] bstansberry: maschmid: that’s a good point. I think the text is fine for what it says, but saying it is deprecated is a good idea
[2:24pm] bstansberry: maschmid: I can file a JIRA unless you were doing it
[2:24pm] bstansberry: late for you
[2:26pm] maschmid: bstansberry, please do.
- duplicates
-
JBEAP-16047 Document DISABLE_EMBEDDED_JMS_BROKER for EAP 7.2
- Closed
- is duplicated by
-
JBEAP-19151 [GSS](7.3.z) EAP Container fails to start if a customized EAP7.2 based standalone-openshift.xml is brought in
- Closed