Details
-
Bug
-
Resolution: Done
-
Major
-
7.4.0.GA
-
None
Description
Steps in [1] to configure pooled connection factory pointing to a remote broker has 1 missing step and 1 typo.
Configuring @JMSConnectionFactoryDefinition Using the Default Resource Adapter
1- [missing step] Create a socket binding to remote instance (using an example of 127.0.0.2 as a host, and 5445 as a port)
/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=messaging-remote-throughput:add(host=127.0.0.2, port=5445)
2- [Typo: change messaging to messaging-activemq] Create a connector:
/subsystem=messaging-activemq/remote-connector=remote-amq:add(socket-binding="messaging-remote-throughput")
2- Create a pooled connection factory:
/subsystem=messaging-activemq/pooled-connection-factory=activemq-ra-remote:add(entries=["java:/jms/remote-amq/JmsConnectionFactory"],connectors=["remote-amq"]
3- Define the default JMS connection factory for the ee subsystem:
/subsystem=ee/service=default-bindings:write-attribute(name=jms-connection-factory, value="java:/jms/remote-amq/JmsConnectionFactory")
4- Use the @JMSConnectionFactoryDefinition annotation in your application code:
@JMSConnectionFactoryDefinition(
name="java:app/myCF"
Attachments
Issue Links
- clones
-
JBEAP-19683 [DOC] typo/missing step in "31.4.1. JMS Resources Configuration Using the JMSConnectionFactoryDefinition Annotation"
- Closed