You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by bu...@apache.org on 2013/11/13 18:23:21 UTC
svn commit: r886526 [21/21] - in /websites/production/activemq/content: ./
2004/04/13/ 2004/05/26/ 2004/06/23/ 2004/06/25/ 2004/08/17/ 2004/08/23/
2004/10/07/ 2004/11/02/ 2004/12/20/ 2005/02/03/ 2005/02/25/ 2005/04/11/
2005/06/06/ 2005/07/04/ 2005/07/1...
Modified: websites/production/activemq/content/why-do-kahadb-log-files-remain-after-cleanup.html
==============================================================================
--- websites/production/activemq/content/why-do-kahadb-log-files-remain-after-cleanup.html (original)
+++ websites/production/activemq/content/why-do-kahadb-log-files-remain-after-cleanup.html Wed Nov 13 17:23:00 2013
@@ -81,8 +81,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-<p>Cleanup of unreferenced KahaDB journal log files data-<id>.log will occur every 30seconds by deafault. If a data file is in-use it will not be cleaned up.<br clear="none">
+<div class="wiki-content maincontent"><p>Cleanup of unreferenced KahaDB journal log files data-<id>.log will occur every 30seconds by deafault. If a data file is in-use it will not be cleaned up.<br clear="none">
The definition of in-use is many fold. In the simplest case, a data file is in-use if it contains a pending message for a destination or durable topic subscription. If it does not contain any message, it may contain acks for messages that are in data files that are in-use, in which case it cannot be removed (b/c a recovery with missing acks would result in redelivery). <br clear="none">
If the journal references a pending transaction it cannot be removed till that transaction completes. Finally, if a data file is the current journal file, it is considered in-use as there may be a pending write to that journal file.</p>
@@ -126,8 +125,7 @@ In any event, the logging will help you
</div></div><br clear="none">
We get one candidate, data-87.log from the existing set of journal data files <tt>[86, 87, 163, 164]</tt>. There is a current transaction using 164, destination (Queue named E) <tt>'0\:E'</tt> has some messages in 163, destination <tt>'0:I'</tt> has messages in 86 and 87 is unreferenced. In this case, there must be some long standing unacked messages or a very slow consumer on destination <tt>'0:I'</tt>.<br clear="none">
The <tt>'0:'</tt> prefix is shorthand for a queue, <tt>'1:'</tt> for a topic, i.e: <tt>dest:1:B</tt> is a topic named B.
-
- </div>
+</div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/wildcards.html
==============================================================================
--- websites/production/activemq/content/wildcards.html (original)
+++ websites/production/activemq/content/wildcards.html Wed Nov 13 17:23:00 2013
@@ -81,8 +81,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-<p>We support destination wildcards to provide easy support for federated name hierarchies. This concept has been popular in financial market data for some time as a way of organizing events (such as price changes) into hierarchies and to use wildcards for easy subscription of the range of information you're interested in.</p>
+<div class="wiki-content maincontent"><p>We support destination wildcards to provide easy support for federated name hierarchies. This concept has been popular in financial market data for some time as a way of organizing events (such as price changes) into hierarchies and to use wildcards for easy subscription of the range of information you're interested in.</p>
<p>For example imagine you are sending price messages from a stock exchange feed. You might use some kind of destination such as</p>
@@ -131,8 +130,7 @@
<p>A default path separator this plugin will use is <tt>/</tt>. You can customize it further using <tt>pathSeparator</tt> property.</p>
-
- </div>
+</div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/wire-protocol.html
==============================================================================
--- websites/production/activemq/content/wire-protocol.html (original)
+++ websites/production/activemq/content/wire-protocol.html Wed Nov 13 17:23:00 2013
@@ -72,8 +72,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-
+<div class="wiki-content maincontent">
<p>This page describes the logical <a shape="rect" href="openwire.html" title="OpenWire">OpenWire</a> protocol for users developing clients in other languages than Java such as C# or C native clients. Note that OpenWire is designed for maximum performance and features; its the protocol used inside ActiveMQ. If you want a simpler protocol to work with to get started with a cross language client then try <a shape="rect" href="stomp.html" title="Stomp">Stomp</a> which is designed for ease-of-implementation so its easy to support many clients.</p>
<h1><a shape="rect" name="WireProtocol-Protocoloverview"></a>Protocol overview</h1>
@@ -128,8 +127,7 @@
<h1><a shape="rect" name="WireProtocol-Finalthoughts"></a>Final thoughts</h1>
-<p>If in doubt about a piece of the protocol, the easiest way to figure out what happens is to check the JMS client code. In particular check out the code of <a shape="rect" class="external-link" href="http://activemq.codehaus.org/maven/xref/org/activemq/ActiveMQSession.html" rel="nofollow">ActiveMQSession</a> which contains pretty much all the above logic. Pay particular attention to calls to <b>syncSendCommand()</b> and <b>asyncSendCommand()</b> when Commands are sent to the Message Broker</p>
- </div>
+<p>If in doubt about a piece of the protocol, the easiest way to figure out what happens is to check the JMS client code. In particular check out the code of <a shape="rect" class="external-link" href="http://activemq.codehaus.org/maven/xref/org/activemq/ActiveMQSession.html" rel="nofollow">ActiveMQSession</a> which contains pretty much all the above logic. Pay particular attention to calls to <b>syncSendCommand()</b> and <b>asyncSendCommand()</b> when Commands are sent to the Message Broker</p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/ws-notification.html
==============================================================================
--- websites/production/activemq/content/ws-notification.html (original)
+++ websites/production/activemq/content/ws-notification.html Wed Nov 13 17:23:00 2013
@@ -72,11 +72,9 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-<h2><a shape="rect" name="WSNotification-WSNotification"></a>WS-Notification</h2>
+<div class="wiki-content maincontent"><h2><a shape="rect" name="WSNotification-WSNotification"></a>WS-Notification</h2>
-<p>This page has now moved to the <a shape="rect" class="external-link" href="http://servicemix.apache.org/">ServiceMix site</a>. You can read about <a shape="rect" class="external-link" href="http://incubator.apache.org/servicemix/ws-notification.html">WS-Notification support here</a></p>
- </div>
+<p>This page has now moved to the <a shape="rect" class="external-link" href="http://servicemix.apache.org/">ServiceMix site</a>. You can read about <a shape="rect" class="external-link" href="http://incubator.apache.org/servicemix/ws-notification.html">WS-Notification support here</a></p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/wsif.html
==============================================================================
--- websites/production/activemq/content/wsif.html (original)
+++ websites/production/activemq/content/wsif.html Wed Nov 13 17:23:00 2013
@@ -72,11 +72,9 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-<p>The <a shape="rect" class="external-link" href="http://ws.apache.org/wsif/">Apache Web Service Invocation Framework (WSIF)</a> allows you to perform web service invocations using a number of different implementation protocols like Axis, local Java, EJB, JMS, JCA CCI etc.</p>
+<div class="wiki-content maincontent"><p>The <a shape="rect" class="external-link" href="http://ws.apache.org/wsif/">Apache Web Service Invocation Framework (WSIF)</a> allows you to perform web service invocations using a number of different implementation protocols like Axis, local Java, EJB, JMS, JCA CCI etc.</p>
-<p>For more information on how to use it with ActiveMQ, take a look at: <a shape="rect" class="external-link" href="http://servicemix.apache.org/wsif.html">http://servicemix.apache.org/wsif.html</a></p>
- </div>
+<p>For more information on how to use it with ActiveMQ, take a look at: <a shape="rect" class="external-link" href="http://servicemix.apache.org/wsif.html">http://servicemix.apache.org/wsif.html</a></p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/xbean-xml-reference-41.html
==============================================================================
--- websites/production/activemq/content/xbean-xml-reference-41.html (original)
+++ websites/production/activemq/content/xbean-xml-reference-41.html Wed Nov 13 17:23:00 2013
@@ -72,8 +72,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-<h3><a shape="rect" name="XBeanXMLReference4.1-ElementsByType"></a>Elements By Type</h3>
+<div class="wiki-content maincontent"><h3><a shape="rect" name="XBeanXMLReference4.1-ElementsByType"></a>Elements By Type</h3>
<p><a shape="rect" name="XBeanXMLReference4.1-org.apache.activemq.network.jms.InboundQueueBr..."></a></p>
<h4><a shape="rect" name="XBeanXMLReference4.1-Theorg.apache.activemq.network.jms.InboundQueueBridge%23org.apache.activemq.network.jms.InboundQueueBridgetypesTypeImplementations"></a>The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.InboundQueueBr...">org.apache.activemq.network.jms.InboundQueueBridge</a></em> Type Implementations</h4>
<div class="table-wrap">
@@ -875,8 +874,7 @@
<table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationEntryelement"><authorizationEntry></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Represents an entry in a {@link DefaultAuthorizationMap} for assigning different operations (read, write, admin) of user roles to a specific destination or a hierarchical wildcard area of destinations. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationMapelement"><authorizationMap></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies. Each entry in the map represents the authorization ACLs for each operation. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"
> <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationPluginelement"><authorizationPlugin></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> An authorization plugin where each operation on a destination is checked against an authorizationMap </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-axionJDBCAdapterelement"><axionJDBCAdapter></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Axion specific Adapter. Axion does not seem to support ALTER statements or sub-selects. This means: - We cannot auto upgrade the schema was we roll out new versions of ActiveMQ - We cannot delete durable sub messages that have be acknowledged by all consumers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-blobJDBCAdapterelement"><blobJDBCAdapter></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> This JDBCAdapte
r inserts and extracts BLOB data using the getBlob()/setBlob() operations. This is a little more involved since to insert a blob you have to: 1: insert empty blob. 2: select the blob 3: finally update the blob with data value. The databases/JDBC drivers that use this adapter are: <ul><li></li></ul> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-brokerelement"><broker></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> An ActiveMQ Message Broker which consists of a number of transport connectors, network connectors and a persistence adaptor </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-bytesJDBCAdapterelement"><bytesJDBCAdapter></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> This JDBCAdapter inserts and extracts BLOB data using the setBytes()/getBytes() operations. The databases/JDBC drivers that use this adapter
are: </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-compositeDemandForwardingBridgeelement"><compositeDemandForwardingBridge></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A demand forwarding bridge which works with multicast style transports where a single Transport could be communicating with multiple remote brokers </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-compositeQueueelement"><compositeQueue></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Represents a virtual queue which forwards to a number of other destinations. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-compositeTopicelement"><compositeTopic></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Represents a virtual topic which forwards to a number of other dest
inations. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-connectionDotFilePluginelement"><connectionDotFilePlugin></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A <a shape="rect" href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current connections </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-constantPendingMessageLimitStrategyelement"><constantPendingMessageLimitStrategy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> This PendingMessageLimitStrategy is configured to a constant value for all subscriptions. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-db2JDBCAdapterelement"><db2JDBCAdapter></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" r
owspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-defaultJDBCAdapterelement"><defaultJDBCAdapter></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. <p></p> sub-classing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p></p> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p></p> The databases/JDBC drivers that use this adapter are: <ul><li></li></ul> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-demandForwardingBridgeelement"><demandForwardingBridge></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Forwards messages from the local broker to the remote broker based on demand. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a
shape="rect" href="#XBeanXMLReference4.1-destinationDotFilePluginelement"><destinationDotFilePlugin></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A <a shape="rect" href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current topic & queue hierarchies. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-destinationEntryelement"><destinationEntry></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A default entry in a DestinationMap which holds a single value. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-fixedCountSubscriptionRecoveryPolicyelement"><fixedCountSubscriptionRecoveryPolicy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message. </td></tr><tr><td colspa
n="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-fixedSizedSubscriptionRecoveryPolicyelement"><fixedSizedSubscriptionRecoveryPolicy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed amount of memory available in RAM for message history which is evicted in time order. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-forwardingBridgeelement"><forwardingBridge></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Forwards all messages from the local broker to the remote broker. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-imageBasedJDBCAdaptorelement"><imageBasedJDBCAdaptor></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Provides JDBCAdapter since that uses IMAGE datatype to hold binar
y data. The databases/JDBC drivers that use this adapter are: <ul><li>Sybase</li><li>MS SQL</li></ul> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-inboundQueueBridgeelement"><inboundQueueBridge></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Create an Inbound Queue Bridge </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-inboundTopicBridgeelement"><inboundTopicBridge></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Create an Inbound Topic Bridge </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-individualDeadLetterStrategyelement"><individualDeadLetterStrategy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A {@link DeadLetterStrategy} where each destination has its own individual DLQ using the subject naming hierarchy. </td></t
r><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-informixJDBCAdapterelement"><informixJDBCAdapter></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> JDBC Adapter for Informix database. Because Informix database restricts length of composite primary keys, length of <i>container name</i> field and <i>subscription id</i> field must be reduced to 150 characters. Therefore be sure not to use longer names for container name and subscription id than 150 characters. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-jaasAuthenticationPluginelement"><jaasAuthenticationPlugin></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Provides a JAAS based authentication plugin </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-jdbcPersistenceAdapterelement"><jdbcPersistenceAdapter>
</a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A {@link PersistenceAdapter} implementation using JDBC for persistence storage. This persistence adapter will correctly remember prepared XA transactions, but it will not keep track of local transaction commits so that operations performed against the Message store are done as a single uow. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-jmsQueueConnectorelement"><jmsQueueConnector></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A Bridge to other JMS Queue providers </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-jmsTopicConnectorelement"><jmsTopicConnector></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A Bridge to other JMS Topic providers </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference
4.1-journalPersistenceAdapterelement"><journalPersistenceAdapter></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-journaledJDBCelement"><journaledJDBC></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Creates a default persistence model using the Journal and JDBC </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-kahaPersistenceAdapterelement"><kahaPersistenceAdapter></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-lastImageSubscriptionRecoveryPolicyel
ement"><lastImageSubscriptionRecoveryPolicy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-loggingBrokerPluginelement"><loggingBrokerPlugin></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A simple Broker interceptor which allows you to enable/disable logging. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-managementContextelement"><managementContext></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A Flow provides different dispatch policies within the NMR </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-memoryPersistenceAdapterelement"><memoryPersistenceAdapter></a></em> </td><td cols
pan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-multicastNetworkConnectorelement"><multicastNetworkConnector></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A network connector which uses some kind of multicast-like transport that communicates with potentially many remote brokers over a single logical {@link Transport} instance such as when using multicast. This implementation does not depend on multicast at all; any other group based transport could be used. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-networkConnectorelement"><networkConnector></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A network connector which uses a discovery agent to detect the remote brokers available and setup a connection to each available remote broker </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-noSubscriptionRecoveryPolicyelement"><noSubscriptionRecoveryPolicy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> This is the default Topic recovery policy which does not recover any messages. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-oldestMessageEvictionStrategyelement"><oldestMessageEvictionStrategy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> An eviction strategy which evicts the oldest message first (which is the default). </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-oldestMessageWithLowestPriorityEvictionStrateg..."><oldestMessageWithLowestPriorityEvictionStrategy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> An eviction strategy which evicts the oldest message with the lowest priority fi
rst. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-oracleJDBCAdapterelement"><oracleJDBCAdapter></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. <p></p> Subclassing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p></p> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p></p> The databases/JDBC drivers that use this adapter are: <ul><li></li></ul> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-outboundQueueBridgeelement"><outboundQueueBridge></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Create an Outbound Queue Bridge </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href=
"#XBeanXMLReference4.1-outboundTopicBridgeelement"><outboundTopicBridge></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Create an Outbound Topic Bridge </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-policyEntryelement"><policyEntry></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Represents an entry in a {@link PolicyMap} for assigning policies to a specific destination or a hierarchical wildcard area of destinations. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-policyMapelement"><policyMap></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="re
ct" href="#XBeanXMLReference4.1-prefetchRatePendingMessageLimitStrategyelement"><prefetchRatePendingMessageLimitStrategy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> This PendingMessageLimitStrategy sets the maximum pending message limit value to be a multiplier of the prefetch limit of the subscription. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-proxyConnectorelement"><proxyConnector></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-queryBasedSubscriptionRecoveryPolicyelement"><queryBasedSubscriptionRecoveryPolicy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> This implementation of {@link SubscriptionRecoveryPolicy} will perform a user specific query mechanism to load any messages they may have missed. </td></tr><tr><td colspan=
"1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-queueelement"><queue></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> An ActiveMQ Queue Destination </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-quickJournalPersistenceAdapterelement"><quickJournalPersistenceAdapter></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-rapidPersistenceAdapterelement"><rapidPersistenceAdapter></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointi
ng asynchronously on a timeout with some other long term persistent storage. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-roundRobinDispatchPolicyelement"><roundRobinDispatchPolicy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Simple dispatch policy that sends a message to every subscription that matches the message. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-sharedDeadLetterStrategyelement"><sharedDeadLetterStrategy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> A default implementation of {@link DeadLetterStrategy} which uses a constant destination. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-simpleAuthenticationPluginelement"><simpleAuthenticationPlugin></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Provides
a simple authentication plugin configured with a map of user-passwords and a map of user-groups </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-simpleAuthorizationMapelement"><simpleAuthorizationMap></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> An AuthorizationMap which is configured with individual DestinationMaps for each operation. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-simpleDispatchPolicyelement"><simpleDispatchPolicy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Simple dispatch policy that sends a message to every subscription that matches the message. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-simpleJmsMessageConvertorelement"><simpleJmsMessageConvertor></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd">
Converts Message from one JMS to another </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-statementselement"><statements></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-streamJDBCAdapterelement"><streamJDBCAdapter></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> This JDBCAdapter inserts and extracts BLOB data using the setBinaryStream()/getBinaryStream() operations. The databases/JDBC drivers that use this adapter are: <ul><li>Axion</li></ul> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-strictOrderDispatchPolicyelement"><strictOrderDispatchPolicy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Dispatch policy that causes every subscription to see messages in the same order.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-timedSubscriptionRecoveryPolicyelement"><timedSubscriptionRecoveryPolicy></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed buffer of messages around in memory and use that to recover new subscriptions. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-topicelement"><topic></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> An ActiveMQ Topic Destination </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-transportConnectorelement"><transportConnector></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-usag
eManagerelement"><usageManager></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Used to keep track of how much of something is being used so that a productive working set usage can be controlled. Main use case is manage memory usage. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-virtualDestinationInterceptorelement"><virtualDestinationInterceptor></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Implements <a shape="rect" href="http://incubator.apache.org/activemq/virtual-destinations.html">Virtual Topics</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em><a shape="rect" href="#XBeanXMLReference4.1-virtualTopicelement"><virtualTopic></a></em> </td><td colspan="1" rowspan="1" class="confluenceTd"> Creates <a shape="rect" href="http://activemq.org/site/virtual-destinations.html">Virtual Topics</a> using a prefix and postfix. The virtual destination c
reates a wildcard that is then used to look up all active queue subscriptions which match. </td></tr></tbody></table>
</div>
-
- </div>
+</div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/xbean-xml-reference-50.html
==============================================================================
--- websites/production/activemq/content/xbean-xml-reference-50.html (original)
+++ websites/production/activemq/content/xbean-xml-reference-50.html Wed Nov 13 17:23:00 2013
@@ -72,8 +72,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-<h3><a shape="rect" name="XBeanXMLReference5.0-ElementsByType"></a>Elements By Type</h3>
+<div class="wiki-content maincontent"><h3><a shape="rect" name="XBeanXMLReference5.0-ElementsByType"></a>Elements By Type</h3>
<p><a shape="rect" name="XBeanXMLReference5.0-org.apache.activemq.broker.TransportConnectortypes"></a></p>
<h4><a shape="rect" name="XBeanXMLReference5.0-Theorg.apache.activemq.broker.TransportConnector%23org.apache.activemq.broker.TransportConnectortypesTypeImplementations"></a>The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.TransportConnectortypes">org.apache.activemq.broker.TransportConnector</a></em> Type Implementations</h4>
<div class="table-wrap">
@@ -1862,8 +1861,7 @@ so that connections created have client
easier comprehension from <a shape="rect" href="http://activemq.apache.org/jmx.html">JMX</a>. </td></tr></tbody></table>
</div>
-
- </div>
+</div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/xml-configuration.html
==============================================================================
--- websites/production/activemq/content/xml-configuration.html (original)
+++ websites/production/activemq/content/xml-configuration.html Wed Nov 13 17:23:00 2013
@@ -82,8 +82,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-<p>We support an XML deployment descriptor for configuring the ActiveMQ Message Broker. There are many things which can be configured such as</p>
+<div class="wiki-content maincontent"><p>We support an XML deployment descriptor for configuring the ActiveMQ Message Broker. There are many things which can be configured such as</p>
<ul><li>transport connectors which consist of transport channels and wire formats TODO: add a link to a page explaining what transport connectors are how to configure and use them.</li><li>network connectors using network channels or discovery TODO: add a link to a page explaining what network connectors are how to configure and use them.</li><li>discovery agents TODO: add a link to a page explaining what discovery agents are how to configure and use them.</li><li>persistence providers & locations TODO: add a link to a page explaining what persistence providers are how to configure and use them.</li><li>custom message containers (such as last image caching etc)</li></ul>
@@ -307,8 +306,7 @@ Or of you want to explicitly configure t
<p>So we use the <a shape="rect" class="external-link" href="http://www.springframework.org/docs/reference/beans.html#beans-basics" rel="nofollow">Spring XML</a> configuration file format, which allows any beans / POJOs to be wired together and configured. However often Spring's XML can be kinda verbose at times, so we have implemented an ActiveMQ extension to the Spring XML which knows about the common, standard ActiveMQ things you're likely to do (e.g. tags like connector, wireFormat, serverTransport, persistence) - but at any time you can fall back to the normal Spring way of doing things (with tags like bean, property etc).</p>
-<p>To see documentation of the XML file we use or to get access to the XSD/DTD see the <a shape="rect" href="xml-reference.html" title="Xml Reference">Xml Reference</a></p>
- </div>
+<p>To see documentation of the XML file we use or to get access to the XSD/DTD see the <a shape="rect" href="xml-reference.html" title="Xml Reference">Xml Reference</a></p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/xml-reference.html
==============================================================================
--- websites/production/activemq/content/xml-reference.html (original)
+++ websites/production/activemq/content/xml-reference.html Wed Nov 13 17:23:00 2013
@@ -82,8 +82,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-<h2><a shape="rect" name="XmlReference-ActiveMQXmlReference"></a>ActiveMQ Xml Reference</h2>
+<div class="wiki-content maincontent"><h2><a shape="rect" name="XmlReference-ActiveMQXmlReference"></a>ActiveMQ Xml Reference</h2>
<p>This page contains a link to the XML reference guides and XML schema documents for <a shape="rect" href="xml-configuration.html" title="Xml Configuration">Xml Configuration</a> with ActiveMQ releases</p>
@@ -323,8 +322,7 @@ ACTIVEMQ_HOME: /Users/bsnyder/amq/apache
ACTIVEMQ_BASE: /Users/bsnyder/amq/apache-activemq-5.4.1<br clear="none">
Loading message broker from: xbean:<a shape="rect" class="external-link" href="file:/Users/bsnyder/SpringSource/clients/Finra/activemq-example-unordered.xml" rel="nofollow">file:/Users/bsnyder/SpringSource/clients/Finra/activemq-example-unordered.xml</a><br clear="none">
...</p>
-</div></div>
- </div>
+</div></div> </div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/xmpp.html
==============================================================================
--- websites/production/activemq/content/xmpp.html (original)
+++ websites/production/activemq/content/xmpp.html Wed Nov 13 17:23:00 2013
@@ -81,8 +81,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-<h2><a shape="rect" name="XMPP-XMPPProtocolSupport%28Jabber%5C%21%29"></a>XMPP Protocol Support (Jabber!)</h2>
+<div class="wiki-content maincontent"><h2><a shape="rect" name="XMPP-XMPPProtocolSupport%28Jabber%5C%21%29"></a>XMPP Protocol Support (Jabber!)</h2>
<p>We have support for <a shape="rect" class="external-link" href="http://www.xmpp.org/" rel="nofollow">XMPP</a> (Jabber) as a transport in ActiveMQ.</p>
@@ -168,8 +167,7 @@ Tested version 4.0.7 works fine, but it
<h4><a shape="rect" name="XMPP-Adium"></a>Adium</h4>
<p>Url: <a shape="rect" class="external-link" href="http://www.adiumx.com/" rel="nofollow">http://www.adiumx.com/</a><br clear="none">
-Tested version 1.3.3 works fine. The only spotted issue is reconnecting to <a shape="rect" href="command-agent.html" title="Command Agent">Command Agent</a> topic. We recommend that you restart the Adium if you need to do this </p>
- </div>
+Tested version 1.3.3 works fine. The only spotted issue is reconnecting to <a shape="rect" href="command-agent.html" title="Command Agent">Command Agent</a> topic. We recommend that you restart the Adium if you need to do this </p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/zeroconf-transport-reference.html
==============================================================================
--- websites/production/activemq/content/zeroconf-transport-reference.html (original)
+++ websites/production/activemq/content/zeroconf-transport-reference.html Wed Nov 13 17:23:00 2013
@@ -81,8 +81,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-<h3><a shape="rect" name="ZeroConfTransportReference-TheZeroConfTransport"></a>The ZeroConf Transport</h3>
+<div class="wiki-content maincontent"><h3><a shape="rect" name="ZeroConfTransportReference-TheZeroConfTransport"></a>The ZeroConf Transport</h3>
<p>The ZeroConf transport works just like <a shape="rect" href="discovery-transport-reference.html" title="Discovery Transport Reference">Discovery Transport</a>, except that it uses a <a shape="rect" href="zeroconf.html" title="ZeroConf">ZeroConf</a> based discovery agent to locate the list of broker uris to connect to.</p>
@@ -113,8 +112,7 @@ or<br clear="none">
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
<pre>zeroconf:_activemq_development.
</pre>
-</div></div>
- </div>
+</div></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/zeroconf.html
==============================================================================
--- websites/production/activemq/content/zeroconf.html (original)
+++ websites/production/activemq/content/zeroconf.html Wed Nov 13 17:23:00 2013
@@ -72,8 +72,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-<h2><a shape="rect" name="ZeroConf-ZeroConf"></a>ZeroConf</h2>
+<div class="wiki-content maincontent"><h2><a shape="rect" name="ZeroConf-ZeroConf"></a>ZeroConf</h2>
<p><a shape="rect" class="external-link" href="http://www.zeroconf.org/" rel="nofollow">ZeroConf</a> is a standard service discovery mechanism. ZeroConf is used on Apple's OS X; which used to call it Rendezvous but now calls it Bonjour.</p>
@@ -85,8 +84,7 @@ based tools can be used in conjunction w
<p>You can use ZeroConf with ActiveMQ's <a shape="rect" href="discovery.html" title="Discovery">Discovery</a> mechanism. For more details see</p>
<ul><li><a shape="rect" href="discovery.html" title="Discovery">Discovery</a></li><li><a shape="rect" href="zeroconf-transport-reference.html" title="ZeroConf Transport Reference">ZeroConf Transport Reference</a></li></ul>
-
- </div>
+</div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/zos.html
==============================================================================
--- websites/production/activemq/content/zos.html (original)
+++ websites/production/activemq/content/zos.html Wed Nov 13 17:23:00 2013
@@ -81,8 +81,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
- <div class="wiki-content maincontent">
-<h1><a shape="rect" name="zOS-RunningActiveMQonz%2FOS"></a>Running ActiveMQ on z/OS</h1>
+<div class="wiki-content maincontent"><h1><a shape="rect" name="zOS-RunningActiveMQonz%2FOS"></a>Running ActiveMQ on z/OS</h1>
<p>It is relatively straightforward to run the ActiveMQ broker on z/OS.</p>
@@ -241,8 +240,7 @@ export IBM_JAVA_ZOS_TDUMP=NO
<p>Once the broker has been started on z/OS, modify one of the example application to have the hostname of the z/OS system and run it to confirm that the broker is functioning correctly.</p>
-<p>You can also gather information about the broker as usual using <a shape="rect" href="jmx.html" title="JMX">JMX</a>.</p>
- </div>
+<p>You can also gather information about the broker as usual using <a shape="rect" href="jmx.html" title="JMX">JMX</a>.</p></div>
</td>
<td valign="top">
<div class="navigation">