com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.

qpid-config.xml

You use the file <MB_HOME>/repository/conf/advanced/qpid-config.xml to configure WSO2 Message Broker. Following is a tree of the XML elements in the file:  

<broker>
    <prefix>
    <work>
    <conf>
    <plugin-directory>
    <cache-directory>   
    <connector>
        <ssl>
            <enabled>
            <sslOnly>
            <keystorePath>
            <keystorePassword>
        <qpidnio>
        <protectio>
            <enabled>
            <readBufferLimitSize>
            <writeBufferLimitSize>    
        <transport>
        <port>
        <sslport>
        <socketReceiveBuffer>
        <socketSendBuffer>
    <management>
        <enabled>
        <jmxport>
        <ssl>
            <enabled>
            <keyStorePath>
            <keyStorePassword>
    <advanced>
        <filterchain>
        <enablePooledAllocator>
        <enableDirectBuffers>
        <framesize>
        <compressBufferOnQueue>
        <enableJMSXUserID>
        <locale>
    <security>
       <pd-auth-manager>
            <principal-database>             
                <class>
                <attributes>
                    <attribute>
                        <name>
                        <value>
       <msg-auth>
    <virtualhosts>   
    <heartbeat>
        <delay>
        <timeoutFactor>
    <queue>
        <auto_register>
        <viewMessageCounts>
    <status-updates>
    <clustering>
        <enabled>       
        <OnceInOrderSupportEnabled>
        <externalCassandraServerRequired>
        <externalZookeeperServerRequired>
        <coordination>
            <ZooKeeperConnection>
            <ReferenceTime>
        <tuning>
            <messageBatchSizes>
                <maxNumberOfUnackedMessages>
                <maxNumberOfReadButUndeliveredMessages>
                <messageBatchSizeForSubscribersQueues>
                <messageBatchSizeForSubscribers>
                <globalQueueWorkerMessageBatchSize>
                <contentPublisherMessageBatchSize>
                <medataDatePublisherMessageBatchSize>
                <messageBatchSizeForBrowserSubscriptions>
            <threading>
                <flusherPoolSize>
                <subscriptionPoolSize>
                <internalSequentialThreadPoolSize>
                <andesInternalParallelThreadPoolSize>
                <publisherPoolSize> 
           <waitTimes>
                <maxAckWaitTime>
                <queueMsgDeliveryCurserResetTimeInterval>
                <maxAckWaitTimeForBatch>
                <queueWorkerInterval>
                <pubSubMessageRemovalTaskInterval>
                <contentRemovalTaskInterval>
                <contentRemovalTimeDifference>
                <topicPublisherTaskInterval>
                <virtualHostSyncTaskInterval> 
           <maximumNumberOfMessageDeliveryAttempts>         

Click an element below for more information about that element.


<broker>

This is the top level element of qpid-config.xml file. It contains all the other elements needed to configure WSO Message Broker. The setting of the prefixes for QPID_HOME and QPID_WORK allows environment variables to be used throughout the config.xml and removes the need for hard coding of paths in this file.

Configurable Sub Elements
Element NameDescriptionTypeDefault ValueFixed ValuesMandatory/OptionalNotes
<prefix>    Mandatory 
<work>    Mandatory 
<conf>    Mandatory 
<plugin-directory>    Mandatory 
<cache-directory>    Mandatory 

<connector>

Defines connection parameters.

Configurable Sub Elements
Element NameDescriptionTypeDefault ValueFixed ValuesMandatory/OptionalNotes
<qpidnio>Enable or disabe NIO support for the broker Boolean false true/falseMandatory 
<transport>transport type to use Stringnio Mandatory 
<port> Int 5672 Mandatory 
<socketReceiveBuffer> Int32768 Mandatory 
<socketSendBuffer> Int 32768  Mandatory 

<ssl>

