This documentation is for WSO2 Message Broker 3.1.0. View documentation for the latest release.
Due to a known issue do not use JDK1.8.0_151 with WSO2 products. Use JDK 1.8.0_144 until JDK 1.8.0_162-ea is released.
Skip to end of metadata
Go to start of metadata

The Advance Message Queueing Protocol (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 related to configuring 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>
	<maximumRedeliveryAttempts>10</maximumRedeliveryAttempts>
	<allowSharedTopicSubscriptions>false</allowSharedTopicSubscriptions>
    <allowStrictNameValidation>true</allowStrictNameValidation>
</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 initialized with this port by default. 8672
maximumRedeliveryAttemptsThe maximum number of times the WSO2 MB should attempt to redeliver a message that has not reached a subscriber. For example, when this value is set to 10, another 10 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 WSO2 MB using the same client ID. Read more about durable subscriptions to topics.false
allowStrictNameValidation
If this parameter is true, the queue names and topic names will be validated according to the AMQP specification. When this parameter is set to false, it is possible to use ":" in topic names.
true

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

  • No labels