This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

AMQP is a wire-level messaging protocol used by WSO2 MB for message-queueing.

Enabling the transport

The <MB_HOME>/repository/conf/broker.xml file contains parameters relating to the configuration of the AMQP transport. The transport can be enabled as shown in the following extract of the broker.xml file.

<amqp enabled="true">
	<!-- most of the amqp configurations reside in qpid-config.xml since we inherit the qpid messaging model during AMQP.-->
	<port>5672</port>
	<sslPort>8672</sslPort>
	<sendExpiredMessagesToDLC>false</sendExpiredMessagesToDLC>
	<maximumRedeliveryAttempts>10</maximumRedeliveryAttempts>
	<allowSharedTopicSubscriptions>false</allowSharedTopicSubscriptions>
</amqp>

Related Parameters

 

Parameter NameDescriptionDefault Value
enabledIf the value of this parameter is true, the AMQP transport is enabled and the AMQP protocol will be applied to messages sent to the specified listening port.true
portThe listening port specified for the AMQP transport. The AMQP broker would be initialized with this port by default.5672
sslPortThe listening SSL port for the specified AMQP transport. The AMQP security socket will be initialised with this port by default. 8672
sendExpiredMessagesToDLCThis parameter determines whether the expired messages should be sent to the DLC (Dead Letter Channel) for later revival. The default value should be changed to false if you want to avoid having the DLC piled up with too many messages.true
maximumRedeliveryAttemptsThe maximum number of times the WSO2 MB should attempt to redeliver a message which has not reached a subscriber. For example, when the value for this is 10, Nine more attempts will be made to deliver the message. The default value can be changed depending on your reliability requirements.10
allowSharedTopicSubscriptionsIf this parameter is true, a durable subscription to a topic can be shared among multiple subscribers. That is, multiple clients can subscribe to a topic in MB using the same client ID. Read more about durable subscriptions to topics. 

Refer the description of the broker.xml file for further details.

  • No labels