This comes under <connector>. SSL section allows configuration of SSL and related keystore settings. By default SSL is enabled with default parameters. If sslOnly is set to 'true' Non-SSL port will be disabled.

Configurable Sub Elements
Element NameDescriptionTypeDefault ValueFixed ValuesMandatory/OptionalNotes
<enabled> If SSL is enabled for Message Broker server Booleantrue true/false Mandatory 
<sslOnly> The sslOnly option is included here for completeness however this will disable the unencrypted port and leave only the SSL port listening for connections. Booleanfalse true/false Mandatory 
<keystorePath> Path for keystore directory String

repository/resources/security/wso2carbon.jks

 

repository/resources/security/wso2carbon.jks  Mandatory 
<keystorePassword> Password for keystore String wso2carbon wso2carbon Mandatory 


<management> 

This configuration option is there for managing JMX console. 

Configurable Sub Elements
Element NameDescriptionTypeDefault ValueFixed ValuesMandatory/OptionalNotes
<enabled>This element allows the user to switch the connectivity of the management console on/off i.e. if the enabled tag is set to false you will not be able to connect a management console to this broker instance.Booleantruetrue/falseMandatory 
<jmxport> The JMX Management port is set to 8999 by default but it can be changed here in the XML.Int8999N/AMandatory 
<ssl>SSL related configurations for management console.     
        <enabled>Sub element of <ssl>. Whether SSL is enabled for management consoleBooleanfalsetrue/falseMandatory 
        <keyStorePath>Sub element of <ssl>. Update below path to your keystore location, or run the bin/create-example-ssl-stores(.sh|.bat) script from within the etc/ folder to generate an example store with self-signed certString${conf}/qpid.keystoreN/AMandatory 
       <keyStorePassword>Password for the keystore provided.StringpasswordN/AMandatory 

<advanced>

The elements in this section are used under the covers in the broker. At present, we do not recommend any changes to these settings.

Configurable Sub Elements
Element NameDescriptionTypeDefault ValueFixed ValuesMandatory/OptionalNotes
<filterchain>  Boolean truetrue/falseMandatory 
<enablePooledAllocator>  Boolean falsetrue/falseMandatory 
<enableDirectBuffers>  Boolean falsetrue/falseMandatory 
<framesize>  Int 65535N/AMandatory 
<compressBufferOnQueue>  Boolean falsetrue/falseMandatory 
<enableJMSXUserID>  Boolean falserue/falseMandatory 
<locale> Stringen_USN/AMandatory 

Back to Top ^

<security>

