Connection to remote Artemis broker must not require the presence of a local Artemis broker ------------------------------------------------------------------------------------------- Key: WFLY-10518 URL: https://issues.jboss.org/browse/WFLY-10518 Project: WildFly Issue Type: Feature Request Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil Connections to remote Artemis-based broker (including A-MQ 7) are handled in WildFly by the pooled-connection-factory resource that is in the messaging-activemq subsystem: https://wildscribe.github.io/WildFly/13.0/subsystem/messaging-activemq/se... This pooled-connection-factory resource can be used to connect to the local Artemis server that "owns" it or to a remote Artemis broker. However, this pooled-connection-factory always require the presence of a local Artemis server even when it connects only to a remote Artemis broker. This use case will become more prevalent as EAP CD is used to connect to A-MQ 7 and will not embed a local Artemis server. The presence of a local Artemis server has impact on the memory and CPU footprint of EAP on OpenShift. This RFE will improve WildFly and EAP so that a connection with remote Artemis-based broker will no longer require the presence of a local instance of Artemis.