From ff1e8a1f0663dec0b193f30c1c60f79bcd954bdc Mon Sep 17 00:00:00 2001 From: Andy Taylor Date: Tue, 24 Mar 2015 11:50:58 +0000 Subject: [PATCH] doc fixes --- docs/user-manual/en/ha.md | 6 +++--- docs/user-manual/en/last-value-queues.md | 2 +- docs/user-manual/en/queue-attributes.md | 6 +++--- docs/user-manual/en/slow-consumers.md | 2 +- docs/user-manual/en/thread-pooling.md | 2 +- docs/user-manual/en/wildcard-routing.md | 4 ++-- 6 files changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/user-manual/en/ha.md b/docs/user-manual/en/ha.md index 94f895ae0a..445ba8f320 100644 --- a/docs/user-manual/en/ha.md +++ b/docs/user-manual/en/ha.md @@ -853,7 +853,7 @@ try only once. Once the number of attempts has been made an exception will be thrown. For examples of automatic failover with transacted and non-transacted -JMS sessions, please see ? and ?. +JMS sessions, please see [the examples](examples.md) chapter. #### A Note on Server Replication @@ -941,7 +941,7 @@ the session - it is already rolled back. The user can then just retry the transactional operations again on the same session. Apache ActiveMQ ships with a fully functioning example demonstrating how to do -this, please see ? +this, please see [the examples](examples.md) chapter. If failover occurs when a commit call is being executed, the server, as previously described, will unblock the call to prevent a hang, since no @@ -1042,7 +1042,7 @@ connection failure is detected. In your `ExceptionListener`, you would close your old JMS connections, potentially look up new connection factory instances from JNDI and creating new connections. -For a working example of application-level failover, please see ?. +For a working example of application-level failover, please see [the examples](examples.md) chapter. If you are using the core API, then the procedure is very similar: you would set a `FailureListener` on the core `ClientSession` instances. diff --git a/docs/user-manual/en/last-value-queues.md b/docs/user-manual/en/last-value-queues.md index 1fc1f32ece..0f5881a3d3 100644 --- a/docs/user-manual/en/last-value-queues.md +++ b/docs/user-manual/en/last-value-queues.md @@ -17,7 +17,7 @@ Last-value queues are defined in the address-setting configuration: By default, `last-value-queue` is false. Address wildcards can be used -to configure Last-Value queues for a set of addresses (see ?). +to configure Last-Value queues for a set of addresses (see [here](wildcard-syntax.md)). ## Using Last-Value Property diff --git a/docs/user-manual/en/queue-attributes.md b/docs/user-manual/en/queue-attributes.md index 6c306bc453..e515d06176 100644 --- a/docs/user-manual/en/queue-attributes.md +++ b/docs/user-manual/en/queue-attributes.md @@ -172,12 +172,12 @@ value must be greater than 0. detected. `KILL` will kill the consumer's connection (which will obviously impact any other client threads using that same connection). `NOTIFY` will send a CONSUMER\_SLOW management notification which an -application could receive and take action with. See ? for more details +application could receive and take action with. See [slow consumers](slow-consumers.md) for more details on this notification. `slow-consumer-check-period`. How often to check for slow consumers on a -particular queue. Measured in minutes. Default is 5. See ? for more -information about slow consumer detection. +particular queue. Measured in minutes. Default is 5. See [slow consumers](slow-consumers.md) +for more information about slow consumer detection. `auto-create-jms-queues`. Whether or not the broker should automatically create a JMS queue when a JMS message is sent to a queue whose name fits diff --git a/docs/user-manual/en/slow-consumers.md b/docs/user-manual/en/slow-consumers.md index c773f7d797..071c9aefa3 100644 --- a/docs/user-manual/en/slow-consumers.md +++ b/docs/user-manual/en/slow-consumers.md @@ -32,4 +32,4 @@ detection enabled will cause a new entry in the internal are a high number of queues and the `slow-consumer-check-period` is relatively low then there may be delays in executing some of the checks. However, this will not impact the accuracy of the calculations used by -the detection algorithm. See ? for more details about this pool. +the detection algorithm. See [thread pooling](thread-pooling.md) for more details about this pool. diff --git a/docs/user-manual/en/thread-pooling.md b/docs/user-manual/en/thread-pooling.md index b26c73e877..fc547efd71 100644 --- a/docs/user-manual/en/thread-pooling.md +++ b/docs/user-manual/en/thread-pooling.md @@ -90,7 +90,7 @@ A single thread is also used on the server side to scan for expired messages in queues. We cannot use either of the thread pools for this since this thread needs to run at its own configurable priority. -For more information on configuring the reaper, please see ?. +For more information on configuring the reaper, please see [message expiry](message-expiry.md). ### Asynchronous IO diff --git a/docs/user-manual/en/wildcard-routing.md b/docs/user-manual/en/wildcard-routing.md index e75b9fbf97..202b053f4f 100644 --- a/docs/user-manual/en/wildcard-routing.md +++ b/docs/user-manual/en/wildcard-routing.md @@ -16,5 +16,5 @@ To enable this functionality set the property `wild-card-routing-enabled` in the `activemq-configuration.xml` file to `true`. This is `true` by default. -For more information on the wild card syntax take a look at ? chapter, -also see ?. +For more information on the wild card syntax take a look at [wildcard syntax](wildcard-syntax.md) chapter, +also see the topic hierarchy example in the [examples](examples.md).