WildFly ActiveMQ-Based Messaging Subsystem Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
{{Internal|Generic JMS Client with EAP/ActiveMQ|Generic JMS Client with EAP/ActiveMQ}} | {{Internal|Generic JMS Client with EAP/ActiveMQ|Generic JMS Client with EAP/ActiveMQ}} | ||
=Resource Adapter= | |||
The ActiveMQ JMS provider is exposed as a resource adapter to the applications deployed within the application server. The relevant configuration is: | |||
<pre> | |||
<subsystem xmlns="urn:jboss:domain:messaging-activemq:..."> | |||
<server name="default"> | |||
<pooled-connection-factory name="activemq-ra" transaction="xa" connectors="in-vm" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory"/> | |||
</server> | |||
</subsystem> | |||
</pre> | |||
Latest revision as of 02:17, 18 March 2017
Internal
Overview
Applies to EAP 7.* and newer.
Generic JMS Client with ActiveMQ
Resource Adapter
The ActiveMQ JMS provider is exposed as a resource adapter to the applications deployed within the application server. The relevant configuration is:
<subsystem xmlns="urn:jboss:domain:messaging-activemq:...">
<server name="default">
<pooled-connection-factory name="activemq-ra" transaction="xa" connectors="in-vm" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory"/>
</server>
</subsystem>