What is true about the network connections when a Mule application uses a JMS connector to interact with a JMS provider (message broker)?
A.
The JMS connector supports both sending and receiving of JMS messages over the protocol determined by the JMS provider
B.
The AMQP protocol can be used by the JMS connector to portably establish connections to various types of JMS providers
C.
To receive messages into the Mule application, the JMS provider initiates a network connection to the JMS connector and pushes messages along this connection
D.
To complete sending a JMS message, the JMS connector must establish a network connection with the JMS message recipient
When Mule uses the JMS connector, it loads the client library supplied by the chosen JMS provider (ActiveMQ, IBM MQ, etc.). That library:
Opens a single TCP connection (or a small pool) from the Mule application to the broker.
Uses the provider’s native wire-protocol (OpenWire, MQI, etc.).
Over the same connection the Mule app can produce (send) and consume (receive) messages.
The other options describe behaviors that do not occur:
B – AMQP is not a universal fallback; Mule still relies on each provider’s own client JARs and protocol.
C – The broker does not open sockets back to Mule; the client connection is outbound from Mule and is reused for message delivery.
D – The sender never contacts the final consumer; all traffic goes through the broker only.
A. Can't be D.The JMS connector does not have to establish a connection with the JMS recipient as the puts and get are done between the JMS recepient and the JMS provider, otherwise it would not be async communication.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
edogwest
3Â days, 12Â hours agoSH65
9Â months agomadgeezer
2Â years, 2Â months agodushnyao
2Â years, 8Â months ago