The security section specifies exactly one authentication manager (responsible for determining that a user's credentials are correct) and zero or more access plugins (limits what the user may and may not do). No configuration change is needed here.

<virtualhosts>

This element allows you to specify a location for the virtualhosts.xml file that you wish to use. If you are not using a subdirectory under $QPID_HOME you can provide a fully qualified path instead. For more information on the content of the virtualhosts.xml file please see 

<heartbeat>

The Qpid broker sends an internal (only) heartbeat. This element allows configuration of the frequency of this heartbeat. It is needed to configure a proper delay for the heartbeat value if the connections are going to stay idle for a long time.All configurations related to this is described here.

Configurable Sub Elements
Element NameDescriptionTypeDefault ValueFixed ValuesMandatory/OptionalNotes
<delay>Heart beating delay Int 0N/A  
<timeoutFactor>Heat beat time out factor Float falseN/A  

<queue>

This should NOT be changed lightly as it sets the broker up to automatically bind queues to exchanges. It could theoretically be used to prevent users creating new queues at runtime, assuming that you have created all queues/topics etc at broker startup. However, best advice is to leave unchanged for now. Enabling the <viewMessageCounts> element in this section will directly effect to broker performance hence make it 'true' only if a performance degrade is acceptable.

Configurable Sub Elements
Element NameDescriptionTypeDefault ValueFixed ValuesMandatory/OptionalNotes
<auto_register>Whether to register the queue name in server or not at the time of it is created.Booleantruetrue/false  
<viewMessageCounts>

Activates the queue message counters and message count of each queue wil be displayed in the admin console by default. When this is 'false' message count can be

read from console on user demand.

Booleanfalsetrue/falseoptional 

<tuning>

 Under this tag all tuning parameters for WSO2 Message Broker is defined. Threading wait times, Thread pool sizes, Message batch sizes can be configured to suit the memory availability and the performance expected. There is a balance between performance, reliability, and the resources in hand.

Configurable Sub Elements
Element NameDescriptionTypeDefault ValueFixed ValuesMandatory/OptionalNotes
<maximumNumberOfMessageDeliveryAttempts> This is used to configure how many times a configured message should be attempted to deliver to the subscriber. If there is no acknowledgement came from the client or there were rollbacks for a "Transacted" message delivery, after this number of delivery attempts has breached, message will be dropped from the store and it will be lost. Int 10 N/A Mandatory 

<clustering>

WSO2 Message Broker can be clustered to meet scalability requirements. There are a few clustering patterns supported by WSO2 MB with Cassandra and Zookeeper servers are also clustered. See Clustered Deployment for more information.  

Configurable Sub Elements
Element NameDescriptionTypeDefault ValueFixed ValuesMandatory/OptionalNotes
<enabled>Configure the broker to start in clustered mode or in stand-alone mode. The value "true" indicates clustered mode whereas "false" indicate the standalone mode.Stringfalsetrue/falseMandatory 
<OnceInOrderSupportEnabled>Generally broker will try its best to deliver messages in order, but time to time this order can be broken if subscriber is receiving messages while sending messages also happen at the same time. Setting this configuration to "true", we ensure messages are delivered strictly in order (even when clustered), but there might be a performance deduction w:r:t the default mode.Stringfalsetrue/falseMandatory 
<coordination>In clustered mode, this configuration is important.     
<ZooKeeperConnection>Sub-element of <coordination>. As WSO2 Message Broker uses Apache ZooKeeper to make synchronizations and notifications in clustered environment, it should be pointed to a running ZooKeeper server configuring this parameter.

String

<ip>:<port>

127.0.0.1:2181N/AOptional 
<ReferenceTime>Sub-element of <coordination>. When message IDs are generated internally during clustered deployment this configuration value is used.String (yyyy-mm-dd hh:mm:ss)2012-02-29 08:08:08N/AMandatory 

<messageBatchSizes>

This configuration is found under <tuning>. In Broker operations at various places messages are read or written, either to memory or to Cassandra Database. In order to handle performance and to cope with the memory requirements, it might be required to configure sizes of message batches that should be handled. 

Configurable Sub Elements
Element NameDescriptionTypeDefault ValueFixed ValuesMandatory/OptionalNotes
<maxNumberOfUnackedMessages>

Message delivery from server to the client will be paused temporarily if number of delivered but unacknowledged message count reaches this size. Should be set considering message consume rate.

Int1000N/AMandatory 
<maxNumberOfReadButUndeliveredMessages>

Maximum number of undelivered messages per a queue that can have in memory.

Int1000N/AMandatoryConsider allocated memory size when increasing this value
<messageBatchSizeForSubscribersQueues>

Message Batch size moved to Subscriber queues from the Global Queue at once. Increasing this values increase the chance of breaking in order delivery guarantee but performance will be improved

Int20N/AMandatory 
<messageBatchSizeForSubscribers>Message Batch size Taken in to memory for a one time to deliver to subscribers.     
<default>sub-element of <messageBatchSizeForSubscribers>. Initially this value will be taken as the batch size of messages to read into memory. Int50N/AMandatoryThis should be a value between max and min values below
<max>sub-element of <messageBatchSizeForSubscribers>. Dynamically broker will increase batch size upto this value if there are many messages.Int300N/AMandatory Consider size of a message when increasing.
<min>Broker will try to read at least this number of messages into memory.Int20N/AMandatoryConsider the performance when decreasing.
<globalQueueWorkerMessageBatchSize>

Maximum number of message taken it to memory when transering from interal queues to node wise queues. We need to increase the memory allocation from the broker if we are to increase this.

Int700N/AMandatoryIncreasing this will increase the consumer throughout
<contentPublisherMessageBatchSize>Max number of Message chunks to buffer before message contents are written to the cassandraInt200N/AMandatory 
<medataDatePublisherMessageBatchSize>Max number of Messages meta data to buffer before message Meta data are written to the cassandraInt200N/AMandatory 
<messageBatchSizeForBrowserSubscriptions>Maximum number of messages to be fetched using Andes message browser when browsing queuesInt200N/AMandatoryNumber of entries attempted to load for Queue Browser Window will depend on this entry.

 

<threading>

Configurations to define thread pool sizes for WSO2 Message Broker

Configurable Sub Elements
Element NameDescriptionTypeDefault ValueFixed ValuesMandatory/OptionalNotes
<flusherPoolSize>

This is the Thread pool size which will be used by the "Sender Task" to send messages asynchronously to the subscriber.

Int10N/AMandatoryYou will have to consider the value of parameter messageBatchSizeForSubscribers when configuring this pool size.
<subscriptionPoolSize>

This is the Thread pool that is used by the Fast Subscription Handing implementation. Make this to a higher number if there are a lot of subscriptions to the system at a given time

Int20N/AMandatory 
<internalSequentialThreadPoolSize>

This is the Thread pool size which will be used by the internal Queue copy Task to move messages to from Global Queue to Node queue in Cassandra tables.

Int5N/AMandatoryIncrease this into a higher value if there are lots of subscriptions in the system.
<andesInternalParallelThreadPoolSize>This is the Thread pool size which will be used by the Andes core to schedule its internal parallel tasksInt50N/AMandatory 
<publisherPoolSize>This is the Thread pool size which will be used by the queue delivery workers.Int50N/AMandatoryIncrease this into a higher value if there are lots of unique queues to the system.

 

<waitTimes> 

These are time based configurations for WSO2 Message Broker. 

Configurable Sub Elements
Element NameDescriptionTypeDefault ValueFixed ValuesMandatory/OptionalNotes
<maxAckWaitTime>Max wait time for a acknowledgement for a given message from the client. After this time is breached broker will try to redeliver the message again.Seconds10N/AMandatory 
<maxAckWaitTimeForBatch>

Max wait time for a acknowledgement for a batch of messages that that is sent from subscribers

Seconds120N/AMandatory 
<queueMsgDeliveryCurserResetTimeInterval>Time to wait until older messages in queues start being delivered. After this much of time messages from beginning of the queue will be starting to delivered. If some message is already sent, but unacked, it will be redelivered if <maxAckWaitTime> is breached. Milliseconds60000N/AMandatory 
<queueWorkerInterval>Running interval for queue worker thread.Milliseconds500N/AMandatory 
<pubSubMessageRemovalTaskInterval>

Messages addressed to topics are buffered to be removed. Thread to clear off messages from store message will be run once this time.

Milliseconds5000N/AMandatory 
<contentRemovalTaskInterval>Content of messages which are delivered to the client is buffered to be removed. Thread to clear the content of delivered messages will be run once this time.Milliseconds4000N/AMandatory 
<contentRemovalTimeDifference>Broker will wait until a timeout happens before removing messages delivered or not delivered for Topic subscribers.Seconds120N/AMandatory 
<topicPublisherTaskInterval>The Running interval for Topic Publisher Task delivering messages to subscribers for topics.Milliseconds1000N/AMandatory 
<virtualHostSyncTaskInterval> 

Virtual host sync interval for the Virtual host syncing Task which will sync the Virtual host details across the cluster

Seconds3600N/AMandatory 

Back to Top ^


 

 

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.