You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by ro...@apache.org on 2021/02/17 11:41:21 UTC
[activemq-website] branch master updated: Remove stale files from
intermediate stages of website rework.
This is an automated email from the ASF dual-hosted git repository.
robbie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/activemq-website.git
The following commit(s) were added to refs/heads/master by this push:
new d2eec59 Remove stale files from intermediate stages of website rework.
d2eec59 is described below
commit d2eec59462ff9b3afde11766d3babc85a42e1467
Author: Robbie Gemmell <ro...@apache.org>
AuthorDate: Wed Feb 17 11:03:04 2021 +0000
Remove stale files from intermediate stages of website rework.
These dont appear to be used. The dir is unchanged since before the new
site was published, it has stale files and largely duplicate content,
and removing the src files makes no difference to the generated output
from Jekyll that is published on the actual site (on asf-site branch).
If they are needed again for some reason they can be found in the repo
history via this commit or via PR #3 which added them.
---
src/_documents/README.md | 30 -
.../JBoss Integration/inbound-communication.md | 107 -
.../JBoss Integration/outbound-communication.md | 168 -
.../Resource Adapter/activation-spec-properties.md | 199 -
.../connection-factory-properties.md | 65 -
.../resource-adapter-properties.md | 180 -
.../Containers/Resource Adapter/tomee.md | 95 -
.../Spring Support/jmstemplate-gotchas.md | 29 -
.../Tomcat/setting-up-activemq-with-tomcat-559.md | 51 -
.../Containers/axis-and-cxf-support.md | 17 -
.../classic/Connectivity/Containers/blazeds.md | 54 -
.../classic/Connectivity/Containers/geronimo.md | 208 -
.../integrating-apache-activemq-with-glassfish.md | 50 -
.../integrating-apache-activemq-with-jboss.md | 724 ---
.../classic/Connectivity/Containers/j2ee.md | 56 -
.../Connectivity/Containers/jboss-integration.md | 724 ---
.../Connectivity/Containers/jca-container.md | 58 -
.../Connectivity/Containers/jndi-support.md | 86 -
.../Containers/old-osgi-integration.md | 166 -
.../Connectivity/Containers/osgi-integration.md | 114 -
.../Connectivity/Containers/resource-adapter.md | 54 -
.../Containers/sjsas-with-genericjmsra.md | 164 -
.../Connectivity/Containers/spring-support.md | 109 -
.../classic/Connectivity/Containers/sun-jndi.md | 99 -
.../classic/Connectivity/Containers/tomcat.md | 101 -
.../Containers/weblogic-integration.md | 618 ---
.../classic/Connectivity/Containers/zos.md | 174 -
.../ActiveMQ C++ Clients/activemq-c-development.md | 99 -
.../ActiveMQ C++ Clients/building-activemq-cpp.md | 141 -
.../configuring-activemq-cpp.md | 242 -
.../downloading-activemq-cpp.md | 23 -
.../ActiveMQ C++ Clients/openwire-cpp-client.md | 113 -
.../C Integration/c-integration-scenarios.md | 52 -
.../C Integration/compile-activemq-with-gcj.md | 255 -
.../C Integration/openwire-c-client.md | 15 -
.../Cross Language Clients/activemq-c-clients.md | 10 -
.../Cross Language Clients/c-integration.md | 22 -
.../Connectivity/Cross Language Clients/cms.md | 169 -
.../delphi-and-freepascal.md | 26 -
.../Connectivity/Cross Language Clients/dot-net.md | 166 -
.../Connectivity/Cross Language Clients/perl.md | 177 -
.../Connectivity/Cross Language Clients/php.md | 170 -
.../Connectivity/Cross Language Clients/pike.md | 169 -
.../Connectivity/Cross Language Clients/python.md | 171 -
.../Connectivity/Cross Language Clients/ruby.md | 185 -
.../OpenWire/openwire-version-2-specification.md | 561 ---
.../classic/Connectivity/Protocols/amqp.md | 353 --
.../classic/Connectivity/Protocols/auto.md | 124 -
.../classic/Connectivity/Protocols/mqtt.md | 124 -
.../classic/Connectivity/Protocols/openwire.md | 26 -
.../classic/Connectivity/Protocols/rest.md | 216 -
.../classic/Connectivity/Protocols/rss-and-atom.md | 45 -
.../classic/Connectivity/Protocols/stomp.md | 431 --
.../Connectivity/Protocols/ws-notification.md | 10 -
.../classic/Connectivity/Protocols/wsif.md | 9 -
.../classic/Connectivity/Protocols/xmpp.md | 102 -
src/_documents/classic/Connectivity/ajax.md | 170 -
src/_documents/classic/Connectivity/containers.md | 26 -
.../classic/Connectivity/cross-language-clients.md | 1028 ----
.../classic/Connectivity/jms-to-jms-bridge.md | 559 ---
src/_documents/classic/Connectivity/protocols.md | 18 -
src/_documents/classic/Connectivity/websockets.md | 73 -
...lass-diagrams-for-activemq-40-m4-source-code.md | 17 -
.../durable-queue-memory-management.md | 42 -
.../message-redelivery-and-dlq-handling.md | 217 -
.../Design Documents/multicast-transport.md | 17 -
.../proposed-c-client-architecture.md | 17 -
.../Design Documents/rest-protocols.md | 57 -
.../Design Documents/slow-consumers.md | 80 -
.../Design Documents/supporting-io-streams.md | 41 -
.../Developer Guide/Release Plans/40-rc-1-guide.md | 47 -
.../Release Plans/how-you-can-help-release.md | 12 -
.../Developer Guide/Release Plans/release-info.md | 13 -
.../Developers/Developer Guide/design-documents.md | 13 -
.../Developer Guide/developing-plugins.md | 68 -
.../maven-snapshot-repository-in-your-pom.md | 33 -
.../Developers/Developer Guide/release-plans.md | 14 -
.../classic/Developers/Ideas/restful-queue.md | 156 -
.../Integration Tests/example-testing-scenario.md | 129 -
.../classic/Developers/becoming-a-committer.md | 44 -
.../classic/Developers/benchmark-tests.md | 18 -
src/_documents/classic/Developers/board-reports.md | 12 -
src/_documents/classic/Developers/building.md | 74 -
src/_documents/classic/Developers/code-overview.md | 121 -
.../classic/Developers/developer-guide.md | 21 -
src/_documents/classic/Developers/ideas.md | 9 -
.../classic/Developers/integration-tests.md | 55 -
.../classic/Developers/jmeter-performance-tests.md | 83 -
.../classic/Developers/jmeter-system-tests.md | 58 -
src/_documents/classic/Developers/junit-reports.md | 7 -
src/_documents/classic/Developers/release-guide.md | 190 -
src/_documents/classic/Developers/sandbox.md | 5 -
src/_documents/classic/Developers/source-xref.md | 9 -
src/_documents/classic/Developers/source.md | 56 -
src/_documents/classic/Developers/svn.md | 56 -
.../classic/Developers/test-source-xref.md | 8 -
src/_documents/classic/Developers/wire-protocol.md | 71 -
.../enable-openssl-support-with-autotools.md | 8 -
...event-autoconf-from-enabling-openssl-support.md | 8 -
.../how-to-enable-ssl-support-on-windows.md | 6 -
...ibstdla-on-solaris-10-using-the-gnu-compiler.md | 85 -
.../errors-saying-no-rule-to-make-target.md | 6 -
.../using-the-solaris-cc-compiler.md | 21 -
.../FAQ/Building FAQs/general-build-issues.md | 8 -
.../classic/FAQ/Building FAQs/openssl-support.md | 10 -
.../classic/FAQ/Building FAQs/solaris-platform.md | 10 -
.../how-can-i-enable-detailed-logging.md | 28 -
...e-10s-of-1000s-of-queues-in-a-single-broker-.md | 43 -
...re-10s-of-1000s-of-queues-in-a-single-broker.md | 43 -
...-to-hold-100s-of-millions-of-queue-messages-.md | 13 -
...q-to-hold-100s-of-millions-of-queue-messages.md | 13 -
...nfigure-activemq-to-use-aio-server-transport.md | 50 -
.../how-do-i-configure-automatic-reconnection.md | 15 -
...-do-i-configure-distributed-queues-or-topics.md | 22 -
.../how-do-i-configure-the-queues-i-want.md | 13 -
...-local-address-and-local-port-for-tcp-or-ssl.md | 14 -
.../Configuration/how-do-i-disable-persistence.md | 15 -
.../how-do-i-run-activemq-under-the-kaffe-jvm.md | 40 -
.../how-does-xbean-compare-to-spring-2.md | 27 -
.../how-to-configure-a-new-database.md | 43 -
...to-deploy-activemq-ra-versionrar-to-weblogic.md | 37 -
.../how-to-disable-multicast-discovery.md | 26 -
.../how-can-i-add-a-new-type-of-transport.md | 15 -
.../Developing ActiveMQ/how-can-i-contribute.md | 96 -
.../how-do-i-add-my-own-plugins.md | 7 -
.../how-do-i-debug-activemq-from-my-ide.md | 11 -
.../FAQ/Errors/Exceptions/certificateunknown.md | 29 -
...oexception-could-not-find-class-for-resource.md | 27 -
.../Exceptions/javaiointerruptedioexception.md | 13 -
...e-derbydb-see-the-next-exception-for-details.md | 83 -
.../Errors/Exceptions/javalangnosuchmethoderror.md | 27 -
...aactivemqresourceadaptersetuseembeddedbroker.md | 39 -
.../FAQ/Errors/Exceptions/javalangoutofmemory.md | 66 -
...on-timeout-peer-did-not-send-his-wire-format.md | 34 -
...otstrap-classloader-but-this-ri-needs-21-api.md | 10 -
...rap-classloader-but-this-ri-xxx-needs-21-api.md | 10 -
...ournal-is-already-opened-by-this-application.md | 37 -
.../FAQ/Errors/Exceptions/no-suitable-driver.md | 19 -
...ffounderror-orgspringframeworkcoreioresource.md | 17 -
...etreader-for-packet-type-unknown-packet-type.md | 15 -
src/_documents/classic/FAQ/Errors/exceptions.md | 21 -
...-having-problems-with-the-spring-jmstemplate.md | 10 -
...-am-not-receiving-any-messages-what-is-wrong.md | 19 -
.../i-cannot-connect-to-activemq-from-jconsole.md | 17 -
...o-not-receive-messages-in-my-second-consumer.md | 36 -
.../i-get-errors-building-the-code-whats-wrong.md | 13 -
...-warn-no-appenders-could-be-found-for-logger.md | 17 -
...-operating-system-or-distribution-or-network.md | 25 -
.../classic/FAQ/Errors/my-producer-blocks.md | 29 -
...ge-method-of-messagelistener-is-never-called.md | 7 -
...ce-adapter-does-not-seem-to-pool-connections.md | 14 -
.../Errors/slow-networks-drop-large-messages.md | 46 -
.../FAQ/Errors/the-broker-will-not-start.md | 11 -
...-a-broker-before-my-configured-broker-starts.md | 21 -
.../why-do-i-not-get-all-of-the-messages-i-sent.md | 11 -
...ve-messages-on-my-durable-topic-subscription.md | 18 -
...why-do-kahadb-log-files-remain-after-cleanup.md | 70 -
.../FAQ/General/can-i-get-commercial-support.md | 10 -
.../classic/FAQ/General/how-can-i-get-help.md | 49 -
...ow-can-i-get-the-source-code-from-subversion.md | 56 -
...how-do-i-avoid-maven-downloading-latest-jars.md | 13 -
.../how-do-i-build-but-disable-the-unit-tests.md | 14 -
.../General/how-do-i-compile-from-the-source.md | 10 -
.../FAQ/General/how-do-i-edit-the-website.md | 31 -
.../General/how-does-activemq-compare-to-amqp.md | 17 -
.../how-does-activemq-compare-to-artemis.md | 9 -
...does-activemq-compare-to-fuse-message-broker.md | 7 -
.../how-does-activemq-compare-to-jbossmq.md | 30 -
.../how-does-activemq-compare-to-mantaray.md | 13 -
.../General/how-does-activemq-compare-to-mule.md | 29 -
.../how-does-activemq-compare-to-spread-toolkit.md | 16 -
.../General/how-does-openwire-compare-to-stomp.md | 10 -
.../FAQ/General/how-does-the-website-work.md | 18 -
.../classic/FAQ/General/how-fast-is-activemq.md | 17 -
...tivemq-on-windows-in-a-directory-with-spaces.md | 12 -
.../classic/FAQ/General/what-is-activemq.md | 7 -
.../classic/FAQ/General/what-is-the-license.md | 10 -
.../classic/FAQ/General/what-jars-do-i-need.md | 10 -
...tegration-solution-works-best-with-activemq-.md | 11 -
...ntegration-solution-works-best-with-activemq.md | 11 -
.../what-platforms-does-activemq-support.md | 19 -
.../FAQ/General/what-version-should-i-use.md | 11 -
.../FAQ/JMS/can-i-modify-messages-on-a-queue.md | 10 -
...-messages-concurrently-on-one-jms-connection.md | 13 -
.../classic/FAQ/JMS/can-you-browse-a-topic.md | 13 -
.../JMS/how-do-durable-queues-and-topics-work.md | 19 -
.../FAQ/JMS/how-do-i-consume-a-specific-message.md | 18 -
.../FAQ/JMS/how-do-i-get-started-with-jms.md | 12 -
.../FAQ/JMS/how-do-i-make-messages-durable.md | 12 -
...t-destinations-from-a-single-messageproducer.md | 16 -
.../FAQ/JMS/how-do-i-use-jms-efficiently.md | 42 -
.../FAQ/JMS/how-does-a-queue-compare-to-a-topic.md | 15 -
...-does-connectionfactory-relate-to-the-broker.md | 16 -
.../FAQ/JMS/how-does-jms-compare-with-email.md | 11 -
...should-i-implement-request-response-with-jms.md | 249 -
.../classic/FAQ/JMS/how-to-unit-test-jms-code.md | 112 -
.../FAQ/JMS/multiple-consumers-on-a-queue.md | 13 -
.../classic/FAQ/JMS/should-i-use-transactions.md | 26 -
src/_documents/classic/FAQ/JMS/should-i-use-xa.md | 50 -
.../FAQ/JMS/what-are-administered-objects.md | 22 -
.../are-messages-read-directly-from-the-journal.md | 9 -
.../does-activemq-support-my-sql-database.md | 7 -
.../how-do-i-back-up-kahadb.md | 12 -
...ssage-store-directory-for-an-embedded-broker.md | 11 -
...w-does-journaling-work-with-multiple-brokers.md | 7 -
.../how-does-the-journal-work.md | 7 -
.../is-there-a-specified-size-of-the-journal.md | 7 -
...at-happens-when-the-journal-size-is-exceeded.md | 7 -
...tween-persistent-and-non-persistent-delivery.md | 19 -
src/_documents/classic/FAQ/Terminology/dr.md | 9 -
src/_documents/classic/FAQ/Terminology/ha.md | 9 -
src/_documents/classic/FAQ/Terminology/latency.md | 9 -
src/_documents/classic/FAQ/Terminology/mom.md | 9 -
src/_documents/classic/FAQ/Terminology/qos.md | 13 -
src/_documents/classic/FAQ/Terminology/seda.md | 7 -
.../classic/FAQ/Terminology/throughput.md | 9 -
.../activemq-command-line-tools-reference.md | 788 ---
.../are-destinations-case-sensitive.md | 7 -
.../can-i-send-really-large-files-over-activemq.md | 16 -
.../can-i-use-activemq-5x-or-later-on-java-14.md | 19 -
.../can-two-brokers-share-the-same-database.md | 14 -
.../does-activemq-support-clustering.md | 7 -
...id-serialization-of-objects-in-objectmessage.md | 7 -
...-a-list-of-the-topics-and-queues-in-a-broker.md | 16 -
.../how-can-i-make-activemq-faster.md | 7 -
.../how-can-i-monitor-activemq.md | 36 -
...can-i-monitor-the-connection-with-the-broker.md | 16 -
.../how-can-i-see-what-destinations-are-used.md | 11 -
.../how-can-i-support-auto-reconnection.md | 20 -
.../how-can-i-support-priority-queues.md | 50 -
.../how-can-i-use-different-network-protocols.md | 7 -
.../how-do-distributed-queues-work.md | 55 -
.../how-do-i-access-activemq-from-c.md | 7 -
...w-do-i-access-activemq-from-csharp-or-dotnet.md | 7 -
...-i-access-activemq-from-ruby-perl-python-php.md | 7 -
.../how-do-i-bridge-different-jms-providers.md | 9 -
.../how-do-i-change-dispatch-policy.md | 33 -
.../how-do-i-change-the-logging.md | 120 -
...onnect-to-one-of-a-number-of-message-brokers.md | 11 -
.../how-do-i-create-new-destinations.md | 33 -
.../how-do-i-delete-a-destination.md | 20 -
.../how-do-i-disable-logging.md | 10 -
.../how-do-i-embed-a-broker-inside-a-connection.md | 201 -
.../how-do-i-enable-asynchronous-sending.md | 14 -
.../how-do-i-enable-debug-logging.md | 14 -
.../how-do-i-find-the-size-of-a-queue.md | 23 -
.../how-do-i-preserve-order-of-messages.md | 12 -
.../how-do-i-purge-a-queue.md | 24 -
.../how-do-i-restart-embedded-broker.md | 36 -
...nnections-from-creating-new-queues-or-topics.md | 12 -
.../Using Apache ActiveMQ/how-do-i-run-a-broker.md | 9 -
.../how-do-i-set-the-message-expiration.md | 10 -
...-activemq-broker-when-using-the-vm-transport.md | 9 -
.../how-do-i-unack-the-message-with-stomp.md | 56 -
...how-do-i-use-activemq-using-in-jvm-messaging.md | 17 -
...-durable-subscribers-in-a-network-of-brokers.md | 25 -
.../how-do-i-use-ivy-with-activemq.md | 44 -
...ow-do-i-use-log4j-jms-appender-with-activemq.md | 79 -
.../FAQ/Using Apache ActiveMQ/how-do-i-use-ssl.md | 133 -
.../how-do-message-groups-compare-to-selectors.md | 21 -
.../how-do-multiple-transports-work.md | 11 -
.../how-do-transactions-work.md | 16 -
.../how-lightweight-is-sending-a-message.md | 17 -
...ackage-applications-using-camel-and-activemq.md | 17 -
.../how-should-i-use-the-vm-transport.md | 28 -
...deal-with-large-number-of-threads-in-clients.md | 34 -
.../how-to-disable-auto-destination-creation.md | 7 -
.../i-see-nc-client-ids-what-does-that-mean.md | 14 -
...atterns-in-the-broker-or-another-application.md | 24 -
...deploy-the-broker-inside-my-jvm-or-appserver.md | 26 -
.../what-are-those-topics-activemqadvisory.md | 7 -
...ppens-with-a-fast-producer-and-slow-consumer.md | 9 -
...-a-virtual-topic-and-a-composite-destination.md | 18 -
...nce-between-discovery-multicast-and-zeroconf.md | 35 -
.../what-is-the-prefetch-limit-for.md | 62 -
...ivemq-is-there-a-way-to-measure-its-progress.md | 10 -
src/_documents/classic/FAQ/building-faqs.md | 16 -
src/_documents/classic/FAQ/configuration.md | 22 -
src/_documents/classic/FAQ/developing-activemq.md | 12 -
src/_documents/classic/FAQ/errors.md | 39 -
src/_documents/classic/FAQ/general.md | 32 -
src/_documents/classic/FAQ/jms.md | 26 -
.../classic/FAQ/persistence-questions.md | 17 -
.../classic/FAQ/should-i-pool-connections.md | 14 -
src/_documents/classic/FAQ/terminology.md | 98 -
.../classic/FAQ/using-apache-activemq.md | 68 -
.../Features/ActiveMQ Real Time/broadcasting.md | 40 -
.../ActiveMQ Real Time/group-membership.md | 33 -
.../Features/ActiveMQ Real Time/life-cycle.md | 52 -
.../the-activeblaze-message-type.md | 61 -
.../Clustering/MasterSlave/jdbc-master-slave.md | 131 -
.../Clustering/MasterSlave/kahadb-master-slave.md | 231 -
.../MasterSlave/kahadb-replication-experimental.md | 65 -
.../Clustering/MasterSlave/pure-master-slave.md | 108 -
.../MasterSlave/shared-file-system-master-slave.md | 87 -
.../classic/Features/Clustering/masterslave.md | 44 -
.../Features/Clustering/networks-of-brokers.md | 543 --
.../Clustering/replicated-message-store.md | 33 -
.../Consumer Features/consumer-dispatch-async.md | 35 -
.../Consumer Features/consumer-priority.md | 20 -
.../Consumer Features/exclusive-consumer.md | 28 -
.../manage-durable-subscribers.md | 47 -
.../Features/Consumer Features/message-groups.md | 144 -
.../Consumer Features/redelivery-policy.md | 94 -
.../Consumer Features/retroactive-consumer.md | 28 -
.../Features/Consumer Features/selectors.md | 37 -
.../Consumer Features/slow-consumer-handling.md | 87 -
.../subscription-recovery-policy.md | 75 -
.../Destination Features/composite-destinations.md | 27 -
.../configure-startup-destinations.md | 15 -
.../delete-inactive-destinations.md | 33 -
.../Destination Features/destination-options.md | 70 -
.../Destination Features/mirrored-queues.md | 42 -
.../per-destination-policies.md | 348 --
.../Destination Features/virtual-destinations.md | 181 -
.../Features/Destination Features/wildcards.md | 67 -
.../Features/Horizontal Scaling/scaling-queues.md | 43 -
.../Features/Interceptors/destinations-plugin.md | 13 -
.../Features/Interceptors/logging-interceptor.md | 88 -
.../Features/Interceptors/statisticsplugin.md | 156 -
.../Features/Interceptors/timestampplugin.md | 56 -
src/_documents/classic/Features/JMX/jmx-support.md | 66 -
.../Message Dispatching Features/async-sends.md | 42 -
.../dispatch-policies.md | 36 -
.../message-cursors.md | 94 -
.../optimized-acknowledgement.md | 26 -
.../producer-flow-control.md | 115 -
.../Message Dispatching Features/total-ordering.md | 36 -
.../activemq-message-properties.md | 168 -
.../Features/Message Features/advisory-message.md | 543 --
.../Features/Message Features/blob-messages.md | 57 -
.../delay-and-schedule-message-delivery.md | 81 -
.../Features/Message Features/jms-streams.md | 57 -
.../Message Features/message-transformation.md | 31 -
.../Features/Message Features/object-message.md | 5 -
.../Features/Message Features/objectmessage.md | 69 -
...tructured-message-properties-and-mapmessages.md | 20 -
.../New Features in 5.9/runtime-configuration.md | 34 -
.../classic/Features/New Features/changes-in-40.md | 60 -
.../Features/New Features/new-features-in-41.md | 14 -
.../Features/New Features/new-features-in-50.md | 20 -
.../Features/New Features/new-features-in-51.md | 20 -
.../Features/New Features/new-features-in-511.md | 18 -
.../Features/New Features/new-features-in-513.md | 18 -
.../Features/New Features/new-features-in-52.md | 26 -
.../Features/New Features/new-features-in-53.md | 22 -
.../Features/New Features/new-features-in-54.md | 27 -
.../Features/New Features/new-features-in-55.md | 23 -
.../Features/New Features/new-features-in-56.md | 17 -
.../Features/New Features/new-features-in-57.md | 13 -
.../Features/New Features/new-features-in-58.md | 12 -
.../Features/New Features/new-features-in-59.md | 14 -
.../Features/New Features/new-features-in-60.md | 7 -
.../sample-report.md | 76 -
.../activemq-performance-module-users-manual.md | 697 ---
.../Performance/load-testing-with-camel.md | 18 -
.../Features/Performance/performance-report.md | 12 -
.../Features/Persistence/JDBC Support/sqlserver.md | 95 -
.../Features/Persistence/JDBC Support/sybase.md | 34 -
.../Features/Persistence/Kaha Persistence/test.md | 166 -
.../Features/Persistence/amq-message-store.md | 160 -
.../configurable-ioexception-handling.md | 122 -
.../classic/Features/Persistence/jdbc-support.md | 78 -
.../Features/Persistence/kaha-persistence.md | 38 -
.../classic/Features/Persistence/kahadb.md | 298 --
.../classic/Features/Persistence/leveldb-store.md | 127 -
.../periodically-checking-disk-limits.md | 15 -
.../Persistence/pluggable-storage-lockers.md | 151 -
.../Persistence/replicated-leveldb-store.md | 228 -
.../classic/Features/Security/audit-logging.md | 38 -
.../Security/cached-ldap-authorization-module.md | 146 -
.../Features/Security/encrypted-passwords.md | 96 -
src/_documents/classic/Features/Security/shiro.md | 370 --
.../classic/Features/URI Protocols/vm-protocol.md | 18 -
.../classic/Features/Unix/unix-service.md | 11 -
.../classic/Features/Unix/unix-shell-script.md | 199 -
.../Visualisation/visualisation-wish-list.md | 11 -
src/_documents/classic/Features/active-groups.md | 23 -
.../classic/Features/activemq-real-time.md | 54 -
.../classic/Features/broker-camel-component.md | 70 -
src/_documents/classic/Features/clustering.md | 61 -
src/_documents/classic/Features/command-agent.md | 45 -
.../classic/Features/consumer-features.md | 16 -
.../classic/Features/destination-features.md | 14 -
src/_documents/classic/Features/discovery.md | 66 -
.../Features/enterprise-integration-patterns.md | 55 -
.../classic/Features/features-overview.md | 24 -
.../classic/Features/horizontal-scaling.md | 5 -
src/_documents/classic/Features/interceptors.md | 127 -
src/_documents/classic/Features/jmsxuserid.md | 30 -
src/_documents/classic/Features/jmx.md | 342 --
...-warning-if-you-forget-to-start-a-connection.md | 14 -
src/_documents/classic/Features/mdc-logging.md | 39 -
.../Features/message-dispatching-features.md | 12 -
.../classic/Features/message-features.md | 14 -
src/_documents/classic/Features/new-features.md | 22 -
src/_documents/classic/Features/performance.md | 38 -
src/_documents/classic/Features/persistence.md | 105 -
.../Features/scaling-the-depth-of-a-queue.md | 13 -
src/_documents/classic/Features/security.md | 183 -
.../classic/Features/the-proxy-connector.md | 32 -
src/_documents/classic/Features/unix.md | 10 -
src/_documents/classic/Features/uri-protocols.md | 109 -
src/_documents/classic/Features/visualisation.md | 37 -
.../Tutorials/handling-advisory-messages.md | 538 --
src/_documents/classic/Overview/javadocs.md | 29 -
src/_documents/classic/Overview/news.md | 103 -
src/_documents/classic/Overview/tutorials.md | 11 -
src/_documents/classic/README.md | 2 -
src/_documents/classic/SUMMARY.md | 611 ---
src/_documents/classic/Site/Navigation/irc.md | 15 -
.../activemq-3-networks-of-brokers.md | 171 -
.../activemq-3-transport-configurations.md | 423 --
.../advisory-support-in-activemq-3.md | 178 -
.../Previous Versions/getting-started-3x.md | 437 --
.../Previous Versions/running-a-3x-broker.md | 225 -
.../classic/Site/Old Links/activemqdtd.md | 172 -
.../classic/Site/Old Links/activesoap.md | 200 -
.../classic/Site/Old Links/activespace.md | 168 -
src/_documents/classic/Site/Old Links/cvs.md | 196 -
.../classic/Site/Old Links/leftheader.md | 168 -
.../classic/Site/Old Links/new-features-in-42.md | 173 -
.../point-to-point-with-multiple-consumers.md | 180 -
src/_documents/classic/Site/Old Links/polo-page.md | 172 -
.../classic/Site/Old Links/previous-versions.md | 172 -
.../classic/Site/Old Links/rightheader.md | 168 -
src/_documents/classic/Site/Old Links/stp.md | 166 -
src/_documents/classic/Site/banner.md | 5 -
src/_documents/classic/Site/navigation.md | 6 -
src/_documents/classic/Site/old-links.md | 183 -
src/_documents/classic/Site/quicklinks.md | 6 -
src/_documents/classic/Site/siteindex.md | 2492 ----------
src/_documents/classic/Site/sitemap.md | 559 ---
.../classic/Tools/Web Console/running-a-broker.md | 164 -
src/_documents/classic/Tools/hermes-jms.md | 37 -
src/_documents/classic/Tools/hermes-screenshot.md | 9 -
.../classic/Tools/java-service-wrapper.md | 52 -
.../classic/Tools/maven2-activemq-broker-plugin.md | 108 -
src/_documents/classic/Tools/web-console.md | 128 -
.../activemq-4-connection-uris.md | 249 -
.../configure-version-5-brokers.md | 125 -
.../configuring-version-5-transports.md | 249 -
.../ldap-broker-discovery-mechanism.md | 291 --
.../classic/Using ActiveMQ 5/version-5-examples.md | 88 -
.../Using ActiveMQ 5/version-5-getting-started.md | 395 --
.../Using ActiveMQ 5/version-5-hello-world.md | 160 -
.../version-5-initial-configuration.md | 93 -
.../Using ActiveMQ 5/version-5-installation.md | 20 -
.../version-5-performance-tuning.md | 61 -
.../Using ActiveMQ 5/version-5-run-broker.md | 79 -
.../Using ActiveMQ 5/version-5-topologies.md | 80 -
.../Using ActiveMQ 5/version-5-web-samples.md | 18 -
.../version-5-xml-configuration.md | 52 -
.../broker-properties-uri.md | 48 -
.../Broker Configuration URI/broker-uri.md | 80 -
.../Broker Configuration URI/broker-xbean-uri.md | 40 -
.../broker-configuration-uri.md | 37 -
.../configuring-wire-formats.md | 90 -
.../connection-configuration-uri.md | 200 -
.../discovery-transport-reference.md | 85 -
.../failover-transport-reference.md | 253 -
.../fanout-transport-reference.md | 91 -
.../http-and-https-transports-reference.md | 33 -
.../multicast-transport-reference.md | 89 -
.../nio-transport-reference.md | 61 -
.../peer-transport-reference.md | 17 -
.../ssl-transport-reference.md | 71 -
.../static-transport-reference.md | 65 -
.../tcp-transport-reference.md | 251 -
.../udp-transport-reference.md | 61 -
.../vm-transport-reference.md | 122 -
.../ZeroConf Transport Reference/zeroconf.md | 20 -
.../activemq-connection-uris.md | 249 -
.../activemq-inactivitymonitor.md | 87 -
.../zeroconf-transport-reference.md | 30 -
.../Getting Started/gettingstarted3x.md | 168 -
.../Getting Started/monitoring-activemq.md | 16 -
...mplex-single-broker-configuration-stomp-only.md | 121 -
.../jms-and-jdbc-operations-in-one-transaction.md | 155 -
.../jms-bridge-with-local-broker.md | 37 -
.../jms-bridge-with-oracle-aq.md | 115 -
.../jms-bridge-with-remote-broker.md | 37 -
.../jms-bridge-with-remote-tibco-broker.md | 41 -
.../sample-camel-routes.md | 144 -
.../Xml Reference/xbean-xml-reference-41.md | 3186 ------------
.../Xml Reference/xbean-xml-reference-50.md | 5234 --------------------
.../classic/Using ActiveMQ/configuring-brokers.md | 41 -
.../Using ActiveMQ/configuring-transports.md | 249 -
src/_documents/classic/Using ActiveMQ/examples.md | 88 -
.../classic/Using ActiveMQ/getting-started.md | 355 --
.../classic/Using ActiveMQ/hello-world.md | 160 -
.../Using ActiveMQ/initial-configuration.md | 89 -
.../classic/Using ActiveMQ/installation.md | 20 -
.../known-bad-os-and-jvm-combinations.md | 17 -
.../classic/Using ActiveMQ/performance-tuning.md | 67 -
.../classic/Using ActiveMQ/run-broker.md | 70 -
.../classic/Using ActiveMQ/topologies.md | 80 -
src/_documents/classic/Using ActiveMQ/use-cases.md | 52 -
.../user-submitted-configurations.md | 15 -
.../classic/Using ActiveMQ/web-samples.md | 20 -
.../classic/Using ActiveMQ/xml-configuration.md | 80 -
.../classic/Using ActiveMQ/xml-reference.md | 511 --
src/_documents/classic/activemq-artemis-roadmap.md | 89 -
src/_documents/classic/activemq6.md | 7 -
src/_documents/classic/amqp-manual.md | 167 -
.../apache-activemq-board-report-april-2008.md | 44 -
src/_documents/classic/architecture.md | 62 -
src/_documents/classic/authentication.md | 50 -
src/_documents/classic/authorization.md | 162 -
src/_documents/classic/chat.md | 37 -
src/_documents/classic/community.md | 34 -
src/_documents/classic/connectivity.md | 45 -
src/_documents/classic/connectors.md | 94 -
src/_documents/classic/destinations.md | 57 -
src/_documents/classic/developers.md | 42 -
src/_documents/classic/docs.md | 34 -
src/_documents/classic/extending-guide.md | 184 -
src/_documents/classic/faq.md | 219 -
src/_documents/classic/features.md | 126 -
src/_documents/classic/images/ActiveMQ-CPP.png | Bin 11290 -> 0 bytes
.../classic/images/ActiveMQConnections.png | Bin 119034 -> 0 bytes
.../classic/images/ActiveMQDestinations.png | Bin 107839 -> 0 bytes
src/_documents/classic/images/Broker Diagram.png | Bin 54184 -> 0 bytes
src/_documents/classic/images/BrokerDiagram-1.png | Bin 79273 -> 0 bytes
src/_documents/classic/images/BrokerDiagram.jpg | Bin 307755 -> 0 bytes
src/_documents/classic/images/BrokerDiagram.png | Bin 108476 -> 0 bytes
src/_documents/classic/images/BrokerDiagram2.png | Bin 64236 -> 0 bytes
src/_documents/classic/images/BrokerTopology-1.png | Bin 77584 -> 0 bytes
src/_documents/classic/images/BrokerTopology.png | Bin 78699 -> 0 bytes
src/_documents/classic/images/BrokerTopology2.png | Bin 99237 -> 0 bytes
src/_documents/classic/images/BrokerTopology3.png | Bin 53821 -> 0 bytes
.../classic/images/DispatchFastConsumers.png | Bin 63183 -> 0 bytes
.../classic/images/DispatchSlowConsumers.png | Bin 72397 -> 0 bytes
.../classic/images/Example1-DirectoryStructure.jpg | Bin 20383 -> 0 bytes
src/_documents/classic/images/Example1-Entry.jpg | Bin 50757 -> 0 bytes
.../classic/images/Example1-Topology.jpg | Bin 14069 -> 0 bytes
src/_documents/classic/images/Example1.jpg | Bin 64717 -> 0 bytes
.../classic/images/Example2-DirectoryStructure.jpg | Bin 33149 -> 0 bytes
.../classic/images/Example2-Topology.jpg | Bin 22705 -> 0 bytes
src/_documents/classic/images/Example2.jpg | Bin 112722 -> 0 bytes
src/_documents/classic/images/FileCursor.png | Bin 92799 -> 0 bytes
src/_documents/classic/images/Fisheye_logo.png | Bin 19153 -> 0 bytes
src/_documents/classic/images/I.png | Bin 206 -> 0 bytes
.../classic/images/JConsole Hierarchy.jpg | Bin 72263 -> 0 bytes
.../classic/images/JConsole-Hierarchy.jpg | Bin 72263 -> 0 bytes
src/_documents/classic/images/JConsoleAMQ.png | Bin 180278 -> 0 bytes
src/_documents/classic/images/L.png | Bin 210 -> 0 bytes
src/_documents/classic/images/LB_logo.jpg | Bin 32067 -> 0 bytes
src/_documents/classic/images/LB_logo_200.jpg | Bin 22240 -> 0 bytes
src/_documents/classic/images/LB_logo_200crop.jpg | Bin 32067 -> 0 bytes
src/_documents/classic/images/Lminus.png | Bin 280 -> 0 bytes
src/_documents/classic/images/Lplus.png | Bin 283 -> 0 bytes
src/_documents/classic/images/MasterFailed.png | Bin 39989 -> 0 bytes
src/_documents/classic/images/MasterRestarted.png | Bin 43045 -> 0 bytes
.../classic/images/NonPersistentMsgs.png | Bin 117640 -> 0 bytes
src/_documents/classic/images/Startup.png | Bin 42706 -> 0 bytes
src/_documents/classic/images/T.png | Bin 211 -> 0 bytes
src/_documents/classic/images/Tminus.png | Bin 269 -> 0 bytes
src/_documents/classic/images/Tplus.png | Bin 279 -> 0 bytes
src/_documents/classic/images/VMCursor.png | Bin 69474 -> 0 bytes
src/_documents/classic/images/about_16.gif | Bin 1128 -> 0 bytes
src/_documents/classic/images/about_16.png | Bin 1451 -> 0 bytes
.../classic/images/activemq-4.1-box-reflection.png | Bin 166392 -> 0 bytes
.../classic/images/activemq-5.x-box-reflection.png | Bin 189159 -> 0 bytes
.../classic/images/activemq-in-weblogic.png | Bin 125283 -> 0 bytes
src/_documents/classic/images/activemq-jmx.png | Bin 171708 -> 0 bytes
src/_documents/classic/images/activemq-logo.png | Bin 18178 -> 0 bytes
src/_documents/classic/images/add_16.gif | Bin 538 -> 0 bytes
src/_documents/classic/images/add_blogentry_16.gif | Bin 644 -> 0 bytes
src/_documents/classic/images/add_blogentry_32.gif | Bin 1435 -> 0 bytes
src/_documents/classic/images/add_comment_16.gif | Bin 445 -> 0 bytes
src/_documents/classic/images/add_page_16.gif | Bin 485 -> 0 bytes
src/_documents/classic/images/add_page_32.gif | Bin 1078 -> 0 bytes
.../classic/images/add_page_child_16.gif | Bin 436 -> 0 bytes
.../classic/images/add_page_faded_16.gif | Bin 319 -> 0 bytes
.../classic/images/add_page_notification_16.gif | Bin 429 -> 0 bytes
src/_documents/classic/images/add_space_16.gif | Bin 1159 -> 0 bytes
src/_documents/classic/images/add_space_32.gif | Bin 2507 -> 0 bytes
.../classic/images/add_space_notification_16.gif | Bin 1295 -> 0 bytes
src/_documents/classic/images/addbk_16.gif | Bin 1166 -> 0 bytes
src/_documents/classic/images/adfav_16.gif | Bin 1113 -> 0 bytes
src/_documents/classic/images/alarm_16.gif | Bin 1119 -> 0 bytes
src/_documents/classic/images/amqdir.png | Bin 57516 -> 0 bytes
src/_documents/classic/images/amqstore.png | Bin 47744 -> 0 bytes
.../classic/images/apache-camel-100h.png | Bin 30811 -> 0 bytes
src/_documents/classic/images/apps_16.gif | Bin 1759 -> 0 bytes
src/_documents/classic/images/arrow_block.png | Bin 48397 -> 0 bytes
src/_documents/classic/images/arrow_block_16.gif | Bin 136 -> 0 bytes
.../classic/images/arrow_closed_active_16.gif | Bin 261 -> 0 bytes
.../classic/images/arrow_closing_active.png | Bin 51163 -> 0 bytes
.../classic/images/arrow_closing_active_16.gif | Bin 506 -> 0 bytes
.../classic/images/arrow_open_active_16.gif | Bin 506 -> 0 bytes
.../classic/images/arrow_opening_active.png | Bin 51178 -> 0 bytes
.../classic/images/arrow_opening_active_16.gif | Bin 506 -> 0 bytes
src/_documents/classic/images/asf-logo.png | Bin 19333 -> 0 bytes
src/_documents/classic/images/atom.gif | Bin 356 -> 0 bytes
src/_documents/classic/images/attach-file.png | Bin 50966 -> 0 bytes
src/_documents/classic/images/attach_file_16.gif | Bin 1070 -> 0 bytes
src/_documents/classic/images/attachment-icons.png | Bin 67143 -> 0 bytes
src/_documents/classic/images/back_16.gif | Bin 553 -> 0 bytes
src/_documents/classic/images/bad.gif | Bin 479 -> 0 bytes
src/_documents/classic/images/big-bullet.png | Bin 486 -> 0 bytes
.../classic/images/black-footer-bottom.png | Bin 376 -> 0 bytes
.../classic/images/black-footer-left.png | Bin 731 -> 0 bytes
.../classic/images/black-footer-right.png | Bin 820 -> 0 bytes
src/_documents/classic/images/blank.png | Bin 197 -> 0 bytes
src/_documents/classic/images/blogentry.png | Bin 53503 -> 0 bytes
src/_documents/classic/images/blogentry_16.gif | Bin 479 -> 0 bytes
src/_documents/classic/images/blogentry_24.png | Bin 53876 -> 0 bytes
src/_documents/classic/images/blogentry_add_32.png | Bin 55727 -> 0 bytes
.../classic/images/blogentry_faded_16.gif | Bin 356 -> 0 bytes
.../classic/images/blogentry_faded_16.png | Bin 53071 -> 0 bytes
src/_documents/classic/images/border_bottom.gif | Bin 181 -> 0 bytes
src/_documents/classic/images/bottom-red-bar.png | Bin 360 -> 0 bytes
src/_documents/classic/images/browse_space.gif | Bin 1915 -> 0 bytes
src/_documents/classic/images/bullet_blue.gif | Bin 86 -> 0 bytes
src/_documents/classic/images/bullet_creme.gif | Bin 86 -> 0 bytes
src/_documents/classic/images/bullet_creme_6.gif | Bin 69 -> 0 bytes
src/_documents/classic/images/bullet_done.gif | Bin 77 -> 0 bytes
src/_documents/classic/images/bullet_done.png | Bin 48874 -> 0 bytes
.../classic/images/bullet_inprogress.gif | Bin 86 -> 0 bytes
.../classic/images/bullet_inprogress.png | Bin 48936 -> 0 bytes
src/_documents/classic/images/bullet_notdone.gif | Bin 88 -> 0 bytes
src/_documents/classic/images/bullet_notdone.png | Bin 48157 -> 0 bytes
src/_documents/classic/images/bullet_red.gif | Bin 88 -> 0 bytes
src/_documents/classic/images/cal_16.gif | Bin 970 -> 0 bytes
src/_documents/classic/images/calc_16.gif | Bin 1036 -> 0 bytes
src/_documents/classic/images/cancl_16.gif | Bin 1122 -> 0 bytes
src/_documents/classic/images/cart_16.gif | Bin 637 -> 0 bytes
src/_documents/classic/images/cd_16.gif | Bin 1796 -> 0 bytes
src/_documents/classic/images/chart_16.gif | Bin 962 -> 0 bytes
src/_documents/classic/images/checker-bg.png | Bin 47732 -> 0 bytes
src/_documents/classic/images/close_16.gif | Bin 998 -> 0 bytes
src/_documents/classic/images/comment-add.png | Bin 52284 -> 0 bytes
src/_documents/classic/images/comment-del.png | Bin 52215 -> 0 bytes
src/_documents/classic/images/comment.png | Bin 51584 -> 0 bytes
src/_documents/classic/images/comment_16.gif | Bin 317 -> 0 bytes
.../classic/images/competing-consumers.png | Bin 24508 -> 0 bytes
src/_documents/classic/images/confg_16.gif | Bin 718 -> 0 bytes
.../classic/images/configure_icon_16.gif | Bin 586 -> 0 bytes
.../classic/images/configure_icon_16.png | Bin 51091 -> 0 bytes
src/_documents/classic/images/confluence_logo.gif | Bin 760 -> 0 bytes
.../classic/images/confluence_logo_darkbg.gif | Bin 549 -> 0 bytes
src/_documents/classic/images/content-left.png | Bin 317 -> 0 bytes
src/_documents/classic/images/content-right.png | Bin 364 -> 0 bytes
src/_documents/classic/images/copy_16.gif | Bin 665 -> 0 bytes
src/_documents/classic/images/cut_16.gif | Bin 984 -> 0 bytes
src/_documents/classic/images/del_16.gif | Bin 889 -> 0 bytes
src/_documents/classic/images/del_blogentry_16.gif | Bin 647 -> 0 bytes
src/_documents/classic/images/del_comment_16.gif | Bin 456 -> 0 bytes
src/_documents/classic/images/del_page_16.gif | Bin 514 -> 0 bytes
.../classic/images/del_page_notification_16.gif | Bin 484 -> 0 bytes
src/_documents/classic/images/del_space_16.gif | Bin 1174 -> 0 bytes
.../classic/images/del_space_notification_16.gif | Bin 1108 -> 0 bytes
src/_documents/classic/images/discussion-large.png | Bin 56874 -> 0 bytes
src/_documents/classic/images/docs_16.gif | Bin 1033 -> 0 bytes
.../classic/images/document_attachment.png | Bin 1170 -> 0 bytes
.../classic/images/document_exchange.gif | Bin 973 -> 0 bytes
.../classic/images/document_exchange.png | Bin 1339 -> 0 bytes
.../classic/images/document_zoom_in_16.gif | Bin 1219 -> 0 bytes
.../classic/images/document_zoom_in_16.png | Bin 1302 -> 0 bytes
src/_documents/classic/images/down_16.gif | Bin 563 -> 0 bytes
src/_documents/classic/images/dummy.gif | Bin 43415 -> 0 bytes
src/_documents/classic/images/edit_16.gif | Bin 350 -> 0 bytes
src/_documents/classic/images/edit_16.png | Bin 49582 -> 0 bytes
.../classic/images/edit_blogentry_16.gif | Bin 669 -> 0 bytes
src/_documents/classic/images/edit_only_16.gif | Bin 350 -> 0 bytes
src/_documents/classic/images/edit_only_16.png | Bin 49941 -> 0 bytes
src/_documents/classic/images/edit_space_16.gif | Bin 1159 -> 0 bytes
src/_documents/classic/images/en_UK.gif | Bin 4196 -> 0 bytes
src/_documents/classic/images/encodingtest.jpg | Bin 7448 -> 0 bytes
src/_documents/classic/images/exp_16.gif | Bin 376 -> 0 bytes
src/_documents/classic/images/exp_32.gif | Bin 1267 -> 0 bytes
src/_documents/classic/images/failoverclient.png | Bin 85613 -> 0 bytes
src/_documents/classic/images/fastf_16.gif | Bin 654 -> 0 bytes
src/_documents/classic/images/favicon.png | Bin 613 -> 0 bytes
src/_documents/classic/images/favs_16.gif | Bin 975 -> 0 bytes
src/_documents/classic/images/fax_16.gif | Bin 1086 -> 0 bytes
src/_documents/classic/images/feed-icon-10x10.png | Bin 818 -> 0 bytes
src/_documents/classic/images/feed-icon-12x12.png | Bin 936 -> 0 bytes
src/_documents/classic/images/feed-icon-16x16.png | Bin 1319 -> 0 bytes
src/_documents/classic/images/feed-icon-24x24.png | Bin 1937 -> 0 bytes
src/_documents/classic/images/feed-icon-32x32.png | Bin 2541 -> 0 bytes
src/_documents/classic/images/feed_wizard.gif | Bin 1412 -> 0 bytes
src/_documents/classic/images/file.png | Bin 359 -> 0 bytes
src/_documents/classic/images/flag_16.gif | Bin 1775 -> 0 bytes
src/_documents/classic/images/foldericon.png | Bin 359 -> 0 bytes
src/_documents/classic/images/foldr_16.gif | Bin 1071 -> 0 bytes
src/_documents/classic/images/forwd_16.gif | Bin 543 -> 0 bytes
src/_documents/classic/images/forwd_24.png | Bin 1250 -> 0 bytes
src/_documents/classic/images/games_16.gif | Bin 715 -> 0 bytes
src/_documents/classic/images/go_16.gif | Bin 1023 -> 0 bytes
src/_documents/classic/images/good.gif | Bin 485 -> 0 bytes
src/_documents/classic/images/group-anyone.png | Bin 50498 -> 0 bytes
src/_documents/classic/images/group_16.gif | Bin 1533 -> 0 bytes
src/_documents/classic/images/group_anyone_16.gif | Bin 409 -> 0 bytes
src/_documents/classic/images/hd_16.gif | Bin 971 -> 0 bytes
src/_documents/classic/images/help.png | Bin 123381 -> 0 bytes
src/_documents/classic/images/help_16.gif | Bin 1095 -> 0 bytes
src/_documents/classic/images/help_24.gif | Bin 1528 -> 0 bytes
src/_documents/classic/images/help_24.png | Bin 2752 -> 0 bytes
src/_documents/classic/images/hermes.png | Bin 1214900 -> 0 bytes
src/_documents/classic/images/hist_16.gif | Bin 916 -> 0 bytes
src/_documents/classic/images/history_16.gif | Bin 477 -> 0 bytes
src/_documents/classic/images/history_arrow.png | Bin 48571 -> 0 bytes
src/_documents/classic/images/home_16.gif | Bin 914 -> 0 bytes
src/_documents/classic/images/home_16_faded.png | Bin 49788 -> 0 bytes
src/_documents/classic/images/home_faded_16.gif | Bin 289 -> 0 bytes
src/_documents/classic/images/image_16.gif | Bin 1694 -> 0 bytes
src/_documents/classic/images/import_mbox_16.gif | Bin 617 -> 0 bytes
src/_documents/classic/images/import_mbox_16.png | Bin 53802 -> 0 bytes
src/_documents/classic/images/impt_16.gif | Bin 409 -> 0 bytes
src/_documents/classic/images/label_16.gif | Bin 385 -> 0 bytes
src/_documents/classic/images/layout_northwest.gif | Bin 321 -> 0 bytes
src/_documents/classic/images/layout_northwest.png | Bin 535 -> 0 bytes
src/_documents/classic/images/left-box-bottom.png | Bin 690 -> 0 bytes
src/_documents/classic/images/left-box-right.png | Bin 360 -> 0 bytes
src/_documents/classic/images/left-box-top.png | Bin 620 -> 0 bytes
src/_documents/classic/images/left-nav-theme.gif | Bin 1769 -> 0 bytes
src/_documents/classic/images/left-nav-theme.png | Bin 61855 -> 0 bytes
src/_documents/classic/images/lgicn_16.gif | Bin 1022 -> 0 bytes
src/_documents/classic/images/link-attachment.png | Bin 48778 -> 0 bytes
src/_documents/classic/images/link-external.png | Bin 48181 -> 0 bytes
src/_documents/classic/images/link_16.gif | Bin 536 -> 0 bytes
.../classic/images/link_attachment_7.gif | Bin 220 -> 0 bytes
src/_documents/classic/images/link_in_bot.gif | Bin 96 -> 0 bytes
src/_documents/classic/images/link_in_mid.gif | Bin 98 -> 0 bytes
src/_documents/classic/images/link_in_only.gif | Bin 91 -> 0 bytes
src/_documents/classic/images/link_in_top.gif | Bin 97 -> 0 bytes
src/_documents/classic/images/link_out_bot.gif | Bin 98 -> 0 bytes
src/_documents/classic/images/link_out_mid.gif | Bin 103 -> 0 bytes
src/_documents/classic/images/link_out_top.gif | Bin 103 -> 0 bytes
src/_documents/classic/images/linkext7.gif | Bin 220 -> 0 bytes
src/_documents/classic/images/list-pages-large.png | Bin 51458 -> 0 bytes
src/_documents/classic/images/list-pages.png | Bin 49252 -> 0 bytes
.../classic/images/list-pages_faded_16.png | Bin 49582 -> 0 bytes
.../classic/images/list_blogentries_32.gif | Bin 1063 -> 0 bytes
.../classic/images/list_blogentries_32.png | Bin 55670 -> 0 bytes
.../classic/images/list_blogposts_32.gif | Bin 1063 -> 0 bytes
.../classic/images/list_less_pages_16.gif | Bin 408 -> 0 bytes
.../classic/images/list_less_pages_16.png | Bin 49388 -> 0 bytes
src/_documents/classic/images/list_mail_16.png | Bin 50720 -> 0 bytes
src/_documents/classic/images/list_mail_32.gif | Bin 692 -> 0 bytes
src/_documents/classic/images/list_mail_32.png | Bin 55482 -> 0 bytes
.../classic/images/list_mail_content_16.gif | Bin 323 -> 0 bytes
.../classic/images/list_mail_faded_16.gif | Bin 281 -> 0 bytes
.../classic/images/list_mail_faded_16.png | Bin 50962 -> 0 bytes
src/_documents/classic/images/list_pages_16.gif | Bin 441 -> 0 bytes
src/_documents/classic/images/list_pages_32.gif | Bin 858 -> 0 bytes
.../classic/images/list_pages_faded_16.gif | Bin 480 -> 0 bytes
src/_documents/classic/images/lock_16.gif | Bin 945 -> 0 bytes
src/_documents/classic/images/locked-pages_16.png | Bin 51829 -> 0 bytes
src/_documents/classic/images/locked_pages_16.gif | Bin 1090 -> 0 bytes
src/_documents/classic/images/logo.gif | Bin 2321 -> 0 bytes
src/_documents/classic/images/logo.jpg | Bin 22168 -> 0 bytes
src/_documents/classic/images/logo2.gif | Bin 2086 -> 0 bytes
src/_documents/classic/images/logo_add_16.gif | Bin 1611 -> 0 bytes
src/_documents/classic/images/logo_jprofiler01.gif | Bin 4521 -> 0 bytes
src/_documents/classic/images/mail.png | Bin 3326 -> 0 bytes
src/_documents/classic/images/mail_16.gif | Bin 712 -> 0 bytes
src/_documents/classic/images/mail_16.png | Bin 52722 -> 0 bytes
src/_documents/classic/images/mail_content_16.gif | Bin 439 -> 0 bytes
src/_documents/classic/images/mail_delete.png | Bin 3829 -> 0 bytes
src/_documents/classic/images/mail_small.gif | Bin 338 -> 0 bytes
src/_documents/classic/images/mail_small.png | Bin 48753 -> 0 bytes
src/_documents/classic/images/mail_thread_16.gif | Bin 401 -> 0 bytes
src/_documents/classic/images/mail_thread_16.png | Bin 51229 -> 0 bytes
src/_documents/classic/images/main-theme.gif | Bin 1576 -> 0 bytes
src/_documents/classic/images/main-theme.png | Bin 57491 -> 0 bytes
src/_documents/classic/images/message-flow.png | Bin 54873 -> 0 bytes
.../classic/images/module-deps-graph.png | Bin 14559 -> 0 bytes
src/_documents/classic/images/move_16.gif | Bin 565 -> 0 bytes
src/_documents/classic/images/music_16.gif | Bin 986 -> 0 bytes
src/_documents/classic/images/nav_down.gif | Bin 1030 -> 0 bytes
src/_documents/classic/images/nav_up.gif | Bin 906 -> 0 bytes
src/_documents/classic/images/new.png | Bin 359 -> 0 bytes
src/_documents/classic/images/new_16.gif | Bin 1005 -> 0 bytes
src/_documents/classic/images/news.gif | Bin 752 -> 0 bytes
src/_documents/classic/images/no-icon.gif | Bin 2442 -> 0 bytes
src/_documents/classic/images/notep_16.gif | Bin 606 -> 0 bytes
src/_documents/classic/images/ntwrk_16.gif | Bin 762 -> 0 bytes
src/_documents/classic/images/open-active.png | Bin 49225 -> 0 bytes
src/_documents/classic/images/open_16.gif | Bin 1044 -> 0 bytes
src/_documents/classic/images/openfoldericon.png | Bin 366 -> 0 bytes
src/_documents/classic/images/opnbr_16.gif | Bin 1149 -> 0 bytes
src/_documents/classic/images/opts_16.gif | Bin 1030 -> 0 bytes
src/_documents/classic/images/oval-arrow.png | Bin 7007 -> 0 bytes
src/_documents/classic/images/page-add-child.png | Bin 50344 -> 0 bytes
src/_documents/classic/images/page-add-large.png | Bin 53341 -> 0 bytes
src/_documents/classic/images/page-add.png | Bin 50228 -> 0 bytes
.../classic/images/page-add_faded_16.png | Bin 50163 -> 0 bytes
src/_documents/classic/images/page-del.png | Bin 50515 -> 0 bytes
.../classic/images/page-hierarchy-large.png | Bin 52091 -> 0 bytes
src/_documents/classic/images/page-hierarchy.png | Bin 49817 -> 0 bytes
src/_documents/classic/images/page-history.png | Bin 50499 -> 0 bytes
.../classic/images/page-notification.png | Bin 50450 -> 0 bytes
.../classic/images/page_hierarchy_16.gif | Bin 412 -> 0 bytes
src/_documents/classic/images/paint_16.gif | Bin 944 -> 0 bytes
src/_documents/classic/images/paste_16.gif | Bin 952 -> 0 bytes
src/_documents/classic/images/pause_16.gif | Bin 414 -> 0 bytes
src/_documents/classic/images/phone_16.gif | Bin 1157 -> 0 bytes
src/_documents/classic/images/photo_scenery.gif | Bin 1077 -> 0 bytes
src/_documents/classic/images/picts_16.gif | Bin 845 -> 0 bytes
src/_documents/classic/images/play_16.gif | Bin 572 -> 0 bytes
src/_documents/classic/images/plus.gif | Bin 155 -> 0 bytes
src/_documents/classic/images/plus_sign.png | Bin 48034 -> 0 bytes
src/_documents/classic/images/prefs_16.gif | Bin 913 -> 0 bytes
src/_documents/classic/images/print_16.gif | Bin 682 -> 0 bytes
.../classic/images/project-logo-vector.png | Bin 97156 -> 0 bytes
src/_documents/classic/images/project-logo.png | Bin 3069 -> 0 bytes
src/_documents/classic/images/prtpv_16.gif | Bin 580 -> 0 bytes
src/_documents/classic/images/redo_116.gif | Bin 802 -> 0 bytes
src/_documents/classic/images/ref_16.gif | Bin 1005 -> 0 bytes
src/_documents/classic/images/refresh_16.png | Bin 1603 -> 0 bytes
src/_documents/classic/images/refresh_24.png | Bin 2797 -> 0 bytes
.../classic/images/reloadLog4jProperties1.png | Bin 180881 -> 0 bytes
.../classic/images/reloadLog4jProperties2.png | Bin 211703 -> 0 bytes
src/_documents/classic/images/remov_16.gif | Bin 1099 -> 0 bytes
.../classic/images/replicated-leveldb-store.png | Bin 45666 -> 0 bytes
src/_documents/classic/images/rewnd_16.gif | Bin 647 -> 0 bytes
src/_documents/classic/images/right-box-bottom.png | Bin 647 -> 0 bytes
src/_documents/classic/images/right-box-left.png | Bin 364 -> 0 bytes
src/_documents/classic/images/right-box-top.png | Bin 674 -> 0 bytes
src/_documents/classic/images/rss.gif | Bin 1846 -> 0 bytes
src/_documents/classic/images/rss.png | Bin 48677 -> 0 bytes
src/_documents/classic/images/rss10.gif | Bin 317 -> 0 bytes
src/_documents/classic/images/rss20.gif | Bin 346 -> 0 bytes
src/_documents/classic/images/rss_32.gif | Bin 275 -> 0 bytes
src/_documents/classic/images/rss_32.png | Bin 50123 -> 0 bytes
src/_documents/classic/images/run_test_fail_16.gif | Bin 485 -> 0 bytes
src/_documents/classic/images/run_test_pass_16.gif | Bin 488 -> 0 bytes
src/_documents/classic/images/savas_16.gif | Bin 1201 -> 0 bytes
src/_documents/classic/images/save_16.gif | Bin 1115 -> 0 bytes
src/_documents/classic/images/sinfo_16.gif | Bin 946 -> 0 bytes
src/_documents/classic/images/skipb_16.gif | Bin 934 -> 0 bytes
src/_documents/classic/images/skipf_16.gif | Bin 941 -> 0 bytes
.../classic/images/small-bullet-gray.png | Bin 275 -> 0 bytes
src/_documents/classic/images/small-bullet-red.png | Bin 271 -> 0 bytes
src/_documents/classic/images/smicn_16.gif | Bin 1004 -> 0 bytes
src/_documents/classic/images/space-add-large.png | Bin 59507 -> 0 bytes
src/_documents/classic/images/space-add.png | Bin 51735 -> 0 bytes
src/_documents/classic/images/space-del.png | Bin 51691 -> 0 bytes
src/_documents/classic/images/space-edit.png | Bin 51832 -> 0 bytes
.../classic/images/space-notification.png | Bin 53311 -> 0 bytes
src/_documents/classic/images/spacer.gif | Bin 53 -> 0 bytes
src/_documents/classic/images/splay_16.gif | Bin 392 -> 0 bytes
src/_documents/classic/images/srch_16.gif | Bin 655 -> 0 bytes
src/_documents/classic/images/star_grey.gif | Bin 1328 -> 0 bytes
src/_documents/classic/images/star_yellow.gif | Bin 980 -> 0 bytes
src/_documents/classic/images/step1.png | Bin 46125 -> 0 bytes
src/_documents/classic/images/step2.png | Bin 45285 -> 0 bytes
src/_documents/classic/images/step3.png | Bin 40581 -> 0 bytes
src/_documents/classic/images/step4.png | Bin 41541 -> 0 bytes
src/_documents/classic/images/step5.png | Bin 32677 -> 0 bytes
src/_documents/classic/images/step6-new.png | Bin 223279 -> 0 bytes
src/_documents/classic/images/step6.png | Bin 202115 -> 0 bytes
src/_documents/classic/images/step7-new.png | Bin 184834 -> 0 bytes
src/_documents/classic/images/step7.png | Bin 168194 -> 0 bytes
src/_documents/classic/images/step8.png | Bin 38267 -> 0 bytes
src/_documents/classic/images/stop_16.gif | Bin 956 -> 0 bytes
src/_documents/classic/images/subtract_16.gif | Bin 576 -> 0 bytes
src/_documents/classic/images/test-ran-green.png | Bin 49440 -> 0 bytes
src/_documents/classic/images/test-ran-red.png | Bin 49346 -> 0 bytes
src/_documents/classic/images/test.png | Bin 11305 -> 0 bytes
src/_documents/classic/images/text_abc.gif | Bin 3885 -> 0 bytes
src/_documents/classic/images/text_abc_16.gif | Bin 2500 -> 0 bytes
src/_documents/classic/images/text_bold.gif | Bin 741 -> 0 bytes
src/_documents/classic/images/text_bold_16.png | Bin 945 -> 0 bytes
src/_documents/classic/images/text_italics.gif | Bin 711 -> 0 bytes
src/_documents/classic/images/text_tree.png | Bin 2492 -> 0 bytes
src/_documents/classic/images/text_tree_16.png | Bin 913 -> 0 bytes
src/_documents/classic/images/text_underlined.gif | Bin 720 -> 0 bytes
src/_documents/classic/images/text_view.png | Bin 5062 -> 0 bytes
src/_documents/classic/images/text_view_16.png | Bin 1267 -> 0 bytes
src/_documents/classic/images/thread.png | Bin 1291 -> 0 bytes
src/_documents/classic/images/tools_16.gif | Bin 638 -> 0 bytes
src/_documents/classic/images/top-red-bar.png | Bin 317 -> 0 bytes
.../classic/images/trafficlight_green_16.png | Bin 1094 -> 0 bytes
.../classic/images/trafficlight_green_24.png | Bin 1724 -> 0 bytes
.../classic/images/trafficlight_red_16.png | Bin 1021 -> 0 bytes
.../classic/images/trafficlight_red_24.png | Bin 1686 -> 0 bytes
src/_documents/classic/images/trash_16.gif | Bin 667 -> 0 bytes
src/_documents/classic/images/tree_minus.gif | Bin 481 -> 0 bytes
src/_documents/classic/images/tree_plus.gif | Bin 484 -> 0 bytes
src/_documents/classic/images/tree_square.gif | Bin 388 -> 0 bytes
src/_documents/classic/images/tree_square.png | Bin 48892 -> 0 bytes
src/_documents/classic/images/uat-test-theme.png | Bin 57990 -> 0 bytes
src/_documents/classic/images/ulock_16.gif | Bin 943 -> 0 bytes
src/_documents/classic/images/undo_16.gif | Bin 916 -> 0 bytes
src/_documents/classic/images/up_16.gif | Bin 510 -> 0 bytes
src/_documents/classic/images/user_12.gif | Bin 778 -> 0 bytes
src/_documents/classic/images/user_16.gif | Bin 1507 -> 0 bytes
src/_documents/classic/images/user_bw_16.gif | Bin 1930 -> 0 bytes
src/_documents/classic/images/user_small.png | Bin 50647 -> 0 bytes
src/_documents/classic/images/wait.gif | Bin 2399 -> 0 bytes
src/_documents/classic/images/watch-large.png | Bin 58495 -> 0 bytes
src/_documents/classic/images/watch_16.gif | Bin 1194 -> 0 bytes
src/_documents/classic/images/watch_16.png | Bin 51311 -> 0 bytes
src/_documents/classic/images/watch_32.gif | Bin 617 -> 0 bytes
src/_documents/classic/images/watch_cancel_16.gif | Bin 1306 -> 0 bytes
src/_documents/classic/images/watch_cancel_32.gif | Bin 1484 -> 0 bytes
src/_documents/classic/images/web-console.png | Bin 857109 -> 0 bytes
src/_documents/classic/images/web_16.gif | Bin 2017 -> 0 bytes
src/_documents/classic/images/web_console.png | Bin 857109 -> 0 bytes
src/_documents/classic/images/web_faded_16.gif | Bin 810 -> 0 bytes
src/_documents/classic/images/web_faded_16.png | Bin 51494 -> 0 bytes
.../classic/images/white-header-left.png | Bin 473 -> 0 bytes
.../classic/images/white-header-right.png | Bin 582 -> 0 bytes
src/_documents/classic/images/white-header-top.png | Bin 352 -> 0 bytes
src/_documents/classic/images/wiz_16.gif | Bin 964 -> 0 bytes
src/_documents/classic/images/yklogo.png | Bin 10037 -> 0 bytes
src/_documents/classic/images/yourkit.jpg | Bin 4867 -> 0 bytes
src/_documents/classic/images/zoomi_16.gif | Bin 736 -> 0 bytes
src/_documents/classic/images/zoomo_16.gif | Bin 712 -> 0 bytes
src/_documents/classic/management-api.md | 900 ----
src/_documents/classic/migration-guide.md | 45 -
src/_documents/classic/migration.md | 22 -
src/_documents/classic/module-organization.md | 28 -
src/_documents/classic/mqtt-manual.md | 168 -
src/_documents/classic/notice.md | 34 -
src/_documents/classic/openwire-manual.md | 236 -
.../classic/osgi-support-in-development.md | 114 -
src/_documents/classic/overview.md | 74 -
src/_documents/classic/past-releases.md | 492 --
src/_documents/classic/performance-scaling.md | 34 -
src/_documents/classic/previous-docs.md | 147 -
src/_documents/classic/site.md | 11 -
src/_documents/classic/ssl.md | 79 -
src/_documents/classic/stomp-manual.md | 496 --
src/_documents/classic/the-jms-connector.md | 7 -
src/_documents/classic/tools.md | 11 -
src/_documents/classic/user-manual.md | 863 ----
src/_documents/classic/using-activemq-4.md | 59 -
src/_documents/classic/using-activemq-5.md | 28 -
src/_documents/classic/using-activemq.md | 59 -
src/_documents/classic/verification.md | 57 -
.../NMS API Downloads/apachenms-api-v110.md | 55 -
.../NMS API Downloads/apachenms-api-v120.md | 61 -
.../NMS API Downloads/apachenms-api-v130.md | 56 -
.../NMS API Downloads/apachenms-api-v140.md | 58 -
.../NMS API Downloads/apachenms-api-v150.md | 56 -
.../NMS API Downloads/apachenms-api-v151.md | 56 -
.../NMS API Downloads/apachenms-api-v160.md | 56 -
.../NMS API Downloads/apachenms-api-v170.md | 56 -
.../NMS API Downloads/apachenms-api-v171.md | 52 -
.../nms-simple-asynchronous-consumer-example.md | 125 -
.../nms-simple-synchornous-consumer-example.md | 110 -
.../Apache.NMS.AMQP/amqp-build-notes.md | 37 -
.../Apache.NMS.AMQP/amqp-downloads.md | 5 -
.../NMS Providers/Apache.NMS.AMQP/amqp-examples.md | 17 -
.../NMS Providers/Apache.NMS.AMQP/amqp-faq.md | 5 -
.../activemq-consumer-dispatch-async.md | 31 -
.../activemq-consumer-priority.md | 22 -
.../activemq-exclusive-consumers.md | 20 -
.../activemq-retroactive-consumers.md | 28 -
.../activemq-destination-management.md | 28 -
.../activemq-destination-options.md | 70 -
.../activemq-mirrored-queues.md | 42 -
.../activemq-virtual-destinations.md | 149 -
.../activemq-wildcards.md | 67 -
.../activemq-async-sends.md | 42 -
.../activemq-delay-and-schedule-message-feature.md | 75 -
.../activemq-consumer-features.md | 5 -
.../activemq-destination-features.md | 11 -
.../activemq-message-dispatching-features.md | 7 -
.../activemq-message-features.md | 7 -
.../ActiveMQ Downloads/apachenms-activemq-v110.md | 61 -
.../ActiveMQ Downloads/apachenmsactivemq-v120.md | 62 -
.../ActiveMQ Downloads/apachenmsactivemq-v130.md | 58 -
.../ActiveMQ Downloads/apachenmsactivemq-v140.md | 63 -
.../ActiveMQ Downloads/apachenmsactivemq-v141.md | 59 -
.../ActiveMQ Downloads/apachenmsactivemq-v150.md | 67 -
.../ActiveMQ Downloads/apachenmsactivemq-v151.md | 56 -
.../ActiveMQ Downloads/apachenmsactivemq-v152.md | 56 -
.../ActiveMQ Downloads/apachenmsactivemq-v153.md | 56 -
.../ActiveMQ Downloads/apachenmsactivemq-v154.md | 56 -
.../ActiveMQ Downloads/apachenmsactivemq-v155.md | 62 -
.../ActiveMQ Downloads/apachenmsactivemq-v156.md | 59 -
.../ActiveMQ Downloads/apachenmsactivemq-v160.md | 65 -
.../ActiveMQ Downloads/apachenmsactivemq-v161.md | 63 -
.../ActiveMQ Downloads/apachenmsactivemq-v162.md | 56 -
.../ActiveMQ Downloads/apachenmsactivemq-v163.md | 52 -
.../ActiveMQ Downloads/apachenmsactivemq-v164.md | 52 -
.../ActiveMQ Downloads/apachenmsactivemq-v165.md | 52 -
.../ActiveMQ Downloads/apachenmsactivemq-v170.md | 52 -
.../ActiveMQ Downloads/apachenmsactivemq-v171.md | 52 -
.../ActiveMQ Downloads/apachenmsactivemq-v172.md | 52 -
...numerate-destination-using-advisory-messages.md | 159 -
.../activemq-advisory-message-examples.md | 7 -
.../activemq-advanced-features.md | 23 -
.../Apache.NMS.ActiveMQ/activemq-build-notes.md | 5 -
.../Apache.NMS.ActiveMQ/activemq-downloads.md | 137 -
.../Apache.NMS.ActiveMQ/activemq-examples.md | 8 -
.../Apache.NMS.ActiveMQ/activemq-faq.md | 5 -
.../activemq-uri-configuration.md | 402 --
.../EMS Downloads/apachenms-ems-v110.md | 51 -
.../Apache.NMS.EMS/ems-build-notes.md | 5 -
.../NMS Providers/Apache.NMS.EMS/ems-downloads.md | 17 -
.../NMS Providers/Apache.NMS.EMS/ems-examples.md | 5 -
.../NMS Providers/Apache.NMS.EMS/ems-faq.md | 5 -
.../MSMQ Downloads/apachenms-msmq-v110.md | 47 -
.../Apache.NMS.MSMQ/msmq-build-notes.md | 5 -
.../Apache.NMS.MSMQ/msmq-downloads.md | 17 -
.../NMS Providers/Apache.NMS.MSMQ/msmq-examples.md | 5 -
.../NMS Providers/Apache.NMS.MSMQ/msmq-faq.md | 5 -
.../stomp-delayed-and-scheduled-message-feature.md | 77 -
.../stomp-message-features.md | 7 -
.../Stomp Downloads/apachenmsstomp-v120.md | 56 -
.../Stomp Downloads/apachenmsstomp-v130.md | 62 -
.../Stomp Downloads/apachenmsstomp-v140.md | 62 -
.../Stomp Downloads/apachenmsstomp-v150.md | 61 -
.../Stomp Downloads/apachenmsstomp-v151.md | 64 -
.../Stomp Downloads/apachenmsstomp-v152.md | 56 -
.../Stomp Downloads/apachenmsstomp-v153.md | 56 -
.../Stomp Downloads/apachenmsstomp-v154.md | 56 -
.../Apache.NMS.Stomp/stomp-advanced-features.md | 8 -
.../Apache.NMS.Stomp/stomp-build-notes.md | 5 -
.../Apache.NMS.Stomp/stomp-downloads.md | 59 -
.../NMS Providers/Apache.NMS.Stomp/stomp-faq.md | 5 -
.../Apache.NMS.Stomp/stomp-uri-configuration.md | 292 --
.../WCF Downloads/apachenmswcf-v110.md | 52 -
.../NMS Providers/Apache.NMS.WCF/wcf-downloads.md | 17 -
.../NMS Providers/Apache.NMS.WCF/wcf-examples.md | 5 -
.../Apache.NMS/NMS Providers/apachenmsactivemq.md | 14 -
.../nms/Apache.NMS/NMS Providers/apachenmsamqp.md | 12 -
.../nms/Apache.NMS/NMS Providers/apachenmsems.md | 12 -
.../nms/Apache.NMS/NMS Providers/apachenmsmqtt.md | 7 -
.../nms/Apache.NMS/NMS Providers/apachenmsmsmq.md | 12 -
.../nms/Apache.NMS/NMS Providers/apachenmsstomp.md | 13 -
.../nms/Apache.NMS/NMS Providers/apachenmswcf.md | 10 -
.../nms/Apache.NMS/NMS Providers/apachenmsxms.md | 7 -
src/_documents/nms/Apache.NMS/nms-api-downloads.md | 45 -
src/_documents/nms/Apache.NMS/nms-api.md | 16 -
src/_documents/nms/Apache.NMS/nms-examples.md | 10 -
src/_documents/nms/Apache.NMS/nms-faq.md | 5 -
src/_documents/nms/Apache.NMS/nms-providers.md | 18 -
.../nms/Apache.NMS/nms-uri-configuration.md | 48 -
src/_documents/nms/README.md | 2 -
src/_documents/nms/apachenms.md | 34 -
src/_documents/nms/nms.md | 42 -
src/_documents/nms/using-nms.md | 12 -
src/_documents/nms/what-is-nms.md | 12 -
.../how-can-i-enable-detailed-logging.md | 28 -
...e-10s-of-1000s-of-queues-in-a-single-broker-.md | 43 -
...re-10s-of-1000s-of-queues-in-a-single-broker.md | 43 -
...-to-hold-100s-of-millions-of-queue-messages-.md | 13 -
...q-to-hold-100s-of-millions-of-queue-messages.md | 13 -
...nfigure-activemq-to-use-aio-server-transport.md | 50 -
.../how-do-i-configure-automatic-reconnection.md | 15 -
...-do-i-configure-distributed-queues-or-topics.md | 22 -
.../how-do-i-configure-the-queues-i-want.md | 13 -
...-local-address-and-local-port-for-tcp-or-ssl.md | 14 -
.../Configuration/how-do-i-disable-persistence.md | 15 -
.../how-do-i-run-activemq-under-the-kaffe-jvm.md | 40 -
.../how-does-xbean-compare-to-spring-2.md | 27 -
.../how-to-configure-a-new-database.md | 43 -
...to-deploy-activemq-ra-versionrar-to-weblogic.md | 37 -
.../how-to-disable-multicast-discovery.md | 26 -
.../how-can-i-add-a-new-type-of-transport.md | 15 -
.../Developing ActiveMQ/how-can-i-contribute.md | 96 -
.../how-do-i-add-my-own-plugins.md | 7 -
.../how-do-i-debug-activemq-from-my-ide.md | 11 -
.../FAQ/Errors/Exceptions/certificateunknown.md | 29 -
...oexception-could-not-find-class-for-resource.md | 27 -
.../Exceptions/javaiointerruptedioexception.md | 13 -
...e-derbydb-see-the-next-exception-for-details.md | 83 -
.../Errors/Exceptions/javalangnosuchmethoderror.md | 27 -
...aactivemqresourceadaptersetuseembeddedbroker.md | 39 -
.../FAQ/Errors/Exceptions/javalangoutofmemory.md | 66 -
...on-timeout-peer-did-not-send-his-wire-format.md | 34 -
...otstrap-classloader-but-this-ri-needs-21-api.md | 10 -
...rap-classloader-but-this-ri-xxx-needs-21-api.md | 10 -
...ournal-is-already-opened-by-this-application.md | 37 -
.../FAQ/Errors/Exceptions/no-suitable-driver.md | 19 -
...ffounderror-orgspringframeworkcoreioresource.md | 17 -
...etreader-for-packet-type-unknown-packet-type.md | 15 -
.../original/Community/FAQ/Errors/exceptions.md | 21 -
...-having-problems-with-the-spring-jmstemplate.md | 10 -
...-am-not-receiving-any-messages-what-is-wrong.md | 19 -
.../i-cannot-connect-to-activemq-from-jconsole.md | 17 -
...o-not-receive-messages-in-my-second-consumer.md | 36 -
.../i-get-errors-building-the-code-whats-wrong.md | 13 -
...-warn-no-appenders-could-be-found-for-logger.md | 17 -
...-operating-system-or-distribution-or-network.md | 25 -
.../Community/FAQ/Errors/my-producer-blocks.md | 29 -
...ge-method-of-messagelistener-is-never-called.md | 7 -
...ce-adapter-does-not-seem-to-pool-connections.md | 14 -
.../Errors/slow-networks-drop-large-messages.md | 46 -
.../FAQ/Errors/the-broker-will-not-start.md | 11 -
...-a-broker-before-my-configured-broker-starts.md | 21 -
.../why-do-i-not-get-all-of-the-messages-i-sent.md | 11 -
...ve-messages-on-my-durable-topic-subscription.md | 18 -
...why-do-kahadb-log-files-remain-after-cleanup.md | 70 -
.../FAQ/General/can-i-get-commercial-support.md | 10 -
.../Community/FAQ/General/how-can-i-get-help.md | 49 -
...ow-can-i-get-the-source-code-from-subversion.md | 56 -
...how-do-i-avoid-maven-downloading-latest-jars.md | 13 -
.../how-do-i-build-but-disable-the-unit-tests.md | 14 -
.../General/how-do-i-compile-from-the-source.md | 10 -
.../FAQ/General/how-do-i-edit-the-website.md | 31 -
.../General/how-does-activemq-compare-to-amqp.md | 17 -
.../how-does-activemq-compare-to-artemis.md | 9 -
...does-activemq-compare-to-fuse-message-broker.md | 7 -
.../how-does-activemq-compare-to-jbossmq.md | 30 -
.../how-does-activemq-compare-to-mantaray.md | 13 -
.../General/how-does-activemq-compare-to-mule.md | 29 -
.../how-does-activemq-compare-to-spread-toolkit.md | 16 -
.../General/how-does-openwire-compare-to-stomp.md | 10 -
.../FAQ/General/how-does-the-website-work.md | 18 -
.../Community/FAQ/General/how-fast-is-activemq.md | 17 -
...tivemq-on-windows-in-a-directory-with-spaces.md | 12 -
.../Community/FAQ/General/what-is-activemq.md | 7 -
.../Community/FAQ/General/what-is-the-license.md | 10 -
.../Community/FAQ/General/what-jars-do-i-need.md | 10 -
...tegration-solution-works-best-with-activemq-.md | 11 -
...ntegration-solution-works-best-with-activemq.md | 11 -
.../what-platforms-does-activemq-support.md | 19 -
.../FAQ/General/what-version-should-i-use.md | 11 -
.../FAQ/JMS/can-i-modify-messages-on-a-queue.md | 10 -
...-messages-concurrently-on-one-jms-connection.md | 13 -
.../Community/FAQ/JMS/can-you-browse-a-topic.md | 13 -
.../JMS/how-do-durable-queues-and-topics-work.md | 19 -
.../FAQ/JMS/how-do-i-consume-a-specific-message.md | 18 -
.../FAQ/JMS/how-do-i-get-started-with-jms.md | 12 -
.../FAQ/JMS/how-do-i-make-messages-durable.md | 12 -
...t-destinations-from-a-single-messageproducer.md | 16 -
.../FAQ/JMS/how-do-i-use-jms-efficiently.md | 42 -
.../FAQ/JMS/how-does-a-queue-compare-to-a-topic.md | 15 -
...-does-connectionfactory-relate-to-the-broker.md | 16 -
.../FAQ/JMS/how-does-jms-compare-with-email.md | 11 -
...should-i-implement-request-response-with-jms.md | 249 -
.../Community/FAQ/JMS/how-to-unit-test-jms-code.md | 112 -
.../FAQ/JMS/multiple-consumers-on-a-queue.md | 13 -
.../Community/FAQ/JMS/should-i-use-transactions.md | 26 -
.../original/Community/FAQ/JMS/should-i-use-xa.md | 50 -
.../FAQ/JMS/what-are-administered-objects.md | 22 -
.../are-messages-read-directly-from-the-journal.md | 9 -
.../does-activemq-support-my-sql-database.md | 7 -
.../how-do-i-back-up-kahadb.md | 12 -
...ssage-store-directory-for-an-embedded-broker.md | 11 -
...w-does-journaling-work-with-multiple-brokers.md | 7 -
.../how-does-the-journal-work.md | 7 -
.../is-there-a-specified-size-of-the-journal.md | 7 -
...at-happens-when-the-journal-size-is-exceeded.md | 7 -
...tween-persistent-and-non-persistent-delivery.md | 19 -
.../original/Community/FAQ/Terminology/dr.md | 9 -
.../original/Community/FAQ/Terminology/ha.md | 9 -
.../original/Community/FAQ/Terminology/latency.md | 9 -
.../original/Community/FAQ/Terminology/mom.md | 9 -
.../original/Community/FAQ/Terminology/qos.md | 13 -
.../original/Community/FAQ/Terminology/seda.md | 7 -
.../Community/FAQ/Terminology/throughput.md | 9 -
.../activemq-command-line-tools-reference.md | 788 ---
.../are-destinations-case-sensitive.md | 7 -
.../can-i-send-really-large-files-over-activemq.md | 16 -
.../can-i-use-activemq-5x-or-later-on-java-14.md | 19 -
.../can-two-brokers-share-the-same-database.md | 14 -
.../does-activemq-support-clustering.md | 7 -
...id-serialization-of-objects-in-objectmessage.md | 7 -
...-a-list-of-the-topics-and-queues-in-a-broker.md | 16 -
.../how-can-i-make-activemq-faster.md | 7 -
.../how-can-i-monitor-activemq.md | 36 -
...can-i-monitor-the-connection-with-the-broker.md | 16 -
.../how-can-i-see-what-destinations-are-used.md | 11 -
.../how-can-i-support-auto-reconnection.md | 20 -
.../how-can-i-support-priority-queues.md | 50 -
.../how-can-i-use-different-network-protocols.md | 7 -
.../how-do-distributed-queues-work.md | 55 -
.../how-do-i-access-activemq-from-c.md | 7 -
...w-do-i-access-activemq-from-csharp-or-dotnet.md | 7 -
...-i-access-activemq-from-ruby-perl-python-php.md | 7 -
.../how-do-i-bridge-different-jms-providers.md | 9 -
.../how-do-i-change-dispatch-policy.md | 33 -
.../how-do-i-change-the-logging.md | 120 -
...onnect-to-one-of-a-number-of-message-brokers.md | 11 -
.../how-do-i-create-new-destinations.md | 33 -
.../how-do-i-delete-a-destination.md | 20 -
.../how-do-i-disable-logging.md | 10 -
.../how-do-i-embed-a-broker-inside-a-connection.md | 201 -
.../how-do-i-enable-asynchronous-sending.md | 14 -
.../how-do-i-enable-debug-logging.md | 14 -
.../how-do-i-find-the-size-of-a-queue.md | 23 -
.../how-do-i-preserve-order-of-messages.md | 12 -
.../how-do-i-purge-a-queue.md | 24 -
.../how-do-i-restart-embedded-broker.md | 36 -
...nnections-from-creating-new-queues-or-topics.md | 12 -
.../Using Apache ActiveMQ/how-do-i-run-a-broker.md | 9 -
.../how-do-i-set-the-message-expiration.md | 10 -
...-activemq-broker-when-using-the-vm-transport.md | 9 -
.../how-do-i-unack-the-message-with-stomp.md | 56 -
...how-do-i-use-activemq-using-in-jvm-messaging.md | 17 -
...-durable-subscribers-in-a-network-of-brokers.md | 25 -
.../how-do-i-use-ivy-with-activemq.md | 44 -
...ow-do-i-use-log4j-jms-appender-with-activemq.md | 79 -
.../FAQ/Using Apache ActiveMQ/how-do-i-use-ssl.md | 133 -
.../how-do-message-groups-compare-to-selectors.md | 21 -
.../how-do-multiple-transports-work.md | 11 -
.../how-do-transactions-work.md | 16 -
.../how-lightweight-is-sending-a-message.md | 17 -
...ackage-applications-using-camel-and-activemq.md | 17 -
.../how-should-i-use-the-vm-transport.md | 28 -
...deal-with-large-number-of-threads-in-clients.md | 34 -
.../how-to-disable-auto-destination-creation.md | 7 -
.../i-see-nc-client-ids-what-does-that-mean.md | 14 -
...atterns-in-the-broker-or-another-application.md | 24 -
...deploy-the-broker-inside-my-jvm-or-appserver.md | 26 -
.../what-are-those-topics-activemqadvisory.md | 7 -
...ppens-with-a-fast-producer-and-slow-consumer.md | 9 -
...-a-virtual-topic-and-a-composite-destination.md | 18 -
...nce-between-discovery-multicast-and-zeroconf.md | 35 -
.../what-is-the-prefetch-limit-for.md | 62 -
...ivemq-is-there-a-way-to-measure-its-progress.md | 10 -
.../original/Community/FAQ/configuration.md | 22 -
.../original/Community/FAQ/developing-activemq.md | 12 -
src/_documents/original/Community/FAQ/errors.md | 39 -
src/_documents/original/Community/FAQ/general.md | 32 -
src/_documents/original/Community/FAQ/jms.md | 26 -
.../Community/FAQ/persistence-questions.md | 17 -
.../original/Community/FAQ/terminology.md | 98 -
.../Community/FAQ/using-apache-activemq.md | 68 -
.../original/Community/Mailing Lists/all-forums.md | 7 -
.../Community/Mailing Lists/developer-forum.md | 7 -
.../original/Community/Mailing Lists/user-forum.md | 7 -
.../original/Community/activemq-pmc-templates.md | 184 -
src/_documents/original/Community/articles.md | 122 -
src/_documents/original/Community/books.md | 47 -
src/_documents/original/Community/contributing.md | 93 -
.../original/Community/discussion-forums.md | 18 -
src/_documents/original/Community/faq.md | 219 -
src/_documents/original/Community/mailing-lists.md | 72 -
src/_documents/original/Community/pmc-templates.md | 186 -
.../original/Community/privacy-policy.md | 19 -
.../original/Community/projects-using-activemq.md | 22 -
.../original/Community/security-advisories.md | 40 -
src/_documents/original/Community/sponsorship.md | 9 -
src/_documents/original/Community/support.md | 49 -
src/_documents/original/Community/team.md | 640 ---
.../original/Community/tips-for-getting-help.md | 17 -
src/_documents/original/Community/users.md | 80 -
.../JBoss Integration/inbound-communication.md | 107 -
.../JBoss Integration/outbound-communication.md | 168 -
.../Resource Adapter/activation-spec-properties.md | 199 -
.../connection-factory-properties.md | 65 -
.../resource-adapter-properties.md | 180 -
.../Containers/Resource Adapter/tomee.md | 95 -
.../Spring Support/jmstemplate-gotchas.md | 29 -
.../Tomcat/setting-up-activemq-with-tomcat-559.md | 51 -
.../Containers/axis-and-cxf-support.md | 17 -
.../original/Connectivity/Containers/blazeds.md | 54 -
.../original/Connectivity/Containers/geronimo.md | 198 -
.../integrating-apache-activemq-with-glassfish.md | 50 -
.../integrating-apache-activemq-with-jboss.md | 724 ---
.../original/Connectivity/Containers/j2ee.md | 56 -
.../Connectivity/Containers/jboss-integration.md | 724 ---
.../Connectivity/Containers/jca-container.md | 58 -
.../Connectivity/Containers/jndi-support.md | 86 -
.../Containers/old-osgi-integration.md | 166 -
.../Connectivity/Containers/osgi-integration.md | 114 -
.../Connectivity/Containers/resource-adapter.md | 54 -
.../Containers/sjsas-with-genericjmsra.md | 164 -
.../Connectivity/Containers/spring-support.md | 109 -
.../original/Connectivity/Containers/sun-jndi.md | 99 -
.../original/Connectivity/Containers/tomcat.md | 101 -
.../Containers/weblogic-integration.md | 618 ---
.../original/Connectivity/Containers/zos.md | 174 -
.../ActiveMQ C++ Clients/activemq-c-development.md | 99 -
.../ActiveMQ C++ Clients/building-activemq-cpp.md | 141 -
.../configuring-activemq-cpp.md | 242 -
.../downloading-activemq-cpp.md | 23 -
.../ActiveMQ C++ Clients/openwire-cpp-client.md | 113 -
.../C Integration/c-integration-scenarios.md | 52 -
.../C Integration/compile-activemq-with-gcj.md | 255 -
.../C Integration/openwire-c-client.md | 15 -
.../Cross Language Clients/activemq-c-clients.md | 10 -
.../Cross Language Clients/c-integration.md | 22 -
.../Connectivity/Cross Language Clients/cms.md | 169 -
.../delphi-and-freepascal.md | 26 -
.../Connectivity/Cross Language Clients/dot-net.md | 166 -
.../Connectivity/Cross Language Clients/perl.md | 177 -
.../Connectivity/Cross Language Clients/php.md | 170 -
.../Connectivity/Cross Language Clients/pike.md | 169 -
.../Connectivity/Cross Language Clients/python.md | 171 -
.../Connectivity/Cross Language Clients/ruby.md | 185 -
.../OpenWire/openwire-version-2-specification.md | 561 ---
.../original/Connectivity/Protocols/amqp.md | 353 --
.../original/Connectivity/Protocols/auto.md | 124 -
.../original/Connectivity/Protocols/mqtt.md | 124 -
.../original/Connectivity/Protocols/openwire.md | 26 -
.../original/Connectivity/Protocols/rest.md | 216 -
.../Connectivity/Protocols/rss-and-atom.md | 45 -
.../original/Connectivity/Protocols/stomp.md | 431 --
.../Connectivity/Protocols/ws-notification.md | 10 -
.../original/Connectivity/Protocols/wsif.md | 9 -
.../original/Connectivity/Protocols/xmpp.md | 102 -
src/_documents/original/Connectivity/ajax.md | 170 -
src/_documents/original/Connectivity/containers.md | 26 -
.../Connectivity/cross-language-clients.md | 1028 ----
.../original/Connectivity/jms-to-jms-bridge.md | 559 ---
src/_documents/original/Connectivity/protocols.md | 18 -
src/_documents/original/Connectivity/websockets.md | 73 -
.../Developers/Board Reports/2007-april.md | 12 -
...lass-diagrams-for-activemq-40-m4-source-code.md | 17 -
.../durable-queue-memory-management.md | 42 -
.../message-redelivery-and-dlq-handling.md | 217 -
.../Design Documents/multicast-transport.md | 17 -
.../proposed-c-client-architecture.md | 17 -
.../Design Documents/rest-protocols.md | 57 -
.../Design Documents/slow-consumers.md | 80 -
.../Design Documents/supporting-io-streams.md | 41 -
.../Developer Guide/Release Plans/40-rc-1-guide.md | 47 -
.../Release Plans/how-you-can-help-release.md | 12 -
.../Developer Guide/Release Plans/release-info.md | 13 -
.../Developers/Developer Guide/design-documents.md | 13 -
.../Developer Guide/developing-plugins.md | 68 -
.../maven-snapshot-repository-in-your-pom.md | 33 -
.../Developers/Developer Guide/release-plans.md | 14 -
.../original/Developers/Ideas/restful-queue.md | 156 -
.../Integration Tests/example-testing-scenario.md | 129 -
.../original/Developers/becoming-a-committer.md | 44 -
.../original/Developers/benchmark-tests.md | 18 -
.../original/Developers/board-reports.md | 12 -
src/_documents/original/Developers/building.md | 74 -
.../original/Developers/code-overview.md | 121 -
.../original/Developers/developer-guide.md | 21 -
src/_documents/original/Developers/ideas.md | 9 -
.../original/Developers/integration-tests.md | 55 -
.../Developers/jmeter-performance-tests.md | 83 -
.../original/Developers/jmeter-system-tests.md | 58 -
.../original/Developers/junit-reports.md | 7 -
.../original/Developers/release-guide.md | 190 -
src/_documents/original/Developers/sandbox.md | 5 -
src/_documents/original/Developers/source-xref.md | 9 -
src/_documents/original/Developers/source.md | 56 -
src/_documents/original/Developers/svn.md | 56 -
.../original/Developers/test-source-xref.md | 8 -
.../original/Developers/wire-protocol.md | 71 -
.../Features/ActiveMQ Real Time/broadcasting.md | 40 -
.../ActiveMQ Real Time/group-membership.md | 33 -
.../Features/ActiveMQ Real Time/life-cycle.md | 52 -
.../the-activeblaze-message-type.md | 61 -
.../Clustering/MasterSlave/jdbc-master-slave.md | 131 -
.../Clustering/MasterSlave/kahadb-master-slave.md | 231 -
.../MasterSlave/kahadb-replication-experimental.md | 65 -
.../Clustering/MasterSlave/pure-master-slave.md | 108 -
.../MasterSlave/shared-file-system-master-slave.md | 87 -
.../original/Features/Clustering/masterslave.md | 44 -
.../Features/Clustering/networks-of-brokers.md | 543 --
.../Clustering/replicated-message-store.md | 33 -
.../Consumer Features/consumer-dispatch-async.md | 35 -
.../Consumer Features/consumer-priority.md | 20 -
.../Consumer Features/exclusive-consumer.md | 28 -
.../manage-durable-subscribers.md | 47 -
.../Features/Consumer Features/message-groups.md | 144 -
.../Consumer Features/redelivery-policy.md | 94 -
.../Consumer Features/retroactive-consumer.md | 28 -
.../Features/Consumer Features/selectors.md | 37 -
.../Consumer Features/slow-consumer-handling.md | 87 -
.../subscription-recovery-policy.md | 75 -
.../Destination Features/composite-destinations.md | 27 -
.../configure-startup-destinations.md | 15 -
.../delete-inactive-destinations.md | 33 -
.../Destination Features/destination-options.md | 70 -
.../Destination Features/mirrored-queues.md | 42 -
.../per-destination-policies.md | 348 --
.../Destination Features/virtual-destinations.md | 181 -
.../Features/Destination Features/wildcards.md | 67 -
.../Features/Horizontal Scaling/scaling-queues.md | 43 -
.../Features/Interceptors/destinations-plugin.md | 13 -
.../Features/Interceptors/logging-interceptor.md | 88 -
.../Features/Interceptors/statisticsplugin.md | 156 -
.../Features/Interceptors/timestampplugin.md | 56 -
.../original/Features/JMX/jmx-support.md | 66 -
.../Message Dispatching Features/async-sends.md | 42 -
.../dispatch-policies.md | 36 -
.../message-cursors.md | 94 -
.../optimized-acknowledgement.md | 26 -
.../producer-flow-control.md | 115 -
.../Message Dispatching Features/total-ordering.md | 36 -
.../activemq-message-properties.md | 168 -
.../Features/Message Features/advisory-message.md | 543 --
.../Features/Message Features/blob-messages.md | 57 -
.../delay-and-schedule-message-delivery.md | 81 -
.../Features/Message Features/jms-streams.md | 57 -
.../Message Features/message-transformation.md | 31 -
.../Features/Message Features/object-message.md | 5 -
.../Features/Message Features/objectmessage.md | 69 -
...tructured-message-properties-and-mapmessages.md | 20 -
.../New Features in 5.9/runtime-configuration.md | 34 -
.../Features/New Features/changes-in-40.md | 60 -
.../Features/New Features/new-features-in-41.md | 14 -
.../Features/New Features/new-features-in-50.md | 20 -
.../Features/New Features/new-features-in-51.md | 20 -
.../Features/New Features/new-features-in-511.md | 18 -
.../Features/New Features/new-features-in-513.md | 18 -
.../Features/New Features/new-features-in-52.md | 26 -
.../Features/New Features/new-features-in-53.md | 22 -
.../Features/New Features/new-features-in-54.md | 27 -
.../Features/New Features/new-features-in-55.md | 23 -
.../Features/New Features/new-features-in-56.md | 17 -
.../Features/New Features/new-features-in-57.md | 13 -
.../Features/New Features/new-features-in-58.md | 12 -
.../Features/New Features/new-features-in-59.md | 14 -
.../Features/New Features/new-features-in-60.md | 7 -
.../sample-report.md | 76 -
.../activemq-performance-module-users-manual.md | 697 ---
.../Performance/load-testing-with-camel.md | 18 -
.../Features/Performance/performance-report.md | 12 -
.../Features/Persistence/JDBC Support/sqlserver.md | 95 -
.../Features/Persistence/JDBC Support/sybase.md | 34 -
.../Features/Persistence/Kaha Persistence/test.md | 166 -
.../Features/Persistence/amq-message-store.md | 160 -
.../configurable-ioexception-handling.md | 122 -
.../original/Features/Persistence/jdbc-support.md | 78 -
.../Features/Persistence/kaha-persistence.md | 38 -
.../original/Features/Persistence/kahadb.md | 298 --
.../original/Features/Persistence/leveldb-store.md | 127 -
.../periodically-checking-disk-limits.md | 15 -
.../Persistence/pluggable-storage-lockers.md | 151 -
.../Persistence/replicated-leveldb-store.md | 228 -
.../original/Features/Security/audit-logging.md | 38 -
.../Security/cached-ldap-authorization-module.md | 146 -
.../Features/Security/encrypted-passwords.md | 96 -
src/_documents/original/Features/Security/shiro.md | 370 --
.../original/Features/URI Protocols/vm-protocol.md | 18 -
.../original/Features/Unix/unix-service.md | 11 -
.../original/Features/Unix/unix-shell-script.md | 199 -
.../Visualisation/visualisation-wish-list.md | 11 -
src/_documents/original/Features/active-groups.md | 23 -
.../original/Features/activemq-real-time.md | 54 -
.../original/Features/broker-camel-component.md | 70 -
src/_documents/original/Features/clustering.md | 61 -
src/_documents/original/Features/command-agent.md | 45 -
.../original/Features/consumer-features.md | 16 -
.../original/Features/destination-features.md | 14 -
src/_documents/original/Features/discovery.md | 66 -
.../Features/enterprise-integration-patterns.md | 55 -
.../original/Features/features-overview.md | 24 -
.../original/Features/horizontal-scaling.md | 5 -
src/_documents/original/Features/interceptors.md | 127 -
src/_documents/original/Features/jmsxuserid.md | 30 -
src/_documents/original/Features/jmx.md | 342 --
...-warning-if-you-forget-to-start-a-connection.md | 14 -
src/_documents/original/Features/mdc-logging.md | 39 -
.../Features/message-dispatching-features.md | 12 -
.../original/Features/message-features.md | 14 -
src/_documents/original/Features/new-features.md | 22 -
src/_documents/original/Features/performance.md | 38 -
src/_documents/original/Features/persistence.md | 105 -
.../Features/scaling-the-depth-of-a-queue.md | 13 -
src/_documents/original/Features/security.md | 183 -
.../original/Features/the-proxy-connector.md | 32 -
src/_documents/original/Features/unix.md | 10 -
src/_documents/original/Features/uri-protocols.md | 109 -
src/_documents/original/Features/visualisation.md | 37 -
.../apache-activemq-board-report-200708-august.md | 27 -
.../apache-activemq-board-report-200710-october.md | 24 -
.../apache-activemq-board-report-200801-january.md | 26 -
.../apache-activemq-board-report-200807-july.md | 30 -
.../apache-activemq-board-report-200810-october.md | 20 -
.../apache-activemq-board-report-200901-january.md | 27 -
.../apache-activemq-board-report-200904-april.md | 24 -
.../apache-activemq-board-report-200907-july.md | 22 -
.../apache-activemq-board-report-200910-october.md | 23 -
.../apache-activemq-board-report-201001-january.md | 17 -
.../apache-activemq-board-report-201005-may.md | 26 -
.../apache-activemq-board-report-201007-july.md | 24 -
.../apache-activemq-board-report-201010-october.md | 27 -
.../apache-activemq-board-report-201101-january.md | 22 -
.../apache-activemq-board-report-201104-april.md | 26 -
.../apache-activemq-board-report-201107-july.md | 39 -
.../apache-activemq-board-report-201110-october.md | 30 -
.../apache-activemq-board-report-201201-january.md | 34 -
.../apache-activemq-board-report-201204-april.md | 32 -
.../apache-activemq-board-report-201207-july.md | 40 -
.../apache-activemq-board-report-201210-october.md | 34 -
.../apache-activemq-board-report-201301-january.md | 31 -
.../apache-activemq-board-report-201304-april.md | 31 -
.../apache-activemq-board-report-201307-july.md | 31 -
.../apache-activemq-board-report-201310-october.md | 28 -
.../apache-activemq-board-report-201401-january.md | 28 -
.../apache-activemq-board-report-201404-april.md | 26 -
.../apache-activemq-board-report-201407-july.md | 22 -
.../apache-activemq-board-report-201410-october.md | 29 -
...apache-activemq-board-report-201502-february.md | 31 -
.../apache-activemq-board-report-201504-april.md | 85 -
.../apache-activemq-board-report-201505-may.md | 167 -
.../apache-activemq-board-report-201506-june.md | 38 -
.../apache-activemq-board-report-201507-july.md | 28 -
.../apache-activemq-board-report-201508-august.md | 37 -
.../apache-activemq-board-report-201510-october.md | 75 -
.../apache-activemq-board-report-2016-05-may.md | 37 -
...apache-activemq-board-report-201602-february.md | 88 -
.../apache-activemq-board-report-201604-april.md | 65 -
.../apache-activemq-board-report-201605-may.md | 37 -
.../apache-activemq-board-report-201607-july.md | 93 -
.../apache-activemq-board-report-20161-january.md | 81 -
.../apache-activemq-board-report-201610-october.md | 62 -
.../apache-activemq-board-report-20162-february.md | 88 -
.../apache-activemq-board-report-201701-january.md | 63 -
.../apache-activemq-board-report-201704-april.md | 50 -
.../apache-activemq-board-report-201707-july.md | 52 -
.../apache-activemq-board-report-201710-october.md | 36 -
.../apache-activemq-board-report-april-2009.md | 144 -
.../apache-activemq-board-report-april-2011.md | 160 -
.../apache-activemq-board-report-april-2012.md | 166 -
.../apache-activemq-board-report-april-2013.md | 165 -
.../apache-activemq-board-report-april-2014.md | 160 -
.../apache-activemq-board-report-august-2007.md | 144 -
.../apache-activemq-board-report-february-2015.md | 165 -
.../apache-activemq-board-report-january-2008.md | 144 -
.../apache-activemq-board-report-january-2009.md | 144 -
.../apache-activemq-board-report-january-2010.md | 151 -
.../apache-activemq-board-report-january-2011.md | 156 -
.../apache-activemq-board-report-january-2012.md | 168 -
.../apache-activemq-board-report-january-2013.md | 165 -
.../apache-activemq-board-report-january-2014.md | 162 -
.../apache-activemq-board-report-july-2008.md | 144 -
.../apache-activemq-board-report-july-2009.md | 156 -
.../apache-activemq-board-report-july-2010.md | 158 -
.../apache-activemq-board-report-july-2011.md | 173 -
.../apache-activemq-board-report-july-2012.md | 174 -
.../apache-activemq-board-report-july-2013.md | 165 -
.../apache-activemq-board-report-july-2014.md | 156 -
.../apache-activemq-board-report-may-2010.md | 144 -
.../apache-activemq-board-report-october-2007.md | 144 -
.../apache-activemq-board-report-october-2008.md | 144 -
.../apache-activemq-board-report-october-2009.md | 157 -
.../apache-activemq-board-report-october-2010.md | 161 -
.../apache-activemq-board-report-october-2011.md | 164 -
.../apache-activemq-board-report-october-2012.md | 168 -
.../apache-activemq-board-report-october-2013.md | 162 -
.../apache-activemq-board-report-october-2014.md | 163 -
...of-apache-activemq-board-report-201604-april.md | 65 -
.../NMS API Downloads/apachenms-api-v110.md | 55 -
.../NMS API Downloads/apachenms-api-v120.md | 61 -
.../NMS API Downloads/apachenms-api-v130.md | 56 -
.../NMS API Downloads/apachenms-api-v140.md | 58 -
.../NMS API Downloads/apachenms-api-v150.md | 56 -
.../NMS API Downloads/apachenms-api-v151.md | 56 -
.../NMS API Downloads/apachenms-api-v160.md | 56 -
.../NMS API Downloads/apachenms-api-v170.md | 56 -
.../NMS API Downloads/apachenms-api-v171.md | 52 -
.../nms-simple-asynchronous-consumer-example.md | 125 -
.../nms-simple-synchornous-consumer-example.md | 110 -
.../Apache.NMS.AMQP/amqp-build-notes.md | 37 -
.../Apache.NMS.AMQP/amqp-downloads.md | 5 -
.../NMS Providers/Apache.NMS.AMQP/amqp-examples.md | 17 -
.../NMS Providers/Apache.NMS.AMQP/amqp-faq.md | 5 -
.../activemq-consumer-dispatch-async.md | 31 -
.../activemq-consumer-priority.md | 22 -
.../activemq-exclusive-consumers.md | 20 -
.../activemq-retroactive-consumers.md | 28 -
.../activemq-destination-management.md | 28 -
.../activemq-destination-options.md | 70 -
.../activemq-mirrored-queues.md | 42 -
.../activemq-virtual-destinations.md | 149 -
.../activemq-wildcards.md | 67 -
.../activemq-async-sends.md | 42 -
.../activemq-delay-and-schedule-message-feature.md | 75 -
.../activemq-consumer-features.md | 5 -
.../activemq-destination-features.md | 11 -
.../activemq-message-dispatching-features.md | 7 -
.../activemq-message-features.md | 7 -
.../ActiveMQ Downloads/apachenms-activemq-v110.md | 61 -
.../ActiveMQ Downloads/apachenmsactivemq-v120.md | 62 -
.../ActiveMQ Downloads/apachenmsactivemq-v130.md | 58 -
.../ActiveMQ Downloads/apachenmsactivemq-v140.md | 63 -
.../ActiveMQ Downloads/apachenmsactivemq-v141.md | 59 -
.../ActiveMQ Downloads/apachenmsactivemq-v150.md | 67 -
.../ActiveMQ Downloads/apachenmsactivemq-v151.md | 56 -
.../ActiveMQ Downloads/apachenmsactivemq-v152.md | 56 -
.../ActiveMQ Downloads/apachenmsactivemq-v153.md | 56 -
.../ActiveMQ Downloads/apachenmsactivemq-v154.md | 56 -
.../ActiveMQ Downloads/apachenmsactivemq-v155.md | 62 -
.../ActiveMQ Downloads/apachenmsactivemq-v156.md | 59 -
.../ActiveMQ Downloads/apachenmsactivemq-v160.md | 65 -
.../ActiveMQ Downloads/apachenmsactivemq-v161.md | 63 -
.../ActiveMQ Downloads/apachenmsactivemq-v162.md | 56 -
.../ActiveMQ Downloads/apachenmsactivemq-v163.md | 52 -
.../ActiveMQ Downloads/apachenmsactivemq-v164.md | 52 -
.../ActiveMQ Downloads/apachenmsactivemq-v165.md | 52 -
.../ActiveMQ Downloads/apachenmsactivemq-v170.md | 52 -
.../ActiveMQ Downloads/apachenmsactivemq-v171.md | 52 -
.../ActiveMQ Downloads/apachenmsactivemq-v172.md | 52 -
...numerate-destination-using-advisory-messages.md | 159 -
.../activemq-advisory-message-examples.md | 7 -
.../activemq-advanced-features.md | 23 -
.../Apache.NMS.ActiveMQ/activemq-build-notes.md | 5 -
.../Apache.NMS.ActiveMQ/activemq-downloads.md | 137 -
.../Apache.NMS.ActiveMQ/activemq-examples.md | 8 -
.../Apache.NMS.ActiveMQ/activemq-faq.md | 5 -
.../activemq-uri-configuration.md | 402 --
.../EMS Downloads/apachenms-ems-v110.md | 51 -
.../Apache.NMS.EMS/ems-build-notes.md | 5 -
.../NMS Providers/Apache.NMS.EMS/ems-downloads.md | 17 -
.../NMS Providers/Apache.NMS.EMS/ems-examples.md | 5 -
.../NMS Providers/Apache.NMS.EMS/ems-faq.md | 5 -
.../MSMQ Downloads/apachenms-msmq-v110.md | 47 -
.../Apache.NMS.MSMQ/msmq-build-notes.md | 5 -
.../Apache.NMS.MSMQ/msmq-downloads.md | 17 -
.../NMS Providers/Apache.NMS.MSMQ/msmq-examples.md | 5 -
.../NMS Providers/Apache.NMS.MSMQ/msmq-faq.md | 5 -
.../stomp-delayed-and-scheduled-message-feature.md | 77 -
.../stomp-message-features.md | 7 -
.../Stomp Downloads/apachenmsstomp-v120.md | 56 -
.../Stomp Downloads/apachenmsstomp-v130.md | 62 -
.../Stomp Downloads/apachenmsstomp-v140.md | 62 -
.../Stomp Downloads/apachenmsstomp-v150.md | 61 -
.../Stomp Downloads/apachenmsstomp-v151.md | 64 -
.../Stomp Downloads/apachenmsstomp-v152.md | 56 -
.../Stomp Downloads/apachenmsstomp-v153.md | 56 -
.../Stomp Downloads/apachenmsstomp-v154.md | 56 -
.../Apache.NMS.Stomp/stomp-advanced-features.md | 8 -
.../Apache.NMS.Stomp/stomp-build-notes.md | 5 -
.../Apache.NMS.Stomp/stomp-downloads.md | 59 -
.../NMS Providers/Apache.NMS.Stomp/stomp-faq.md | 5 -
.../Apache.NMS.Stomp/stomp-uri-configuration.md | 292 --
.../WCF Downloads/apachenmswcf-v110.md | 52 -
.../NMS Providers/Apache.NMS.WCF/wcf-downloads.md | 17 -
.../NMS Providers/Apache.NMS.WCF/wcf-examples.md | 5 -
.../Apache.NMS/NMS Providers/apachenmsactivemq.md | 14 -
.../Apache.NMS/NMS Providers/apachenmsamqp.md | 12 -
.../Index/Apache.NMS/NMS Providers/apachenmsems.md | 12 -
.../Apache.NMS/NMS Providers/apachenmsmqtt.md | 7 -
.../Apache.NMS/NMS Providers/apachenmsmsmq.md | 12 -
.../Apache.NMS/NMS Providers/apachenmsstomp.md | 13 -
.../Index/Apache.NMS/NMS Providers/apachenmswcf.md | 10 -
.../Index/Apache.NMS/NMS Providers/apachenmsxms.md | 7 -
.../original/Index/Apache.NMS/nms-api-downloads.md | 45 -
.../original/Index/Apache.NMS/nms-api.md | 16 -
.../original/Index/Apache.NMS/nms-examples.md | 10 -
.../original/Index/Apache.NMS/nms-faq.md | 5 -
.../original/Index/Apache.NMS/nms-providers.md | 18 -
.../Index/Apache.NMS/nms-uri-configuration.md | 48 -
.../how-do-i-use-the-ssl-transport.md | 26 -
.../enable-openssl-support-with-autotools.md | 8 -
...event-autoconf-from-enabling-openssl-support.md | 8 -
.../how-to-enable-ssl-support-on-windows.md | 6 -
...ibstdla-on-solaris-10-using-the-gnu-compiler.md | 85 -
.../errors-saying-no-rule-to-make-target.md | 6 -
.../using-the-solaris-cc-compiler.md | 21 -
.../FAQ/Building FAQs/general-build-issues.md | 8 -
.../Community/FAQ/Building FAQs/openssl-support.md | 10 -
.../FAQ/Building FAQs/solaris-platform.md | 10 -
.../FAQ/General/are-there-more-faq-entries.md | 9 -
.../Community/FAQ/General/what-is-activemq-cpp.md | 9 -
.../Index/Community/FAQ/activemq-cpp-usage-faqs.md | 8 -
.../original/Index/Community/FAQ/building-faqs.md | 16 -
.../Index/Developers/creating-distributions.md | 79 -
.../Index/FAQ/should-i-pool-connections.md | 14 -
src/_documents/original/Index/FAQ/what-is-nms.md | 12 -
.../activemq-cpp-product-version-number.md | 37 -
.../Overview/Download/activemq-cpp-10-release.md | 52 -
.../Overview/Download/activemq-cpp-11-release.md | 54 -
.../Overview/Download/activemq-cpp-20-release.md | 54 -
.../Overview/Download/activemq-cpp-201-release.md | 51 -
.../Overview/Download/activemq-cpp-21-release.md | 51 -
.../Overview/Download/activemq-cpp-211-release.md | 51 -
.../Overview/Download/activemq-cpp-212-release.md | 51 -
.../Overview/Download/activemq-cpp-213-release.md | 51 -
.../Overview/Download/activemq-cpp-22-release.md | 59 -
.../Overview/Download/activemq-cpp-221-release.md | 53 -
.../Overview/Download/activemq-cpp-222-release.md | 58 -
.../Overview/Download/activemq-cpp-223-release.md | 57 -
.../Overview/Download/activemq-cpp-224-release.md | 54 -
.../Overview/Download/activemq-cpp-225-release.md | 54 -
.../Overview/Download/activemq-cpp-226-release.md | 56 -
.../Overview/Download/activemq-cpp-30-release.md | 63 -
.../Overview/Download/activemq-cpp-301-release.md | 55 -
.../Overview/Download/activemq-cpp-310-release.md | 56 -
.../Overview/Download/activemq-cpp-311-release.md | 51 -
.../Overview/Download/activemq-cpp-312-release.md | 51 -
.../Overview/Download/activemq-cpp-313-release.md | 51 -
.../Overview/Download/activemq-cpp-320-release.md | 53 -
.../Overview/Download/activemq-cpp-321-release.md | 51 -
.../Overview/Download/activemq-cpp-322-release.md | 51 -
.../Overview/Download/activemq-cpp-323-release.md | 51 -
.../Overview/Download/activemq-cpp-324-release.md | 51 -
.../Overview/Download/activemq-cpp-325-release.md | 51 -
.../Overview/Download/activemq-cpp-330-release.md | 64 -
.../Overview/Download/activemq-cpp-340-release.md | 62 -
.../Overview/Download/activemq-cpp-341-release.md | 63 -
.../Overview/Download/activemq-cpp-342-release.md | 63 -
.../Overview/Download/activemq-cpp-343-release.md | 57 -
.../Overview/Download/activemq-cpp-344-release.md | 57 -
.../Overview/Download/activemq-cpp-345-release.md | 57 -
.../Overview/Download/activemq-cpp-350-release.md | 66 -
.../Overview/Download/activemq-cpp-360-release.md | 57 -
.../Overview/Download/activemq-cpp-370-release.md | 65 -
.../Overview/Download/activemq-cpp-371-release.md | 70 -
.../Overview/Download/activemq-cpp-380-release.md | 74 -
.../Overview/Download/activemq-cpp-381-release.md | 56 -
.../Overview/Download/activemq-cpp-382-release.md | 56 -
.../Overview/Download/activemq-cpp-383-release.md | 57 -
.../Overview/Download/activemq-cpp-384-release.md | 57 -
.../Overview/Download/activemq-cpp-390-release.md | 57 -
.../Overview/Download/activemq-cpp-391-release.md | 57 -
.../Overview/Download/activemq-cpp-392-release.md | 57 -
.../Overview/Download/activemq-cpp-393-release.md | 57 -
.../Overview/Download/activemq-cpp-394-release.md | 57 -
.../activemq-cpp-libtool-and-packaging-notes.md | 52 -
.../Overview/Download/activemq-net-110-release.md | 132 -
.../Overview/Download/activemq-net-120-release.md | 179 -
.../Overview/Download/activemq-net-130-release.md | 170 -
.../Overview/Download/activemq-net-140-release.md | 170 -
.../Overview/Download/apachenms-150-release.md | 196 -
.../Index/Overview/Download/cms-api-10-release.md | 50 -
.../Index/Overview/Download/cms-api-11-release.md | 52 -
.../Index/Overview/Download/cms-api-12-release.md | 51 -
.../Tutorials/handling-advisory-messages.md | 538 --
.../original/Index/Overview/cms-api-overview.md | 859 ----
src/_documents/original/Index/Overview/nms.md | 42 -
.../original/Index/Overview/tutorials.md | 11 -
.../original/Index/Overview/using-nms.md | 12 -
.../original/Index/Site/Navigation/api.md | 11 -
.../Index/Site/Navigation/openwire-support.md | 11 -
.../Index/Site/Navigation/stomp-support.md | 31 -
.../Index/Site/Navigation/using-activemq-cpp.md | 12 -
.../original/Index/activemq-cpp-stomp.md | 27 -
.../Index/apache-activemq-board-reports.md | 52 -
src/_documents/original/Index/apachenms.md | 34 -
src/_documents/original/Index/configuring.md | 485 --
src/_documents/original/Index/example.md | 426 --
...o-become-a-committer-on-the-activemq-project.md | 21 -
src/_documents/original/Index/thanks.md | 19 -
.../using-activemq-with-ejb3-jboss-example.md | 35 -
src/_documents/original/Index/verify-downloads.md | 36 -
.../ActiveMQ 5.8.0 Release/58-migration-guide.md | 54 -
.../ActiveMQ 5.9.0 Release/59-migration-guide.md | 11 -
.../Overview/Download/activemq-11-release.md | 55 -
.../Overview/Download/activemq-12-release.md | 47 -
.../Overview/Download/activemq-13-release.md | 47 -
.../Overview/Download/activemq-14-release.md | 47 -
.../Overview/Download/activemq-15-release.md | 47 -
.../Overview/Download/activemq-20-release.md | 60 -
.../Overview/Download/activemq-21-release.md | 47 -
.../Overview/Download/activemq-30-release.md | 49 -
.../Overview/Download/activemq-31-release.md | 66 -
.../Overview/Download/activemq-32-release.md | 50 -
.../Overview/Download/activemq-321-release.md | 42 -
.../Overview/Download/activemq-322-release.md | 42 -
.../Overview/Download/activemq-40-m4-release.md | 42 -
.../Overview/Download/activemq-40-rc2-release.md | 52 -
.../Overview/Download/activemq-40-release.md | 66 -
.../Overview/Download/activemq-401-release.md | 57 -
.../Overview/Download/activemq-402-release.md | 57 -
.../Overview/Download/activemq-410-release.md | 55 -
.../Overview/Download/activemq-411-release.md | 80 -
.../Overview/Download/activemq-412-release.md | 80 -
.../Overview/Download/activemq-500-release.md | 94 -
.../Overview/Download/activemq-510-release.md | 144 -
.../Overview/Download/activemq-5100-release.md | 120 -
.../Overview/Download/activemq-5101-release.md | 104 -
.../Overview/Download/activemq-5102-release.md | 104 -
.../Overview/Download/activemq-5110-release.md | 116 -
.../Overview/Download/activemq-5111-release.md | 104 -
.../Overview/Download/activemq-5112-release.md | 104 -
.../Overview/Download/activemq-5113-release.md | 104 -
.../Overview/Download/activemq-5120-release.md | 104 -
.../Overview/Download/activemq-5121-release.md | 104 -
.../Overview/Download/activemq-5122-release.md | 106 -
.../Overview/Download/activemq-5130-release.md | 106 -
.../Overview/Download/activemq-5131-release.md | 106 -
.../Overview/Download/activemq-5132-release.md | 106 -
.../Overview/Download/activemq-5133-release.md | 106 -
.../Overview/Download/activemq-5134-release.md | 106 -
.../Overview/Download/activemq-5140-release.md | 106 -
.../Overview/Download/activemq-5141-release.md | 106 -
.../Overview/Download/activemq-5142-release.md | 106 -
.../Overview/Download/activemq-5143-release.md | 106 -
.../Overview/Download/activemq-5144-release.md | 106 -
.../Overview/Download/activemq-5145-release.md | 106 -
.../Overview/Download/activemq-5150-release.md | 110 -
.../Overview/Download/activemq-5151-release.md | 110 -
.../Overview/Download/activemq-5152-release.md | 110 -
.../Overview/Download/activemq-520-release.md | 131 -
.../Overview/Download/activemq-530-release.md | 125 -
.../Overview/Download/activemq-531-release.md | 114 -
.../Overview/Download/activemq-532-release.md | 106 -
.../Overview/Download/activemq-540-release.md | 140 -
.../Overview/Download/activemq-541-release.md | 133 -
.../Overview/Download/activemq-542-release.md | 111 -
.../Overview/Download/activemq-543-release.md | 101 -
.../Overview/Download/activemq-550-release.md | 122 -
.../Overview/Download/activemq-551-release.md | 95 -
.../Overview/Download/activemq-560-release.md | 112 -
.../Overview/Download/activemq-570-release.md | 108 -
.../Overview/Download/activemq-580-release.md | 156 -
.../Overview/Download/activemq-590-release.md | 115 -
.../Overview/Download/activemq-591-release.md | 117 -
.../original/Overview/Download/in-progress.md | 10 -
.../original/Overview/download-archives.md | 80 -
src/_documents/original/Overview/download.md | 25 -
src/_documents/original/Overview/javadocs.md | 29 -
src/_documents/original/Overview/news.md | 103 -
src/_documents/original/README.md | 2 -
src/_documents/original/SUMMARY.md | 1024 ----
src/_documents/original/Site/Navigation/irc.md | 15 -
.../activemq-3-networks-of-brokers.md | 171 -
.../activemq-3-transport-configurations.md | 423 --
.../advisory-support-in-activemq-3.md | 178 -
.../Previous Versions/getting-started-3x.md | 437 --
.../Previous Versions/running-a-3x-broker.md | 225 -
.../original/Site/Old Links/activemqdtd.md | 172 -
.../original/Site/Old Links/activesoap.md | 200 -
.../original/Site/Old Links/activespace.md | 168 -
src/_documents/original/Site/Old Links/cvs.md | 196 -
.../original/Site/Old Links/leftheader.md | 168 -
.../original/Site/Old Links/new-features-in-42.md | 173 -
.../point-to-point-with-multiple-consumers.md | 180 -
.../original/Site/Old Links/polo-page.md | 172 -
.../original/Site/Old Links/previous-versions.md | 172 -
.../original/Site/Old Links/rightheader.md | 168 -
src/_documents/original/Site/Old Links/stp.md | 166 -
src/_documents/original/Site/banner.md | 5 -
src/_documents/original/Site/navigation.md | 6 -
src/_documents/original/Site/old-links.md | 183 -
src/_documents/original/Site/quicklinks.md | 6 -
src/_documents/original/Site/siteindex.md | 2492 ----------
src/_documents/original/Site/sitemap.md | 559 ---
.../original/Tools/Web Console/running-a-broker.md | 164 -
src/_documents/original/Tools/hermes-jms.md | 37 -
src/_documents/original/Tools/hermes-screenshot.md | 9 -
.../original/Tools/java-service-wrapper.md | 52 -
.../Tools/maven2-activemq-broker-plugin.md | 108 -
src/_documents/original/Tools/web-console.md | 128 -
.../activemq-4-connection-uris.md | 249 -
.../configure-version-5-brokers.md | 125 -
.../configuring-version-5-transports.md | 249 -
.../ldap-broker-discovery-mechanism.md | 291 --
.../Using ActiveMQ 5/version-5-examples.md | 88 -
.../Using ActiveMQ 5/version-5-getting-started.md | 395 --
.../Using ActiveMQ 5/version-5-hello-world.md | 160 -
.../version-5-initial-configuration.md | 93 -
.../Using ActiveMQ 5/version-5-installation.md | 20 -
.../version-5-performance-tuning.md | 61 -
.../Using ActiveMQ 5/version-5-run-broker.md | 79 -
.../Using ActiveMQ 5/version-5-topologies.md | 80 -
.../Using ActiveMQ 5/version-5-web-samples.md | 18 -
.../version-5-xml-configuration.md | 52 -
.../broker-properties-uri.md | 48 -
.../Broker Configuration URI/broker-uri.md | 80 -
.../Broker Configuration URI/broker-xbean-uri.md | 40 -
.../broker-configuration-uri.md | 37 -
.../configuring-wire-formats.md | 90 -
.../connection-configuration-uri.md | 200 -
.../discovery-transport-reference.md | 85 -
.../failover-transport-reference.md | 253 -
.../fanout-transport-reference.md | 91 -
.../http-and-https-transports-reference.md | 33 -
.../multicast-transport-reference.md | 89 -
.../nio-transport-reference.md | 61 -
.../peer-transport-reference.md | 17 -
.../ssl-transport-reference.md | 71 -
.../static-transport-reference.md | 65 -
.../tcp-transport-reference.md | 251 -
.../udp-transport-reference.md | 61 -
.../vm-transport-reference.md | 122 -
.../ZeroConf Transport Reference/zeroconf.md | 20 -
.../activemq-connection-uris.md | 249 -
.../activemq-inactivitymonitor.md | 87 -
.../zeroconf-transport-reference.md | 30 -
.../Getting Started/gettingstarted3x.md | 168 -
.../Getting Started/monitoring-activemq.md | 16 -
...mplex-single-broker-configuration-stomp-only.md | 121 -
.../jms-and-jdbc-operations-in-one-transaction.md | 155 -
.../jms-bridge-with-local-broker.md | 37 -
.../jms-bridge-with-oracle-aq.md | 115 -
.../jms-bridge-with-remote-broker.md | 37 -
.../jms-bridge-with-remote-tibco-broker.md | 41 -
.../sample-camel-routes.md | 144 -
.../Xml Reference/xbean-xml-reference-41.md | 3186 ------------
.../Xml Reference/xbean-xml-reference-50.md | 5234 --------------------
.../original/Using ActiveMQ/configuring-brokers.md | 41 -
.../Using ActiveMQ/configuring-transports.md | 249 -
src/_documents/original/Using ActiveMQ/examples.md | 88 -
.../original/Using ActiveMQ/getting-started.md | 355 --
.../original/Using ActiveMQ/hello-world.md | 160 -
.../Using ActiveMQ/initial-configuration.md | 89 -
.../original/Using ActiveMQ/installation.md | 20 -
.../known-bad-os-and-jvm-combinations.md | 17 -
.../original/Using ActiveMQ/performance-tuning.md | 67 -
.../original/Using ActiveMQ/run-broker.md | 70 -
.../original/Using ActiveMQ/topologies.md | 80 -
.../original/Using ActiveMQ/use-cases.md | 52 -
.../user-submitted-configurations.md | 15 -
.../original/Using ActiveMQ/web-samples.md | 20 -
.../original/Using ActiveMQ/xml-configuration.md | 80 -
.../original/Using ActiveMQ/xml-reference.md | 511 --
.../original/activemq-artemis-roadmap.md | 89 -
src/_documents/original/activemq6.md | 7 -
src/_documents/original/amqp-manual.md | 167 -
.../apache-activemq-board-report-april-2008.md | 44 -
src/_documents/original/architecture.md | 62 -
src/_documents/original/authentication.md | 50 -
src/_documents/original/authorization.md | 162 -
src/_documents/original/chat.md | 37 -
src/_documents/original/community.md | 34 -
src/_documents/original/connectivity.md | 45 -
src/_documents/original/connectors.md | 94 -
src/_documents/original/destinations.md | 57 -
src/_documents/original/developers.md | 42 -
src/_documents/original/docs.md | 34 -
src/_documents/original/extending-guide.md | 184 -
src/_documents/original/features.md | 126 -
src/_documents/original/images/ActiveMQ-CPP.png | Bin 6414 -> 0 bytes
.../original/images/ActiveMQConnections.png | Bin 65754 -> 0 bytes
.../original/images/ActiveMQDestinations.png | Bin 60045 -> 0 bytes
src/_documents/original/images/Broker Diagram.png | Bin 30239 -> 0 bytes
src/_documents/original/images/BrokerDiagram-1.png | Bin 43577 -> 0 bytes
src/_documents/original/images/BrokerDiagram.jpg | Bin 163577 -> 0 bytes
src/_documents/original/images/BrokerDiagram.png | Bin 59729 -> 0 bytes
src/_documents/original/images/BrokerDiagram2.png | Bin 34914 -> 0 bytes
.../original/images/BrokerTopology-1.png | Bin 42571 -> 0 bytes
src/_documents/original/images/BrokerTopology.png | Bin 43528 -> 0 bytes
src/_documents/original/images/BrokerTopology2.png | Bin 54692 -> 0 bytes
src/_documents/original/images/BrokerTopology3.png | Bin 29548 -> 0 bytes
.../original/images/DispatchFastConsumers.png | Bin 34641 -> 0 bytes
.../original/images/DispatchSlowConsumers.png | Bin 39607 -> 0 bytes
.../images/Example1-DirectoryStructure.jpg | Bin 11397 -> 0 bytes
src/_documents/original/images/Example1-Entry.jpg | Bin 27975 -> 0 bytes
.../original/images/Example1-Topology.jpg | Bin 7922 -> 0 bytes
src/_documents/original/images/Example1.jpg | Bin 34587 -> 0 bytes
.../images/Example2-DirectoryStructure.jpg | Bin 18491 -> 0 bytes
.../original/images/Example2-Topology.jpg | Bin 12704 -> 0 bytes
src/_documents/original/images/Example2.jpg | Bin 60160 -> 0 bytes
src/_documents/original/images/FileCursor.png | Bin 51315 -> 0 bytes
src/_documents/original/images/Fisheye_logo.png | Bin 10543 -> 0 bytes
src/_documents/original/images/I.png | Bin 148 -> 0 bytes
.../original/images/JConsole Hierarchy.jpg | Bin 39885 -> 0 bytes
.../original/images/JConsole-Hierarchy.jpg | Bin 39885 -> 0 bytes
src/_documents/original/images/JConsoleAMQ.png | Bin 98896 -> 0 bytes
src/_documents/original/images/L.png | Bin 153 -> 0 bytes
src/_documents/original/images/LB_logo.jpg | Bin 20802 -> 0 bytes
src/_documents/original/images/LB_logo_200.jpg | Bin 12524 -> 0 bytes
src/_documents/original/images/LB_logo_200crop.jpg | Bin 20802 -> 0 bytes
src/_documents/original/images/Lminus.png | Bin 219 -> 0 bytes
src/_documents/original/images/Lplus.png | Bin 224 -> 0 bytes
src/_documents/original/images/MasterFailed.png | Bin 22018 -> 0 bytes
src/_documents/original/images/MasterRestarted.png | Bin 23791 -> 0 bytes
.../original/images/NonPersistentMsgs.png | Bin 64717 -> 0 bytes
src/_documents/original/images/Startup.png | Bin 23468 -> 0 bytes
src/_documents/original/images/T.png | Bin 152 -> 0 bytes
src/_documents/original/images/Tminus.png | Bin 207 -> 0 bytes
src/_documents/original/images/Tplus.png | Bin 222 -> 0 bytes
src/_documents/original/images/VMCursor.png | Bin 38472 -> 0 bytes
src/_documents/original/images/about_16.gif | Bin 636 -> 0 bytes
src/_documents/original/images/about_16.png | Bin 809 -> 0 bytes
.../images/activemq-4.1-box-reflection.png | Bin 90694 -> 0 bytes
.../images/activemq-5.x-box-reflection.png | Bin 103078 -> 0 bytes
.../original/images/activemq-in-weblogic.png | Bin 68448 -> 0 bytes
src/_documents/original/images/activemq-jmx.png | Bin 94240 -> 0 bytes
src/_documents/original/images/activemq-logo.png | Bin 10062 -> 0 bytes
src/_documents/original/images/add_16.gif | Bin 360 -> 0 bytes
.../original/images/add_blogentry_16.gif | Bin 385 -> 0 bytes
.../original/images/add_blogentry_32.gif | Bin 835 -> 0 bytes
src/_documents/original/images/add_comment_16.gif | Bin 251 -> 0 bytes
src/_documents/original/images/add_page_16.gif | Bin 259 -> 0 bytes
src/_documents/original/images/add_page_32.gif | Bin 567 -> 0 bytes
.../original/images/add_page_child_16.gif | Bin 253 -> 0 bytes
.../original/images/add_page_faded_16.gif | Bin 186 -> 0 bytes
.../original/images/add_page_notification_16.gif | Bin 255 -> 0 bytes
src/_documents/original/images/add_space_16.gif | Bin 653 -> 0 bytes
src/_documents/original/images/add_space_32.gif | Bin 1567 -> 0 bytes
.../original/images/add_space_notification_16.gif | Bin 651 -> 0 bytes
src/_documents/original/images/addbk_16.gif | Bin 631 -> 0 bytes
src/_documents/original/images/adfav_16.gif | Bin 625 -> 0 bytes
src/_documents/original/images/alarm_16.gif | Bin 672 -> 0 bytes
src/_documents/original/images/amqdir.png | Bin 31506 -> 0 bytes
src/_documents/original/images/amqstore.png | Bin 27104 -> 0 bytes
.../original/images/apache-camel-100h.png | Bin 17175 -> 0 bytes
src/_documents/original/images/apps_16.gif | Bin 1041 -> 0 bytes
src/_documents/original/images/arrow_block.png | Bin 26205 -> 0 bytes
src/_documents/original/images/arrow_block_16.gif | Bin 79 -> 0 bytes
.../original/images/arrow_closed_active_16.gif | Bin 145 -> 0 bytes
.../original/images/arrow_closing_active.png | Bin 27905 -> 0 bytes
.../original/images/arrow_closing_active_16.gif | Bin 298 -> 0 bytes
.../original/images/arrow_open_active_16.gif | Bin 298 -> 0 bytes
.../original/images/arrow_opening_active.png | Bin 27923 -> 0 bytes
.../original/images/arrow_opening_active_16.gif | Bin 298 -> 0 bytes
src/_documents/original/images/asf-logo.png | Bin 10783 -> 0 bytes
src/_documents/original/images/atom.gif | Bin 201 -> 0 bytes
src/_documents/original/images/attach-file.png | Bin 27713 -> 0 bytes
src/_documents/original/images/attach_file_16.gif | Bin 604 -> 0 bytes
.../original/images/attachment-icons.png | Bin 37297 -> 0 bytes
src/_documents/original/images/back_16.gif | Bin 358 -> 0 bytes
src/_documents/original/images/bad.gif | Bin 291 -> 0 bytes
src/_documents/original/images/big-bullet.png | Bin 325 -> 0 bytes
.../original/images/black-footer-bottom.png | Bin 265 -> 0 bytes
.../original/images/black-footer-left.png | Bin 433 -> 0 bytes
.../original/images/black-footer-right.png | Bin 473 -> 0 bytes
src/_documents/original/images/blank.png | Bin 144 -> 0 bytes
src/_documents/original/images/blogentry.png | Bin 29482 -> 0 bytes
src/_documents/original/images/blogentry_16.gif | Bin 268 -> 0 bytes
src/_documents/original/images/blogentry_24.png | Bin 29543 -> 0 bytes
.../original/images/blogentry_add_32.png | Bin 30574 -> 0 bytes
.../original/images/blogentry_faded_16.gif | Bin 197 -> 0 bytes
.../original/images/blogentry_faded_16.png | Bin 29293 -> 0 bytes
src/_documents/original/images/border_bottom.gif | Bin 117 -> 0 bytes
src/_documents/original/images/bottom-red-bar.png | Bin 282 -> 0 bytes
src/_documents/original/images/browse_space.gif | Bin 1072 -> 0 bytes
src/_documents/original/images/bullet_blue.gif | Bin 60 -> 0 bytes
src/_documents/original/images/bullet_creme.gif | Bin 60 -> 0 bytes
src/_documents/original/images/bullet_creme_6.gif | Bin 51 -> 0 bytes
src/_documents/original/images/bullet_done.gif | Bin 59 -> 0 bytes
src/_documents/original/images/bullet_done.png | Bin 26609 -> 0 bytes
.../original/images/bullet_inprogress.gif | Bin 58 -> 0 bytes
.../original/images/bullet_inprogress.png | Bin 26540 -> 0 bytes
src/_documents/original/images/bullet_notdone.gif | Bin 56 -> 0 bytes
src/_documents/original/images/bullet_notdone.png | Bin 26181 -> 0 bytes
src/_documents/original/images/bullet_red.gif | Bin 60 -> 0 bytes
src/_documents/original/images/cal_16.gif | Bin 619 -> 0 bytes
src/_documents/original/images/calc_16.gif | Bin 616 -> 0 bytes
src/_documents/original/images/cancl_16.gif | Bin 643 -> 0 bytes
src/_documents/original/images/cart_16.gif | Bin 370 -> 0 bytes
src/_documents/original/images/cd_16.gif | Bin 1071 -> 0 bytes
src/_documents/original/images/chart_16.gif | Bin 618 -> 0 bytes
src/_documents/original/images/checker-bg.png | Bin 25888 -> 0 bytes
src/_documents/original/images/close_16.gif | Bin 619 -> 0 bytes
src/_documents/original/images/comment-add.png | Bin 28475 -> 0 bytes
src/_documents/original/images/comment-del.png | Bin 28461 -> 0 bytes
src/_documents/original/images/comment.png | Bin 28007 -> 0 bytes
src/_documents/original/images/comment_16.gif | Bin 178 -> 0 bytes
.../original/images/competing-consumers.png | Bin 13627 -> 0 bytes
src/_documents/original/images/confg_16.gif | Bin 378 -> 0 bytes
.../original/images/configure_icon_16.gif | Bin 369 -> 0 bytes
.../original/images/configure_icon_16.png | Bin 27846 -> 0 bytes
src/_documents/original/images/confluence_logo.gif | Bin 454 -> 0 bytes
.../original/images/confluence_logo_darkbg.gif | Bin 364 -> 0 bytes
src/_documents/original/images/content-left.png | Bin 231 -> 0 bytes
src/_documents/original/images/content-right.png | Bin 249 -> 0 bytes
src/_documents/original/images/copy_16.gif | Bin 371 -> 0 bytes
src/_documents/original/images/cut_16.gif | Bin 574 -> 0 bytes
src/_documents/original/images/del_16.gif | Bin 588 -> 0 bytes
.../original/images/del_blogentry_16.gif | Bin 383 -> 0 bytes
src/_documents/original/images/del_comment_16.gif | Bin 251 -> 0 bytes
src/_documents/original/images/del_page_16.gif | Bin 260 -> 0 bytes
.../original/images/del_page_notification_16.gif | Bin 268 -> 0 bytes
src/_documents/original/images/del_space_16.gif | Bin 644 -> 0 bytes
.../original/images/del_space_notification_16.gif | Bin 634 -> 0 bytes
.../original/images/discussion-large.png | Bin 31093 -> 0 bytes
src/_documents/original/images/docs_16.gif | Bin 614 -> 0 bytes
.../original/images/document_attachment.png | Bin 720 -> 0 bytes
.../original/images/document_exchange.gif | Bin 600 -> 0 bytes
.../original/images/document_exchange.png | Bin 803 -> 0 bytes
.../original/images/document_zoom_in_16.gif | Bin 626 -> 0 bytes
.../original/images/document_zoom_in_16.png | Bin 771 -> 0 bytes
src/_documents/original/images/down_16.gif | Bin 365 -> 0 bytes
src/_documents/original/images/dummy.gif | Bin 24354 -> 0 bytes
src/_documents/original/images/edit_16.gif | Bin 214 -> 0 bytes
src/_documents/original/images/edit_16.png | Bin 26918 -> 0 bytes
.../original/images/edit_blogentry_16.gif | Bin 391 -> 0 bytes
src/_documents/original/images/edit_only_16.gif | Bin 214 -> 0 bytes
src/_documents/original/images/edit_only_16.png | Bin 27217 -> 0 bytes
src/_documents/original/images/edit_space_16.gif | Bin 654 -> 0 bytes
src/_documents/original/images/en_UK.gif | Bin 2320 -> 0 bytes
src/_documents/original/images/encodingtest.jpg | Bin 4527 -> 0 bytes
src/_documents/original/images/exp_16.gif | Bin 224 -> 0 bytes
src/_documents/original/images/exp_32.gif | Bin 749 -> 0 bytes
src/_documents/original/images/failoverclient.png | Bin 47626 -> 0 bytes
src/_documents/original/images/fastf_16.gif | Bin 345 -> 0 bytes
src/_documents/original/images/favicon.png | Bin 391 -> 0 bytes
src/_documents/original/images/favs_16.gif | Bin 599 -> 0 bytes
src/_documents/original/images/fax_16.gif | Bin 609 -> 0 bytes
src/_documents/original/images/feed-icon-10x10.png | Bin 469 -> 0 bytes
src/_documents/original/images/feed-icon-12x12.png | Bin 552 -> 0 bytes
src/_documents/original/images/feed-icon-16x16.png | Bin 764 -> 0 bytes
src/_documents/original/images/feed-icon-24x24.png | Bin 1090 -> 0 bytes
src/_documents/original/images/feed-icon-32x32.png | Bin 1441 -> 0 bytes
src/_documents/original/images/feed_wizard.gif | Bin 787 -> 0 bytes
src/_documents/original/images/file.png | Bin 251 -> 0 bytes
src/_documents/original/images/flag_16.gif | Bin 1023 -> 0 bytes
src/_documents/original/images/foldericon.png | Bin 229 -> 0 bytes
src/_documents/original/images/foldr_16.gif | Bin 612 -> 0 bytes
src/_documents/original/images/forwd_16.gif | Bin 355 -> 0 bytes
src/_documents/original/images/forwd_24.png | Bin 754 -> 0 bytes
src/_documents/original/images/games_16.gif | Bin 397 -> 0 bytes
src/_documents/original/images/go_16.gif | Bin 607 -> 0 bytes
src/_documents/original/images/good.gif | Bin 289 -> 0 bytes
src/_documents/original/images/group-anyone.png | Bin 27455 -> 0 bytes
src/_documents/original/images/group_16.gif | Bin 1013 -> 0 bytes
src/_documents/original/images/group_anyone_16.gif | Bin 271 -> 0 bytes
src/_documents/original/images/hd_16.gif | Bin 617 -> 0 bytes
src/_documents/original/images/help.png | Bin 67792 -> 0 bytes
src/_documents/original/images/help_16.gif | Bin 634 -> 0 bytes
src/_documents/original/images/help_24.gif | Bin 840 -> 0 bytes
src/_documents/original/images/help_24.png | Bin 1615 -> 0 bytes
src/_documents/original/images/hermes.png | Bin 671906 -> 0 bytes
src/_documents/original/images/hist_16.gif | Bin 616 -> 0 bytes
src/_documents/original/images/history_16.gif | Bin 264 -> 0 bytes
src/_documents/original/images/history_arrow.png | Bin 26366 -> 0 bytes
src/_documents/original/images/home_16.gif | Bin 594 -> 0 bytes
src/_documents/original/images/home_16_faded.png | Bin 26965 -> 0 bytes
src/_documents/original/images/home_faded_16.gif | Bin 159 -> 0 bytes
src/_documents/original/images/image_16.gif | Bin 1042 -> 0 bytes
src/_documents/original/images/import_mbox_16.gif | Bin 381 -> 0 bytes
src/_documents/original/images/import_mbox_16.png | Bin 29436 -> 0 bytes
src/_documents/original/images/impt_16.gif | Bin 225 -> 0 bytes
src/_documents/original/images/label_16.gif | Bin 221 -> 0 bytes
.../original/images/layout_northwest.gif | Bin 204 -> 0 bytes
.../original/images/layout_northwest.png | Bin 354 -> 0 bytes
src/_documents/original/images/left-box-bottom.png | Bin 430 -> 0 bytes
src/_documents/original/images/left-box-right.png | Bin 248 -> 0 bytes
src/_documents/original/images/left-box-top.png | Bin 376 -> 0 bytes
src/_documents/original/images/left-nav-theme.gif | Bin 953 -> 0 bytes
src/_documents/original/images/left-nav-theme.png | Bin 33911 -> 0 bytes
src/_documents/original/images/lgicn_16.gif | Bin 610 -> 0 bytes
src/_documents/original/images/link-attachment.png | Bin 26466 -> 0 bytes
src/_documents/original/images/link-external.png | Bin 26257 -> 0 bytes
src/_documents/original/images/link_16.gif | Bin 355 -> 0 bytes
.../original/images/link_attachment_7.gif | Bin 163 -> 0 bytes
src/_documents/original/images/link_in_bot.gif | Bin 62 -> 0 bytes
src/_documents/original/images/link_in_mid.gif | Bin 64 -> 0 bytes
src/_documents/original/images/link_in_only.gif | Bin 64 -> 0 bytes
src/_documents/original/images/link_in_top.gif | Bin 67 -> 0 bytes
src/_documents/original/images/link_out_bot.gif | Bin 65 -> 0 bytes
src/_documents/original/images/link_out_mid.gif | Bin 67 -> 0 bytes
src/_documents/original/images/link_out_top.gif | Bin 67 -> 0 bytes
src/_documents/original/images/linkext7.gif | Bin 166 -> 0 bytes
.../original/images/list-pages-large.png | Bin 27920 -> 0 bytes
src/_documents/original/images/list-pages.png | Bin 26796 -> 0 bytes
.../original/images/list-pages_faded_16.png | Bin 26871 -> 0 bytes
.../original/images/list_blogentries_32.gif | Bin 630 -> 0 bytes
.../original/images/list_blogentries_32.png | Bin 30542 -> 0 bytes
.../original/images/list_blogposts_32.gif | Bin 630 -> 0 bytes
.../original/images/list_less_pages_16.gif | Bin 236 -> 0 bytes
.../original/images/list_less_pages_16.png | Bin 26786 -> 0 bytes
src/_documents/original/images/list_mail_16.png | Bin 27598 -> 0 bytes
src/_documents/original/images/list_mail_32.gif | Bin 391 -> 0 bytes
src/_documents/original/images/list_mail_32.png | Bin 30372 -> 0 bytes
.../original/images/list_mail_content_16.gif | Bin 165 -> 0 bytes
.../original/images/list_mail_faded_16.gif | Bin 173 -> 0 bytes
.../original/images/list_mail_faded_16.png | Bin 27767 -> 0 bytes
src/_documents/original/images/list_pages_16.gif | Bin 240 -> 0 bytes
src/_documents/original/images/list_pages_32.gif | Bin 456 -> 0 bytes
.../original/images/list_pages_faded_16.gif | Bin 260 -> 0 bytes
src/_documents/original/images/lock_16.gif | Bin 582 -> 0 bytes
src/_documents/original/images/locked-pages_16.png | Bin 28210 -> 0 bytes
src/_documents/original/images/locked_pages_16.gif | Bin 598 -> 0 bytes
src/_documents/original/images/logo.gif | Bin 1317 -> 0 bytes
src/_documents/original/images/logo.jpg | Bin 12398 -> 0 bytes
src/_documents/original/images/logo2.gif | Bin 1182 -> 0 bytes
src/_documents/original/images/logo_add_16.gif | Bin 1008 -> 0 bytes
.../original/images/logo_jprofiler01.gif | Bin 2520 -> 0 bytes
src/_documents/original/images/mail.png | Bin 1912 -> 0 bytes
src/_documents/original/images/mail_16.gif | Bin 381 -> 0 bytes
src/_documents/original/images/mail_16.png | Bin 28853 -> 0 bytes
src/_documents/original/images/mail_content_16.gif | Bin 250 -> 0 bytes
src/_documents/original/images/mail_delete.png | Bin 2161 -> 0 bytes
src/_documents/original/images/mail_small.gif | Bin 202 -> 0 bytes
src/_documents/original/images/mail_small.png | Bin 26504 -> 0 bytes
src/_documents/original/images/mail_thread_16.gif | Bin 235 -> 0 bytes
src/_documents/original/images/mail_thread_16.png | Bin 28085 -> 0 bytes
src/_documents/original/images/main-theme.gif | Bin 810 -> 0 bytes
src/_documents/original/images/main-theme.png | Bin 31497 -> 0 bytes
src/_documents/original/images/message-flow.png | Bin 30950 -> 0 bytes
.../original/images/module-deps-graph.png | Bin 8278 -> 0 bytes
src/_documents/original/images/move_16.gif | Bin 352 -> 0 bytes
src/_documents/original/images/music_16.gif | Bin 610 -> 0 bytes
src/_documents/original/images/nav_down.gif | Bin 591 -> 0 bytes
src/_documents/original/images/nav_up.gif | Bin 574 -> 0 bytes
src/_documents/original/images/new.png | Bin 251 -> 0 bytes
src/_documents/original/images/new_16.gif | Bin 597 -> 0 bytes
src/_documents/original/images/news.gif | Bin 452 -> 0 bytes
src/_documents/original/images/no-icon.gif | Bin 1333 -> 0 bytes
src/_documents/original/images/notep_16.gif | Bin 373 -> 0 bytes
src/_documents/original/images/ntwrk_16.gif | Bin 391 -> 0 bytes
src/_documents/original/images/open-active.png | Bin 26688 -> 0 bytes
src/_documents/original/images/open_16.gif | Bin 607 -> 0 bytes
src/_documents/original/images/openfoldericon.png | Bin 232 -> 0 bytes
src/_documents/original/images/opnbr_16.gif | Bin 626 -> 0 bytes
src/_documents/original/images/opts_16.gif | Bin 603 -> 0 bytes
src/_documents/original/images/oval-arrow.png | Bin 3878 -> 0 bytes
src/_documents/original/images/page-add-child.png | Bin 27532 -> 0 bytes
src/_documents/original/images/page-add-large.png | Bin 28945 -> 0 bytes
src/_documents/original/images/page-add.png | Bin 27294 -> 0 bytes
.../original/images/page-add_faded_16.png | Bin 27255 -> 0 bytes
src/_documents/original/images/page-del.png | Bin 27470 -> 0 bytes
.../original/images/page-hierarchy-large.png | Bin 28284 -> 0 bytes
src/_documents/original/images/page-hierarchy.png | Bin 27251 -> 0 bytes
src/_documents/original/images/page-history.png | Bin 27470 -> 0 bytes
.../original/images/page-notification.png | Bin 27503 -> 0 bytes
.../original/images/page_hierarchy_16.gif | Bin 232 -> 0 bytes
src/_documents/original/images/paint_16.gif | Bin 615 -> 0 bytes
src/_documents/original/images/paste_16.gif | Bin 617 -> 0 bytes
src/_documents/original/images/pause_16.gif | Bin 218 -> 0 bytes
src/_documents/original/images/phone_16.gif | Bin 612 -> 0 bytes
src/_documents/original/images/photo_scenery.gif | Bin 614 -> 0 bytes
src/_documents/original/images/picts_16.gif | Bin 603 -> 0 bytes
src/_documents/original/images/play_16.gif | Bin 312 -> 0 bytes
src/_documents/original/images/plus.gif | Bin 109 -> 0 bytes
src/_documents/original/images/plus_sign.png | Bin 26077 -> 0 bytes
src/_documents/original/images/prefs_16.gif | Bin 614 -> 0 bytes
src/_documents/original/images/print_16.gif | Bin 372 -> 0 bytes
.../original/images/project-logo-vector.png | Bin 58826 -> 0 bytes
src/_documents/original/images/project-logo.png | Bin 1750 -> 0 bytes
src/_documents/original/images/prtpv_16.gif | Bin 347 -> 0 bytes
src/_documents/original/images/redo_116.gif | Bin 562 -> 0 bytes
src/_documents/original/images/ref_16.gif | Bin 589 -> 0 bytes
src/_documents/original/images/refresh_16.png | Bin 947 -> 0 bytes
src/_documents/original/images/refresh_24.png | Bin 1619 -> 0 bytes
.../original/images/reloadLog4jProperties1.png | Bin 101552 -> 0 bytes
.../original/images/reloadLog4jProperties2.png | Bin 117137 -> 0 bytes
src/_documents/original/images/remov_16.gif | Bin 627 -> 0 bytes
.../original/images/replicated-leveldb-store.png | Bin 25637 -> 0 bytes
src/_documents/original/images/rewnd_16.gif | Bin 346 -> 0 bytes
.../original/images/right-box-bottom.png | Bin 390 -> 0 bytes
src/_documents/original/images/right-box-left.png | Bin 248 -> 0 bytes
src/_documents/original/images/right-box-top.png | Bin 415 -> 0 bytes
src/_documents/original/images/rss.gif | Bin 1166 -> 0 bytes
src/_documents/original/images/rss.png | Bin 26444 -> 0 bytes
src/_documents/original/images/rss10.gif | Bin 187 -> 0 bytes
src/_documents/original/images/rss20.gif | Bin 189 -> 0 bytes
src/_documents/original/images/rss_32.gif | Bin 157 -> 0 bytes
src/_documents/original/images/rss_32.png | Bin 27281 -> 0 bytes
.../original/images/run_test_fail_16.gif | Bin 306 -> 0 bytes
.../original/images/run_test_pass_16.gif | Bin 307 -> 0 bytes
src/_documents/original/images/savas_16.gif | Bin 639 -> 0 bytes
src/_documents/original/images/save_16.gif | Bin 625 -> 0 bytes
src/_documents/original/images/sinfo_16.gif | Bin 612 -> 0 bytes
src/_documents/original/images/skipb_16.gif | Bin 561 -> 0 bytes
src/_documents/original/images/skipf_16.gif | Bin 559 -> 0 bytes
.../original/images/small-bullet-gray.png | Bin 215 -> 0 bytes
.../original/images/small-bullet-red.png | Bin 215 -> 0 bytes
src/_documents/original/images/smicn_16.gif | Bin 596 -> 0 bytes
src/_documents/original/images/space-add-large.png | Bin 32246 -> 0 bytes
src/_documents/original/images/space-add.png | Bin 28131 -> 0 bytes
src/_documents/original/images/space-del.png | Bin 28161 -> 0 bytes
src/_documents/original/images/space-edit.png | Bin 28238 -> 0 bytes
.../original/images/space-notification.png | Bin 29072 -> 0 bytes
src/_documents/original/images/spacer.gif | Bin 43 -> 0 bytes
src/_documents/original/images/splay_16.gif | Bin 211 -> 0 bytes
src/_documents/original/images/srch_16.gif | Bin 349 -> 0 bytes
src/_documents/original/images/star_grey.gif | Bin 925 -> 0 bytes
src/_documents/original/images/star_yellow.gif | Bin 567 -> 0 bytes
src/_documents/original/images/step1.png | Bin 25221 -> 0 bytes
src/_documents/original/images/step2.png | Bin 24842 -> 0 bytes
src/_documents/original/images/step3.png | Bin 22593 -> 0 bytes
src/_documents/original/images/step4.png | Bin 22862 -> 0 bytes
src/_documents/original/images/step5.png | Bin 18364 -> 0 bytes
src/_documents/original/images/step6-new.png | Bin 124142 -> 0 bytes
src/_documents/original/images/step6.png | Bin 114091 -> 0 bytes
src/_documents/original/images/step7-new.png | Bin 103068 -> 0 bytes
src/_documents/original/images/step7.png | Bin 95494 -> 0 bytes
src/_documents/original/images/step8.png | Bin 21797 -> 0 bytes
src/_documents/original/images/stop_16.gif | Bin 617 -> 0 bytes
src/_documents/original/images/subtract_16.gif | Bin 298 -> 0 bytes
src/_documents/original/images/test-ran-green.png | Bin 26832 -> 0 bytes
src/_documents/original/images/test-ran-red.png | Bin 26834 -> 0 bytes
src/_documents/original/images/test.png | Bin 7150 -> 0 bytes
src/_documents/original/images/text_abc.gif | Bin 1895 -> 0 bytes
src/_documents/original/images/text_abc_16.gif | Bin 1030 -> 0 bytes
src/_documents/original/images/text_bold.gif | Bin 396 -> 0 bytes
src/_documents/original/images/text_bold_16.png | Bin 570 -> 0 bytes
src/_documents/original/images/text_italics.gif | Bin 396 -> 0 bytes
src/_documents/original/images/text_tree.png | Bin 1431 -> 0 bytes
src/_documents/original/images/text_tree_16.png | Bin 546 -> 0 bytes
src/_documents/original/images/text_underlined.gif | Bin 399 -> 0 bytes
src/_documents/original/images/text_view.png | Bin 2830 -> 0 bytes
src/_documents/original/images/text_view_16.png | Bin 753 -> 0 bytes
src/_documents/original/images/thread.png | Bin 756 -> 0 bytes
src/_documents/original/images/tools_16.gif | Bin 373 -> 0 bytes
src/_documents/original/images/top-red-bar.png | Bin 233 -> 0 bytes
.../original/images/trafficlight_green_16.png | Bin 633 -> 0 bytes
.../original/images/trafficlight_green_24.png | Bin 1016 -> 0 bytes
.../original/images/trafficlight_red_16.png | Bin 616 -> 0 bytes
.../original/images/trafficlight_red_24.png | Bin 979 -> 0 bytes
src/_documents/original/images/trash_16.gif | Bin 374 -> 0 bytes
src/_documents/original/images/tree_minus.gif | Bin 273 -> 0 bytes
src/_documents/original/images/tree_plus.gif | Bin 274 -> 0 bytes
src/_documents/original/images/tree_square.gif | Bin 179 -> 0 bytes
src/_documents/original/images/tree_square.png | Bin 26586 -> 0 bytes
src/_documents/original/images/uat-test-theme.png | Bin 31694 -> 0 bytes
src/_documents/original/images/ulock_16.gif | Bin 581 -> 0 bytes
src/_documents/original/images/undo_16.gif | Bin 563 -> 0 bytes
src/_documents/original/images/up_16.gif | Bin 345 -> 0 bytes
src/_documents/original/images/user_12.gif | Bin 528 -> 0 bytes
src/_documents/original/images/user_16.gif | Bin 1008 -> 0 bytes
src/_documents/original/images/user_bw_16.gif | Bin 1002 -> 0 bytes
src/_documents/original/images/user_small.png | Bin 27653 -> 0 bytes
src/_documents/original/images/wait.gif | Bin 1553 -> 0 bytes
src/_documents/original/images/watch-large.png | Bin 31935 -> 0 bytes
src/_documents/original/images/watch_16.gif | Bin 655 -> 0 bytes
src/_documents/original/images/watch_16.png | Bin 27871 -> 0 bytes
src/_documents/original/images/watch_32.gif | Bin 357 -> 0 bytes
src/_documents/original/images/watch_cancel_16.gif | Bin 660 -> 0 bytes
src/_documents/original/images/watch_cancel_32.gif | Bin 833 -> 0 bytes
src/_documents/original/images/web-console.png | Bin 486762 -> 0 bytes
src/_documents/original/images/web_16.gif | Bin 1068 -> 0 bytes
src/_documents/original/images/web_console.png | Bin 486762 -> 0 bytes
src/_documents/original/images/web_faded_16.gif | Bin 422 -> 0 bytes
src/_documents/original/images/web_faded_16.png | Bin 27959 -> 0 bytes
.../original/images/white-header-left.png | Bin 317 -> 0 bytes
.../original/images/white-header-right.png | Bin 362 -> 0 bytes
.../original/images/white-header-top.png | Bin 248 -> 0 bytes
src/_documents/original/images/wiz_16.gif | Bin 588 -> 0 bytes
src/_documents/original/images/yklogo.png | Bin 5554 -> 0 bytes
src/_documents/original/images/yourkit.jpg | Bin 2839 -> 0 bytes
src/_documents/original/images/zoomi_16.gif | Bin 385 -> 0 bytes
src/_documents/original/images/zoomo_16.gif | Bin 371 -> 0 bytes
src/_documents/original/management-api.md | 900 ----
src/_documents/original/migration-guide.md | 45 -
src/_documents/original/migration.md | 22 -
src/_documents/original/module-organization.md | 28 -
src/_documents/original/mqtt-manual.md | 168 -
src/_documents/original/notice.md | 34 -
src/_documents/original/openwire-manual.md | 236 -
.../original/osgi-support-in-development.md | 114 -
src/_documents/original/overview.md | 74 -
src/_documents/original/past-releases.md | 492 --
src/_documents/original/performance-scaling.md | 34 -
src/_documents/original/previous-docs.md | 147 -
src/_documents/original/release-1.0.md | 51 -
src/_documents/original/release-1.1.md | 23 -
src/_documents/original/release-1.2.md | 30 -
src/_documents/original/release-1.3.md | 25 -
src/_documents/original/release-1.4.md | 21 -
src/_documents/original/release-1.5.md | 35 -
src/_documents/original/release-1.6.md | 28 -
src/_documents/original/release-1.7.md | 44 -
src/_documents/original/release-notes-1.1.0.md | 41 -
src/_documents/original/release-notes-1.2.0.md | 17 -
src/_documents/original/release-notes-1.3.0.md | 23 -
src/_documents/original/release-notes-1.4.0.md | 24 -
src/_documents/original/release-notes-1.5.0.md | 24 -
src/_documents/original/release-notes-1.5.1.md | 39 -
src/_documents/original/release-notes-1.5.2.md | 42 -
src/_documents/original/release-notes-1.5.3.md | 36 -
src/_documents/original/release-notes-1.5.4.md | 52 -
src/_documents/original/release-notes-1.5.5.md | 39 -
src/_documents/original/release-notes-2.0.0.md | 168 -
src/_documents/original/release-notes-2.1.0.md | 146 -
src/_documents/original/release-notes-2.2.0.md | 132 -
src/_documents/original/release-notes-2.3.0.md | 91 -
src/_documents/original/release-notes-2.4.0.md | 115 -
src/_documents/original/site.md | 11 -
src/_documents/original/ssl.md | 79 -
src/_documents/original/stomp-manual.md | 496 --
src/_documents/original/the-jms-connector.md | 7 -
src/_documents/original/tools.md | 11 -
src/_documents/original/user-manual.md | 863 ----
src/_documents/original/using-activemq-4.md | 59 -
src/_documents/original/using-activemq-5.md | 28 -
src/_documents/original/using-activemq.md | 59 -
src/_documents/original/verification.md | 57 -
2345 files changed, 145129 deletions(-)
diff --git a/src/_documents/README.md b/src/_documents/README.md
deleted file mode 100644
index f8a6c96..0000000
--- a/src/_documents/README.md
+++ /dev/null
@@ -1,30 +0,0 @@
-
-## ActiveMQ GitBook Documents.
-
-Install Node
-
-Install GitBook CLI:
-
-```npm install gitbook-cli -g```
-
-
-To Run Locally
-
-```
-cd ./docs
-gitbook serve ./classic
-gitbook serve ./nms
-```
-
-To Generate Static
-
-```
-cd ./docs
-gitbook build ./classic ../gitbook/classic/documents
-gitbook build ./nms ../gitbook/nms/documents
-
-```
-
-
-
-
\ No newline at end of file
diff --git a/src/_documents/classic/Connectivity/Containers/JBoss Integration/inbound-communication.md b/src/_documents/classic/Connectivity/Containers/JBoss Integration/inbound-communication.md
deleted file mode 100644
index 24f7725..0000000
--- a/src/_documents/classic/Connectivity/Containers/JBoss Integration/inbound-communication.md
+++ /dev/null
@@ -1,107 +0,0 @@
-Apache ActiveMQ ™ -- Inbound Communication
-
-[Connectivity](../../../connectivity.md) > [Containers](../../../Connectivity/containers.md) > [JBoss Integration](../../../Connectivity/Containers/jboss-integration.md) > [Inbound Communication](../../../Connectivity/Containers/JBoss Integration/inbound-communication.md)
-
-
-Configuring an MDB to receive messages from ActiveMQ
-----------------------------------------------------
-
-There are three MDBs declared in the [ejb-jar.xml](inbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2) deployment descriptor. For this example, I will be explaining how to configure the `TopicDurableMDB` to be invoked by JBoss when a message is received on an ActiveMQ Topic.
-
-### The Bean
-
-In the [ejb-jar.xml](inbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2) deployment descriptor, the `TopicDurableMDB` is declared as follows:
-
-**ejb-jar.xml**
-
-
-<message-driven>
- ...
- <ejb-name>TopicDurableMDB</ejb-name>
- <ejb-class>com.panacya.platform.service.bus.mdb.SimpleMessageReceiverBean</ejb-class>
- <messaging-type>javax.jms.MessageListener</messaging-type>
- ...
- <activation-config>
- <activation-config-property>
- <activation-config-property-name>Destination</activation-config-property-name>
- <activation-config-property-value>topic.testTopic</activation-config-property-value>
- </activation-config-property>
- <activation-config-property>
- <activation-config-property-name>DestinationType</activation-config-property-name>
- <activation-config-property-value>javax.jms.Topic</activation-config-property-value>
- </activation-config-property>
- ...
- </activation-config>
- ...
-</message-driven>
-
-The `activation-config` element and it's child element, `activation-config-property`, are new elements for EJBs, so you might not be familiar with them. I won't go into to much detail about them, but it is important to understand that this is the first mechanism you use to link an MDB to a JCA.
-
-### The Connector
-
-The two `activation-config-properties` shown above link to the following elements in the [ra.xml](http://activemq.codehaus.org/checkout/activemq/modules/ra/src/rar/META-INF/ra.xml) file, which is contained within the [activemq-ra-1.2.rar](../../../Connectivity/Containers/jboss-integration.md) file:
-
-**ra.xml**
-
-<inbound-resourceadapter>
- ...
- <activationspec>
- <activationspec-class>org.activemq.ra.ActiveMQActivationSpec</activationspec-class>
- <required-config-property>
- <config-property-name>Destination</config-property-name>
- </required-config-property>
- <required-config-property>
- <config-property-name>DestinationType</config-property-name>
- </required-config-property>
- </activationspec>
- ...
-</inbound-resourceadapter>
-
-In the [ejb-jar.xml](inbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2) file section shown above, the value of the `Destination` property is set to `topic.testTopic`. This value is the physical name of the ActiveMQ destination the `TopicDurableMDB` will be receiving messages from and not a JNDI name. In other words, the value of the `Destination` property has no meaning to JBoss. It is purely an ActiveMQ setting.
-
-### The Glue
-
-In JBoss, the thing which connects an inbound JMS destination to an MDB is a JBoss container. To use ActiveMQ as the inbound message source for the `TopicDurableMDB` we must configure a new JBoss container. We do this in the [jboss.xml](inbound-communication.data/jboss.xml?version=3&modificationDate=1117021488000&api=v2) file.
-
-Three things are needed in the [jboss.xml](inbound-communication.data/jboss.xml?version=3&modificationDate=1117021488000&api=v2) file in order to tie an MDB to a connector. They are:
-
-1. Configure a new `invoker-proxy-binding` that declares `JBossMessageEndpointFactory` as the `proxy-factory`
-2. Configure a new MDB container which uses the new `invoker-proxy-binding`
-3. Declare which MDBs should go into the new container
-
-This first snippet configures a new `invoker-proxy-binding`:
-
-**jboss.xml – invoker-proxy-binding**
-
-<invoker-proxy-binding>
- <name>activemq-message-driven-bean</name>
- <invoker-mbean>default</invoker-mbean>
- <proxy-factory>org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory</proxy-factory>
- ...
-</invoker-proxy-binding>
-
-This second snippet configures a new MDB container which uses the `invoker-proxy-binding` configured above:
-
-**jboss.xml – container-configuration**
-
-<container-configuration>
- <container-name>ActiveMQ Message Driven Bean</container-name>
- <call-logging>false</call-logging>
- <invoker-proxy-binding-name>activemq-message-driven-bean</invoker-proxy-binding-name>
- ...
-</container-configuration>
-
-This third snippet links the `TopicDurableMDB` to the [activemq-ra-1.2.rar](../../../Connectivity/Containers/jboss-integration.md) connector and tells JBoss to put instances of `TopicDurableMDB` into the new MDB container declared above:
-
-**jboss.xml – TopicDurableMDB**
-
-<message-driven>
- <ejb-name>TopicDurableMDB</ejb-name>
- <resource-adapter-name>activemq-ra-1.2-SNAPSHOT.rar</resource-adapter-name>
- <configuration-name>ActiveMQ Message Driven Bean</configuration-name>
-</message-driven>
-
-The above examples highlight the key configuration settings needed to enable MDBs deployed in JBoss to process messages from an ActiveMQ destination.
-
-You can try the above example, plus a few more, by downloading the [activemq-jboss-test.zip](inbound-communication.data/activemq-jboss-test.zip?version=3&modificationDate=1117021355000&api=v2) file which contains the complete sample project.
-
diff --git a/src/_documents/classic/Connectivity/Containers/JBoss Integration/outbound-communication.md b/src/_documents/classic/Connectivity/Containers/JBoss Integration/outbound-communication.md
deleted file mode 100644
index ba7c944..0000000
--- a/src/_documents/classic/Connectivity/Containers/JBoss Integration/outbound-communication.md
+++ /dev/null
@@ -1,168 +0,0 @@
-Apache ActiveMQ ™ -- Outbound Communication
-
-[Connectivity](../../../connectivity.md) > [Containers](../../../Connectivity/containers.md) > [JBoss Integration](../../../Connectivity/Containers/jboss-integration.md) > [Outbound Communication](../../../Connectivity/Containers/JBoss Integration/outbound-communication.md)
-
-
-Configuring a Session Bean to send messages to ActiveMQ
--------------------------------------------------------
-
-In the attached [example application](outbound-communication.data/activemq-jboss-test.zip?version=3&modificationDate=1117021355000&api=v2), the three MDBs use the `SenderEJB` to send JMS messages to an ActiveMQ queue. In this example, I will be explaining how to:
-
-1. Configure and deploy an ActiveMQ `Queue` to JBoss
-2. Configure and deploy an ActiveMQ `QueueConnectionFactory` to JBoss
-3. Configure an EJB, deployed to JBoss, to reference the above two.
-
-### The Bean
-
-In the [ejb-jar.xml](outbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2) deployment descriptor, the `SenderEJB` is declared as follows:
-
-**ejb-jar.xml – session bean declaration**
-
-
-<session>
- ...
- <ejb-name>SenderEJB</ejb-name>
- ...
- <ejb-class>com.panacya.platform.service.bus.sender.SenderBean</ejb-class>
- ...
- <resource-ref>
- <res-ref-name>jms/MyQueueConnectionFactory</res-ref-name>
- <res-type>javax.jms.QueueConnectionFactory</res-type>
- ...
- </resource-ref>
- <message-destination-ref>
- <message-destination-ref-name>jms/LogQueue</message-destination-ref-name>
- <message-destination-type>javax.jms.Queue</message-destination-type>
- ...
- <message-destination-link>LoggingQueue</message-destination-link>
- </message-destination-ref>
-</session>
-
-The `jms/MyQueueConnectionFactory` is the JNDI name the `SenderEJB` will use to lookup a `javax.jms.QueueConnectionFactory`. We will configure it to point to an ActiveMQ `QueueConnectionFactory`.
-
-The `jms/LogQueue` is the JNDI name the `SenderEJB` will use to lookup the `javax.jms.Queue` it will send messages to. We use the `message-destination-link` element to refer to the `LoggingQueue` which is declared in the `assembly-descriptor` section of the [ejb-jar.xml](outbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2) deployment descriptor as:
-
-**ejb-jar.xml – assembly descriptor section**
-
-
-<assembly-descriptor>
- ...
- <message-destination>
- <message-destination-name>LoggingQueue</message-destination-name>
- </message-destination>
- ...
-</assembly-descriptor>
-
-This is a standard EJB deployment descriptor, nothing special.
-
-### The Connector
-
-The `resource-ref` element [shown above](../../../Connectivity/Containers/JBoss Integration/outbound-communication.md), will be linked to the following element in the [ra.xml](http://activemq.codehaus.org/checkout/activemq/modules/ra/src/rar/META-INF/ra.xml) file, which is contained within the [activemq-ra-1.2.rar](../../../Connectivity/Containers/jboss-integration.md) file:
-
-**ra.xml – The QueueConnectionFactory**
-
-<outbound-resourceadapter>
- ...
- <connection-definition>
- ...
- <connectionfactory-interface>javax.jms.QueueConnectionFactory</connectionfactory-interface>
- <connectionfactory-impl-class>org.activemq.ra.ActiveMQConnectionFactory</connectionfactory-impl-class>
- <connection-interface>javax.jms.QueueConnection</connection-interface>
- ...
- </connection-definition>
- ...
-</outbound-resourceadapter>
-
-The `message-destination` element [shown above](../../../Connectivity/Containers/JBoss Integration/outbound-communication.md), will be linked to the following element in the [ra.xml](http://activemq.codehaus.org/checkout/activemq/modules/ra/src/rar/META-INF/ra.xml) file:
-
-**ra.xml – The Queue**
-
-<adminobject>
- <adminobject-interface>javax.jms.Queue</adminobject-interface>
- <adminobject-class>org.activemq.message.ActiveMQQueue</adminobject-class>
- <config-property>
- <config-property-name>PhysicalName</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- </config-property>
-</adminobject>
-
-### The Glue
-
-In JBoss, connecting the resources needed by the [ejb-jar.xml](outbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2) file to resources provided by the [ra.xml](http://activemq.codehaus.org/checkout/activemq/modules/ra/src/rar/META-INF/ra.xml) file involves two additional files:
-
-1. **[panacya-jms-ds.xml](outbound-communication.data/panacya-jms-ds.xml?version=5&modificationDate=1117021448000&api=v2)** \- This is a JBoss data source file. It specifies which connector objects JBoss should instantiate and where in JNDI JBoss should place those objects.
-2. **[jboss.xml](outbound-communication.data/jboss.xml?version=3&modificationDate=1117021488000&api=v2)** \- This is a JBoss deployment descriptor which is contained within the [panacya-mdb-test-1.0.jar](../../../Connectivity/Containers/jboss-integration.md) file. It links resources needed by the EJBs to the JNDI names of resources available in JBoss.
-
-##### [panacya-jms-ds.xml](outbound-communication.data/panacya-jms-ds.xml?version=5&modificationDate=1117021448000&api=v2) – _The JBoss Data Source File_
-
-This first snippet configures the `QueueConnectionFactory`, [declared above](../../../Connectivity/Containers/JBoss Integration/outbound-communication.md), and places it in JNDI at `activemq/QueueConnectionFactory`:
-
-**panacya-jms-ds.xml – The QueueConnectionFactory**
-
-<tx-connection-factory>
- <jndi-name>activemq/QueueConnectionFactory</jndi-name>
- <xa-transaction/>
- <rar-name>activemq-ra-1.2-SNAPSHOT.rar</rar-name>
- <connection-definition>javax.jms.QueueConnectionFactory</connection-definition>
- <security-domain-and-application>JmsXARealm</security-domain-and-application>
-</tx-connection-factory>
-
-This second snippet configures the `Queue`, [declared above](../../../Connectivity/Containers/JBoss Integration/outbound-communication.md), and places it in JNDI at `activemq/queue/outbound`:
-
-**panacya-jms-ds.xml – The Queue**
-
-<mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.queue:name=outboundQueue">
- <attribute name="JNDIName">activemq/queue/outbound</attribute>
- <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra-1.2-SNAPSHOT.rar'</depends>
- <attribute name="Type">javax.jms.Queue</attribute>
- <attribute name="Properties">
- PhysicalName=queue.outbound
- </attribute>
-</mbean>
-
-In the [panacya-jms-ds.xml](outbound-communication.data/panacya-jms-ds.xml?version=5&modificationDate=1117021448000&api=v2) file section shown above, the value of the `Properties` element is set to `PhysicalName=queue.outbound`. This value is the physical name of the ActiveMQ destination the `SenderEJB` will be sending messages to and not a JNDI name. In other words, the value of the `PhysicalName` property has no meaning to JBoss. It is purely an ActiveMQ setting.
-
-##### [jboss.xml](outbound-communication.data/jboss.xml?version=3&modificationDate=1117021488000&api=v2) – _The JBoss Deployment Descriptor_
-
-This first snippet links the `[jms/MyQueueConnectionFactory](../../../Connectivity/Containers/JBoss Integration/outbound-communication.md)` JNDI name used by the `SenderEJB` to the resource name `queuefactoryref` which is local to the [jboss.xml](outbound-communication.data/jboss.xml?version=3&modificationDate=1117021488000&api=v2) file:
-
-**jboss.xml – The QueueConnectionFactory for the SenderEJB**
-
-<enterprise-beans>
- <session>
- <ejb-name>SenderEJB</ejb-name>
- <resource-ref>
- <res-ref-name>jms/MyQueueConnectionFactory</res-ref-name>
- <resource-name>queuefactoryref</resource-name>
- </resource-ref>
- </session>
- ...
-</enterprise-beans>
-
-This second snippet links the local `queuefactoryref` name to the global JNDI name `java:/activemq/QueueConnectionFactory` which was [declared above](../../../Connectivity/Containers/JBoss Integration/outbound-communication.md):
-
-**jboss.xml – Linking queuefactoryref to the global JNDI namespace**
-
-<resource-managers>
- <resource-manager>
- <res-name>queuefactoryref</res-name>
- <res-jndi-name>java:/activemq/QueueConnectionFactory</res-jndi-name>
- </resource-manager>
- ...
-</resource-managers>
-
-This third snippet links the `LoggingQueue`, which was [declared](../../../Connectivity/Containers/JBoss Integration/outbound-communication.md) in the `assembly-descriptor` section of the [ejb-jar.xml](outbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2), to the global JNDI name `activemq/queue/outbound` which was [declared above](../../../Connectivity/Containers/JBoss Integration/outbound-communication.md):
-
-**jboss.xml – Linking LoggingQueue to the global JNDI namespace**
-
-<assembly-descriptor>
- <message-destination>
- <message-destination-name>LoggingQueue</message-destination-name>
- <jndi-name>activemq/queue/outbound</jndi-name>
- </message-destination>
-</assembly-descriptor>
-
-The above example highlights the key configuration settings needed to enable EJBs deployed in JBoss to send JMS messages to an ActiveMQ destination.
-
-You can try the above example, plus a few more, by downloading the [activemq-jboss-test.zip](outbound-communication.data/activemq-jboss-test.zip?version=3&modificationDate=1117021355000&api=v2) file which contains the complete sample project.
-
diff --git a/src/_documents/classic/Connectivity/Containers/Resource Adapter/activation-spec-properties.md b/src/_documents/classic/Connectivity/Containers/Resource Adapter/activation-spec-properties.md
deleted file mode 100644
index 24fd1db..0000000
--- a/src/_documents/classic/Connectivity/Containers/Resource Adapter/activation-spec-properties.md
+++ /dev/null
@@ -1,199 +0,0 @@
-Apache ActiveMQ ™ -- Activation Spec Properties
-
-[Connectivity](../../../connectivity.md) > [Containers](../../../Connectivity/containers.md) > [Resource Adapter](../../../Connectivity/Containers/resource-adapter.md) > [Activation Spec Properties](../../../Connectivity/Containers/Resource Adapter/activation-spec-properties.md)
-
-
-An Activation Spec is used to configure the message delivery to an MDB. The ejb-jar.xml deployment descriptor needs to include a <activation-config> element inside the <message-driven> element like:
-
-<activation-config>
- <activation-config-property>
- <activation-config-property-name>destination</activation-config-property-name>
- <activation-config-property-value>queue.testQueue</activation-config-property-value>
- </activation-config-property>
- <activation-config-property>
- <activation-config-property-name>destinationType</activation-config-property-name>
- <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
- </activation-config-property>
-</activation-config>
-
-Here, the value for destination is the physical name of the desired destination. The value for destinationType is the class name that defines the type of destination. It should be javax.jms.Queue or javax.jms.Topic.
-
-
-The Activation Spec properties that can be configured are:
-
-Property Name
-
-Required
-
-Default Value
-
-Description
-
-acknowledgeMode
-
-no
-
-Auto-acknowledge
-
-The JMS Acknowledgement mode to use. Valid values are: Auto-acknowledge or Dups-ok-acknowledge
-
-clientId
-
-no
-
-set in resource adapter
-
-The JMS Client ID to use (only really required for durable topics)
-
-destinationType
-
-yes
-
-null
-
-The type of destination; a queue or topic
-
-destination
-
-yes
-
-null
-
-The destination name (queue or topic name)
-
-enableBatch
-
-no
-
-false
-
-Used to enable transaction batching for increased performance
-
-maxMessagesPerBatch
-
-no
-
-10
-
-The number of messages per transaction batch
-
-maxMessagesPerSessions
-
-no
-
-10
-
-This is actually the prefetch size for the subscription. (Yes, badly named).
-
-maxSessions
-
-no
-
-10
-
-The maximum number of concurrent sessions to use
-
-messageSelector
-
-no
-
-null
-
-The JMS [Message Selector](../../../Features/Consumer Features/selectors.md) to use on the subscription to perform content based routing filtering the messages
-
-noLocal
-
-no
-
-false
-
-Only required for topic subscriptions; indicates if locally published messages should be included in the subscription or not
-
-password
-
-no
-
-set in resource adapter
-
-The password for the JMS connection
-
-subscriptionDurability
-
-no
-
-NonDurable
-
-Whether or not a durable (topic) subscription is required. Valid values are: Durable or NonDurable
-
-subscriptionName
-
-no
-
-null
-
-The name of the durable subscriber. Only used for durable topics and combined with the clientID to uniquely identify the durable topic subscription
-
-userName
-
-no
-
-set in resource adapter
-
-The user for the JMS connection
-
-useRAManagedTransaction
-
-no
-
-false
-
-Typically, a resource adapter delivers messages to an endpoint which is managed by a container. Normally, this container likes to be the one that wants to control the transaction that the inbound message is being delivered on. But sometimes, you want to deliver to a simpler container system that will not be controlling the inbound transaction. In these cases, if you set useRAManagedTransaction to true, the resource adapter will commit the transaction if no exception was generated from th [...]
-
-initialRedeliveryDelay
-
-no
-
-1000
-
-The delay before redeliveries start. Also configurable on the ResourceAdapter
-
-maximumRedeliveries
-
-no
-
-5
-
-The maximum number of redeliveries or -1 for no maximum. Also configurable on the ResourceAdapter
-
-redeliveryBackOffMultiplier
-
-no
-
-5
-
-The multiplier to use if exponential back off is enabled. Also configurable on the ResourceAdapter
-
-redeliveryUseExponentialBackOff
-
-no
-
-false
-
-To enable exponential backoff. Also configurable on the ResourceAdapter
-
-useJndi
-
-no
-
-false
-
-when true, use destination as a jndi name
-
-Maximising Throughput of MDBs
-
-If you want to maximise throughput of MDBs you should really set the **maxSessions** to something fairly large to increase the concurrency. Then set **maxMessagesPerSessions** to something big (say) 1000.
-
-This assumes you have large numbers of messages available (say more than **maxSessions** \* **maxMessagesPerSession**). Otherwise the [prefetch](../../../FAQ/Using Apache ActiveMQ/what-is-the-prefetch-limit-for.md) will end up [starving other consumers](../../../FAQ/Errors/i-do-not-receive-messages-in-my-second-consumer.md).
-
-So if you don't have that many messages available, but maybe they take a while to process then you might want to set a lower value of **maxMessagesPerSessions**
-
diff --git a/src/_documents/classic/Connectivity/Containers/Resource Adapter/connection-factory-properties.md b/src/_documents/classic/Connectivity/Containers/Resource Adapter/connection-factory-properties.md
deleted file mode 100644
index c8de8e7..0000000
--- a/src/_documents/classic/Connectivity/Containers/Resource Adapter/connection-factory-properties.md
+++ /dev/null
@@ -1,65 +0,0 @@
-Apache ActiveMQ ™ -- Connection Factory Properties
-
-[Connectivity](../../../connectivity.md) > [Containers](../../../Connectivity/containers.md) > [Resource Adapter](../../../Connectivity/Containers/resource-adapter.md) > [Connection Factory Properties](../../../Connectivity/Containers/Resource Adapter/connection-factory-properties.md)
-
-
-The 'outbound' Connection Factory objects used to send messages by default use the connection configuration properties of the Resource Adapter deployment, but those properties can be overridden per connection factory.
-
-The Connection Factory properties that can be configured are:
-
-Property Name
-
-Required
-
-Default Value
-
-ServerUrl
-
-no
-
-set in resource adapter
-
-UserName
-
-no
-
-set in resource adapter
-
-Clientid
-
-no
-
-set in resource adapter
-
-Password
-
-no
-
-set in resource adapter
-
-UseInboundSession
-
-no
-
-set in resource adapter
-
-#### ServerUrl
-
-The URL to the ActiveMQ server that you want this connection to connect to. If using an embedded broker, this value should be 'vm://localhost'.
-
-#### UserName
-
-The default user name that will be used to establish connections to the ActiveMQ server.
-
-#### Password
-
-The default password that will be used to log the default user into the ActiveMQ server.
-
-#### Clientid
-
-The client id that will be set on the connection that is established to the ActiveMQ server.
-
-#### UseInboundSession
-
-Boolean to configure if outbound connections should reuse the inbound connection's session for sending messages.
-
diff --git a/src/_documents/classic/Connectivity/Containers/Resource Adapter/resource-adapter-properties.md b/src/_documents/classic/Connectivity/Containers/Resource Adapter/resource-adapter-properties.md
deleted file mode 100644
index 3167928..0000000
--- a/src/_documents/classic/Connectivity/Containers/Resource Adapter/resource-adapter-properties.md
+++ /dev/null
@@ -1,180 +0,0 @@
-Apache ActiveMQ ™ -- Resource Adapter Properties
-
-[Connectivity](../../../connectivity.md) > [Containers](../../../Connectivity/containers.md) > [Resource Adapter](../../../Connectivity/Containers/resource-adapter.md) > [Resource Adapter Properties](../../../Connectivity/Containers/Resource Adapter/resource-adapter-properties.md)
-
-
-The ActiveMQ Resource Adapter allows you to configure several properties that:
-
-* sets the options used for connection used for inbound message delivery
-* sets the default options used for the outbound connection factory objects.
-
-The properties that can be configured are:
-
-Property Name
-
-Required
-
-Default Value
-
-Description
-
-ServerUrl
-
-no
-
-tcp://localhost:61616
-
-The URI to connect to the broker on
-
-UserName
-
-no
-
-defaultUser
-
-User name
-
-Password
-
-no
-
-defaultPassword
-
-Password
-
-Clientid
-
-no
-
-null
-
-The JMS client ID to use
-
-UseInboundSession
-
-no
-
-false
-
-BrokerXmlConfig
-
-no
-
-The ActiveMQ XML config file to use to deploy an embedded broker. E.g. to configure via an XML configuration file then use **xbean:activemq.xml** or to configure via a [Broker Configuration URI](../../../Using ActiveMQ/Configuring Transports/ActiveMQ Connection URIs/broker-configuration-uri.md) (to avoid using Spring, XBean and XML) then use **broker:(tcp://localhost:61616)**
-
-#### Performance related settings
-
-Property Name
-
-Required
-
-Default Value
-
-Description
-
-AllPrefetchValues
-
-no
-
-Sets all the prefetch values in one setting
-
-DurableTopicPrefetch
-
-no
-
-100
-
-The maximum number of messages sent to a consumer on a durable topic until acknowledgements are received
-
-QueuePrefetch
-
-no
-
-1000
-
-The maximum number of messages sent to a consumer on a queue until acknowledgements are received
-
-InputStreamPrefetch
-
-no
-
-100
-
-The maximum number of messages sent to a consumer on a JMS stream until acknowledgements are received
-
-TopicPrefetch
-
-no
-
-Short.MAX_VALUE - 1
-
-The maximum number of messages sent to a consumer on a non-durable topic until acknowledgements are received
-
-#### Redelivery properties
-
-Property Name
-
-Required
-
-Default Value
-
-Description
-
-InitialRedeliveryDelay
-
-no
-
-1000
-
-The delay before redeliveries start. Also configurable on the ActivationSpec.
-
-MaximumRedeliveries
-
-no
-
-5
-
-The maximum number of redeliveries or -1 for no maximum. Also configurable on the ActivationSpec.
-
-RedeliveryBackOffMultiplier
-
-no
-
-5
-
-The multiplier to use if exponential back off is enabled. Also configurable on the ActivationSpec.
-
-RedeliveryUseExponentialBackOff
-
-no
-
-false
-
-To enable exponential backoff. Also configurable on the ActivationSpec.
-
-#### ServerUrl
-
-The URL to the ActiveMQ server that you want this connection to connect to. If using an embedded broker, this value should be 'vm://localhost' if using the auto-created embedded broker, otherwise if you explicitly create a broker (e.g. using one of the [embedded broker](../../../FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md) techniques), then this value should be 'vm://brokerName', where brokerName is replaced by the broker's name.
-
-#### UserName
-
-The default user name that will be used to establish connections to the ActiveMQ server.
-
-#### Password
-
-The default password that will be used to log the default user into the ActiveMQ server.
-
-#### Clientid
-
-The client id that will be set on the connection that is established to the ActiveMQ server.
-
-#### UseInboundSession
-
-Boolean to configure if outbound connections should reuse the inbound connection's session for sending messages.
-
-#### BrokerXmlConfig
-
-Sets the XML configuration file used to configure the embedded ActiveMQ broker via Spring if using embedded mode. If this property is omitted then no embedded broker is used and you must [run the broker](../../../Using ActiveMQ/run-broker.md) in a separate process or deployment unit.
-
-BrokerXmlConfig is the filename which is assumed to be on the classpath unless a URL is specified. So a value of foo/bar.xml would be assumed to be on the classpath whereas file:dir/file.xml would use the file system. Any valid URL string is supported.
-
diff --git a/src/_documents/classic/Connectivity/Containers/Resource Adapter/tomee.md b/src/_documents/classic/Connectivity/Containers/Resource Adapter/tomee.md
deleted file mode 100644
index b643266..0000000
--- a/src/_documents/classic/Connectivity/Containers/Resource Adapter/tomee.md
+++ /dev/null
@@ -1,95 +0,0 @@
-Apache ActiveMQ ™ -- TomEE
-
-[Connectivity](../../../connectivity.md) > [Containers](../../../Connectivity/containers.md) > [Resource Adapter](../../../Connectivity/Containers/resource-adapter.md) > [TomEE](../../../Connectivity/Containers/Resource Adapter/tomee.md)
-
-
-Apache TomEE is a distribution of Tomcat with fully integrated ActiveMQ offering full JMS support to plain war files, Servlets and more. No setup is required and code like the following will work out of the box.
-
-import javax.annotation.Resource;
-import javax.servlet.http.HttpServlet;
-import javax.jms.Topic;
-import javax.jms.Queue;
-import javax.jms.ConnectionFactory;
-
-public class MyServet extends HttpServlet {
-
- @Resource(name = "foo")
- private Topic fooTopic;
-
- @Resource(name = "bar")
- private Queue barQueue;
-
- @Resource
- private ConnectionFactory connectionFactory;
-
- @Override
- protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException {
- //...
-
- Connection connection = connectionFactory.createConnection();
- connection.start();
-
- // Create a Session
- Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
-
- // Create a MessageProducer from the Session to the Topic or Queue
- MessageProducer producer = session.createProducer(fooTopic);
- producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
-
- // Create a message
- TextMessage message = session.createTextMessage("Hello World!");
-
- // Tell the producer to send the message
- producer.send(message);
-
- //...
- }
-}
-
-All topics and queues are created automatically when declared properly in code as above. For example, the following reference in code:
-
- @Resource(name = "foo")
- private Topic fooTopic;
-
-Is identical to the following declaration in the <tomee.home>/conf/tomee.xml file or WEB-INF/resources.xml file:
-
- <Resource id="foo" type="javax.jms.Topic" />
-
-In both situations Topic name would be 'foo'.
-
-Configuring an Embedded Broker
-------------------------------
-
-If no broker is configured and JMS is used in the webapp, TomEE will create a broker equivalent to the following declaration:
-
-<tomee>
- <Resource id="MyJmsResourceAdapter" type="ActiveMQResourceAdapter">
- BrokerXmlConfig = broker:(tcp://someHostName:61616)
- ServerUrl = vm://localhost
- </Resource>
-
- <Resource id="MyJmsConnectionFactory" type="javax.jms.ConnectionFactory">
- ResourceAdapter = MyJmsResourceAdapter
- </Resource>
-</tomee>
-
-This creates an ActiveMQ Broker that runs inside TomEE and is bound to the address `someHostName:61616`. This broker will start when TomEE starts and shutdown when TomEE shuts down. All JMS communication happening inside TomEE itself will happen using the embedded ActiveMQ Broker over the ActiveMQ "vm" transport which is optimized for sending and receiving messages when in the same JVM as the Broker.
-
-Connecting to an External Broker
---------------------------------
-
-It is possible to connect to an ActiveMQ Broker running externally. The setup is similar to the above with only two changes.
-
-<tomee>
- <Resource id="MyJmsResourceAdapter" type="ActiveMQResourceAdapter">
- BrokerXmlConfig =
- ServerUrl = tcp://someHostName:61616
- </Resource>
-
- <Resource id="MyJmsConnectionFactory" type="javax.jms.ConnectionFactory">
- ResourceAdapter = MyJmsResourceAdapter
- </Resource>
-</tomee>
-
-Here the `BrokerXmlConfig` property is empty as we are not configuring an embedded broker to be run inside TomEE. The `ServerUrl` now points to an explicit remote host and port `someHostName:61616` where an ActiveMQ Broker must be running. This Broker can be a plain ActiveMQ install or an ActiveMQ Broker embedded in a TomEE install.
-
diff --git a/src/_documents/classic/Connectivity/Containers/Spring Support/jmstemplate-gotchas.md b/src/_documents/classic/Connectivity/Containers/Spring Support/jmstemplate-gotchas.md
deleted file mode 100644
index d585567..0000000
--- a/src/_documents/classic/Connectivity/Containers/Spring Support/jmstemplate-gotchas.md
+++ /dev/null
@@ -1,29 +0,0 @@
-Apache ActiveMQ ™ -- JmsTemplate Gotchas
-
-[Connectivity](../../../connectivity.md) > [Containers](../../../Connectivity/containers.md) > [Spring Support](Connectivity/Containers/spring-Community/support.md) > [JmsTemplate Gotchas](../../../Connectivity/Containers/Spring Support/jmstemplate-gotchas.md)
-
-
-The thing to remember is JmsTemplate is designed for use in EJBs using the EJB containers JMS pooling abstraction. So every method will typically create a connection, session, producer or consumer, do something, then close them all down again. The idea being that this will use the J2EE containers pooling mechanism to pool the JMS resources under the covers. Without using a pooled JMS provider from the EJB container this is the worst possible way of working with JMS; since typically each [...]
-
-User Story
-
-We had a bug once in ActiveMQ where if you created 65535 MessageProducer instances within the space of a few seconds, we'd get an exception thrown in the broker. Its a kinda silly thing to do, to create that many producers in a small space of time (one for each message to be sent) - JMS is designed for resources like producers and consumers to be created up front and reused across many message exchanges. The bug was highlighted by a user using JmsTemplate without a JMS pool underneath. W [...]
-
-You should only use JmsTemplate with a pooled JMS provider. In J2EE 1.4 or later that typically means a JCA based JMS ConnectionFactory. If you are in an EJB then make sure you use your J2EE containers ConnectionFactory, never a plain-old-connection factory. If you are not inside an EJB Then you should use our [PooledConnectionFactory](http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/pool/PooledConnectionFactory.html), then things will be nicely pooled. If you n [...]
-
-Another gotcha I've seen folks do is to create a MessageConsumer inside one of the SessionCallback methods then wonder why messages are not being received. After the SessionCallback is called, the session will be closed; which will close your consumers too . So if you want to create a MessageConsumer you should create a connection, session and consumer [...]
-
-Another problem I've seen is folks using the JmsTemplate.receive() method; as I've said above if you're not in an EJB using the J2EE containers ConnnectionFactory, a connection, session & consumer will be create and closed for each receive() method. This is all fine and well - if painfully slow unless you are using pooling - but be aware that this mechanism, without pooling, may well miss messages. If you are consuming on a topic which has messages sent with NON_PERSISTENT delivery mode [...]
-
-New in 4.x
-
-In ActiveMQ [4.x](../../../Features/New Features/changes-in-40.md) we have a new feature called [Subscription Recovery Policy](../../../Features/Consumer Features/subscription-recovery-policy.md) which even in non-durable delivery mode allows a new consumer to go back in time and receive messages delivered within a window (a fixed amount of RAM or time window). e.g. if your broker dies you have 2 minutes to reconnect to another broker and not miss any messages - even without durable delivery.
-
-### Recommendations for using JmsTemplate
-
-* Never use a regular ConnectionFactory unless you are totally sure it does all the pooling you need
-* If using in an EJB ensure you use the EJB containers ConnectionFactory
-* If you are only publishing messages and you are not in an EJB container and you are using ActiveMQ, then you can use either the [PooledConnectionFactory](http://activemq.codehaus.org/maven/apidocs/org/activemq/pool/PooledConnectionFactory.html) or the [Spring CachingConnectionFactory](http://static.springsource.org/spring/docs/2.5.x/api/org/springframework/jms/connection/CachingConnectionFactory.html)
-* If you are consuming messages its probably simpler & more efficient & less likely to lose messages to avoid using the receive() method and use Spring's [MessageListenerContainer](http://static.springsource.org/spring/docs/2.5.x/reference/FAQ/jms.md#Community/FAQ/jms.mdp) instead
-* See also [Using Spring to Send JMS Messages](http://bsnyderblog.blogspot.com/2010/02/using-spring-jmstemplate-to-send-/FAQ/jms.md) and [Using Spring to Receive JMS Messages](http://bsnyderblog.blogspot.com/2010/02/using-spring-to-receive-jms-messages.html)
-
diff --git a/src/_documents/classic/Connectivity/Containers/Tomcat/setting-up-activemq-with-tomcat-559.md b/src/_documents/classic/Connectivity/Containers/Tomcat/setting-up-activemq-with-tomcat-559.md
deleted file mode 100644
index 21bfb7b..0000000
--- a/src/_documents/classic/Connectivity/Containers/Tomcat/setting-up-activemq-with-tomcat-559.md
+++ /dev/null
@@ -1,51 +0,0 @@
-Apache ActiveMQ ™ -- Setting up ActiveMQ with Tomcat 5.5.9
-
-[Connectivity](../../../connectivity.md) > [Containers](../../../Connectivity/containers.md) > [Tomcat](../../../Connectivity/Containers/tomcat.md) > [Setting up ActiveMQ with Tomcat 5.5.9](../../../Connectivity/Containers/Tomcat/setting-up-activemq-with-tomcat-559.md)
-
-
-Create the file <webapp-root>/META-INF/context.xml. Here is an example:
-
-<Context antiJARLocking="true">
- <Resource
- name="jms/ConnectionFactory"
- auth="Container"
- type="org.apache.activemq.ActiveMQConnectionFactory"
- description="JMS Connection Factory"
- factory="org.apache.activemq.jndi.JNDIReferenceFactory"
- brokerURL="tcp://localhost:61616"
- brokerName="LocalActiveMQBroker"
- useEmbeddedBroker="false"/>
-
- <Resource name="jms/topic/MyTopic"
- auth="Container"
- type="org.apache.activemq.command.ActiveMQTopic"
- factory="org.apache.activemq.jndi.JNDIReferenceFactory"
- physicalName="MY.TEST.FOO"/>
- <Resource name="jms/queue/MyQueue"
- auth="Container"
- type="org.apache.activemq.command.ActiveMQQueue"
- factory="org.apache.activemq.jndi.JNDIReferenceFactory"
- physicalName="MY.TEST.FOO.QUEUE"/>
-</Context>
-
-This will setup the JNDI for the ConectionFactory and Topic to work within Tomcat.
-
-Here is some example code that will publish a test message to the MY.TEST.FOO Topic:
-
-try {
- InitialContext initCtx = new InitialContext();
- Context envContext = (Context) initCtx.lookup("java:comp/env");
- ConnectionFactory connectionFactory = (ConnectionFactory) envContext.lookup("jms/ConnectionFactory");
- Connection connection = connectionFactory.createConnection();
- Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
- MessageProducer producer = session.createProducer((Destination) envContext.lookup("jms/topic/MyTopic"));
-
- Message testMessage = session.createMessage();
- testMessage.setStringProperty("testKey", "testValue");
- producer.send(testMessage);
-} catch (NamingException e) {
- // TODO handle exception
-} catch (JMSException e) {
- // TODO handle exception
-}
-
diff --git a/src/_documents/classic/Connectivity/Containers/axis-and-cxf-support.md b/src/_documents/classic/Connectivity/Containers/axis-and-cxf-support.md
deleted file mode 100644
index 68d5d03..0000000
--- a/src/_documents/classic/Connectivity/Containers/axis-and-cxf-support.md
+++ /dev/null
@@ -1,17 +0,0 @@
-Apache ActiveMQ ™ -- Axis and CXF Support
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [Axis and CXF Support](axis-and-cxf-CommunityCommunity/Community/support.md)
-
-
-ActiveMQ supports both [Apache Axis](http://ws.apache.org/axis/) and [Apache CXF](http://incubator.apache.org/cxf) out of the box.
-
-Axis support is @deprecated
-
-Support for Axis is deprecated, and will be removed from ActiveMQ 5.8 onwards.
-
-Just add the [required jars](Using ActiveMQ/initial-Community/FAQ/configuration.md) to your classpath and you should be able to use JMS transport support inside either web service framework to send and receive messages using ActiveMQ queues or topics for reliable messaging.
-
-For an example of using the JMS transport with Axis, consult [JMS Transport reference](http://ws.apache.org/axis2/1_2/jms-transport.html) or try looking at the [JMS example](http://svn.apache.org/viewvc/webservices/axis2/branches/java/1_4/modules/samples/jms/) that comes with bundled with Axis' binary and source downloads.
-
-For examples of using JMS transport with CXF, please see its [JMS publish/subscriber sample](http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/jms_pubsub/) and the [JMS queue sample](http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/jms_queue/) available in the CXF source and binary downloads.
-
diff --git a/src/_documents/classic/Connectivity/Containers/blazeds.md b/src/_documents/classic/Connectivity/Containers/blazeds.md
deleted file mode 100644
index 8fe49d2..0000000
--- a/src/_documents/classic/Connectivity/Containers/blazeds.md
+++ /dev/null
@@ -1,54 +0,0 @@
-Apache ActiveMQ ™ -- BlazeDS
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [BlazeDS](../../Connectivity/Containers/blazeds.md)
-
-
-BlazeDS
--------
-
-You may also want to check out the [Simplified BlazeDS and JMS article](http://mmartinsoftware.blogspot.com/2008/05/simplified-blazeds-and-/FAQ/jms.md) by [Michael Martin](http://mmartinsoftware.blogspot.com/).
-
-Using the dynamicQueues feature of the [JNDI Support](Connectivity/Containers/jndi-Community/support.md) Ryan Gardner created thisworking BlazeDS messaging-config.xml file:
-
-<?xml version="1.0" encoding="UTF-8"?>
-<service id="message-service" class="flex.messaging.services.MessageService">
-
- <adapters>
- <adapter-definition id="actionscript" class="flex.messaging.services.messaging.adapters.ActionScriptAdapter" default="true" />
- <adapter-definition id="jms" class="flex.messaging.services.messaging.adapters.JMSAdapter"/>
- </adapters>
-
- <default-channels>
- <channel ref="my-streaming-amf"/>
- <channel ref="my-polling-amf"/>
- </default-channels>
-
- <destination id="inbound-sms-destination">
-
- <properties>
- <jms>
- <destination-type>Topic</destination-type>
- <message-type>javax.jms.TextMessage</message-type>
- <connection-factory>topicConnectionFactory</connection-factory>
- <destination-jndi-name>dynamicTopics/SMSReturnMessages</destination-jndi-name>
-
- <delivery-mode>NON_PERSISTENT</delivery-mode>
- <message-priority>DEFAULT_PRIORITY</message-priority>
- <acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode>
- <initial-context-environment>
- <property>
- <name>Context.INITIAL\_CONTEXT\_FACTORY</name>
- <value>org.apache.activemq.jndi.ActiveMQInitialContextFactory</value>
- </property>
- <property>
- <name>Context.PROVIDER_URL</name>
- <value>vm://localhost</value>
-
- </property>
- </initial-context-environment>
- </jms>
- </properties>
- <adapter ref="jms"/>
- </destination>
-</service>
-
diff --git a/src/_documents/classic/Connectivity/Containers/geronimo.md b/src/_documents/classic/Connectivity/Containers/geronimo.md
deleted file mode 100644
index f2e7ab1..0000000
--- a/src/_documents/classic/Connectivity/Containers/geronimo.md
+++ /dev/null
@@ -1,208 +0,0 @@
-Apache ActiveMQ ™ -- Geronimo
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [Geronimo](../../Connectivity/Containers/geronimo.md)
-
-
-ActiveMQ is the default JMS provider in [Apache Geronimo](http://geronimo.apache.org).
-
-ActiveMQ can be used both as JMS Client and a JMS Broker. This short
-article explains how to use it on a standalone client to access the
-topics/queues setup on a remote Geronimo/ActiveMQ broker.
-
-1) Setup the queues and topics on the ActiveMQ Broker
-If you're using a standalone ActiveMQ broker, then following the instructions on
-ActiveMQ's website should be enough to setup everything.
-However, if your ActiveMQ's instance is embedded inside the J2EE Geronimo
-Application Server, creating Queues and Topics is about deploying Resource
-Adapters to your Geronimo server.
-The following deployment descriptor can be used to deploy two topics and a
-ConnectionFactory: weatherTopic and weatherRequestsTopic
-
-```
-<?xml version="1.0" encoding="UTF-8"?>
-<connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector"
- version="1.5"
- configId="weather/Topics"
- parentId="org/apache/geronimo/SystemJMS">
- <resourceadapter>
- <resourceadapter-instance>
- <resourceadapter-name>ActiveMQ RA</resourceadapter-name>
- <config-property-setting name="ServerUrl">tcp://localhost:61616</config-property-setting>
- <config-property-setting name="UserName">geronimo</config-property-setting>
- <config-property-setting name="Password">geronimo</config-property-setting>
- <workmanager>
- <gbean-link>DefaultWorkManager</gbean-link>
- </workmanager>
- </resourceadapter-instance>
- <outbound-resourceadapter>
- <connection-definition>
-
-<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
- <connectiondefinition-instance>
- <name>ConnectionFactory</name>
-
-<implemented-interface>javax.jms.QueueConnectionFactory</implemented-interface>
-
-<implemented-interface>javax.jms.TopicConnectionFactory</implemented-interface>
- <connectionmanager>
- <xa-transaction>
- <transaction-caching/>
- </xa-transaction>
- <single-pool>
- <max-size>10</max-size>
-
-<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
- <match-one/>
- </single-pool>
- </connectionmanager>
- <global-jndi-name>ConnectionFactory</global-jndi-name>
- <!--
-<credential-interface>javax.resource.spi.security.PasswordCredential</credential-interface>
--->
- </connectiondefinition-instance>
- </connection-definition>
- </outbound-resourceadapter>
- </resourceadapter>
- <adminobject>
- <adminobject-interface>javax.jms.Topic</adminobject-interface>
-
-<adminobject-class>org.codehaus.activemq.message.ActiveMQTopic</adminobject-class>
- <adminobject-instance>
- <message-destination-name>weatherTopic</message-destination-name>
- <config-property-setting
-name="PhysicalName">weatherTopic</config-property-setting>
- </adminobject-instance>
- </adminobject>
- <adminobject>
- <adminobject-interface>javax.jms.Topic</adminobject-interface>
-
-<adminobject-class>org.codehaus.activemq.message.ActiveMQTopic</adminobject-class>
- <adminobject-instance>
-
-<message-destination-name>weatherRequestsTopic</message-destination-name>
- <config-property-setting
-name="PhysicalName">weatherRequestsTopic</config-property-setting>
- </adminobject-instance>
- </adminobject>
-
-</connector>
-```
-
-Then deploy it using Geronimo's deploy tool :
-
-```
-D:\\geronimo>java -jar bin\\deployer.jar deploy d:\\projects\\weather\\src\\resources\
-geronimo-activemq.xml repository\\activemq\\rars\\activemq-ra-3.1-SNAPSHOT.rar
-Username: system
-Password: manager
-Deployed weather/Topics
-```
-
-The geronimo.log file should now refer to these newly deployed Topics.
-
-2) Now that the queues are available server-side, what we want is access them
-thanks to a standalone Client.
-Usually, the process is the following one :
-
-* Contact the J2EE naming server (port 1099, RMI) to get an JNDI InitialContext.
-* The J2EE server automatically exposes the ConnectionFactory and the Topics
- through JNDI, so the InitialContext allows you to retrieve both the
- ConnectionFactory and the Topics
-* Once you have your Topics, you just use them..
-
-However, ActiveMQ's JNDI Implementation does NOT talk to the naming server. It's
-a stripped down version of a JNDI client that just allows to get Topics and
-Queues directly from a JMS instance.
-So, instead of supplying the naming server address, you have to supply the JMS
-server address.
-Most JNDI implementations use the java.naming.provider.url property to specify
-the naming server's address. ActiveMQ uses the brokerURL one. Using the
-java.naming.provider.url one instead will result in ActiveMQ trying to load the
-whole Broker.
-
-3) So, now we have explained the process, let's detail the Spring way of doing
-things :
-
-* Create a bootstrap.properties file that's available in your classpath
- ```
- jms.connectionFactoryName=ConnectionFactory
- jms.jndiProviderUrl=tcp://localhost:61616
- jms.jndiContextFactory=org.activemq.jndi.ActiveMQInitialContextFactory
-
- jms.weatherTopic=weatherTopic
- jms.weatherRequestsTopic=weatherRequestsTopic
- ```
-
-
-
-* Now, in your Spring description file, declare the bean that will read
- the properties from the bootstrap.properties file
-
- <bean id="placeholderConfig"
- class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
- <property name="location"><value>classpath:/bootstrap.properties</value></property>
- </bean>
-
-
-* Create a JNDI template (A Spring-specific wrapper around the JNDI InitialContext
- ```
- <bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
- <property name="environment">
- <props>
- <prop key="java.naming.factory.initial">${jms.jndiContextFactory}</prop>
-
- <!\-\- Specific to ActiveMQ -->
-
- <!\-\- the address of the ActiveMQ broker -->
- <prop key="brokerURL">${jms.jndiProviderUrl}</prop>
- <!\-\- Some Topics Registration, since we are using a fake JNDI implementation -->
- <prop key="topic.${jms.weatherTopic}">${jms.weatherTopic}</prop>
- <prop key="topic.${jms.weatherRequestsTopic}">${jms.weatherRequestsTopic}</prop>
- </props>
- </property>
- </bean>
- ```
-
-* Retrieve the ConnectionFactory from the JNDI context
-
- ```
- <bean id="internalJmsQueueConnectionFactory"
- class="org.springframework.jndi.JndiObjectFactoryBean">
- <property name="jndiTemplate">
- <ref bean="jndiTemplate"/>
- </property>
- <property name="jndiName">
- <value>${jms.connectionFactoryName}</value>
- </property>
- </bean>
- ```
-I'm not 100% sure, but I think that you can put any Factory Name, it will just
-work. (In a scenario where the JNDI context actually contacts a naming server,
-it should match the name of the deployed ConnectionFactory)
-
-* Get the Topics instances from the JNDI Context
- ```
- <bean id="weatherTopic"
- class="org.springframework.jndi.JndiObjectFactoryBean"
- singleton="true">
- <property name="jndiTemplate">
- <ref bean="jndiTemplate"/>
- </property>
- <property name="jndiName">
- <value>${jms.weatherTopic}</value>
- </property>
- </bean>
-
- <bean id="weatherRequestTopic"
- class="org.springframework.jndi.JndiObjectFactoryBean"
- singleton="true">
- <property name="jndiTemplate">
- <ref bean="jndiTemplate"/>
- </property>
- <property name="jndiName">
- <value>${jms.weatherRequestsTopic}</value>
- </property>
- </bean>
- ```
-* Now, you can reuse these Topics beans the way you want.
-
diff --git a/src/_documents/classic/Connectivity/Containers/integrating-apache-activemq-with-glassfish.md b/src/_documents/classic/Connectivity/Containers/integrating-apache-activemq-with-glassfish.md
deleted file mode 100644
index c2f5cbf..0000000
--- a/src/_documents/classic/Connectivity/Containers/integrating-apache-activemq-with-glassfish.md
+++ /dev/null
@@ -1,50 +0,0 @@
-Apache ActiveMQ ™ -- Integrating Apache ActiveMQ with Glassfish
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [Integrating Apache ActiveMQ with Glassfish](../../Connectivity/Containers/integrating-apache-activemq-with-glassfish.md)
-
-
-General
-=======
-
-See this article for a description of how to connect Glassfish 3 to an ActiveMQ 5 broker, and consume messages using a Message Driven Bean: [http://geertschuring.wordpress.com/2012/04/20/how-to-connect-glassfish-3-to-activemq-5/](http://geertschuring.wordpress.com/2012/04/20/how-to-connect-glassfish-3-to-activemq-5/)
-
-Glassfish 4.1
-=============
-
-1. Add resource adapter
- 1. Download the resource-adapter file suitable to your broker version:
- [http://repo1.maven.org/maven2/org/apache/activemq/activemq-rar/](http://repo1.maven.org/maven2/org/apache/activemq/activemq-rar/)
- 2. Deploy the resource adapter with the name "activemq-rar"
-
- bin/asadmin deploy --type rar --name activemq-rar /tmp/activemq-rar-5.11.1.rar
-
- 3. Configure resource adapter
- (Failover Setup)
-
- bin/asadmin create-resource-adapter-config \
- --property ServerUrl='failover\\:(tcp\\://broker-c1.foobar.local\\:61616,tcp\\://broker-c2.foobar.local\\:61616,tcp\\://broker-c3.foobar.local\\:61616)?initialReconnectDelay\\=2000&jms.useCompression\\=true':UserName='admin':Password='admin' activemq-rar
-
-2. Create connector connection pool
-
- bin/asadmin create-connector-connection-pool \
- --raname activemq-rar \
- --connectiondefinition javax.jms.ConnectionFactory \
- --ping true --isconnectvalidatereq true \
- jms/myConnectionPool
-
-3. Create a connector resource (JNDI-Mapping for connection pool)
-
- bin/asadmin create-connector-resource \
- --poolname jms/myConnectionPool \
- jms/myConnectionFactory
-
-4. Configure JNDI mapping for a queue
-
- bin/asadmin create-admin-object \
- --raname activemq-rar \
- --restype javax.jms.Queue \
- --property PhysicalName=MY.MAGIC.OUT \
- jms/queue/MY.MAGIC.OUT
-
-5. Deploy your message driven beans and use the configured jndi names
-
diff --git a/src/_documents/classic/Connectivity/Containers/integrating-apache-activemq-with-jboss.md b/src/_documents/classic/Connectivity/Containers/integrating-apache-activemq-with-jboss.md
deleted file mode 100644
index f3a251b..0000000
--- a/src/_documents/classic/Connectivity/Containers/integrating-apache-activemq-with-jboss.md
+++ /dev/null
@@ -1,724 +0,0 @@
-Apache ActiveMQ ™ -- Integrating Apache ActiveMQ with JBoss
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [Integrating Apache ActiveMQ with JBoss](../../Connectivity/Containers/integrating-apache-activemq-with-jboss.md)
-
-
-Integrating Apache ActiveMQ with JBoss
-======================================
-
-Integration with application servers is a common scenario in the enterprise Java world, especially when it comes to messaging. [ActiveMQ](http://activemq.org/) is a JMS 1.1 compliant, open source, Apache Licensed, message oriented middleware (MOM) with [many](http://activemq.org/siteFeatures/New FeaturesFeatures/New Features/Features/New Features/changes-in-40.md), [many](http://activemq.org/siteFeatures/New Features/new-features-in-41.md) features far beyond the JMS specification. Activ [...]
-
-One of the application servers in the open source world is JBoss. A very common requirement is to configure ActiveMQ as the messaging infrastructure within JBoss. Although there is [a bit of documentation](http://www.activemq.org/siteConnectivity/ContainersConnectivity/Containers/Connectivity/Containers/jboss-integration.md) on this integration, this article seeks to provide much more detail and explanation. So if you have a need to integrate ActiveMQ with JBoss, this article is for you.
-
-This article explains how to configure JBoss to start up ActiveMQ as part of its lifecycle and how to configure the ActiveMQ resource adapter to handle the messaging and transactionality between ActiveMQ and JBoss.
-
-Requirements
-------------
-
-Below are the software requirements for this article with links to download each:
-
-* [Apache ActiveMQ 4.0.1+](http://activemq.org/siteOverviewOverview/Overview/download.md)
-* [JBoss 4.0.4+](http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=416591)
-* [Sun Java 1.5+](http://www.java.com/en/download/index.jsp)
-* [Apache Ant 1.6+](http://ant.apache.org/bindownload.cgi)
-
-Though this article is using Unix, the installation and integration will work on any platform running Sun Java. It is recommended that each piece of software be downloaded before working through the steps is this article. Once each piece of software has been downloaded, proceed to the first step.
-
-Install the J2SE 1.5
---------------------
-
-The first step in this process is to install Java 1.5 and verify that it runs correctly. Using the link above, find, download and install the correct version of Java for your platform. Once Java is installed and in the PATH, test it to see that it runs correctly using the following command:
-
-$ java -version
-java version "1.5.0_06"
-Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112)
-Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing)
-
-Depending upon your platform and the exact build number of Java 1.5, your output may vary slightly. As long as it's Java 1.5 and the version information is output, you should be ready to proceed to the next step.
-
-Install Apache Ant
-------------------
-
-The second step is to install Apache Ant. Simply download it using the link above, expand somewhere on your hard drive and place the `bin` directory in the PATH. This will allow you to test it quickly using the commands below:
-
-$ ant -version
-Apache Ant version 1.6.2 compiled on July 16 2004
-
-As long as you see the version output above, Ant should be usable. If you did not see the version output or received an error, consult the Ant documentation or mailing list archives to work out the issue. Please note that Ant is not used until the end of this whole exercise to test the integration.
-
-Install the JBoss Application Server
-------------------------------------
-
-The third step in this process is to install JBoss and make sure it runs correctly before installing and configuring ActiveMQ. Upon downloading JBoss-4.0.4, expand it in a place where it can create a directory. Next, run the server using the following commands:
-
-$ cd jboss-4.0.4.GA
-$ ./bin/run.sh -c default
-=========================================================================
-
- JBoss Bootstrap Environment
-
- JBOSS_HOME: /opt/jboss-4.0.4.GA
-
- JAVA: java
-
- JAVA_OPTS: -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000
--Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh
-
- CLASSPATH: /opt/jboss-4.0.4.GA/bin/run.jar:/lib/tools.jar
-
-=========================================================================
-
-15:34:47,999 INFO \[Server\] Starting JBoss (MX MicroKernel)...
-15:34:48,001 INFO \[Server\] Release ID: JBoss \[Zion\] 4.0.4.GA (build: CVSTag=JBoss\_4\_0\_4\_GA date=200605151000)
-15:34:48,004 INFO \[Server\] Home Dir: /opt/jboss-4.0.4.GA
-15:34:48,005 INFO \[Server\] Home URL: file:/opt/jboss-4.0.4.GA/
-15:34:48,007 INFO \[Server\] Patch URL: null
-15:34:48,007 INFO \[Server\] Server Name: default
-15:34:48,007 INFO \[Server\] Server Home Dir: /opt/jboss-4.0.4.GA/server/default
-15:34:48,011 INFO \[Server\] Server Home URL: file:/opt/jboss-4.0.4.GA/server/default/
-15:34:48,012 INFO \[Server\] Server Log Dir: /opt/jboss-4.0.4.GA/server/default/log
-15:34:48,017 INFO \[Server\] Server Temp Dir: /opt/jboss-4.0.4.GA/server/default/tmp
-15:34:48,022 INFO \[Server\] Root Deployment Filename: jboss-service.xml
-...
-15:35:17,360 INFO \[Server\] JBoss (MX MicroKernel) \[4.0.4.GA (build: CVSTag=JBoss\_4\_0\_4\_GA date=200605151000)\]
-Started in 22s:238ms
-
-The first few lines of output from the JBoss startup indicates the configuration being used but the last line is the most important one. It tells you that JBoss has been started successfully on your system. For an extra measure of assurance, visit [http://localhost:8080/web-console/](http://localhost:8080/web-console/) in a web browser to make sure you are able to see the JBoss web console. If you can see this console, everything should be ready to go.
-
-As a side note, the left-hand side of the web-console requires that the [Java plugin](http://java.sun.com/products/plugin/) be properly installed. This is supposed to take place when installing the J2SE, so if it did not work correctly for you, I suggest that you consult some documentation about any errors you may be seeing. The Java plugin is not required for JBoss or ActiveMQ to function properly, it is simply for the JBoss web-console.
-
-Once JBoss is installed properly, shut it down using either the shutdown script or by simply typing ctrl-c to activate the shutdown hook. Once it is shut down, proceed to the next step.
-
-Prepare for Integrating Apache ActiveMQ with the JBoss Application Server
--------------------------------------------------------------------------
-
-The fourth step is to prepare your environment for integrating ActiveMQ with JBoss. If you haven't done so already, download Apache ActiveMQ using the link above. As of the writing of this article, the latest released version is 4.0.2-RC4. Upon downloading this archive, expand it in a place where it can create a directory, preferably in the same location where JBoss was expanded. Verify that the ActiveMQ RAR file is included using the following commands:
-
-$ cd ./incubator-activemq-4.0.2.tar.gz
-$ jar tvf /opt/incubator-activemq-4.0.2/lib/optional/activemq-ra-4.0.2.rar
- 0 Mon Sep 25 19:00:50 MDT 2006 META-INF/
- 399 Mon Sep 25 19:00:48 MDT 2006 META-INF/MANIFEST.MF
- 523 Mon Sep 25 13:07:40 MDT 2006 META-INF/DISCLAIMER.txt
- 11359 Mon Sep 25 13:07:40 MDT 2006 META-INF/LICENSE.txt
- 20305 Mon Sep 25 13:07:40 MDT 2006 META-INF/ra.xml
- 2334 Mon Sep 25 13:07:40 MDT 2006 broker-config.xml
- 70023 Mon Sep 25 19:00:48 MDT 2006 activemq-ra-4.0.2.jar
-1351744 Mon Sep 25 19:00:14 MDT 2006 activemq-core-4.0.2.jar
-232107 Mon Sep 25 18:22:48 MDT 2006 activeio-core-3.0-beta4.jar
-2143211 Tue Aug 01 11:44:50 MDT 2006 derby-10.1.1.0.jar
-1901653 Tue Aug 01 11:47:08 MDT 2006 spring-1.2.6.jar
- 94713 Tue Aug 01 11:47:22 MDT 2006 xbean-spring-2.2.jar
- 52915 Tue Aug 01 12:22:16 MDT 2006 commons-logging-1.1.jar
- 16030 Tue Aug 01 12:22:32 MDT 2006 geronimo-j2ee-management\_1.0\_spec-1.0.jar
-329586 Tue Aug 01 12:22:54 MDT 2006 backport-util-concurrent-2.1.jar
-358085 Tue Aug 01 12:23:26 MDT 2006 log4j-1.2.12.jar
- 523 Mon Sep 25 19:00:50 MDT 2006 META-INF/DISCLAIMER.txt
- 11359 Mon Sep 25 19:00:50 MDT 2006 META-INF/LICENSE.txt
-
-This is simply a table of contents of the RAR file. There should only be one reason that this will fail - an incomplete download of the ActiveMQ tarball or zip file. Beyond that, depending on the version you download, some of the library versions may be slightly different.
-
-Now go back to the JBoss installation and create a directory for ActiveMQ in the JBoss deploy directory for the default JBoss context. Below are the commands to achieve this task:
-
-$ mkdir /opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-$ cd /opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-$ pwd
-/opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-
-**_NOTE:_** The creation of a directory is not required but is the easiest way to set up the ActiveMQ RAR when you're just getting started. This is due to the flexibility it affords during the development phase for the configuration to be changed very easily. The alternative is to JAR up the directory as a RAR file once the configuration is solid enough that it no longer needs to be changed. But leaving everything in a directory during development is the easiest path.
-
-Now expand the activemq-ra-4.0.2.rar into the current working directory:
-
-jar xvf /opt/incubator-activemq-4.0.2/lib/optional/activemq-ra-4.0.2.rar
- created: META-INF/
- inflated: META-INF/MANIFEST.MF
- inflated: META-INF/DISCLAIMER.txt
- inflated: META-INF/LICENSE.txt
- inflated: META-INF/ra.xml
- inflated: broker-config.xml
- inflated: activemq-ra-4.0.2.jar
- inflated: activemq-core-4.0.2.jar
- inflated: activeio-core-3.0-beta4.jar
- inflated: derby-10.1.1.0.jar
- inflated: spring-1.2.6.jar
- inflated: xbean-spring-2.2.jar
- inflated: commons-logging-1.1.jar
- inflated: geronimo-j2ee-management\_1.0\_spec-1.0.jar
- inflated: backport-util-concurrent-2.1.jar
- inflated: log4j-1.2.12.jar
- inflated: META-INF/DISCLAIMER.txt
- inflated: META-INF/LICENSE.txt
-
-Below is a quick listing of the contents of that directory:
-
-$ ls -l
-total 12848
-drwxr-xr-x 6 bsnyder bsnyder 204 Oct 16 16:27 META-INF
--rw-r--r-- 1 bsnyder bsnyder 232107 Oct 16 16:27 activeio-core-3.0-beta4.jar
--rw-r--r-- 1 bsnyder bsnyder 1351744 Oct 16 16:27 activemq-core-4.0.2.jar
--rw-r--r-- 1 bsnyder bsnyder 70023 Oct 16 16:27 activemq-ra-4.0.2.jar
--rw-r--r-- 1 bsnyder bsnyder 329586 Oct 16 16:27 backport-util-concurrent-2.1.jar
--rw-r--r-- 1 bsnyder bsnyder 2334 Oct 16 16:27 broker-config.xml
--rw-r--r-- 1 bsnyder bsnyder 52915 Oct 16 16:27 commons-logging-1.1.jar
--rw-r--r-- 1 bsnyder bsnyder 2143211 Oct 16 16:27 derby-10.1.1.0.jar
--rw-r--r-- 1 bsnyder bsnyder 16030 Oct 16 16:27 geronimo-j2ee-management\_1.0\_spec-1.0.jar
--rw-r--r-- 1 bsnyder bsnyder 358085 Oct 16 16:27 log4j-1.2.12.jar
--rw-r--r-- 1 bsnyder bsnyder 1901653 Oct 16 16:27 spring-1.2.6.jar
--rw-r--r-- 1 bsnyder bsnyder 94713 Oct 16 16:27 xbean-spring-2.2.jar
-
-Now it's time to configure ActiveMQ.
-
-Configuring Apache ActiveMQ
----------------------------
-
-The fifth step is to actually configure ActiveMQ for integration with JBoss. Remember that you should be sitting in the following directory:
-
-/opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-
-You may or may not have installed JBoss in `/opt`, that doesn't particularly matter. What does matter is that you're sitting in the directory that was created above to hold the contents of the expanded ActiveMQ RAR file.
-
-**_NOTE:_** A RAR file is a Resource adapter ARchive (RAR). Resource adapters are a concept from the [J2EE Connector Architecture (JCA)](http://java.sun.com/j2ee/connector/) and are used to interface with Enterprise Information Systems (EIS), i.e., systems external to the application server (e.g., relational databases, mainframes, MOMs, accounting systems, etc.). Resource adapters are often referred to as J2EE connectors and are very similar to the concept of a device driver for, say, a [...]
-
-Version 1.0 Contracts
-
-In version 1.0 of the Connector Architecture, three contracts are defined to address the functions mentioned above:
-
-* Connection Management Contract: Lets applications connect to an EIS through the resource adapter. It also allows the application server to pool connection requests to the EIS.
-* Transaction Management Contract: Allows an application to manage and perform transactional access across one-to-many EIS resource managers.
-* Security Contract: Provides support for secure access to the EIS.
-
-New Contracts in Version 1.5
-
-In version 1.5 of the J2EE Connector Architecture, there are more contracts that a resource adapter must support, as new functionality and features made their way into the specification. A resource adapter can support these four new contracts by implementing the required interfaces defined in the specification for each contract.
-
-* Lifecycle Management Contract: Lets the application server manage the lifecycle – that is, the startup and shutdown functionality – of the resource adapter.
-* Work Management Contract: Allows the resource adapter to do work by submitting it to an application server for execution. Since the application server does the work for the resource adapter, the resource adapter needn't worry about thread management. Instead, the application server manages this aspect efficiently and can use thread pooling if necessary. Although the work management contract is not required (the resource adapter can choose to manage its own thread for work), it is def [...]
-* Transaction Inflow Contract: Allows a resource adapter to propagate an imported transaction to an application server, as well as flow-in transaction completion and crash recovery initiated by an EIS.
-* Message Inflow Contract: Allows the resource adapter to synchronously or asynchronously deliver messages to endpoints in the application server, irrespective of message style, semantics, and infrastructure.
-
-Quoted from [What's New in the J2EE Connector Architecture 1.5](http://java.sun.com/developer/technicalArticles/J2EE/connectorarch1_5/)
-
-For more information about JCA, please consult the [J2EE Connector Architecture documentation](http://java.sun.com/j2ee/connector/index.jsp).
-
-Open the `META-INF/ra.xml` file and look for the following section:
-
-**META-INF/ra.xml**
-
-<config-property>
- <description>
- The URL to the ActiveMQ server that you want this connection to connect to. If using
- an embedded broker, this value should be 'vm://localhost'.
- </description>
- <config-property-name>ServerUrl</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <config-property-value>tcp://localhost:61616</config-property-value>
-<!\-\- <config-property-value>vm://localhost</config-property-value> -->
- </config-property>
-
-The section above is used to tell the ActiveMQ RAR where ActiveMQ is located. By default, the in-VM protocol is commented out in favor of the tcp protocol. This will find ActiveMQ running on any interface on the localhost on port 61616. It's ok to just leave this alone if you don't mind the inefficiency of communicating within the JVM via TCP. However, it is recommended that `vm://` transport be used for an embedded broker, so comment out the `tcp://` transport and uncomment the `vm://` [...]
-
-**META-INF/ra.xml**
-
-<config-property>
- <description>
- The URL to the ActiveMQ server that you want this connection to connect to. If using
- an embedded broker, this value should be 'vm://localhost'.
- </description>
- <config-property-name>ServerUrl</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <!\-\- <config-property-value>tcp://localhost:61616</config-property-value> -->
- <config-property-value>vm://localhost</config-property-value>
- </config-property>
-
-Because we're embedding ActiveMQ inside of JBoss, it is more efficient to use the `vm://` transport, rather than to perform messaging over the `tcp://` transport.
-
-Now look further down the `META-INF/ra.xml` file and locate the following section:
-
-**META-INF/ra.xml**
-
-<config-property>
- <description>
- Sets the XML configuration file used to configure the embedded ActiveMQ broker via
- Spring if using embedded mode.
-
- BrokerXmlConfig is the filename which is assumed to be on the classpath unless
- a URL is specified. So a value of foo/bar.xml would be assumed to be on the
- classpath whereas file:dir/file.xml would use the file system.
- Any valid URL string is supported.
- </description>
- <config-property-name>BrokerXmlConfig</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <config-property-value></config-property-value>
- <!--
- <config-property-value>xbean:broker-config.xml</config-property-value>
- -->
- </config-property>
-
-The section above needs to be changed to uncomment the second to last line and remove/replace the empty element that is above it. Below is an example of how this should be changed:
-
-**META-INF/ra.xml**
-
-<config-property>
- <description>
- Sets the XML configuration file used to configure the embedded ActiveMQ broker via
- Spring if using embedded mode.
-
- BrokerXmlConfig is the filename which is assumed to be on the classpath unless
- a URL is specified. So a value of foo/bar.xml would be assumed to be on the
- classpath whereas file:dir/file.xml would use the file system.
- Any valid URL string is supported.
- </description>
- <config-property-name>BrokerXmlConfig</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <config-property-value>xbean:broker-config.xml</config-property-value>
- </config-property>
-
-This change tells the ActiveMQ RAR to read a configuration file named `broker-config.xml` (the `xbean:` that proceeds the filename is simply a hint to class doing the reading of the configuration file) which is located on the CLASSPATH. In this case, the `broker-config.xml` file is located in the `activemq-ra.rar` directory. Save the changes to that file and then open the `broker-config.xml` file.
-
-The `broker-config.xml` file _is_ the ActiveMQ configuration file. This is the file used to configure ActiveMQ. The default contents of this file are usable, but should be customized to suit your environment. There are several items of note about this configuration. The most prominent sections to note in this file are the `<persistenceAdapter>` element and the `<transportConnectors>` and `<networkConnectors>` elements as seen below:
-
-**broker-config.xml**
-
-<beans xmlns="http://activemq.org/config/1.0">
-
- <broker useJmx="true">
- ...
- <persistenceAdapter>
- <journaledJDBC journalLogFiles="5" dataDirectory="activemq-data"/>
- <!\-\- To use a different datasource, use th following syntax : -->
- <!--
- <journaledJDBC journalLogFiles="5" dataDirectory="../data" dataSource="#postgres-ds"/>
- -->
- </persistenceAdapter>
-
- <transportConnectors>
- <!\-\- prefixing a connector with discovery: causes the connector to be advertiesed over rendezvous -->
- <transportConnector uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
- </transportConnectors>
-
- <networkConnectors>
- <!\-\- by default just auto discover the other brokers -->
- <networkConnector uri="multicast://default"/>
- <!--
- <networkConnector uri="static://(tcp://host1:61616,tcp://host2:61616)"/>
- -->
- </networkConnectors>
-
- </broker>
-
-</beans>
-
-The first change to this file is to add the brokerName attribute to the broker element and provide a name:
-
-<broker useJmx="true" brokerName="bruce.broker1">
-
-In addition, this same name is used further down the configuration to provide a name for the `<transportConnector>` element:
-
-<transportConnector name="bruce.broker1" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
-
-Now we'll tell ActiveMQ not to initialize JMX because we'll use the existing one that JBoss has:
-
-<!\-\- put the following as the first child of the broker tag -->
-<managementContext><!-- we'll use an existing one (JBoss) instead of creating one -->
- <managementContext createConnector="false"/>
-</managementContext>
-
-The `<persistenceAdapter>` element should be reconfigured to store its data in an appropriate place. On JBoss, that's most likely within the "data" directory of the server configuration you're using. We're going to set this dynamically using an XBean and Spring feature that allows us to inject system properties values into the configuration. First this needs to be enabled:
-
-<!\-\- put the following as the first child of the beans element -->
-<bean xmlns="" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
-
-Now, modify the `dataDirectory` attribute of the `journaledJDBC` element to be the following: `${jboss.server.data.dir}/activemq`.
-
-The `<transportConnectors>` element is used to advertise the ActiveMQ broker for client-to-broker communications and the `<networkConnectors>` element advertises the ActiveMQ broker for broker-to-broker communications. The default configuration is to use the ActiveMQ [multicast transport](http://www.activemq.org/siteUsing ActiveMQ/Configuring Transports/ActiveMQ Connection URIs/multicast-transport-reference.md) for both. This is simply an easy configuration under which to get ActiveMQ up [...]
-
-**_NOTE:_** There are far more configuration options available for ActiveMQ than are noted here. The configuration above is only enough to just get ActiveMQ up and running, nothing more. For more information on the ActiveMQ configuration, see the [ActiveMQ 4.1 XML Reference](http://www.activemq.org/siteUsing ActiveMQ/Xml ReferenceUsing ActiveMQ/Xml Reference/Using ActiveMQ/Xml Reference/xbean-xml-reference-41.md).
-
-Now we just need to start up JBoss to assure that it comes up correctly without error using the same commands we used previously to start JBoss:
-
-$ cd jboss-4.0.4.GA
-$ ./bin/run.sh -c default
-=========================================================================
-
- JBoss Bootstrap Environment
-
- JBOSS_HOME: /opt/jboss-4.0.4.GA
-
- JAVA: java
-
- JAVA_OPTS: -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000
--Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh
-
- CLASSPATH: /opt/jboss-4.0.4.GA/bin/run.jar:/lib/tools.jar
-
-=========================================================================
-
-15:34:47,999 INFO \[Server\] Starting JBoss (MX MicroKernel)...
-15:34:48,001 INFO \[Server\] Release ID: JBoss \[Zion\] 4.0.4.GA (build: CVSTag=JBoss\_4\_0\_4\_GA date=200605151000)
-15:34:48,004 INFO \[Server\] Home Dir: /opt/jboss-4.0.4.GA
-15:34:48,005 INFO \[Server\] Home URL: file:/opt/jboss-4.0.4.GA/
-15:34:48,007 INFO \[Server\] Patch URL: null
-15:34:48,007 INFO \[Server\] Server Name: default
-15:34:48,007 INFO \[Server\] Server Home Dir: /opt/jboss-4.0.4.GA/server/default
-15:34:48,011 INFO \[Server\] Server Home URL: file:/opt/jboss-4.0.4.GA/server/default/
-15:34:48,012 INFO \[Server\] Server Log Dir: /opt/jboss-4.0.4.GA/server/default/log
-15:34:48,017 INFO \[Server\] Server Temp Dir: /opt/jboss-4.0.4.GA/server/default/tmp
-15:34:48,022 INFO \[Server\] Root Deployment Filename: jboss-service.xml
-...
-15:35:17,360 INFO \[Server\] JBoss (MX MicroKernel) \[4.0.4.GA (build: CVSTag=JBoss\_4\_0\_4\_GA date=200605151000)\]
-Started in 28s:576ms
-
-As long as JBoss comes up without error, you're ready to move on to the next step.
-
-Configuring JBoss
------------------
-
-The sixth step is to configure JBoss to initialize and start ActiveMQ whenever JBoss starts up. This is accomplished using an XML file that abides by the [JBoss JCA DTD](http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd) for data sources. Like most other Java application servers on the market, the JBoss architecture uses the J2EE Connector Architecture to manage connections of any kind including JDBC, JMS, etc. and the JBoss JCA DTD denotes the allowed contents for creating an XML data sour [...]
-
-**activemq-jms-ds.xml**
-
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!DOCTYPE connection-factories
- PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN"
- "http://www.jboss.org/j2ee/dtd/jboss-ds\_1\_5.dtd">
-
-<connection-factories>
-
- <tx-connection-factory>
- <jndi-name>activemq/QueueConnectionFactory</jndi-name>
- <xa-transaction/>
- <track-connection-by-tx/>
- <rar-name>activemq-ra.rar</rar-name>
- <connection-definition>javax.jms.QueueConnectionFactory</connection-definition>
- <ServerUrl>vm://localhost</ServerUrl>
- <!--
- <UserName>sa</UserName>
- <Password></Password>
- -->
- <min-pool-size>1</min-pool-size>
- <max-pool-size>200</max-pool-size>
- <blocking-timeout-millis>30000</blocking-timeout-millis>
- <idle-timeout-minutes>3</idle-timeout-minutes>
- </tx-connection-factory>
-
- <tx-connection-factory>
- <jndi-name>activemq/TopicConnectionFactory</jndi-name>
- <xa-transaction/>
- <track-connection-by-tx/>
- <rar-name>activemq-ra.rar</rar-name>
- <connection-definition>javax.jms.TopicConnectionFactory</connection-definition>
- <ServerUrl>vm://localhost</ServerUrl>
- <!--
- <UserName>sa</UserName>
- <Password></Password>
- -->
- <min-pool-size>1</min-pool-size>
- <max-pool-size>200</max-pool-size>
- <blocking-timeout-millis>30000</blocking-timeout-millis>
- <idle-timeout-minutes>3</idle-timeout-minutes>
- </tx-connection-factory>
-
- <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.queue:name=outboundQueue">
- <attribute name="JNDIName">activemq/queue/outbound</attribute>
- <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends>
- <attribute name="Type">javax.jms.Queue</attribute>
- <attribute name="Properties">PhysicalName=queue.outbound</attribute>
- </mbean>
-
- <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.topic:name=inboundTopic">
- <attribute name="JNDIName">activemq/topic/inbound</attribute>
- <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends>
- <attribute name="Type">javax.jms.Topic</attribute>
- <attribute name="Properties">PhysicalName=topic.inbound</attribute>
- </mbean>
-
-</connection-factories>
-
-This XML instance configures a JMS `QueueConnectionFactory` and a JMS `TopicConnectionFactory` and makes them available via JNDI. Also defined in this file are some {{AdminObject}}s which are used to specify a topic and a queue. This file should be dropped into the JBoss deploy directory. Its name (*-ds.xml) will cause it to be picked up by the JBoss deployer upon startup. Speaking of which, once this file is in place, a quick smoke test can be performed by simply starting up the JBoss s [...]
-
-=========================================================================
-
- JBoss Bootstrap Environment
-
- JBOSS_HOME: /opt/jboss
-
- JAVA: java
-
- JAVA_OPTS: -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000
--Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh
-
- CLASSPATH: /opt/jboss/bin/run.jar:/lib/tools.jar
-
-=========================================================================
-
-22:55:48,686 INFO \[Server\] Starting JBoss (MX MicroKernel)...
-22:55:48,688 INFO \[Server\] Release ID: JBoss \[Zion\] 4.0.4.GA (build: CVSTag=JBoss\_4\_0\_4\_GA date=200605151000)
-22:55:48,690 INFO \[Server\] Home Dir: /opt/jboss-4.0.4.GA
-22:55:48,692 INFO \[Server\] Home URL: file:/opt/jboss-4.0.4.GA/
-22:55:48,695 INFO \[Server\] Patch URL: null
-22:55:48,697 INFO \[Server\] Server Name: default
-22:55:48,698 INFO \[Server\] Server Home Dir: /opt/jboss-4.0.4.GA/server/default
-22:55:48,701 INFO \[Server\] Server Home URL: file:/opt/jboss-4.0.4.GA/server/default/
-22:55:48,702 INFO \[Server\] Server Log Dir: /opt/jboss-4.0.4.GA/server/default/log
-22:55:48,704 INFO \[Server\] Server Temp Dir: /opt/jboss-4.0.4.GA/server/default/tmp
-22:55:48,706 INFO \[Server\] Root Deployment Filename: jboss-service.xml
-22:55:49,092 INFO \[ServerInfo\] Java version: 1.5.0_06,Apple Computer, Inc.
-22:55:49,101 INFO \[ServerInfo\] Java VM: Java HotSpot(TM) Server VM 1.5.0_06-64,"Apple Computer, Inc."
-22:55:49,102 INFO \[ServerInfo\] OS-System: Mac OS X 10.4.8,i386
-22:55:49,803 INFO \[Server\] Core system initialized
-22:55:53,379 INFO \[WebService\] Using RMI server codebase: http://rattlesnake:8083/
-22:55:53,400 INFO \[Log4jService$URLWatchTimerTask\] Configuring from URL: resource:log4j.xml
-22:55:54,034 INFO \[NamingService\] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50,
-no client SocketFactory, Server SocketFactory=class
-org.jboss.net.sockets.DefaultSocketFactory
-22:55:58,475 INFO \[Embedded\] Catalina naming disabled
-22:55:58,566 INFO \[ClusterRuleSetFactory\] Unable to find a cluster rule set in the classpath.
-Will load the default rule set.
-22:55:58,569 INFO \[ClusterRuleSetFactory\] Unable to find a cluster rule set in the classpath.
-Will load the default rule set.
-22:55:59,110 INFO \[Http11BaseProtocol\] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
-22:55:59,114 INFO \[Catalina\] Initialization processed in 545 ms
-22:55:59,116 INFO \[StandardService\] Starting service jboss.web
-22:55:59,121 INFO \[StandardEngine\] Starting Servlet Engine: Apache Tomcat/5.5.17
-22:55:59,179 INFO \[StandardHost\] XML validation disabled
-22:55:59,221 INFO \[Catalina\] Server startup in 105 ms
-22:55:59,600 INFO \[TomcatDeployer\] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
-22:55:59,874 INFO \[WebappLoader\] Dual registration of jndi stream handler: factory already defined
-22:56:00,899 INFO \[TomcatDeployer\] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
-22:56:01,700 INFO \[TomcatDeployer\] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp60528jbossws-exp.war/
-22:56:01,891 INFO \[SubscriptionManager\] Bound event dispatcher to java:/EventDispatcher
-22:56:02,203 INFO \[TomcatDeployer\] deploy, ctxPath=/jbossmq-httpil,
-warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
-22:56:04,546 INFO \[TomcatDeployer\] deploy, ctxPath=/web-console,
-warUrl=.../deploy/management/console-mgr.sar/web-console.war/
-22:56:05,690 INFO \[MailService\] Mail Service bound to java:/Mail
-22:56:07,215 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/activemq-ra.rar/
-22:56:07,452 INFO \[XBeanXmlBeanDefinitionReader\] Loading XML bean definitions from class
-path resource \[broker-config.xml\]
-22:56:07,750 INFO \[ClassPathXmlApplicationContext\] Bean factory for application context
-\[org.apache.xbean.spring.context.ClassPathXmlApplicationContext;hashCode=13887543\]:
-org.springframework.beans.factory.support.DefaultListableBeanFactory defining
-beans \[org.apache.activemq.xbean.XBeanBrokerService\]; root of BeanFactory hierarchy
-22:56:07,765 INFO \[ClassPathXmlApplicationContext\] 1 beans defined in application context
-\[org.apache.xbean.spring.context.ClassPathXmlApplicationContext;hashCode=13887543\]
-22:56:07,773 INFO \[CollectionFactory\] JDK 1.4+ collections available
-22:56:07,778 INFO \[ClassPathXmlApplicationContext\] Unable to locate MessageSource with name
-'messageSource': using default
-\[org.springframework.context.support.DelegatingMessageSource@5fee96\]
-22:56:07,781 INFO \[ClassPathXmlApplicationContext\] Unable to locate ApplicationEventMulticaster
-with name 'applicationEventMulticaster': using default
-\[org.springframework.context.event.SimpleApplicationEventMulticaster@78c714\]
-22:56:07,783 INFO \[DefaultListableBeanFactory\] Pre-instantiating singletons in factory
- \[org.springframework.beans.factory.support.DefaultListableBeanFactory
-defining beans \[org.apache.activemq.xbean.XBeanBrokerService\]; root of BeanFactory hierarchy\]
-22:56:08,181 INFO \[BrokerService\] ActiveMQ 4.0.2 JMS Message Broker (bruce.broker1) is starting
-22:56:08,181 INFO \[BrokerService\] For help or more information please see:
-http://incubator.apache.org/activemq/
-22:56:09,989 INFO \[JDBCPersistenceAdapter\] Database driver recognized:
-\[apache\_derby\_embedded\_jdbc\_driver\]
-22:56:11,026 INFO \[JournalPersistenceAdapter\] Journal Recovery Started from: Active Journal:
-using 5 x 20.0 Megs at: /opt/jboss-4.0.4.GA/activemq-data/journal
-22:56:11,169 INFO \[JournalPersistenceAdapter\] Journal Recovered: 0 message(s) in transactions recovered.
-22:56:11,489 INFO \[TransportServerThreadSupport\] Listening for connections at: tcp://rattlesnake:61616
-22:56:11,491 WARN \[MulticastDiscoveryAgent\] brokerName not set
-22:56:11,519 INFO \[TransportConnector\] Connector bruce.broker1 Started
-22:56:11,522 INFO \[NetworkConnector\] Network Connector bridge Started
-22:56:11,522 INFO \[BrokerService\] ActiveMQ JMS Message Broker
-(bruce.broker1, ID:rattlesnake-59052-1161060967859-1:0) started
-22:56:11,556 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jboss-ha-local-jdbc.rar
-22:56:11,599 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jboss-ha-xa-jdbc.rar
-22:56:11,623 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jboss-local-jdbc.rar
-22:56:11,647 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jboss-xa-jdbc.rar
-22:56:11,737 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jms/jms-ra.rar
-22:56:11,847 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/mail-ra.rar
-22:56:12,251 INFO \[ConnectionFactoryBindingService\] Bound ConnectionManager
-'jboss.jca:service=ConnectionFactoryBinding,name=activemq/QueueConnectionFactory' to
-JNDI name 'java:activemq/QueueConnectionFactory'
-22:56:12,258 INFO \[ConnectionFactoryBindingService\] Bound ConnectionManager
-'jboss.jca:service=ConnectionFactoryBinding,name=activemq/TopicConnectionFactory' to
-JNDI name 'java:activemq/TopicConnectionFactory'
-22:56:12,265 INFO \[AdminObject\] Bound admin object 'org.apache.activemq.command.ActiveMQQueue'
-at 'activemq/queue/outbound'
-22:56:12,330 INFO \[AdminObject\] Bound admin object 'org.apache.activemq.command.ActiveMQTopic'
-at 'activemq/topic/inbound'
-22:56:13,246 INFO \[ConnectionFactoryBindingService\] Bound ConnectionManager
-'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
-22:56:13,842 INFO \[A\] Bound to JNDI name: queue/A
-22:56:13,845 INFO \[B\] Bound to JNDI name: queue/B
-22:56:13,846 INFO \[C\] Bound to JNDI name: queue/C
-22:56:13,848 INFO \[D\] Bound to JNDI name: queue/D
-22:56:13,850 INFO \[ex\] Bound to JNDI name: queue/ex
-22:56:13,876 INFO \[testTopic\] Bound to JNDI name: topic/testTopic
-22:56:13,879 INFO \[securedTopic\] Bound to JNDI name: topic/securedTopic
-22:56:13,880 INFO \[testDurableTopic\] Bound to JNDI name: topic/testDurableTopic
-22:56:13,883 INFO \[testQueue\] Bound to JNDI name: queue/testQueue
-22:56:13,994 INFO \[UILServerILService\] JBossMQ UIL service available at : /0.0.0.0:8093
-22:56:14,055 INFO \[DLQ\] Bound to JNDI name: queue/DLQ
-22:56:14,375 INFO \[ConnectionFactoryBindingService\] Bound ConnectionManager
-'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
-22:56:14,525 INFO \[TomcatDeployer\] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
-22:56:14,991 INFO \[Http11BaseProtocol\] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
-22:56:15,071 INFO \[ChannelSocket\] JK: ajp13 listening on /0.0.0.0:8009
-22:56:15,082 INFO \[JkMain\] Jk running ID=0 time=0/25 config=null
-22:56:15,108 INFO \[Server\] JBoss (MX MicroKernel) \[4.0.4.GA (build: CVSTag=JBoss\_4\_0\_4\_GA date=200605151000)\]
-Started in 26s:398ms
-
-Note the startup messages from both ActiveMQ and from the `AdminObject}}s creating an {{ActiveMQQueue` and an `ActiveMQTopic`. These are good indications that the configuration is correct, but needs to be verified a bit further. This is covered in the next section.
-
-Testing the Integration
------------------------
-
-The seventh and final step is to perform a slightly more comprehensive smoke test of the integration. This can be accomplished using Apache Ant via the examples that come with the ActiveMQ binary distribution. An Ant build.xml file is included which provides easy access to a simple consumer and a simple producer. The producer will be used to send messages that are received by the consumer. To proceed with this testing, just follow the steps below:
-
-1. In the first terminal, start up JBoss. The same startup script can be used here as was used above.
-2. In the second terminal, use the commands below to run the ActiveMQ consumer:
-
- $ cd /opt/incubator-activemq-4.0.2/examples #note in activemq v5 the directory is just "example" not "examples"
- $ ant consumer
- Buildfile: build.xml
-
- init:
- \[mkdir\] Created dir: /opt/incubator-activemq-4.0.2/example/target/classes
- \[mkdir\] Created dir: /opt/incubator-activemq-4.0.2/example/src/ddl
-
- compile:
- \[javac\] Compiling 6 source files to /opt/incubator-activemq-4.0.2/example/target/classes
-
- consumer:
- \[echo\] Running consumer against server at $url = tcp://localhost:61616 for subject $subject = TEST.FOO
- \[java\] Connecting to URL: tcp://localhost:61616
- \[java\] Consuming queue: TEST.FOO
- \[java\] Using non-durable subscription
- \[java\] We are about to wait until we consume: 10 message(s) then we will shutdown
-
-3. In the third terminal, use the commands below to run the ActiveMQ producer:
-
- $ cd /opt/incubator-activemq-4.0.2/examples
- $ ant producer
- Buildfile: build.xml
-
- init:
-
- compile:
-
- producer:
- \[echo\] Running producer against server at $url = tcp://localhost:61616 for subject $subject = TEST.FOO
- \[java\] Connecting to URL: tcp://localhost:61616
- \[java\] Publishing a Message with size 1000 to queue: TEST.FOO
- \[java\] Using non-durable publishing
- \[java\] Sleeping between publish 0 ms
- \[java\] Sending message: Message: 0 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 1 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 2 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 3 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 4 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 5 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 6 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 7 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 8 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 9 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Done.
- \[java\] connection {
- \[java\] session {
- \[java\] messageCount{ count: 10 unit: count startTime: 1161062468001 lastSampleTime:
- 1161062468340 description: Number of messages exchanged }
- \[java\] messageRateTime{ count: 10 maxTime: 142 minTime: 1 totalTime: 315 averageTime: 31.5
- averageTimeExMinMax: 21.5 averagePerSecond: 31.746031746031747
- averagePerSecondExMinMax: 46.51162790697674 unit: millis startTime: 1161062468002 lastSampleTime:
- 1161062468340 description: Time taken to process a message (thoughtput rate) }
- \[java\] pendingMessageCount{ count: 0 unit: count startTime: 1161062468001 lastSampleTime:
- 1161062468001 description: Number of pending messages }
- \[java\] expiredMessageCount{ count: 0 unit: count startTime: 1161062468001 lastSampleTime:
- 1161062468001 description: Number of expired messages }
- \[java\] messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0
- averageTimeExMinMax: 0.0 averagePerSecond: 0.0
- averagePerSecondExMinMax: 0.0 unit: millis startTime: 1161062468002 lastSampleTime: 1161062468002
- description: Time spent by a message before being delivered }
- \[java\] durableSubscriptionCount{ count: 0 unit: count startTime: 1161062468002 lastSampleTime:
- 1161062468002 description: The number of durable
- subscriptions }
-
- \[java\] producers {
- \[java\] producer queue://TEST.FOO {
- \[java\] messageCount{ count: 10 unit: count startTime: 1161062468025 lastSampleTime:
- 1161062468340 description: Number of messages processed }
- \[java\] messageRateTime{ count: 10 maxTime: 142 minTime: 1 totalTime: 315 averageTime:
- 31.5 averageTimeExMinMax: 21.5 averagePerSecond:
- 31.746031746031747 averagePerSecondExMinMax: 46.51162790697674 unit: millis startTime: 1161062468025
- lastSampleTime: 1161062468340 description: Time taken to
- process a message (thoughtput rate) }
- \[java\] pendingMessageCount{ count: 0 unit: count startTime: 1161062468025 lastSampleTime:
- 1161062468025 description: Number of pending messages }
- \[java\] messageRateTime{ count: 10 maxTime: 142 minTime: 1 totalTime: 315 averageTime: 31.5
- averageTimeExMinMax: 21.5 averagePerSecond:
- 31.746031746031747 averagePerSecondExMinMax: 46.51162790697674 unit: millis startTime: 1161062468025
- lastSampleTime: 1161062468340 description: Time taken to
- process a message (thoughtput rate) }
- \[java\] expiredMessageCount{ count: 0 unit: count startTime: 1161062468025 lastSampleTime:
- 1161062468025 description: Number of expired messages }
- \[java\] messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0
- averageTimeExMinMax: 0.0 averagePerSecond: 0.0
- averagePerSecondExMinMax: 0.0 unit: millis startTime: 1161062468025 lastSampleTime: 1161062468025
- description: Time spent by a message before being delivered }
- \[java\] }
- \[java\] }
- \[java\] consumers {
- \[java\] }
- \[java\] }
- \[java\] }
-
-
-Step 1 above just starts up JBoss. Step 2 above starts up a simple message consumer that comes with ActiveMQ. Step 3 above starts up a simple message producer that comes with ActiveMQ. Though the message consumer and message producer are simple utilities, the each one accepts many parameters making them extremely useful for testing ActiveMQ configurations.
-
-To paraphrase, what just happened was that the message producer sent 10 messages to the TEST.FOO destination and the message consumer received 10 messages from the TEST.FOO destination. Despite being a simple test, it does utilize the ActiveMQ broker, albeit only on a single machine. The next logical step is to set up a full network of ActiveMQ brokers.
-
-After setting up one broker within one instance of JBoss, setting up another is made much easier, but requires another machine or operating system instance. But that's a whole separate article and something to address another day.
-
-Conclusion
-----------
-
-What has been demonstrated here is the integration of ActiveMQ with the JBoss application server. This integration is quite common and performed by many enterprises. I hope that this was helpful to people interested in the integration of ActiveMQ with JBoss application server. If you have any questions or are interested in consulting services surrounding ActiveMQ, please [contact us](http://www.logicblaze.com/contact.jsp) for more information.
-
-### Resources
-
-Below are the configurations for use with both Spring 1.x and Spring 2.x:
-
-
-
-
-
-[File](Connectivity/Containers/integrating-apache-activemq-with-jboss.md?sortBy=name&sortOrder=ascending)
-
-[Modified](Connectivity/Containers/integrating-apache-activemq-with-jboss.md?sortBy=date&sortOrder=descending)
-
-File [amq-spring-1.2.6.tgz](integrating-apache-activemq-with-jboss.data/amq-spring-1.2.6.tgz?api=v2 "Download")
-
-Oct 03, 2007 by [Bruce Snyder](https://cwiki.apache.org/confluence/display/~bsnyder)
-
-Labels
-
-* No labels
-* [Edit Labels](# "Edit Labels")
-
-Preview
-
-File [amq-spring-2.0.tgz](integrating-apache-activemq-with-jboss.data/amq-spring-2.0.tgz?api=v2 "Download")
-
-Oct 03, 2007 by [Bruce Snyder](https://cwiki.apache.org/confluence/display/~bsnyder)
-
-Labels
-
-* No labels
-* [Edit Labels](# "Edit Labels")
-
-Preview
-
-[Download All](/confluence/pages/downloadallattachments.action?pageId=67786 "Download all the latest versions of attachments on this page as single zip file.")
-
diff --git a/src/_documents/classic/Connectivity/Containers/j2ee.md b/src/_documents/classic/Connectivity/Containers/j2ee.md
deleted file mode 100644
index 48078c4..0000000
--- a/src/_documents/classic/Connectivity/Containers/j2ee.md
+++ /dev/null
@@ -1,56 +0,0 @@
-Apache ActiveMQ ™ -- J2EE
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [J2EE](../../Connectivity/Containers/j2ee.md)
-
-
-In J2EE 1.4 or later the standard way to integrate with a JMS provider is via JCA 1.5 and a [Resource Adapter](../../Connectivity/Containers/resource-adapter.md).
-
-Introduction
-------------
-
-ActiveMQ includes a Java Connector Architecture (JCA) 1.5 Resource Adapter. JCA 1.5 defines the contract between an J2EE application server and external resources such as databases and messaging middleware. It allows the application server to efficiently pool connections, control transactions and manage security. The Resource Adapter allows ActiveMQ to be used from any J2EE 1.4 application server. We have tested that the Resource Adapter works in the following J2EE 1.4 containers
-
-* [TomEE](http://tomee.apache.org/tomcat-/FAQ/jms.md) 1
-* Geronimo 1
-* GlassFish
-* JBoss 4
-* WebLogic 9
-* WebSphere 6
-
-Features
---------
-
-* Inbound connection delivers messages to MDBs via XA or local transactions.
-* Outbound connections support standard container pooling or can reuse the inbound connection/session to avoid XA.
-* JTA support: Can be enlisted in XA and local transactions.
-* XA transaction recovery via XAResource.recover() supported.
-* When used outside a JTA transaction, session transaction settings retain normal JMS semantics so that it be used by your web-app tier.
-* Can configure and start up embedded broker.
-* Can connect to external ActiveMQ broker or embedded broker.
-* Inbound message delivery supports fine grain control of concurrency and prefetching.
-* Batching so that multiple messages can be delivered within the same transaction for optimal performances.
-
-Downloading the RAR
--------------------
-
-The RAR is available via [maven central](http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22activemq-rar%22)
-
-Deployment Guides
-
-* [TomEE](../../Connectivity/Containers/Resource Adapter/tomee.md)
-* [Geronimo](../../Connectivity/Containers/geronimo.md)
-* [Integrating Apache ActiveMQ with Glassfish](../../Connectivity/Containers/integrating-apache-activemq-with-glassfish.md)
-* [JBoss Integration](../../Connectivity/Containers/jboss-integration.md)
-
-The use of an Embedded Broker
------------------------------
-
-The ActiveMQ Resource Adapter can connect to a remote broker using any of the available transports, or it can start up an embedded broker. As described in the [Resource Adapter Properties](../../Connectivity/Containers/Resource Adapter/resource-adapter-properties.md), you can enable an embedded broker using the **BrokerXmlConfig** property.
-
-Configuration Reference
------------------------
-
-* [Resource Adapter Properties](../../Connectivity/Containers/Resource Adapter/resource-adapter-properties.md)
-* [Connection Factory Properties](../../Connectivity/Containers/Resource Adapter/connection-factory-properties.md)
-* [Activation Spec Properties](../../Connectivity/Containers/Resource Adapter/activation-spec-properties.md)
-
diff --git a/src/_documents/classic/Connectivity/Containers/jboss-integration.md b/src/_documents/classic/Connectivity/Containers/jboss-integration.md
deleted file mode 100644
index 80736a0..0000000
--- a/src/_documents/classic/Connectivity/Containers/jboss-integration.md
+++ /dev/null
@@ -1,724 +0,0 @@
-Apache ActiveMQ ™ -- JBoss Integration
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [JBoss Integration](../../Connectivity/Containers/jboss-integration.md)
-
-
-Integrating Apache ActiveMQ with JBoss
-======================================
-
-Integration with application servers is a common scenario in the enterprise Java world, especially when it comes to messaging. [ActiveMQ](http://activemq.org/) is a JMS 1.1 compliant, open source, Apache Licensed, message oriented middleware (MOM) with [many](http://activemq.org/siteFeatures/New FeaturesFeatures/New Features/Features/New Features/changes-in-40.md), [many](http://activemq.org/siteFeatures/New Features/new-features-in-41.md) features far beyond the JMS specification. Activ [...]
-
-One of the application servers in the open source world is JBoss. A very common requirement is to configure ActiveMQ as the messaging infrastructure within JBoss. Although there is [a bit of documentation](http://www.activemq.org/siteConnectivity/ContainersConnectivity/Containers/Connectivity/Containers/jboss-integration.md) on this integration, this article seeks to provide much more detail and explanation. So if you have a need to integrate ActiveMQ with JBoss, this article is for you.
-
-This article explains how to configure JBoss to start up ActiveMQ as part of its lifecycle and how to configure the ActiveMQ resource adapter to handle the messaging and transactionality between ActiveMQ and JBoss.
-
-Requirements
-------------
-
-Below are the software requirements for this article with links to download each:
-
-* [Apache ActiveMQ 4.0.1+](http://activemq.org/siteOverviewOverview/Overview/download.md)
-* [JBoss 4.0.4+](http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=416591)
-* [Sun Java 1.5+](http://www.java.com/en/download/index.jsp)
-* [Apache Ant 1.6+](http://ant.apache.org/bindownload.cgi)
-
-Though this article is using Unix, the installation and integration will work on any platform running Sun Java. It is recommended that each piece of software be downloaded before working through the steps is this article. Once each piece of software has been downloaded, proceed to the first step.
-
-Install the J2SE 1.5
---------------------
-
-The first step in this process is to install Java 1.5 and verify that it runs correctly. Using the link above, find, download and install the correct version of Java for your platform. Once Java is installed and in the PATH, test it to see that it runs correctly using the following command:
-
-$ java -version
-java version "1.5.0_06"
-Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112)
-Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing)
-
-Depending upon your platform and the exact build number of Java 1.5, your output may vary slightly. As long as it's Java 1.5 and the version information is output, you should be ready to proceed to the next step.
-
-Install Apache Ant
-------------------
-
-The second step is to install Apache Ant. Simply download it using the link above, expand somewhere on your hard drive and place the `bin` directory in the PATH. This will allow you to test it quickly using the commands below:
-
-$ ant -version
-Apache Ant version 1.6.2 compiled on July 16 2004
-
-As long as you see the version output above, Ant should be usable. If you did not see the version output or received an error, consult the Ant documentation or mailing list archives to work out the issue. Please note that Ant is not used until the end of this whole exercise to test the integration.
-
-Install the JBoss Application Server
-------------------------------------
-
-The third step in this process is to install JBoss and make sure it runs correctly before installing and configuring ActiveMQ. Upon downloading JBoss-4.0.4, expand it in a place where it can create a directory. Next, run the server using the following commands:
-
-$ cd jboss-4.0.4.GA
-$ ./bin/run.sh -c default
-=========================================================================
-
- JBoss Bootstrap Environment
-
- JBOSS_HOME: /opt/jboss-4.0.4.GA
-
- JAVA: java
-
- JAVA_OPTS: -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000
--Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh
-
- CLASSPATH: /opt/jboss-4.0.4.GA/bin/run.jar:/lib/tools.jar
-
-=========================================================================
-
-15:34:47,999 INFO \[Server\] Starting JBoss (MX MicroKernel)...
-15:34:48,001 INFO \[Server\] Release ID: JBoss \[Zion\] 4.0.4.GA (build: CVSTag=JBoss\_4\_0\_4\_GA date=200605151000)
-15:34:48,004 INFO \[Server\] Home Dir: /opt/jboss-4.0.4.GA
-15:34:48,005 INFO \[Server\] Home URL: file:/opt/jboss-4.0.4.GA/
-15:34:48,007 INFO \[Server\] Patch URL: null
-15:34:48,007 INFO \[Server\] Server Name: default
-15:34:48,007 INFO \[Server\] Server Home Dir: /opt/jboss-4.0.4.GA/server/default
-15:34:48,011 INFO \[Server\] Server Home URL: file:/opt/jboss-4.0.4.GA/server/default/
-15:34:48,012 INFO \[Server\] Server Log Dir: /opt/jboss-4.0.4.GA/server/default/log
-15:34:48,017 INFO \[Server\] Server Temp Dir: /opt/jboss-4.0.4.GA/server/default/tmp
-15:34:48,022 INFO \[Server\] Root Deployment Filename: jboss-service.xml
-...
-15:35:17,360 INFO \[Server\] JBoss (MX MicroKernel) \[4.0.4.GA (build: CVSTag=JBoss\_4\_0\_4\_GA date=200605151000)\]
-Started in 22s:238ms
-
-The first few lines of output from the JBoss startup indicates the configuration being used but the last line is the most important one. It tells you that JBoss has been started successfully on your system. For an extra measure of assurance, visit [http://localhost:8080/web-console/](http://localhost:8080/web-console/) in a web browser to make sure you are able to see the JBoss web console. If you can see this console, everything should be ready to go.
-
-As a side note, the left-hand side of the web-console requires that the [Java plugin](http://java.sun.com/products/plugin/) be properly installed. This is supposed to take place when installing the J2SE, so if it did not work correctly for you, I suggest that you consult some documentation about any errors you may be seeing. The Java plugin is not required for JBoss or ActiveMQ to function properly, it is simply for the JBoss web-console.
-
-Once JBoss is installed properly, shut it down using either the shutdown script or by simply typing ctrl-c to activate the shutdown hook. Once it is shut down, proceed to the next step.
-
-Prepare for Integrating Apache ActiveMQ with the JBoss Application Server
--------------------------------------------------------------------------
-
-The fourth step is to prepare your environment for integrating ActiveMQ with JBoss. If you haven't done so already, download Apache ActiveMQ using the link above. As of the writing of this article, the latest released version is 4.0.2-RC4. Upon downloading this archive, expand it in a place where it can create a directory, preferably in the same location where JBoss was expanded. Verify that the ActiveMQ RAR file is included using the following commands:
-
-$ cd ./incubator-activemq-4.0.2.tar.gz
-$ jar tvf /opt/incubator-activemq-4.0.2/lib/optional/activemq-ra-4.0.2.rar
- 0 Mon Sep 25 19:00:50 MDT 2006 META-INF/
- 399 Mon Sep 25 19:00:48 MDT 2006 META-INF/MANIFEST.MF
- 523 Mon Sep 25 13:07:40 MDT 2006 META-INF/DISCLAIMER.txt
- 11359 Mon Sep 25 13:07:40 MDT 2006 META-INF/LICENSE.txt
- 20305 Mon Sep 25 13:07:40 MDT 2006 META-INF/ra.xml
- 2334 Mon Sep 25 13:07:40 MDT 2006 broker-config.xml
- 70023 Mon Sep 25 19:00:48 MDT 2006 activemq-ra-4.0.2.jar
-1351744 Mon Sep 25 19:00:14 MDT 2006 activemq-core-4.0.2.jar
-232107 Mon Sep 25 18:22:48 MDT 2006 activeio-core-3.0-beta4.jar
-2143211 Tue Aug 01 11:44:50 MDT 2006 derby-10.1.1.0.jar
-1901653 Tue Aug 01 11:47:08 MDT 2006 spring-1.2.6.jar
- 94713 Tue Aug 01 11:47:22 MDT 2006 xbean-spring-2.2.jar
- 52915 Tue Aug 01 12:22:16 MDT 2006 commons-logging-1.1.jar
- 16030 Tue Aug 01 12:22:32 MDT 2006 geronimo-j2ee-management\_1.0\_spec-1.0.jar
-329586 Tue Aug 01 12:22:54 MDT 2006 backport-util-concurrent-2.1.jar
-358085 Tue Aug 01 12:23:26 MDT 2006 log4j-1.2.12.jar
- 523 Mon Sep 25 19:00:50 MDT 2006 META-INF/DISCLAIMER.txt
- 11359 Mon Sep 25 19:00:50 MDT 2006 META-INF/LICENSE.txt
-
-This is simply a table of contents of the RAR file. There should only be one reason that this will fail - an incomplete download of the ActiveMQ tarball or zip file. Beyond that, depending on the version you download, some of the library versions may be slightly different.
-
-Now go back to the JBoss installation and create a directory for ActiveMQ in the JBoss deploy directory for the default JBoss context. Below are the commands to achieve this task:
-
-$ mkdir /opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-$ cd /opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-$ pwd
-/opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-
-**_NOTE:_** The creation of a directory is not required but is the easiest way to set up the ActiveMQ RAR when you're just getting started. This is due to the flexibility it affords during the development phase for the configuration to be changed very easily. The alternative is to JAR up the directory as a RAR file once the configuration is solid enough that it no longer needs to be changed. But leaving everything in a directory during development is the easiest path.
-
-Now expand the activemq-ra-4.0.2.rar into the current working directory:
-
-jar xvf /opt/incubator-activemq-4.0.2/lib/optional/activemq-ra-4.0.2.rar
- created: META-INF/
- inflated: META-INF/MANIFEST.MF
- inflated: META-INF/DISCLAIMER.txt
- inflated: META-INF/LICENSE.txt
- inflated: META-INF/ra.xml
- inflated: broker-config.xml
- inflated: activemq-ra-4.0.2.jar
- inflated: activemq-core-4.0.2.jar
- inflated: activeio-core-3.0-beta4.jar
- inflated: derby-10.1.1.0.jar
- inflated: spring-1.2.6.jar
- inflated: xbean-spring-2.2.jar
- inflated: commons-logging-1.1.jar
- inflated: geronimo-j2ee-management\_1.0\_spec-1.0.jar
- inflated: backport-util-concurrent-2.1.jar
- inflated: log4j-1.2.12.jar
- inflated: META-INF/DISCLAIMER.txt
- inflated: META-INF/LICENSE.txt
-
-Below is a quick listing of the contents of that directory:
-
-$ ls -l
-total 12848
-drwxr-xr-x 6 bsnyder bsnyder 204 Oct 16 16:27 META-INF
--rw-r--r-- 1 bsnyder bsnyder 232107 Oct 16 16:27 activeio-core-3.0-beta4.jar
--rw-r--r-- 1 bsnyder bsnyder 1351744 Oct 16 16:27 activemq-core-4.0.2.jar
--rw-r--r-- 1 bsnyder bsnyder 70023 Oct 16 16:27 activemq-ra-4.0.2.jar
--rw-r--r-- 1 bsnyder bsnyder 329586 Oct 16 16:27 backport-util-concurrent-2.1.jar
--rw-r--r-- 1 bsnyder bsnyder 2334 Oct 16 16:27 broker-config.xml
--rw-r--r-- 1 bsnyder bsnyder 52915 Oct 16 16:27 commons-logging-1.1.jar
--rw-r--r-- 1 bsnyder bsnyder 2143211 Oct 16 16:27 derby-10.1.1.0.jar
--rw-r--r-- 1 bsnyder bsnyder 16030 Oct 16 16:27 geronimo-j2ee-management\_1.0\_spec-1.0.jar
--rw-r--r-- 1 bsnyder bsnyder 358085 Oct 16 16:27 log4j-1.2.12.jar
--rw-r--r-- 1 bsnyder bsnyder 1901653 Oct 16 16:27 spring-1.2.6.jar
--rw-r--r-- 1 bsnyder bsnyder 94713 Oct 16 16:27 xbean-spring-2.2.jar
-
-Now it's time to configure ActiveMQ.
-
-Configuring Apache ActiveMQ
----------------------------
-
-The fifth step is to actually configure ActiveMQ for integration with JBoss. Remember that you should be sitting in the following directory:
-
-/opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-
-You may or may not have installed JBoss in `/opt`, that doesn't particularly matter. What does matter is that you're sitting in the directory that was created above to hold the contents of the expanded ActiveMQ RAR file.
-
-**_NOTE:_** A RAR file is a Resource adapter ARchive (RAR). Resource adapters are a concept from the [J2EE Connector Architecture (JCA)](http://java.sun.com/j2ee/connector/) and are used to interface with Enterprise Information Systems (EIS), i.e., systems external to the application server (e.g., relational databases, mainframes, MOMs, accounting systems, etc.). Resource adapters are often referred to as J2EE connectors and are very similar to the concept of a device driver for, say, a [...]
-
-Version 1.0 Contracts
-
-In version 1.0 of the Connector Architecture, three contracts are defined to address the functions mentioned above:
-
-* Connection Management Contract: Lets applications connect to an EIS through the resource adapter. It also allows the application server to pool connection requests to the EIS.
-* Transaction Management Contract: Allows an application to manage and perform transactional access across one-to-many EIS resource managers.
-* Security Contract: Provides support for secure access to the EIS.
-
-New Contracts in Version 1.5
-
-In version 1.5 of the J2EE Connector Architecture, there are more contracts that a resource adapter must support, as new functionality and features made their way into the specification. A resource adapter can support these four new contracts by implementing the required interfaces defined in the specification for each contract.
-
-* Lifecycle Management Contract: Lets the application server manage the lifecycle – that is, the startup and shutdown functionality – of the resource adapter.
-* Work Management Contract: Allows the resource adapter to do work by submitting it to an application server for execution. Since the application server does the work for the resource adapter, the resource adapter needn't worry about thread management. Instead, the application server manages this aspect efficiently and can use thread pooling if necessary. Although the work management contract is not required (the resource adapter can choose to manage its own thread for work), it is def [...]
-* Transaction Inflow Contract: Allows a resource adapter to propagate an imported transaction to an application server, as well as flow-in transaction completion and crash recovery initiated by an EIS.
-* Message Inflow Contract: Allows the resource adapter to synchronously or asynchronously deliver messages to endpoints in the application server, irrespective of message style, semantics, and infrastructure.
-
-Quoted from [What's New in the J2EE Connector Architecture 1.5](http://java.sun.com/developer/technicalArticles/J2EE/connectorarch1_5/)
-
-For more information about JCA, please consult the [J2EE Connector Architecture documentation](http://java.sun.com/j2ee/connector/index.jsp).
-
-Open the `META-INF/ra.xml` file and look for the following section:
-
-**META-INF/ra.xml**
-
-<config-property>
- <description>
- The URL to the ActiveMQ server that you want this connection to connect to. If using
- an embedded broker, this value should be 'vm://localhost'.
- </description>
- <config-property-name>ServerUrl</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <config-property-value>tcp://localhost:61616</config-property-value>
-<!\-\- <config-property-value>vm://localhost</config-property-value> -->
- </config-property>
-
-The section above is used to tell the ActiveMQ RAR where ActiveMQ is located. By default, the in-VM protocol is commented out in favor of the tcp protocol. This will find ActiveMQ running on any interface on the localhost on port 61616. It's ok to just leave this alone if you don't mind the inefficiency of communicating within the JVM via TCP. However, it is recommended that `vm://` transport be used for an embedded broker, so comment out the `tcp://` transport and uncomment the `vm://` [...]
-
-**META-INF/ra.xml**
-
-<config-property>
- <description>
- The URL to the ActiveMQ server that you want this connection to connect to. If using
- an embedded broker, this value should be 'vm://localhost'.
- </description>
- <config-property-name>ServerUrl</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <!\-\- <config-property-value>tcp://localhost:61616</config-property-value> -->
- <config-property-value>vm://localhost</config-property-value>
- </config-property>
-
-Because we're embedding ActiveMQ inside of JBoss, it is more efficient to use the `vm://` transport, rather than to perform messaging over the `tcp://` transport.
-
-Now look further down the `META-INF/ra.xml` file and locate the following section:
-
-**META-INF/ra.xml**
-
-<config-property>
- <description>
- Sets the XML configuration file used to configure the embedded ActiveMQ broker via
- Spring if using embedded mode.
-
- BrokerXmlConfig is the filename which is assumed to be on the classpath unless
- a URL is specified. So a value of foo/bar.xml would be assumed to be on the
- classpath whereas file:dir/file.xml would use the file system.
- Any valid URL string is supported.
- </description>
- <config-property-name>BrokerXmlConfig</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <config-property-value></config-property-value>
- <!--
- <config-property-value>xbean:broker-config.xml</config-property-value>
- -->
- </config-property>
-
-The section above needs to be changed to uncomment the second to last line and remove/replace the empty element that is above it. Below is an example of how this should be changed:
-
-**META-INF/ra.xml**
-
-<config-property>
- <description>
- Sets the XML configuration file used to configure the embedded ActiveMQ broker via
- Spring if using embedded mode.
-
- BrokerXmlConfig is the filename which is assumed to be on the classpath unless
- a URL is specified. So a value of foo/bar.xml would be assumed to be on the
- classpath whereas file:dir/file.xml would use the file system.
- Any valid URL string is supported.
- </description>
- <config-property-name>BrokerXmlConfig</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <config-property-value>xbean:broker-config.xml</config-property-value>
- </config-property>
-
-This change tells the ActiveMQ RAR to read a configuration file named `broker-config.xml` (the `xbean:` that proceeds the filename is simply a hint to class doing the reading of the configuration file) which is located on the CLASSPATH. In this case, the `broker-config.xml` file is located in the `activemq-ra.rar` directory. Save the changes to that file and then open the `broker-config.xml` file.
-
-The `broker-config.xml` file _is_ the ActiveMQ configuration file. This is the file used to configure ActiveMQ. The default contents of this file are usable, but should be customized to suit your environment. There are several items of note about this configuration. The most prominent sections to note in this file are the `<persistenceAdapter>` element and the `<transportConnectors>` and `<networkConnectors>` elements as seen below:
-
-**broker-config.xml**
-
-<beans xmlns="http://activemq.org/config/1.0">
-
- <broker useJmx="true">
- ...
- <persistenceAdapter>
- <journaledJDBC journalLogFiles="5" dataDirectory="activemq-data"/>
- <!\-\- To use a different datasource, use th following syntax : -->
- <!--
- <journaledJDBC journalLogFiles="5" dataDirectory="../data" dataSource="#postgres-ds"/>
- -->
- </persistenceAdapter>
-
- <transportConnectors>
- <!\-\- prefixing a connector with discovery: causes the connector to be advertiesed over rendezvous -->
- <transportConnector uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
- </transportConnectors>
-
- <networkConnectors>
- <!\-\- by default just auto discover the other brokers -->
- <networkConnector uri="multicast://default"/>
- <!--
- <networkConnector uri="static://(tcp://host1:61616,tcp://host2:61616)"/>
- -->
- </networkConnectors>
-
- </broker>
-
-</beans>
-
-The first change to this file is to add the brokerName attribute to the broker element and provide a name:
-
-<broker useJmx="true" brokerName="bruce.broker1">
-
-In addition, this same name is used further down the configuration to provide a name for the `<transportConnector>` element:
-
-<transportConnector name="bruce.broker1" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
-
-Now we'll tell ActiveMQ not to initialize JMX because we'll use the existing one that JBoss has:
-
-<!\-\- put the following as the first child of the broker tag -->
-<managementContext><!-- we'll use an existing one (JBoss) instead of creating one -->
- <managementContext createConnector="false"/>
-</managementContext>
-
-The `<persistenceAdapter>` element should be reconfigured to store its data in an appropriate place. On JBoss, that's most likely within the "data" directory of the server configuration you're using. We're going to set this dynamically using an XBean and Spring feature that allows us to inject system properties values into the configuration. First this needs to be enabled:
-
-<!\-\- put the following as the first child of the beans element -->
-<bean xmlns="" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
-
-Now, modify the `dataDirectory` attribute of the `journaledJDBC` element to be the following: `${jboss.server.data.dir}/activemq`.
-
-The `<transportConnectors>` element is used to advertise the ActiveMQ broker for client-to-broker communications and the `<networkConnectors>` element advertises the ActiveMQ broker for broker-to-broker communications. The default configuration is to use the ActiveMQ [multicast transport](http://www.activemq.org/siteUsing ActiveMQ/Configuring Transports/ActiveMQ Connection URIs/multicast-transport-reference.md) for both. This is simply an easy configuration under which to get ActiveMQ up [...]
-
-**_NOTE:_** There are far more configuration options available for ActiveMQ than are noted here. The configuration above is only enough to just get ActiveMQ up and running, nothing more. For more information on the ActiveMQ configuration, see the [ActiveMQ 4.1 XML Reference](http://www.activemq.org/siteUsing ActiveMQ/Xml ReferenceUsing ActiveMQ/Xml Reference/Using ActiveMQ/Xml Reference/xbean-xml-reference-41.md).
-
-Now we just need to start up JBoss to assure that it comes up correctly without error using the same commands we used previously to start JBoss:
-
-$ cd jboss-4.0.4.GA
-$ ./bin/run.sh -c default
-=========================================================================
-
- JBoss Bootstrap Environment
-
- JBOSS_HOME: /opt/jboss-4.0.4.GA
-
- JAVA: java
-
- JAVA_OPTS: -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000
--Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh
-
- CLASSPATH: /opt/jboss-4.0.4.GA/bin/run.jar:/lib/tools.jar
-
-=========================================================================
-
-15:34:47,999 INFO \[Server\] Starting JBoss (MX MicroKernel)...
-15:34:48,001 INFO \[Server\] Release ID: JBoss \[Zion\] 4.0.4.GA (build: CVSTag=JBoss\_4\_0\_4\_GA date=200605151000)
-15:34:48,004 INFO \[Server\] Home Dir: /opt/jboss-4.0.4.GA
-15:34:48,005 INFO \[Server\] Home URL: file:/opt/jboss-4.0.4.GA/
-15:34:48,007 INFO \[Server\] Patch URL: null
-15:34:48,007 INFO \[Server\] Server Name: default
-15:34:48,007 INFO \[Server\] Server Home Dir: /opt/jboss-4.0.4.GA/server/default
-15:34:48,011 INFO \[Server\] Server Home URL: file:/opt/jboss-4.0.4.GA/server/default/
-15:34:48,012 INFO \[Server\] Server Log Dir: /opt/jboss-4.0.4.GA/server/default/log
-15:34:48,017 INFO \[Server\] Server Temp Dir: /opt/jboss-4.0.4.GA/server/default/tmp
-15:34:48,022 INFO \[Server\] Root Deployment Filename: jboss-service.xml
-...
-15:35:17,360 INFO \[Server\] JBoss (MX MicroKernel) \[4.0.4.GA (build: CVSTag=JBoss\_4\_0\_4\_GA date=200605151000)\]
-Started in 28s:576ms
-
-As long as JBoss comes up without error, you're ready to move on to the next step.
-
-Configuring JBoss
------------------
-
-The sixth step is to configure JBoss to initialize and start ActiveMQ whenever JBoss starts up. This is accomplished using an XML file that abides by the [JBoss JCA DTD](http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd) for data sources. Like most other Java application servers on the market, the JBoss architecture uses the J2EE Connector Architecture to manage connections of any kind including JDBC, JMS, etc. and the JBoss JCA DTD denotes the allowed contents for creating an XML data sour [...]
-
-**activemq-jms-ds.xml**
-
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!DOCTYPE connection-factories
- PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN"
- "http://www.jboss.org/j2ee/dtd/jboss-ds\_1\_5.dtd">
-
-<connection-factories>
-
- <tx-connection-factory>
- <jndi-name>activemq/QueueConnectionFactory</jndi-name>
- <xa-transaction/>
- <track-connection-by-tx/>
- <rar-name>activemq-ra.rar</rar-name>
- <connection-definition>javax.jms.QueueConnectionFactory</connection-definition>
- <ServerUrl>vm://localhost</ServerUrl>
- <!--
- <UserName>sa</UserName>
- <Password></Password>
- -->
- <min-pool-size>1</min-pool-size>
- <max-pool-size>200</max-pool-size>
- <blocking-timeout-millis>30000</blocking-timeout-millis>
- <idle-timeout-minutes>3</idle-timeout-minutes>
- </tx-connection-factory>
-
- <tx-connection-factory>
- <jndi-name>activemq/TopicConnectionFactory</jndi-name>
- <xa-transaction/>
- <track-connection-by-tx/>
- <rar-name>activemq-ra.rar</rar-name>
- <connection-definition>javax.jms.TopicConnectionFactory</connection-definition>
- <ServerUrl>vm://localhost</ServerUrl>
- <!--
- <UserName>sa</UserName>
- <Password></Password>
- -->
- <min-pool-size>1</min-pool-size>
- <max-pool-size>200</max-pool-size>
- <blocking-timeout-millis>30000</blocking-timeout-millis>
- <idle-timeout-minutes>3</idle-timeout-minutes>
- </tx-connection-factory>
-
- <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.queue:name=outboundQueue">
- <attribute name="JNDIName">activemq/queue/outbound</attribute>
- <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends>
- <attribute name="Type">javax.jms.Queue</attribute>
- <attribute name="Properties">PhysicalName=queue.outbound</attribute>
- </mbean>
-
- <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.topic:name=inboundTopic">
- <attribute name="JNDIName">activemq/topic/inbound</attribute>
- <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends>
- <attribute name="Type">javax.jms.Topic</attribute>
- <attribute name="Properties">PhysicalName=topic.inbound</attribute>
- </mbean>
-
-</connection-factories>
-
-This XML instance configures a JMS `QueueConnectionFactory` and a JMS `TopicConnectionFactory` and makes them available via JNDI. Also defined in this file are some {{AdminObject}}s which are used to specify a topic and a queue. This file should be dropped into the JBoss deploy directory. Its name (*-ds.xml) will cause it to be picked up by the JBoss deployer upon startup. Speaking of which, once this file is in place, a quick smoke test can be performed by simply starting up the JBoss s [...]
-
-=========================================================================
-
- JBoss Bootstrap Environment
-
- JBOSS_HOME: /opt/jboss
-
- JAVA: java
-
- JAVA_OPTS: -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000
--Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh
-
- CLASSPATH: /opt/jboss/bin/run.jar:/lib/tools.jar
-
-=========================================================================
-
-22:55:48,686 INFO \[Server\] Starting JBoss (MX MicroKernel)...
-22:55:48,688 INFO \[Server\] Release ID: JBoss \[Zion\] 4.0.4.GA (build: CVSTag=JBoss\_4\_0\_4\_GA date=200605151000)
-22:55:48,690 INFO \[Server\] Home Dir: /opt/jboss-4.0.4.GA
-22:55:48,692 INFO \[Server\] Home URL: file:/opt/jboss-4.0.4.GA/
-22:55:48,695 INFO \[Server\] Patch URL: null
-22:55:48,697 INFO \[Server\] Server Name: default
-22:55:48,698 INFO \[Server\] Server Home Dir: /opt/jboss-4.0.4.GA/server/default
-22:55:48,701 INFO \[Server\] Server Home URL: file:/opt/jboss-4.0.4.GA/server/default/
-22:55:48,702 INFO \[Server\] Server Log Dir: /opt/jboss-4.0.4.GA/server/default/log
-22:55:48,704 INFO \[Server\] Server Temp Dir: /opt/jboss-4.0.4.GA/server/default/tmp
-22:55:48,706 INFO \[Server\] Root Deployment Filename: jboss-service.xml
-22:55:49,092 INFO \[ServerInfo\] Java version: 1.5.0_06,Apple Computer, Inc.
-22:55:49,101 INFO \[ServerInfo\] Java VM: Java HotSpot(TM) Server VM 1.5.0_06-64,"Apple Computer, Inc."
-22:55:49,102 INFO \[ServerInfo\] OS-System: Mac OS X 10.4.8,i386
-22:55:49,803 INFO \[Server\] Core system initialized
-22:55:53,379 INFO \[WebService\] Using RMI server codebase: http://rattlesnake:8083/
-22:55:53,400 INFO \[Log4jService$URLWatchTimerTask\] Configuring from URL: resource:log4j.xml
-22:55:54,034 INFO \[NamingService\] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50,
-no client SocketFactory, Server SocketFactory=class
-org.jboss.net.sockets.DefaultSocketFactory
-22:55:58,475 INFO \[Embedded\] Catalina naming disabled
-22:55:58,566 INFO \[ClusterRuleSetFactory\] Unable to find a cluster rule set in the classpath.
-Will load the default rule set.
-22:55:58,569 INFO \[ClusterRuleSetFactory\] Unable to find a cluster rule set in the classpath.
-Will load the default rule set.
-22:55:59,110 INFO \[Http11BaseProtocol\] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
-22:55:59,114 INFO \[Catalina\] Initialization processed in 545 ms
-22:55:59,116 INFO \[StandardService\] Starting service jboss.web
-22:55:59,121 INFO \[StandardEngine\] Starting Servlet Engine: Apache Tomcat/5.5.17
-22:55:59,179 INFO \[StandardHost\] XML validation disabled
-22:55:59,221 INFO \[Catalina\] Server startup in 105 ms
-22:55:59,600 INFO \[TomcatDeployer\] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
-22:55:59,874 INFO \[WebappLoader\] Dual registration of jndi stream handler: factory already defined
-22:56:00,899 INFO \[TomcatDeployer\] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
-22:56:01,700 INFO \[TomcatDeployer\] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp60528jbossws-exp.war/
-22:56:01,891 INFO \[SubscriptionManager\] Bound event dispatcher to java:/EventDispatcher
-22:56:02,203 INFO \[TomcatDeployer\] deploy, ctxPath=/jbossmq-httpil,
-warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
-22:56:04,546 INFO \[TomcatDeployer\] deploy, ctxPath=/web-console,
-warUrl=.../deploy/management/console-mgr.sar/web-console.war/
-22:56:05,690 INFO \[MailService\] Mail Service bound to java:/Mail
-22:56:07,215 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/activemq-ra.rar/
-22:56:07,452 INFO \[XBeanXmlBeanDefinitionReader\] Loading XML bean definitions from class
-path resource \[broker-config.xml\]
-22:56:07,750 INFO \[ClassPathXmlApplicationContext\] Bean factory for application context
-\[org.apache.xbean.spring.context.ClassPathXmlApplicationContext;hashCode=13887543\]:
-org.springframework.beans.factory.support.DefaultListableBeanFactory defining
-beans \[org.apache.activemq.xbean.XBeanBrokerService\]; root of BeanFactory hierarchy
-22:56:07,765 INFO \[ClassPathXmlApplicationContext\] 1 beans defined in application context
-\[org.apache.xbean.spring.context.ClassPathXmlApplicationContext;hashCode=13887543\]
-22:56:07,773 INFO \[CollectionFactory\] JDK 1.4+ collections available
-22:56:07,778 INFO \[ClassPathXmlApplicationContext\] Unable to locate MessageSource with name
-'messageSource': using default
-\[org.springframework.context.support.DelegatingMessageSource@5fee96\]
-22:56:07,781 INFO \[ClassPathXmlApplicationContext\] Unable to locate ApplicationEventMulticaster
-with name 'applicationEventMulticaster': using default
-\[org.springframework.context.event.SimpleApplicationEventMulticaster@78c714\]
-22:56:07,783 INFO \[DefaultListableBeanFactory\] Pre-instantiating singletons in factory
- \[org.springframework.beans.factory.support.DefaultListableBeanFactory
-defining beans \[org.apache.activemq.xbean.XBeanBrokerService\]; root of BeanFactory hierarchy\]
-22:56:08,181 INFO \[BrokerService\] ActiveMQ 4.0.2 JMS Message Broker (bruce.broker1) is starting
-22:56:08,181 INFO \[BrokerService\] For help or more information please see:
-http://incubator.apache.org/activemq/
-22:56:09,989 INFO \[JDBCPersistenceAdapter\] Database driver recognized:
-\[apache\_derby\_embedded\_jdbc\_driver\]
-22:56:11,026 INFO \[JournalPersistenceAdapter\] Journal Recovery Started from: Active Journal:
-using 5 x 20.0 Megs at: /opt/jboss-4.0.4.GA/activemq-data/journal
-22:56:11,169 INFO \[JournalPersistenceAdapter\] Journal Recovered: 0 message(s) in transactions recovered.
-22:56:11,489 INFO \[TransportServerThreadSupport\] Listening for connections at: tcp://rattlesnake:61616
-22:56:11,491 WARN \[MulticastDiscoveryAgent\] brokerName not set
-22:56:11,519 INFO \[TransportConnector\] Connector bruce.broker1 Started
-22:56:11,522 INFO \[NetworkConnector\] Network Connector bridge Started
-22:56:11,522 INFO \[BrokerService\] ActiveMQ JMS Message Broker
-(bruce.broker1, ID:rattlesnake-59052-1161060967859-1:0) started
-22:56:11,556 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jboss-ha-local-jdbc.rar
-22:56:11,599 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jboss-ha-xa-jdbc.rar
-22:56:11,623 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jboss-local-jdbc.rar
-22:56:11,647 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jboss-xa-jdbc.rar
-22:56:11,737 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jms/jms-ra.rar
-22:56:11,847 INFO \[RARDeployment\] Required license terms exist, view META-INF/ra.xml in
-.../deploy/mail-ra.rar
-22:56:12,251 INFO \[ConnectionFactoryBindingService\] Bound ConnectionManager
-'jboss.jca:service=ConnectionFactoryBinding,name=activemq/QueueConnectionFactory' to
-JNDI name 'java:activemq/QueueConnectionFactory'
-22:56:12,258 INFO \[ConnectionFactoryBindingService\] Bound ConnectionManager
-'jboss.jca:service=ConnectionFactoryBinding,name=activemq/TopicConnectionFactory' to
-JNDI name 'java:activemq/TopicConnectionFactory'
-22:56:12,265 INFO \[AdminObject\] Bound admin object 'org.apache.activemq.command.ActiveMQQueue'
-at 'activemq/queue/outbound'
-22:56:12,330 INFO \[AdminObject\] Bound admin object 'org.apache.activemq.command.ActiveMQTopic'
-at 'activemq/topic/inbound'
-22:56:13,246 INFO \[ConnectionFactoryBindingService\] Bound ConnectionManager
-'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
-22:56:13,842 INFO \[A\] Bound to JNDI name: queue/A
-22:56:13,845 INFO \[B\] Bound to JNDI name: queue/B
-22:56:13,846 INFO \[C\] Bound to JNDI name: queue/C
-22:56:13,848 INFO \[D\] Bound to JNDI name: queue/D
-22:56:13,850 INFO \[ex\] Bound to JNDI name: queue/ex
-22:56:13,876 INFO \[testTopic\] Bound to JNDI name: topic/testTopic
-22:56:13,879 INFO \[securedTopic\] Bound to JNDI name: topic/securedTopic
-22:56:13,880 INFO \[testDurableTopic\] Bound to JNDI name: topic/testDurableTopic
-22:56:13,883 INFO \[testQueue\] Bound to JNDI name: queue/testQueue
-22:56:13,994 INFO \[UILServerILService\] JBossMQ UIL service available at : /0.0.0.0:8093
-22:56:14,055 INFO \[DLQ\] Bound to JNDI name: queue/DLQ
-22:56:14,375 INFO \[ConnectionFactoryBindingService\] Bound ConnectionManager
-'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
-22:56:14,525 INFO \[TomcatDeployer\] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
-22:56:14,991 INFO \[Http11BaseProtocol\] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
-22:56:15,071 INFO \[ChannelSocket\] JK: ajp13 listening on /0.0.0.0:8009
-22:56:15,082 INFO \[JkMain\] Jk running ID=0 time=0/25 config=null
-22:56:15,108 INFO \[Server\] JBoss (MX MicroKernel) \[4.0.4.GA (build: CVSTag=JBoss\_4\_0\_4\_GA date=200605151000)\]
-Started in 26s:398ms
-
-Note the startup messages from both ActiveMQ and from the `AdminObject}}s creating an {{ActiveMQQueue` and an `ActiveMQTopic`. These are good indications that the configuration is correct, but needs to be verified a bit further. This is covered in the next section.
-
-Testing the Integration
------------------------
-
-The seventh and final step is to perform a slightly more comprehensive smoke test of the integration. This can be accomplished using Apache Ant via the examples that come with the ActiveMQ binary distribution. An Ant build.xml file is included which provides easy access to a simple consumer and a simple producer. The producer will be used to send messages that are received by the consumer. To proceed with this testing, just follow the steps below:
-
-1. In the first terminal, start up JBoss. The same startup script can be used here as was used above.
-2. In the second terminal, use the commands below to run the ActiveMQ consumer:
-
- $ cd /opt/incubator-activemq-4.0.2/examples #note in activemq v5 the directory is just "example" not "examples"
- $ ant consumer
- Buildfile: build.xml
-
- init:
- \[mkdir\] Created dir: /opt/incubator-activemq-4.0.2/example/target/classes
- \[mkdir\] Created dir: /opt/incubator-activemq-4.0.2/example/src/ddl
-
- compile:
- \[javac\] Compiling 6 source files to /opt/incubator-activemq-4.0.2/example/target/classes
-
- consumer:
- \[echo\] Running consumer against server at $url = tcp://localhost:61616 for subject $subject = TEST.FOO
- \[java\] Connecting to URL: tcp://localhost:61616
- \[java\] Consuming queue: TEST.FOO
- \[java\] Using non-durable subscription
- \[java\] We are about to wait until we consume: 10 message(s) then we will shutdown
-
-3. In the third terminal, use the commands below to run the ActiveMQ producer:
-
- $ cd /opt/incubator-activemq-4.0.2/examples
- $ ant producer
- Buildfile: build.xml
-
- init:
-
- compile:
-
- producer:
- \[echo\] Running producer against server at $url = tcp://localhost:61616 for subject $subject = TEST.FOO
- \[java\] Connecting to URL: tcp://localhost:61616
- \[java\] Publishing a Message with size 1000 to queue: TEST.FOO
- \[java\] Using non-durable publishing
- \[java\] Sleeping between publish 0 ms
- \[java\] Sending message: Message: 0 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 1 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 2 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 3 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 4 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 5 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 6 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 7 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 8 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Sending message: Message: 9 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- \[java\] Done.
- \[java\] connection {
- \[java\] session {
- \[java\] messageCount{ count: 10 unit: count startTime: 1161062468001 lastSampleTime:
- 1161062468340 description: Number of messages exchanged }
- \[java\] messageRateTime{ count: 10 maxTime: 142 minTime: 1 totalTime: 315 averageTime: 31.5
- averageTimeExMinMax: 21.5 averagePerSecond: 31.746031746031747
- averagePerSecondExMinMax: 46.51162790697674 unit: millis startTime: 1161062468002 lastSampleTime:
- 1161062468340 description: Time taken to process a message (thoughtput rate) }
- \[java\] pendingMessageCount{ count: 0 unit: count startTime: 1161062468001 lastSampleTime:
- 1161062468001 description: Number of pending messages }
- \[java\] expiredMessageCount{ count: 0 unit: count startTime: 1161062468001 lastSampleTime:
- 1161062468001 description: Number of expired messages }
- \[java\] messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0
- averageTimeExMinMax: 0.0 averagePerSecond: 0.0
- averagePerSecondExMinMax: 0.0 unit: millis startTime: 1161062468002 lastSampleTime: 1161062468002
- description: Time spent by a message before being delivered }
- \[java\] durableSubscriptionCount{ count: 0 unit: count startTime: 1161062468002 lastSampleTime:
- 1161062468002 description: The number of durable
- subscriptions }
-
- \[java\] producers {
- \[java\] producer queue://TEST.FOO {
- \[java\] messageCount{ count: 10 unit: count startTime: 1161062468025 lastSampleTime:
- 1161062468340 description: Number of messages processed }
- \[java\] messageRateTime{ count: 10 maxTime: 142 minTime: 1 totalTime: 315 averageTime:
- 31.5 averageTimeExMinMax: 21.5 averagePerSecond:
- 31.746031746031747 averagePerSecondExMinMax: 46.51162790697674 unit: millis startTime: 1161062468025
- lastSampleTime: 1161062468340 description: Time taken to
- process a message (thoughtput rate) }
- \[java\] pendingMessageCount{ count: 0 unit: count startTime: 1161062468025 lastSampleTime:
- 1161062468025 description: Number of pending messages }
- \[java\] messageRateTime{ count: 10 maxTime: 142 minTime: 1 totalTime: 315 averageTime: 31.5
- averageTimeExMinMax: 21.5 averagePerSecond:
- 31.746031746031747 averagePerSecondExMinMax: 46.51162790697674 unit: millis startTime: 1161062468025
- lastSampleTime: 1161062468340 description: Time taken to
- process a message (thoughtput rate) }
- \[java\] expiredMessageCount{ count: 0 unit: count startTime: 1161062468025 lastSampleTime:
- 1161062468025 description: Number of expired messages }
- \[java\] messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0
- averageTimeExMinMax: 0.0 averagePerSecond: 0.0
- averagePerSecondExMinMax: 0.0 unit: millis startTime: 1161062468025 lastSampleTime: 1161062468025
- description: Time spent by a message before being delivered }
- \[java\] }
- \[java\] }
- \[java\] consumers {
- \[java\] }
- \[java\] }
- \[java\] }
-
-
-Step 1 above just starts up JBoss. Step 2 above starts up a simple message consumer that comes with ActiveMQ. Step 3 above starts up a simple message producer that comes with ActiveMQ. Though the message consumer and message producer are simple utilities, the each one accepts many parameters making them extremely useful for testing ActiveMQ configurations.
-
-To paraphrase, what just happened was that the message producer sent 10 messages to the TEST.FOO destination and the message consumer received 10 messages from the TEST.FOO destination. Despite being a simple test, it does utilize the ActiveMQ broker, albeit only on a single machine. The next logical step is to set up a full network of ActiveMQ brokers.
-
-After setting up one broker within one instance of JBoss, setting up another is made much easier, but requires another machine or operating system instance. But that's a whole separate article and something to address another day.
-
-Conclusion
-----------
-
-What has been demonstrated here is the integration of ActiveMQ with the JBoss application server. This integration is quite common and performed by many enterprises. I hope that this was helpful to people interested in the integration of ActiveMQ with JBoss application server. If you have any questions or are interested in consulting services surrounding ActiveMQ, please [contact us](http://www.logicblaze.com/contact.jsp) for more information.
-
-### Resources
-
-Below are the configurations for use with both Spring 1.x and Spring 2.x:
-
-
-
-
-
-[File](Connectivity/Containers/integrating-apache-activemq-with-jboss.md?sortBy=name&sortOrder=ascending)
-
-[Modified](Connectivity/Containers/integrating-apache-activemq-with-jboss.md?sortBy=date&sortOrder=descending)
-
-File [amq-spring-1.2.6.tgz](jboss-integration.data/amq-spring-1.2.6.tgz?api=v2 "Download")
-
-Oct 03, 2007 by [Bruce Snyder](https://cwiki.apache.org/confluence/display/~bsnyder)
-
-Labels
-
-* No labels
-* [Edit Labels](# "Edit Labels")
-
-Preview
-
-File [amq-spring-2.0.tgz](jboss-integration.data/amq-spring-2.0.tgz?api=v2 "Download")
-
-Oct 03, 2007 by [Bruce Snyder](https://cwiki.apache.org/confluence/display/~bsnyder)
-
-Labels
-
-* No labels
-* [Edit Labels](# "Edit Labels")
-
-Preview
-
-[Download All](/confluence/pages/downloadallattachments.action?pageId=67786 "Download all the latest versions of attachments on this page as single zip file.")
-
diff --git a/src/_documents/classic/Connectivity/Containers/jca-container.md b/src/_documents/classic/Connectivity/Containers/jca-container.md
deleted file mode 100644
index 532b50e..0000000
--- a/src/_documents/classic/Connectivity/Containers/jca-container.md
+++ /dev/null
@@ -1,58 +0,0 @@
-Apache ActiveMQ ™ -- JCA Container
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [JCA Container](../../Connectivity/Containers/jca-container.md)
-
-
-The JCA Container is moving
-
-We will continune to support the ActiveMQ JCA Container up until ActiveMQ 3.1.
-
-After that point we will be moving to [Jencks](http://jencks.codehaus.org/) which is a migration of the ActiveMQ codebase together with code [Geronimo](http://geronimo.apache.org) and from some other contributors.
-
-Jencks is completely logically equivalent to the ActiveMQ JCA Container and migrating to it is pretty simple (mostly just a class name change for the JCA container) - though the benefits of Jencks are that it supports full XA recovery and works well with Geronimo's TransactionManager and WorkManager.
-
-So we do recommend you migrate to [Jencks](http://jencks.codehaus.org/) whenever its easy for you to do so; projects such as [Lingo](http://lingo.codehaus.org/) and [ServiceMix](http://servicemix.org/) already have and it was an easy migration.
-
-We have a lightweight, easily embeddable Spring based JCA container which allows us to provide MDB like functionality inside any Java application without requiring a full EJB container.
-
-This allows us to support _message driven pojos_ using dependency injection for efficient JMS consumption together with pooling of the pojos using lightweight containers rather than relying on EJB.
-
-The JCA container also makes it easy to programatically at runtime create new message driven pojos rather than relying on the fixed deployment-time only option with EJB.
-
-Example
--------
-
-Here is [an example](http://docs.codehaus.org/download/attachments/23776/spring.xml) of the Spring XML to deploy a pojo (EchoBean) on an inbound JMS subscription, on a topic in this particular example.
-
-Firstly we can create as many JCAContainer instances as we need; currently we create one per JCA [Resource Adapter](../../Connectivity/Containers/resource-adapter.md) (i.e. JMS provider). The JCAContainer also uses a WorkManager which is JCA speak for a bunch of thread pools. We can share the WorkManager across JCAContainer instances or create one per JCAContainer.
-
-Once we have a JCAContainer we can add as many JCAConnector instances to it, via the **addConnector** factory method, each one representing a JMS subscription and providing a pool of POJOs to process the message. The subscription details are specified by an activationSpec property which is a bean typically dependent on the JMS provider; this allows providers to add new extensions while leaving your application code pure JMS.
-
-Notice that the regular Spring pooling mechanism, the **targetSource** property, is used to pool the actual POJO and that Spring uses Dependency Injection to construct instances of the POJO.
-
-**Note** you must set the **singleton** flag to false for the POJOs if they are not thread safe.
-
-Requirements
-------------
-
-To be able to use the JCA container, you just need the following jars on your classpath
-
-* [required ActiveMQ jars](Using ActiveMQ/initial-Community/FAQ/configuration.md) if you are using ActiveMQ as your JMS provider - or your provider's jars if not
-* activemq-container.jar
-* spring.jar
-* J2EE.jar (for the JCA APIs). If you are inside Tomcat, it doesn't like j2ee.jar on the classpath, so use the individual jars from Geronimo - e.g. geronimo-spec-j2ee-connector-*.jar for the JCA APIs
-* commons-collections.jar
-* commons-pool.jar
-* aopalliance.jar (a temporary dependency introduced by Spring's use of the TargetSource, we should be able to remove this dependency later on).
-
-**Note** the classes and resources in activemq-container.jar are not included in activemq.jar
-
-To use the JCA Container please use the 2.x code release. Several problems were found and fixed with the 1.x branch of code.
-
-Things to watch
----------------
-
-By default the ActiveMQ [Resource Adapter](../../Connectivity/Containers/resource-adapter.md) will try to connect to a remote broker (ie. tcp://localhost:61616). Also if you want to set how the broker is configured via XML then try the _brokerXmlConfig_ property.
-
-_Note:_ In AMQ 3.x the default behavior is the ActiveMQ resource adapter will create an embedded broker
-
diff --git a/src/_documents/classic/Connectivity/Containers/jndi-support.md b/src/_documents/classic/Connectivity/Containers/jndi-support.md
deleted file mode 100644
index 2e25e6a..0000000
--- a/src/_documents/classic/Connectivity/Containers/jndi-support.md
+++ /dev/null
@@ -1,86 +0,0 @@
-Apache ActiveMQ ™ -- JNDI Support
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [JNDI Support](Connectivity/Containers/jndi-Community/support.md)
-
-
-ActiveMQ will work with any JNDI provider capable of storing Java objects. However it is common to require a JNDI initial context to be able to run many JMS example programs, like [Sun's JMS tutorial.](http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/jms_tutorialTOC.html)
-
-So we provide a simple JNDI **`InitialContextFactory`** which can be used to lookup JMS connection factory objects as well as Destination objects. For example if you place this [jndi.properties](http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/jndi.properties) file on your classpath, you can look inside the **`InitialContext`** and lookup **`ConnectionFactory`** objects and **`Destinations`** etc.
-
-java.naming.factory.initial = org.apache.activemq.jndi.ActiveMQInitialContextFactory # Use the following property to configure the default connector java.naming.provider.url = vm://localhost # Use the following property to specify the JNDI name the connection factory # should appear as. #connectionFactoryNames = connectionFactory, queueConnectionFactory, topicConnectionFactry # Register some queues in JNDI using the form: # queue.\[jndiName\] = \[physicalName\] queue.MyQueue = example.My [...]
-
-You can edit the **`jndi.properties`** file to configure the **`ActiveMQConnectionFactory`**'s properties such as **`brokerURL`** and whether or not there should be an embedded broker etc. See [how to embed a broker in a connection](../../FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md) for more details.
-
-### ActiveMQ JNDI Tutorial
-
-This is a quick one page tutorial on how to setup and use JNDI to create a connection to ActiveMQ. The first thing is ActiveMQ does not provide a full JNDI server. This means JMS clients need to use properties files to create a JNDI **`IntialContextFactory`**. If you need an example properties file, you can look the source distribution [https://github.com/apache/activemq/blob/master/activemq-unit-tests/src/test/resources/jndi.properties](https://github.com/apache/activemq/blob/master/act [...]
-
-Name
-
-Value
-
-`java.naming.factory.initial`
-
-`org.apache.activemq.jndi.ActiveMQInitialContextFactory`
-
-`java.naming.provider.url`
-
-`tcp://hostname:61616`
-
-`topic.MyTopic`
-
-`example.MyTopic`
-
-Make sure to add **`activemq-_<version>_.jar`** and **`spring-1.x.jar`** to your classpath. If the libraries are not in the classpath, you will get a **`ClassNotFoundException`** at runtime. If you get **`ClassNotFoundException`**, try printing out the classpath and check it is present. You can also run ActiveMQ with **`-verbose`** option to verify the jar was loaded correctly.
-
-**Sample Code**
-
-java// Create a new intial context, which loads from jndi.properties file: javax.naming.Context ctx = new javax.naming.InitialContext(); // Lookup the connection factory: javax.jms.TopicConnectionFactory factory = (javax.jms.TopicConnectionFactory)ctx.lookup("ConnectionFactory"); // Create a new TopicConnection for pub/sub messaging: javax.jms.TopicConnection conn = factory.getTopicConnection(); // Lookup an existing topic: javax.jms.Topic mytopic = (javax.jms.Topic)ctx.lookup("MyTopic") [...]
-
-Notice the name of the topic in the sample is **`MyTopic`**. ActiveMQ will read the **`jndi.properties`** files and creates the topics and queues in a lazy fashion. The prefix topic and queue is stripped, so the JNDI name begins after the prefix.
-
-Once you have the **`jndi.properties`** edited and ready, it needs to be accessible to your application. The easiest way is to add **`jndi.properties`** to a jar file. When **`new InitialContext()`** is called, it will scan the resources and find the file. If you get **`javax.naming.NamingException`**, it usually means the **`jndi.properties`** file is not accessible.
-
-You can also try to create a new initial context using either an instance of properties file or a map. For example, the approach recommended by JMS specification will work just fine.
-
-Example Recommended by Specification
-
-javaProperties props = new Properties(); props.setProperty(Context.INITIAL\_CONTEXT\_FACTORY,"org.apache.activemq.jndi.ActiveMQInitialContextFactory"); props.setProperty(Context.PROVIDER_URL,"tcp://hostname:61616"); javax.naming.Context ctx = new InitialContext(props);||
-
-If ActiveMQ is embedded within an EJB container, you will need to look at the containers documentation for the correct JNDI values.
-
-### Dynamically Creating Destinations
-
-For the easiest possible configuration with JNDI based programs, there are two dynamic contexts, namely:
-
-* **`dynamicQueues`**
-* **`dynamicTopics`**
-
-These allow you to lookup queues and topics using JNDI without any configuration.
-
-For example, if you use the following name to lookup into JNDI:
-
-dynamicQueues/FOO.BAR
-
-you will get back an **`ActiveMQQueue`** of the name **`FOO.BAR`**. This can be very handy if you can easily reconfigure the JNDI name to use to lookup something in JNDI, but don't want to have to double configure a **`jndi.properties`** to match.
-
-### Working With Embedded Brokers
-
-It is often useful to use an embedded broker in the same JVM as the JMS client. For this see [How do I embed a Broker inside a Connection](../../FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md).
-
-If you want to use an embedded broker with your JNDI provider you can just use the [VM Transport](../../Using ActiveMQ/Configuring Transports/ActiveMQ Connection URIs/vm-transport-reference.md) to connect to the broker in your URL. e.g. to create a purely in JVM broker use this URI
-
-vm://locahost
-
-If you want to customize the broker use something like this:
-
-vm:broker:(tcp://localhost:61616)
-
-More options are available in the [VM Transport Reference](../../Using ActiveMQ/Configuring Transports/ActiveMQ Connection URIs/vm-transport-reference.md)
-
-### Example Java Code
-
-Once you have configured JNDI on the classpath you can run any normal JMS application such as the following [example](http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/demo/SimpleProducer.java). Notice that the Java code just uses pure JMS APIs and is not in any way ActiveMQ specific
-
-java/\*\* \* The SimpleQueueSender class consists only of a main method, * which sends several messages to a queue. * * Run this program in conjunction with SimpleQueueReceiver. * Specify a queue name on the command line when you run the * program. By default, the program sends one message. Specify * a number after the queue name to send that number of messages. */ package org.apache.activemq.demo; import javax.jms.Connection; import javax.jms.ConnectionFactory; import javax.jms.Destinat [...]
-
diff --git a/src/_documents/classic/Connectivity/Containers/old-osgi-integration.md b/src/_documents/classic/Connectivity/Containers/old-osgi-integration.md
deleted file mode 100644
index 4a20e69..0000000
--- a/src/_documents/classic/Connectivity/Containers/old-osgi-integration.md
+++ /dev/null
@@ -1,166 +0,0 @@
-Apache ActiveMQ ™ -- Old OSGi Integration
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [Old OSGi Integration](../../Connectivity/Containers/old-osgi-integration.md)
-
-
-**This article applies to versions of ActiveMQ prior to 5.4.0. If you use version 5.4.0 or newer proceed to the [following article](../../Connectivity/Containers/osgi-integration.md).**
-
-Introduction
-============
-
-All ActiveMQ modules are packaged as OSGi bundles and can be used in any OSGi container. This article will provide more details on how to use ActiveMQ in [Apache Karaf](http://felix.apache.org/site/apache-felix-karaf.html), small OSGi based runtime. Apache Karaf was previously know as _ServiceMix kernel_, so informations found here are applicable to [Apache ServiceMix Enterprise Service Bus](http://servicemix.apache.org/home.html) as well.
-
-ActiveMQ
-========
-
-ActiveMQ comes as a feature in ServiceMix (Karaf). So instead of installing all necessary bundles one by one, you can simply install it using a single command. But first of all, you need to setup ServiceMix features url.
-
-smx@root:/> features/addUrl mvn:org.apache.servicemix/apache-servicemix/4.0.0/xml/features
-
-Now you can install ActiveMQ like this
-
-smx@root:/> features/install activemq
-
-This command will install all necessary ActiveMQ bundles and if you type
-
-smx@root:/> osgi/list
-
-you should see something like this
-
-\[ 50\] \[Active \] \[ \] \[ 60\] geronimo-jta\_1.1\_spec (1.1.1)
-\[ 51\] \[Active \] \[ \] \[ 60\] geronimo-j2ee-connector\_1.5\_spec (2.0.0)
-\[ 52\] \[Active \] \[ \] \[ 60\] Apache ServiceMix Bundles: howl-1.0.1-1 (1.0.1.1_1)
-\[ 53\] \[Active \] \[ \] \[ 60\] Geronimo TxManager :: Transaction (2.2.0.r634076)
-\[ 54\] \[Active \] \[ \] \[ 60\] Spring Transaction (2.5.6)
-\[ 55\] \[Active \] \[Started\] \[ 60\] Apache ServiceMix Transaction (1.0.0)
-\[ 56\] \[Active \] \[ \] \[ 60\] Geronimo TxManager :: Connector (2.2.0.r634076)
-\[ 57\] \[Active \] \[ \] \[ 60\] geronimo-jms\_1.1\_spec (1.1.1)
-\[ 58\] \[Active \] \[ \] \[ 60\] Apache ServiceMix Bundles: jencks-2.1 (2.1.0.1)
-\[ 59\] \[Active \] \[ \] \[ 60\] geronimo-j2ee-management\_1.1\_spec (1.0.1)
-\[ 60\] \[Active \] \[ \] \[ 60\] Apache Commons Pool Bundle (1.4)
-\[ 61\] \[Active \] \[ \] \[ 60\] xbean-spring (3.5)
-\[ 62\] \[Active \] \[ \] \[ 60\] activemq-core (5.2.0)
-\[ 63\] \[Active \] \[ \] \[ 60\] activemq-ra (5.2.0)
-\[ 64\] \[Active \] \[ \] \[ 60\] activemq-console (5.2.0)
-\[ 65\] \[Active \] \[ \] \[ 60\] activemq-pool (5.2.0)
-\[ 66\] \[Active \] \[Started\] \[ 60\] Apache ServiceMix Features :: ActiveMQ Commands (4.0.0)
-
-Once installed, this feature offers a special set of commands which enables you easily use the broker.
-
-This feature comes pre-installed with the ServiceMix ESB so previous steps are not necessary.
-
-The following example shows how to create and destroy the broker using the `create-broker` and `destroy-broker` commands.
-
-smx@root:/> activemq/create-broker
-Creating file: /Users/dejanb/workspace/apache-servicemix-kernel-1.1.0/deploy/localhost-broker.xml
-
-Default ActiveMQ Broker (localhost) configuration file created at: /Users/dejanb/workspace/apache-servicemix-kernel-1.1.0/deploy/localhost-broker.xml
-Please review the configuration and modify to suite your needs.
-
-smx@root:/> activemq/destroy-broker
-
-Default ActiveMQ Broker (localhost) configuration file created at: /Users/dejanb/workspace/apache-servicemix-kernel-1.1.0/deploy/localhost-broker.xml removed.
-
-For more information on ActiveMQ feature take a look at the [ServiceMix ActiveMQ integration guide](http://servicemix.apache.org/SMX4/activemq-integration.html)
-
-Web console
-===========
-
-[Web console](../../Tools/web-console.md) is included in ActiveMQ distribution and you'll probably want to have it to monitor your broker. First of all you'll have to install the `web` feature, so that you have a web container ready to deploy our web application. To do that you should first add the ServiceMix features url, like we did above (if you didn't already). Now, you can just run
-
-smx@root:/> features/install web
-
-to grab all necessary bundles. If you type
-
-smx@root:/> osgi/list
-
-you'll see all installed bundles (such as)
-
-\[ 43\] \[Active \] \[ \] \[ 60\] Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.1)
-\[ 44\] \[Active \] \[ \] \[ 60\] OPS4J Pax Web - Jsp Support (0.5.2)
-\[ 45\] \[Active \] \[ \] \[ 60\] OPS4J Pax Web - Web Container (0.5.2)
-\[ 46\] \[Active \] \[ \] \[ 60\] OPS4J Pax Web Extender - WAR (0.5.0)
-\[ 47\] \[Active \] \[ \] \[ 60\] OPS4J Pax Web Extender - Whiteboard (0.5.0)
-\[ 48\] \[Active \] \[ \] \[ 60\] OPS4J Pax Url - war:, war-i: (0.3.3)
-\[ 49\] \[Active \] \[Started\] \[ 60\] Apache ServiceMix WAR Deployer (4.0.0)
-
-This feature comes pre-installed with the ServiceMix ESB so previous steps are not necessary.
-
-The important thing is that we need to use proper versions of Pax web bundles to make all this work, and those are:
-
-* pax-web-bundle version 0.6.0
-* pax-web-jsp version 0.6.0
-* pax-web-ex-war version 0.5.1
-* pax-web-ex-whiteboard version 0.5.1
-
-So if you have older bundles, like it is the case in our example, you'll need to unistall them and install new ones. To uninstall old bundles, simply look at their id and execute
-
-smx@root:/> osgi/uninstall \[id\]
-
-In this example it would be
-
-smx@root:/> osgi/uninstall 44
-smx@root:/> osgi/uninstall 45
-smx@root:/> osgi/uninstall 46
-smx@root:/> osgi/uninstall 47
-
-Now install new ones
-
-smx@root:/> osgi/install mvn:org.ops4j.pax.web/pax-web-bundle/0.6.0
-smx@root:/> osgi/install mvn:org.ops4j.pax.web/pax-web-jsp/0.6.0
-smx@root:/> osgi/install mvn:org.ops4j.pax.web-extender/pax-web-ex-war/0.5.1
-smx@root:/> osgi/install mvn:org.ops4j.pax.web-extender/pax-web-ex-whiteboard/0.5.1
-
-After successful installation, you should start your newly added bundles. You can do that by executing
-
-smx@root:/> osgi/start \[id\]
-
-It's best to restart your container at this point and afterwards we're finally ready to deploy our war. To do that we'll use the Pax Web War Extender. The following example will use the latest `5.3-SNAPSHOT` build and deploy it in the OSGi runtime
-
-smx@root:/> osgi/install war:mvn:org.apache.activemq/activemq-web-console/5.3-SNAPSHOT/war?Webapp-Context=activemqweb
-
-You have to use the latest 5.3-SNAPSHOT web console, since this doesn't work right with previous versions.
-
-Also, if you have problems installing the war with the previous method, download it manually from [https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-web-console/5.3-SNAPSHOT/](https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-web-console/5.3-SNAPSHOT/) and install using
-
-smx@root:/> osgi/install war:file:///path\_to\_the_war/activemq-web-console-5.3-SNAPSHOT.war?Webapp-Context=activemqweb
-
-Unfortunately the command
-
-osgi/install \
-war:mvn:https://repository.apache.org/content/repositories/snapshots@snapshots!org.apache.activemq/activemq-web-console/5.3-SNAPSHOT/war?Webapp-Context=activemqweb
-
-does not work with pax web war extender 0.5.1, but you try it if you're using the newer one.
-
-If you execute
-
-smx@root:/> osgi/list
-
-you'll see the newly added bundle here.
-
-\[ 84\] \[Resolved \] \[ \] \[ 60\] mvn\_org.apache.activemq\_activemq-web-console\_5.3-SNAPSHOT\_war (0)
-
-It's time t start it now
-
-smx@root:/> osgi/start 84
-
-Use the id of your bundle
-
-The important thing to note here is that by default, web console will start an embedded broker and monitor it. So if you have a broker already running it will fail to start.
-
-Note that we have used `activemqweb` as a `WebApp-Context` while deploying the war, so the console will be available at [http://localhost:8080/activemqweb](http://localhost:8080/activemqweb). Visit this URL and administer your embedded broker.
-
-There a big chance that you don't want to monitor an embedded broker, but the broker you have started separately (in the OSGi runtime or elsewhere). To configure your web console to do that, you have to do the following. First, exit your OSGi runtime. Now you can edit the `etc/system.properties` file and add some configuration details. The following configuration snippet
-
-webconsole.type=properties
-webconsole.jms.url=tcp://localhost:61616
-webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/karaf-root
-webconsole.jmx.user=karaf
-webconsole.jmx.password=karaf
-
-should work fine with default broker started in the Karaf (ServiceMix). Adapt it to your specific needs.
-
-Now if you run the runtime (and the console bundle), you'll notice that the console will not start the broker and will try to use one defined with the system properties.
-
-Visit [http://localhost:8080/activemqweb](http://localhost:8080/activemqweb) and enjoy.
-
diff --git a/src/_documents/classic/Connectivity/Containers/osgi-integration.md b/src/_documents/classic/Connectivity/Containers/osgi-integration.md
deleted file mode 100644
index d2dba34..0000000
--- a/src/_documents/classic/Connectivity/Containers/osgi-integration.md
+++ /dev/null
@@ -1,114 +0,0 @@
-Apache ActiveMQ ™ -- OSGi Integration
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [OSGi Integration](../../Connectivity/Containers/osgi-integration.md)
-
-
-Introduction
-============
-
-This article will provide more details on how to use ActiveMQ in [Apache Karaf](http://karaf.apache.org/), small OSGi based runtime. Apache Karaf was previously know as _ServiceMix kernel_, so informations found here are applicable to [Apache ServiceMix Enterprise Service Bus](http://servicemix.apache.org/home.html) as well.
-
-Procedures described in this article were tested using Apache karaf 2.3.0
-
-Installation
-============
-
-ActiveMQ provides Karaf features which will help you integrate and use the broker in OSGi environment. For starters you need to add the features URL to Karaf. For version 5.9.0 you can do it like this:
-
-karaf@root> features:chooseurl activemq 5.9.0
-
-After that you should see newly added features
-
-karaf@root> features:list
-State Version Name Repository
-\[uninstalled\] \[5.9.0 \] activemq-broker activemq-5.9.0
-\[uninstalled\] \[5.9.0 \] activemq-http activemq-5.9.0
-\[uninstalled\] \[5.9.0 \] activemq-camel activemq-5.9.0
-\[uninstalled\] \[5.9.0 \] activemq-web-console activemq-5.9.0
-
-Installing and running the broker is as simple as installing `activemq-broker` feature, like
-
-karaf@root> features:install activemq-broker
-
-This will install and start the full broker (including the web console), just as if you started the standalone distribution.
-
-Broker Configuration
-====================
-
-Broker is configured using OSGi Config Admin mechanism and could be easily managed in [Karaf](http://karaf.apache.org/manual/latest-2.3.x/users-guideCommunity/FAQ/configuration.md). Configuration can be done by modifying `${KARAF_BASE}/etc/org.apache.activemq.server-default.cfg` file or respective config admin property. An example of the file looks like
-
-broker-name=amq-broker
-data=${karaf.data}/${broker-name}
-config=${karaf.base}/etc/activemq.xml
-
-Mandatory properties are listed in the following table
-
-Property Name
-
-Property Description
-
-broker-name
-
-Name of the broker
-
-config
-
-Location of the XML configuration file
-
-You can also use this file to set other properties which will replace placeholders in XML configuration file, as the `${data`} property is used in this example.
-
-Default XML configuration file is located in the `${KARAF_BASE}/etc/activemq.xml` by default.
-
-Web Console
-===========
-
-Web Console is installed by default and can be reached at [http://localhost:8181/activemqweb/](http://localhost:8181/activemqweb/)
-
-The configuration for the console is done in a similar fashion to the broker itself. Configuration is located in `${KARAF_BASE}/etc/org.apache.activemq.webconsole.cfg` and by default looks like
-
-webconsole.jms.url=tcp://localhost:61616
-webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/karaf-root
-webconsole.jmx.user=karaf
-webconsole.jmx.password=karaf
-
-**Optional:** In order to use the ActiveMQ console with a broker configured with authentication, it is necessary to configure the username/password for JMS connection as well.
-
-webconsole.jms.user=system
-webconsole.jms.password=manager
-
-Commands
-========
-
-After these simple steps you have all necessary libraries installed in the container. Also, now you have specific commands on your disposal that you can use to manage your broker:
-
- browse Display selected messages in a specified destination
- bstat Displays useful broker statistics
- list Lists all available brokers in the specified JMX context
- purge Delete selected destination's messages that matches the message selector
- query Display selected broker component's attributes and statistics
- dstat Performs a predefined query that displays useful tabular statistics regarding the specified destination type
-
-Help on commands
-
-To obtain some detailed help on a given command, you can run:
-
-activemq:\[command\] --help
-
-Broker querying
----------------
-
-Several commands are available to query the broker. To address local brokers, you need to use the `--jmxlocal` parameter.
-
-The following command displays available brokers:
-
-karaf@root> activemq:list --jmxlocal
-BrokerName = mybroker
-
-To have more detailed informations, run:
-
-karaf@root> activemq:query --jmxlocal
-
-It will display informations about the connectors, list of queues, etc...
-
-You can also browse or purge queues using the `activemq:browse` and `activemq:purge` commands.
-
diff --git a/src/_documents/classic/Connectivity/Containers/resource-adapter.md b/src/_documents/classic/Connectivity/Containers/resource-adapter.md
deleted file mode 100644
index f51d241..0000000
--- a/src/_documents/classic/Connectivity/Containers/resource-adapter.md
+++ /dev/null
@@ -1,54 +0,0 @@
-Apache ActiveMQ ™ -- Resource Adapter
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [Resource Adapter](../../Connectivity/Containers/resource-adapter.md)
-
-
-Introduction
-------------
-
-ActiveMQ includes a Java Connector Architecture (JCA) 1.5 Resource Adapter. JCA 1.5 defines the contract between an J2EE application server and external resources such as databases and messaging middleware. It allows the application server to efficiently pool connections, control transactions and manage security. The Resource Adapter allows ActiveMQ to be used from any J2EE 1.4 application server. We have tested that the Resource Adapter works in the following J2EE 1.4 containers
-
-* [TomEE](http://tomee.apache.org/tomcat-/FAQ/jms.md) 1
-* Geronimo 1
-* GlassFish
-* JBoss 4
-* WebLogic 9
-* WebSphere 6
-
-Features
---------
-
-* Inbound connection delivers messages to MDBs via XA or local transactions.
-* Outbound connections support standard container pooling or can reuse the inbound connection/session to avoid XA.
-* JTA support: Can be enlisted in XA and local transactions.
-* XA transaction recovery via XAResource.recover() supported.
-* When used outside a JTA transaction, session transaction settings retain normal JMS semantics so that it be used by your web-app tier.
-* Can configure and start up embedded broker.
-* Can connect to external ActiveMQ broker or embedded broker.
-* Inbound message delivery supports fine grain control of concurrency and prefetching.
-* Batching so that multiple messages can be delivered within the same transaction for optimal performances.
-
-Downloading the RAR
--------------------
-
-The RAR is available via [maven central](http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22activemq-rar%22)
-
-Deployment Guides
-
-* [TomEE](../../Connectivity/Containers/Resource Adapter/tomee.md)
-* [Geronimo](../../Connectivity/Containers/geronimo.md)
-* [Integrating Apache ActiveMQ with Glassfish](../../Connectivity/Containers/integrating-apache-activemq-with-glassfish.md)
-* [JBoss Integration](../../Connectivity/Containers/jboss-integration.md)
-
-The use of an Embedded Broker
------------------------------
-
-The ActiveMQ Resource Adapter can connect to a remote broker using any of the available transports, or it can start up an embedded broker. As described in the [Resource Adapter Properties](../../Connectivity/Containers/Resource Adapter/resource-adapter-properties.md), you can enable an embedded broker using the **BrokerXmlConfig** property.
-
-Configuration Reference
------------------------
-
-* [Resource Adapter Properties](../../Connectivity/Containers/Resource Adapter/resource-adapter-properties.md)
-* [Connection Factory Properties](../../Connectivity/Containers/Resource Adapter/connection-factory-properties.md)
-* [Activation Spec Properties](../../Connectivity/Containers/Resource Adapter/activation-spec-properties.md)
-
diff --git a/src/_documents/classic/Connectivity/Containers/sjsas-with-genericjmsra.md b/src/_documents/classic/Connectivity/Containers/sjsas-with-genericjmsra.md
deleted file mode 100644
index ecbb82a..0000000
--- a/src/_documents/classic/Connectivity/Containers/sjsas-with-genericjmsra.md
+++ /dev/null
@@ -1,164 +0,0 @@
-Apache ActiveMQ ™ -- SJSAS with GenericJMSRA
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [SJSAS with GenericJMSRA](../../Connectivity/Containers/sjsas-with-genericjmsra.md)
-
-
-Using ActiveMQ, Generic JMS RA and SJSAS (Glassfish)
-====================================================
-
-This document is my notes on making ActiveMQ and SJSAS work together using GenericJMSRA. The objectives is to make ActiveMQ as the JMS provider and MDB can be deployed in SJSAS, listening messages from ActiveMQ. Please note that, the SJSAS version I use is 9.0 Update 1. I don't have time to test it with SJSAS 9.1 or Glassfish v2.
-
-The procedures
---------------
-
-First, download all binaries:
-
-* genericra 1.7 (rar)
-* activemq 4.1.1 (zip or tar.gz)
-
-The activemq have some dependencies, however, you can easily found all of them in the distribution (the zip or tar.gz). The following is list of minimum dependencies:
-
-* activemq-core
-* activeio
-* commons-logging
-* backport-util-concurrent
-
-In order to use genericra you need to first create a resource adapter config using asadmin (Command line tools of SJSAS).
-
-asadmin create-resource-adapter-config
- --property
- SupportsXA=false
- :RMPolicy=OnePerPhysicalConnection
- :ProviderIntegrationMode=javabean
- :ConnectionFactoryClassName=org.apache.activemq.ActiveMQConnectionFactory
- :QueueConnectionFactoryClassName=org.apache.activemq.ActiveMQConnectionFactory
- :TopicConnectionFactoryClassName=org.apache.activemq.ActiveMQConnectionFactory
- :XAConnectionFactoryClassName=org.apache.activemq.ActiveMQXAConnectionFactory
- :XAQueueConnectionFactoryClassName=org.apache.activemq.ActiveMQXAConnectionFactory
- :XATopicConnectionFactoryClassName=org.apache.activemq.ActiveMQXAConnectionFactory
- :UnifiedDestinationClassName=org.apache.activemq.command.ActiveMQDestination
- :QueueClassName=org.apache.activemq.command.ActiveMQQueue
- :TopicClassName=org.apache.activemq.command.ActiveMQTopic
- :ConnectionFactoryProperties=brokerURL\\\=tcp\\\://127.0.0.1\\\:61616
- :LogLevel=FINE
- myapp#genericra
-
-You should note that, the above command should executed as one single line and no space around ':'. Just like:
-
-asadmin create-resource-adapter-config --property SupportsXA=false:ConnectionFactoryProperties=brokerURL\\\=tcp\\\://127.0.0.1\\\:61616 myapp#genericra
-
-Under DOS prompt, you should use ONLY ONE '/' to do espcape, like this.
-
-asadmin create-resource-adapter-config --property SupportsXA=false:ConnectionFactoryProperties=brokerURL\\=tcp\\://127.0.0.1\\:61616 myapp#genericra
-
-Package your application, genericra.rar and activemq dependencies in one single EAR. The structure of the EAR should like this:
-
- lib/activemq-core-4.1.1.jar
- lib/log4j-1.2.13.jar
- lib/commons-logging-1.1.jar
- lib/backport-util-concurrent-2.1.jar
- lib/activeio-core-3.0.0-incubator.jar
- META-INF/application.xml
- genericra.rar
- mymodules.jar
-
-Inside the mymodules.jar (where I put my MDB), the sun-ejb-jar.xml should look like this:
-
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE sun-ejb-jar
- PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 EJB 2.1//EN"
- "http://www.sun.com/software/appserver/dtds/sun-ejb-jar\_2\_1-1.dtd">
-<sun-ejb-jar>
- <enterprise-beans>
- <ejb>
- <ejb-name>TestingMessageDrivenBean</ejb-name>
- <mdb-connection-factory>
- <jndi-name>jms/SimpleQueueConnectionFactory</jndi-name>
- </mdb-connection-factory>
- <mdb-resource-adapter>
- <resource-adapter-mid>myapp#genericra</resource-adapter-mid>
- <activation-config>
- <activation-config-property>
- <activation-config-property-name>DestinationType</activation-config-property-name>
- <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
- </activation-config-property>
- <activation-config-property>
- <activation-config-property-name>DestinationProperties</activation-config-property-name>
- <activation-config-property-value>PhysicalName=Foo.Bar</activation-config-property-value>
- </activation-config-property>
- </activation-config>
- </mdb-resource-adapter>
- </ejb>
- </enterprise-beans>
-</sun-ejb-jar>
-
-And the application.xml should look like this:
-
-<?xml version="1.0" encoding="UTF-8"?>
-<application
- xmlns="http://java.sun.com/xml/ns/javaee"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
- version="5">
- <description>Example DD</description>
- <display-name>sample app with amq and genericra</display-name>
- <module>
- <ejb>mymodules.jar</ejb>
- </module>
- <module>
- <connector>genericra.rar</connector>
- </module>
-</application>
-
-Deploy the genericra:
-
-asadmin deploy --name myapp myapp.ear
-
-Create connection pool. Run the following command in one single line:
-
-asadmin create-connector-connection-pool
- --raname myapp#genericra
- --connectiondefinition javax.jms.QueueConnectionFactory
- --transactionsupport LocalTransaction
- ActiveMQQueueConnectionFactoryPool
-
-Create connection factory admin object. Run the following command in one single line, note that, "jms/SimpleQueueConnectionFactory" need to match in your sun-ejb-jar.xml:
-
-asadmin create-connector-resource
- --poolname ActiveMQQueueConnectionFactoryPool
- jms/SimpleQueueConnectionFactory
-
-Classloader / commons-logging+log4j issue
------------------------------------------
-
-In the procedure shown above, you should notice one thing, ie, the RA, ActiveMQ and my MDB is deployed as one single EAR. You can deploy the genericra standalone without putting it into the ear, provided that you are not using commons-logging and log4j (directly or indirectly).
-
-In the application I'm working on, commons-logging is used, and ActiveMQ also use commons-logging. In SJSAS, connector classloader is parent of the application classloader, as a result, if you deploy genericra independently, and then you deploy your application, log4j.xml will never get loaded except you put your application log4j.xml along with the ActiveMQ jars.
-
-With Java standard classloading procedure, classloader will first delegate the loading to parent. When application classloader lookup the LogFactory class, it will first delegate to its parent classloader (ie the connector classloader). As the connector classloader have loaded ActiveMQ and its dependencies (which include commons-logging), LogFactory will finally loaded by the connector classloader. When commons-logging try to initialize the LogFactoryImpl, and hence trigger the standard [...]
-
-As a result, deploy genericra independently is not the perfect solution in this case.
-
-Luckily, with some advice from Glassfish forum (thanks Sivakumar), I worked out a better solution, ie, packaged all things (including genericra and activemq) into one EAR. When packaged in this way, all classes will be loaded under one classloader, and the good thing is, you can put your log4j.xml within one of the your jar (ie, the normal way!).
-
-However, you should note one minor point, deploying genericra standalone and packaged with the EAR have one minor difference. If you deploy the RA with EAR, you need to reference the RA using the format 'appName#raName'. As a result, the reference name of the RA is myapp#genericra (see create-resource-adapter-config and sun-ejb-jar.xml part).
-
-If you deploy the RA independently, the ra name is just genericra (as shown in the example by Ramesh).
-
-LocalTransaction
-----------------
-
-In the instruction described above, LocalTransaction is used. (SupportsXA=false and --transactionsupport LocalTransaction) as I am currently using Non-XA transaction, however, as example shown by Ramesh, XA should also work.
-
-Configuring genericra
----------------------
-
-When you create the resource-adapter-config, there is two way to configure. One way is using JNDI, another way is using JavaBean introspection feature of genericra. In the example above, I go with JavaBean introspection feature (so 'ProviderIntegrationMode=javabean'). For more details on this, please checkout the user guide of genericra. Also, I found that expample provided on the genericra website is also valuable resource.
-
-Reference
----------
-
-* [Another example on using genericjmsra and activemq by Ramesh](http://weblogs.java.net/blog/rampsarathy/archive/2007/03/glassfish_v2_an_1.html)
-* [Official user guide on configuring genericjmsra](https://genericjmsra.dev.java.net/docs/userguide/userguide.html)
-* [The thread in Glassfish forum which I found my answer](http://forums.java.net/jive/thread.jspa?messageID=211849)
-
diff --git a/src/_documents/classic/Connectivity/Containers/spring-support.md b/src/_documents/classic/Connectivity/Containers/spring-support.md
deleted file mode 100644
index 133d9f0..0000000
--- a/src/_documents/classic/Connectivity/Containers/spring-support.md
+++ /dev/null
@@ -1,109 +0,0 @@
-Apache ActiveMQ ™ -- Spring Support
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [Spring Support](Connectivity/Containers/spring-Community/support.md)
-
-
-We fully support Spring for configuration of the JMS client side as well as for configuring the JMS Message Broker.
-There is a great [article](http://codedependents.com/2009/10/16/efficient-lightweight-jms-with-spring-and-activemq/) on using Spring with ActiveMQ - I'd recommend reading it first.
-
-Configuring the JMS client
---------------------------
-
-To configure an ActiveMQ JMS client in Spring it is just a simple matter of configuring an instance of ActiveMQConnectionFactory within a standard Spring XML configuration file like any other bean. There are [several examples and test cases](https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/spring/) available and [this one](https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/xbean/s [...]
-
-e.g. the following fragment of XML shows us creating a JMS connection factory for ActiveMQ connecting to a remote broker on a specific host name and port.
-
-<bean id="jmsFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL">
- <value>tcp://localhost:61616</value>
- </property>
- </bean>
-
-The following shows how to use Zeroconf to discover the available brokers to connect to.
-
-<bean id="jmsFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL">
- <value>zeroconf://_activemq.broker.development.</value>
- </property>
- </bean>
-
-From 1.1 of ActiveMQ onwards you can also use JNDI to configure ActiveMQ within Spring. [This example](http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/spring-jndi.xml) shows how to configure Spring using ActiveMQ's [JNDI Support](Connectivity/Containers/jndi-Community/support.md).
-
-### Using Spring
-
-If you are using the new [XML Schema-based configuration](http://static.springframework.org/spring/docs/2.0.x/reference/xsd-config.html) of Spring 2.0 you can embed the ActiveMQ broker XML inside any regular Spring.xml file without requiring the above factory bean. e.g. here is an example of a regular Spring XML file in Spring 2.0 which also configures a broker.
-
-<beans
- xmlns="http://www.springframework.org/schema/beans"
- xmlns:amq="http://activemq.apache.org/schema/core"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
- http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
-
- <amq:broker useJmx="false" persistent="false">
- <amq:transportConnectors>
- <amq:transportConnector uri="tcp://localhost:0" />
- </amq:transportConnectors>
- </amq:broker>
-
- <amq:connectionFactory id="jmsFactory" brokerURL="vm://localhost"/>
-</beans>
-
-This allows you to configure JMS artifacts like destinations and connection factories together with the entire broker.
-
-Working with Spring's JmsTemplate
----------------------------------
-
-Spring supports a handy abstraction, JmsTemplate, which allows you to hide some of the lower level JMS details when sending messages etc.
-
-Please be aware that there are a number of [JmsTemplate Gotchas](../../Connectivity/Containers/Spring Support/jmstemplate-gotchas.md) to be careful of.
-
-One thing to bear in mind with JmsTemplate is that by default it will create a new connection, session, producer for each message sent - then close them all down again. This is very inefficient! It is done like this to work in EJB containers which tend to use a special ConnectionFactory which does pooling.
-
-If you are not using a JCA container to manage your JMS connections, we recommend you use our pooling JMS connection provider, (org.apache.activemq.pool.PooledConnectionFactory) from the `activemq-pool` library, which will pool the JMS resources to work efficiently with Spring's JmsTemplate or with EJBs.
-
-e.g.
-
-<!\-\- a pooling based JMS provider -->
- <bean id="jmsFactory" class="org.apache.activemq.pool.PooledConnectionFactory" destroy-method="stop">
- <property name="connectionFactory">
- <bean class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL">
- <value>tcp://localhost:61616</value>
- </property>
- </bean>
- </property>
- </bean>
-
- <!\-\- Spring JMS Template -->
- <bean id="myJmsTemplate" class="org.springframework.jms.core.JmsTemplate">
- <property name="connectionFactory">
- <ref local="jmsFactory"/>
- </property>
- </bean>
-
-The `PooledConnectionFactory` supports the pooling of Connection, Session and MessageProducer instances so it can be used with tools like [Camel](http://camel.apache.org/activemq.html) and Spring's [JmsTemplate and MessagListenerContainer](http://activemq.apache.orgConnectivity/Containers/spring-Community/support.md) . Connections, sessions and producers are returned to a pool after use so that they can be reused later without having to undergo the cost of creating them again.
-
-Note: while the `PooledConnectionFactory` does allow the creation of a collection of active consumers, it does not 'pool' consumers. Pooling makes sense for connections, sessions and producers, which can be seldom-used resources, are expensive to create and can remain idle a minimal cost. Consumers, on the other hand, are usually just created at startup and left going, handling incoming messages as they come. When a consumer is complete, it's preferred to shut down it down rather than le [...]
-
-If you are creating a collection of consumers (for example, for multi-threaded message consumption), you should consider keeping a low prefetch value (e.g. 10 or 20), to ensure that all messages don't end up going to just one of the consumers.
-
-We do also have a pooling JMS ConnectionFactory for use inside a JCA / MDB container (org.apache.activemq.ra.InboundConnectionProxyFactory), when using our JCA Resource Adapter which will reuse the same JMS connection/session which is being used for inbound messages.
-
-Consuming JMS from inside Spring
---------------------------------
-
-Spring's [MessagListenerContainer](http://static.springsource.org/spring/docs/2.5.x/reference/FAQ/jms.md#Community/FAQ/jms.mdp) should be used for message consumption. This provides all the power of MDBs - efficient JMS consumption and pooling of the message listeners - but without requiring a full EJB container.
-
-You can use the `activemq-pool` `org.apache.activemq.pool.PooledConnectionFactory` for efficient pooling of the connections and sessions for your collection of consumers, or you can use the Spring JMS `org.springframework.jms.connection.CachingConnectionFactory` to achieve the same effect.
-
-More Information
-----------------
-
-Also check out the following blogs for information about using Spring JMS with ActiveMQ:
-
-* [Synchronous Request Response with ActiveMQ and Spring](http://codedependents.com/2010/03/04/synchronous-request-response-with-activemq-and-spring/)
-* [Using Spring to Send JMS Messages](http://bsnyderblog.blogspot.com/2010/02/using-spring-jmstemplate-to-send-/FAQ/jms.md)
-* [Using Spring to Receive JMS Messages](http://bsnyderblog.blogspot.com/2010/02/using-spring-to-receive-jms-messages.html)
-* [Tuning JMS Message Consumption In Spring](http://bsnyderblog.blogspot.com/2010/05/tuning-jms-message-consumption-in.html)
-
diff --git a/src/_documents/classic/Connectivity/Containers/sun-jndi.md b/src/_documents/classic/Connectivity/Containers/sun-jndi.md
deleted file mode 100644
index cb78535..0000000
--- a/src/_documents/classic/Connectivity/Containers/sun-jndi.md
+++ /dev/null
@@ -1,99 +0,0 @@
-Apache ActiveMQ ™ -- Sun JNDI
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [Sun JNDI](../../Connectivity/Containers/sun-jndi.md)
-
-
-here's an example jndi.properties file:
-
-java.naming.factory.initial = com.sun.jndi.fscontext.RefFSContextFactory
-
-Here's an example .bindind file:
-
-For ActiveMQ 4.x its
-
-Archive/ClassName=org.apache.activemq.command.ActiveMQQueue
-Archive/FactoryName=org.apache.activemq.jndi.JNDIReferenceFactory
-Archive/RefAddr/0/Type=physicalName
-Archive/RefAddr/0/Content=Archive
-Archive/RefAddr/0/Encoding=String
-
-GateIn/ClassName=org.apache.activemq.command.ActiveMQQueue
-GateIn/FactoryName=org.apache.activemq.jndi.JNDIReferenceFactory
-GateIn/RefAddr/0/Type=physicalName
-GateIn/RefAddr/0/Content=GateIn
-GateIn/RefAddr/0/Encoding=String
-
-ProviderIn/ClassName=org.apache.activemq.command.ActiveMQQueue
-ProviderIn/FactoryName=org.apache.activemq.jndi.JNDIReferenceFactory
-ProviderIn/RefAddr/0/Type=physicalName
-ProviderIn/RefAddr/0/Content=ProviderIn
-ProviderIn/RefAddr/0/Encoding=String
-
-ProviderOut/ClassName=org.apache.activemq.command.ActiveMQQueue
-ProviderOut/FactoryName=org.apache.activemq.jndi.JNDIReferenceFactory
-ProviderOut/RefAddr/0/Type=physicalName
-ProviderOut/RefAddr/0/Content=ProviderOut
-ProviderOut/RefAddr/0/Encoding=String
-
-QueueConnectionFactory/ClassName=org.apache.activemq.ActiveMQConnectionFactory
-QueueConnectionFactory/FactoryName=org.apache.activemq.jndi.JNDIReferenceFactory
-QueueConnectionFactory/RefAddr/0/Type=brokerURL
-QueueConnectionFactory/RefAddr/0/Content=vm\\://localhost
-QueueConnectionFactory/RefAddr/0/Encoding=String
-QueueConnectionFactory/RefAddr/1/Type=brokerName
-QueueConnectionFactory/RefAddr/1/Content=ID\\:zdv-1189-1098562819250-0\\:0
-QueueConnectionFactory/RefAddr/1/Encoding=String
-QueueConnectionFactory/RefAddr/2/Type=password
-QueueConnectionFactory/RefAddr/2/Content=defaultPassword
-QueueConnectionFactory/RefAddr/2/Encoding=String
-QueueConnectionFactory/RefAddr/3/Type=userName
-QueueConnectionFactory/RefAddr/3/Content=defaultUser
-QueueConnectionFactory/RefAddr/3/Encoding=String
-
-For ActiveMQ 3.x it is
-
-Archive/ClassName=org.activemq.message.ActiveMQQueue
-Archive/FactoryName=org.activemq.jndi.JNDIReferenceFactory
-Archive/RefAddr/0/Type=physicalName
-Archive/RefAddr/0/Content=Archive
-Archive/RefAddr/0/Encoding=String
-
-GateIn/ClassName=org.activemq.message.ActiveMQQueue
-GateIn/FactoryName=org.activemq.jndi.JNDIReferenceFactory
-GateIn/RefAddr/0/Type=physicalName
-GateIn/RefAddr/0/Content=GateIn
-GateIn/RefAddr/0/Encoding=String
-
-ProviderIn/ClassName=org.activemq.message.ActiveMQQueue
-ProviderIn/FactoryName=org.activemq.jndi.JNDIReferenceFactory
-ProviderIn/RefAddr/0/Type=physicalName
-ProviderIn/RefAddr/0/Content=ProviderIn
-ProviderIn/RefAddr/0/Encoding=String
-
-ProviderOut/ClassName=org.activemq.message.ActiveMQQueue
-ProviderOut/FactoryName=org.activemq.jndi.JNDIReferenceFactory
-ProviderOut/RefAddr/0/Type=physicalName
-ProviderOut/RefAddr/0/Content=ProviderOut
-ProviderOut/RefAddr/0/Encoding=String
-
-QueueConnectionFactory/ClassName=org.activemq.ActiveMQConnectionFactory
-QueueConnectionFactory/FactoryName=org.activemq.jndi.JNDIReferenceFactory
-QueueConnectionFactory/RefAddr/0/Type=brokerURL
-QueueConnectionFactory/RefAddr/0/Content=vm\\://localhost
-QueueConnectionFactory/RefAddr/0/Encoding=String
-QueueConnectionFactory/RefAddr/1/Type=brokerName
-QueueConnectionFactory/RefAddr/1/Content=ID\\:zdv-1189-1098562819250-0\\:0
-QueueConnectionFactory/RefAddr/1/Encoding=String
-QueueConnectionFactory/RefAddr/2/Type=password
-QueueConnectionFactory/RefAddr/2/Content=defaultPassword
-QueueConnectionFactory/RefAddr/2/Encoding=String
-QueueConnectionFactory/RefAddr/3/Type=useEmbeddedBroker
-QueueConnectionFactory/RefAddr/3/Content=true
-QueueConnectionFactory/RefAddr/3/Encoding=String
-QueueConnectionFactory/RefAddr/4/Type=userName
-QueueConnectionFactory/RefAddr/4/Content=defaultUser
-QueueConnectionFactory/RefAddr/4/Encoding=String
-QueueConnectionFactory/RefAddr/5/Type=useAsyncSend
-QueueConnectionFactory/RefAddr/5/Content=true
-QueueConnectionFactory/RefAddr/5/Encoding=String
-
diff --git a/src/_documents/classic/Connectivity/Containers/tomcat.md b/src/_documents/classic/Connectivity/Containers/tomcat.md
deleted file mode 100644
index 79e908d..0000000
--- a/src/_documents/classic/Connectivity/Containers/tomcat.md
+++ /dev/null
@@ -1,101 +0,0 @@
-Apache ActiveMQ ™ -- Tomcat
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [Tomcat](../../Connectivity/Containers/tomcat.md)
-
-
-#### Configuration issues for Tomcat 7 and later
-
-Tomcat needs to be configured to ignore Jetty SCI annotations so that the Jetty WebSocket ServerContainerInitializer class is not inadvertently picked up by Tomcat. For more information on this problem see [AMQ-6154](https://issues.apache.org/jira/browse/AMQ-6154) and [https://wiki.apache.org/tomcat/HowTo/FasterStartUp](https://wiki.apache.org/tomcat/HowTo/FasterStartUp) and consult the Tomcat documentation for the version you are using to properly exclude the Jetty jar files from being [...]
-
-Pre-integrated Tomcat with ActiveMQ
------------------------------------
-
-Apache TomEE is a distribution of [Tomcat with fully integrated ActiveMQ](http://tomee.apache.org/tomcat-/FAQ/jms.md). All integration steps detailed here have already been done. The stack supports injection of Topic, Queue and ConnectionFactory references as well as transactional sending and delivery.
-
-Something like the following works out of the box with no configuration:
-
-import javax.annotation.Resource;
-import javax.servlet.http.HttpServlet;
-import javax.jms.Topic;
-import javax.jms.Queue;
-import javax.jms.ConnectionFactory;
-
-public class MyServet extends HttpServlet {
-
- @Resource(name = "foo")
- private Topic fooTopic;
-
- @Resource(name = "bar")
- private Queue barQueue;
-
- @Resource
- private ConnectionFactory connectionFactory;
-
-Manually integrating Tomcat and ActiveMQ
-----------------------------------------
-
-Note, manually integrating ActiveMQ with Tomcat does allow for Topic, Queue, and ConnectionFactory injection but does not support transactional sending and delivery.
-
-You should go to Tomcat documentation and read JNDI Resources HOW-TO, especially part: Configure Tomcat's Resource Factory.
-
-ActiveMQ has ready JNDI resource factory for all its administered objects: ConnectionFactory and destinations.
-
-You must provide it as a parameter factory for your resources:
-
-<Context ...>
- ...
- <Resource name="jms/ConnectionFactory" auth="Container"
- type="org.apache.activemq.ActiveMQConnectionFactory"/>
- <ResourceParams name="jms/ConnectionFactory">
- <parameter>
- <name>factory</name>
- <value>org.activemq.jndi.JNDIReferenceFactory</value>
- </parameter>
- <parameter>
- <name>brokerURL</name>
- <value>vm://localhost</value>
- </parameter>
- <parameter>
- <name>brokerName</name>
- <value>LocalActiveMQBroker</value>
- </parameter>
- <parameter>
- <name>useEmbeddedBroker</name>
- <value>true</value>
- </parameter>
- </ResourceParams>
- ...
-</Context>
-
-If you are using Tomcat 5.5 or later then try this instead...
-
-<Context>
- ...
- <Resource name="jms/ConnectionFactory" auth="Container" type="org.apache.activemq.ActiveMQConnectionFactory" description="JMS Connection Factory"
- factory="org.apache.activemq.jndi.JNDIReferenceFactory" brokerURL="vm://localhost" brokerName="LocalActiveMQBroker"/>
- ....
-</Context>
-
-Also, don't forget to put ActiveMQ and dependent jars to tomcat shared lib directory.
-
-### Creating destinations in Tomcat 5.5 or later
-
-This is completely untested but should work 
-
-<Context>
- ...
- <Resource name="jms/someTopic" auth="Container" type="org.apache.activemq.command.ActiveMQTopic" description="my Topic"
- factory="org.apache.activemq.jndi.JNDIReferenceFactory" physicalName="FOO.BAR"/>
-
- <Resource name="jms/aQueue" auth="Container" type="org.apache.activemq.command.ActiveMQQueue" description="my Queue"
- factory="org.apache.activemq.jndi.JNDIReferenceFactory" physicalName="FOO.BAR"/>
- ....
-</Context>
-
-JMX Tip when working with Tomcat
-
-If you want to use JMX with Tomcat and then connect via JConsole to view the [JMX](../../Features/jmx.md) MBeans of the server then set the following
-
-CATALINA\_OPTS="$CATALINA\_OPTS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 \
- -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"
-
diff --git a/src/_documents/classic/Connectivity/Containers/weblogic-integration.md b/src/_documents/classic/Connectivity/Containers/weblogic-integration.md
deleted file mode 100644
index 830a4ba..0000000
--- a/src/_documents/classic/Connectivity/Containers/weblogic-integration.md
+++ /dev/null
@@ -1,618 +0,0 @@
-Apache ActiveMQ ™ -- WebLogic Integration
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [WebLogic Integration](../../Connectivity/Cross Language Clients/c-integration.md)
-
-
-ActiveMQ WebLogic Integration
-=============================
-
-ActiveMQ clients and brokers can be run in WebLogic Server or WebLogic Express. This is usually done for licensing reasons:
-
-* WebLogic Server includes JMS client and server features, but it may cost extra to use these JMS features to connect multiple servers together (as opposed to only using JMS internally within one server)
-* WebLogic Express disables the JMS features via the license, so while JMS classes are on the class path, there are no JMS features available.
- An ActiveMQ broker may be run within WebLogic to provide JMS features while avoiding these issues. As well, an ActiveMQ client may be run within WebLogic to connect to either an ActiveMQ broker running in the same WebLogic instance, and ActiveMQ broker running in a remote WebLogic instance, or a standalone ActiveMQ broker running elsewhere on the network.
-
-ActiveMQ Clients in WebLogic
-----------------------------
-
-An ActiveMQ client can be run in any recent version of WebLogic. However, the specifics depend on which revision of JMS is supported by your version of WebLogic.
-
-### WebLogic Server/Express versions including JMS 1.0.x
-
-This is known to include **WebLogic 8.1** and all previous versions.
-
-**Note:** ActiveMQ cannot deliver messages to message-driven beans in this version of WebLogic. You will need to create JMS clients manually to send and receive JMS messages.
-
-To work with ActiveMQ from one of these releases of WebLogic, you should not include any `javax.jms` classes with your application, but should instead use the JMS 1.0.x classes distributed with WebLogic. This means you should not use a fully-aggregated ActiveMQ JAR such as `activemq-4.0.1/incubator-activemq-4.0.1.jar` but instead, individual ActiveMQ JARs such as `activemq-4.0.1/lib/activeio-core-3.0-beta3.jar` and `activemq-4.0.1/lib/activemq-core-4.0.1.jar`.
-
-Further, your code should use only JMS 1.0.x versions of the JMS interfaces (such as `javax.jms.Session`). Note that JMS 1.1 uses many of the same interfaces, but has added numerous methods to them, and if you use the new methods your code will not run in this version of WebLogic. Try to ensure you're compiling your client code against the `weblogic.jar` from the correct version of WebLogic, or else a dedicated JMS 1.0.x JAR such as the one you can download from Sun. _Do not compile agai [...]
-
-Finally, you can connect to ActiveMQ using the normal ActiveMQ JNDI settings including a connect URL. Do not attempt to use WebLogic JNDI to connect to ActiveMQ, and do not use the WebLogic host name or listen port in the ActiveMQ connect URL – even if the ActiveMQ broker is run within WebLogic it will listen on a separate network port from the one that WebLogic uses.
-
-**TODO:** Add sample JMS 1.0.x code
-
-### WebLogic Server versions including JMS 1.1
-
-**WebLogic 9.2** and above are known to support JMS 1.1. (I don't know what JMS release WebLogic 9.0-9.1 support)
-
-To work with ActiveMQ in one of these release of WebLogic Server, you can use the J2EE Connector included with ActiveMQ (known as ActiveMQ-RA). This will provide full ActiveMQ support to J2EE applications – ActiveMQ can be used to both send messages and to deliver incoming messages to message-driven beans. Your J2EE applications can map connection factory and destination references in JNDI.
-
-_I don't have an example of using the J2EE Connector from a J2EE 1.4 application in WebLogic. If someone can contribute one that would be great!_
-
-If you're using Spring or another non-J2EE architecture in your application, you may choose to skip the J2EE Connector and just connect directly to ActiveMQ using the technique described in the next section.
-
-### WebLogic Express versions including JMS 1.1
-
-**WebLogic 9.2** and above are known to support JMS 1.1. (I don't know what JMS release WebLogic 9.0-9.1 support)
-
-J2EE Connectors are not supported in WebLogic Express, so that approach is out. Instead, any components that want to connect to ActiveMQ need to manually create the connection (or use a technique like Spring message-driven POJOs to manage it). However, this should be relatively trouble-free since ActiveMQ and WebLogic support the same JMS release.
-
-**TODO:** Example of JMS 1.1 client and Spring Message-Driven POJO client for WebLogic
-
-ActiveMQ Brokers in WebLogic
-----------------------------
-
-On the surface it's not obvious why you might want to run an ActiveMQ broker within WebLogic instead of standalone, but the considerations include:
-
-* When ActiveMQ is run within WebLogic, it can be deployed, started, stopped, and redeployed like other applications, using the WebLogic console or other tools, while the JVM and WebLogic are still running
-* ActiveMQ can hook into the WebLogic JMX management system (as well as e.g. JRockit) to provide a single management interface to the app server, applications, ActiveMQ, and even the JVM.
-* ActiveMQ can leverage WebLogic security realms for authentication and authorization – not only are there more security realm types available for WebLogic, but they're also easier to configure via the WebLogic console
-
-If you decide to run ActiveMQ standalone, that's fine, you can skip this section. Otherwise, read on.
-
-The specific integration techniques depend on whether you're using WebLogic Server or WebLogic Express, and whether your version supports JMS 1.0.x or JMS 1.1.
-
-### WebLogic Server/Express versions including JMS 1.0.x
-
-Deploying an ActiveMQ broker in a release of WebLogic Server or WebLogic Express that supports only JMS 1.0.x has not been tested. This is known to include **WebLogic 8.1** and all previous versions. It will probably have trouble due to conflicting versions of JMS used by ActiveMQ and by WebLogic.
-
-_Please report your results if you try this_
-
-### WebLogic Server versions including JMS 1.1
-
-**WebLogic 9.2** and above are known to support JMS 1.1. (I don't know what JMS release WebLogic 9.0-9.1 support)
-
-It is possible to deploy ActiveMQ in WebLogic Server in one of two ways:
-
-* **Using the ActiveMQ-RA J2EE Connector** – ActiveMQ provides a J2EE Connector that is normally used by clients to connect to a separate ActiveMQ broker. However, the J2EE Connector accepts arguments to run an embedded broker and provide the location of an XML config file for an embedded broker. This is probably the best way to deploy an ActiveMQ broker in WebLogic Server, because ActiveMQ then has access to WebLogic thread pools and other resources.
-* **Deploying an ActiveMQ Broker as a WebLogic Application** – This is the technique described below for WebLogic Express. It works equally well in WebLogic Server.
-
-The J2EE Connector approach has not be specifically tested, but should work well. It would need some additional classes to support the security and management integration as described in the next section, so those would need to be added to a JAR which is in turn added to the J2EE Connector RAR file. _Please report your results if you try this_
-
-### WebLogic Express versions including JMS 1.1
-
-**WebLogic 9.2** and above are known to support JMS 1.1. (I don't know what JMS release WebLogic 9.0-9.1 support)
-
-Since WebLogic Express does not support J2EE Connectors, it is necessary to deploy ActiveMQ wrapped in an application that is deployed to WebLogic. Note that ActiveMQ runs in the XBean container, so XBean must be pointed to an appropriate configuration file to start up and it will then configure and start all the ActiveMQ components. The first challenge is then to construct an application that locates the right config file(s) and starts the ActiveMQ broker when it is deployed.
-
-#### ActiveMQ as a WebLogic Application
-
-The easiest type of WebLogic application to configure with all the needed ActiveMQ libraries and configuration and not much else is a web application. The JARs go in `WEB-INF/lib/` and config files typically in `WEB-INF/`. The only necessary configuration for the web application itself is to install a listener that will start and stop ActiveMQ when the web application is started and stopped. There are also a couple optional classes that can be used to integrate ActiveMQ with WebLogic's s [...]
-
-#### Management Options
-
-ActiveMQ exposes a number of management and monitoring features via JMX. There are three ways to expose these JMX objects:
-
-1. Have ActiveMQ start its own JMX MBeanServer and network connector (typically on port 1099)
-2. Have ActiveMQ use the JVM's MBeanServer (for Java 5 and higher, either Sun VM or JRockit VM)
-3. Have ActiveMQ use the MBeanServer provided by a runtime environment such as WebLogic
-
-Each approach has its advantages and disadvantages. A few things to note:
-
-* Make sure that each ActiveMQ instance on the same machine uses a separate network port to handle JMX requests. This is set in the config file when using the ActiveMQ MBeanServer, in a system property (command-line argument) when using the JVM's MBeanServer, and it uses the standard WebLogic listen port for WebLogic JMX
-* JRockit appears to require a runtime license to use the embedded MBeanServer, while the Sun JVM provides it for free
-
-The sample below includes an optional configuration block that lets ActiveMQ hook into the WebLogic runtime MBeanServer. This means ActiveMQ MBeans will appear alongside WebLogic MBeans (and even JVM MBeans if they are enabled). With this approach, management clients will access ActiveMQ MBeans through the normal WebLogic listen port (e.g. 7001) rather than using a dedicated JMX port, though IIOP must be enabled for this to work. However, note that this is optional, and you can skip that [...]
-
-#### Security Options
-
-ActiveMQ has optional authentication and authorization plugins, which are based on JAAS. Fortunately, WebLogic provides a JAAS LoginModule that performs the authentication against the default WebLogic security realm, and returns the appropriate principals for authorization. Unfortunately, by default, ActiveMQ cannot authorize access to specific users within the security realm based on WebLogic principals, meaning either there's no security or a login is required but any user with a valid [...]
-
-You may choose to use authentication only, in which case any user with a valid WebLogic login can access ActiveMQ, and no custom code is necessary. You may also add authorization to that using some custom code, to apply specific security constraints to specific users or destinations. For purposes of this example, we have only implemented an authorization approach that allows any member of a single specific WebLogic group to access all resources in ActiveMQ. Between the authorization plug [...]
-
-#### Persistence Options
-
-ActiveMQ uses a combination of a local journal (files on the file system) and a backing database by default. In the standard configuration, an embedded Derby database is used. This runs fine in WebLogic, but it's also possible to have ActiveMQ use a database connection pool defined in WebLogic, rather than using a separate Derby database. The configuration files shown later have commented-out sections referring to a WebLogic database connection pool – if you want to use those, you'll jus [...]
-
-Note that ActiveMQ will create the tables it needs the first time it connects to a database, so no particular preparation is required for the database.
-
-#### ActiveMQ Integration Architecture
-
-The ActiveMQ-in-WebLogic combination looks like this:
-
-
-
-To summarize this diagram:
-
-* ActiveMQ runs as a web application, which runs in the web container inside WebLogic Express
-* ActiveMQ reads two configuration files from a directory on the WebLogic class path – one to configure ActiveMQ itself, and one to configure its logging output
-* ActiveMQ uses two main resources from WebLogic Express – the JMX management server (MBeanServer) and the WebLogic security realm (in the form of a JAAS LoginModule).
-* In order to start ActiveMQ when the web application is deployed, the `web.xml` includes a context listener for Spring, and the Spring `applicationContext.xml` file loads the ActiveMQ broker and points it to the ActiveMQ configuration file (which as mentioned above, is stored in a directory on the class path).
-* Within ActiveMQ:
- * A configuration block in the ActiveMQ configuration file causes ActiveMQ to register all its JMX MBeans with the WebLogic JMX MBeanServer
- * A security plugin causes all clients to authenticate against the WebLogic security realm
- * The security plugin also reads the name of a WebLogic group from the ActiveMQ configuration file, and requires that any client must be a member of that group (when WebLogic processed the login, it must have created a principal for that group for the user)
- * The ActiveMQ configuration file also identifies a network listen port that ActiveMQ will listen on for JMS clients. Any clients must include the server's hostname and this listen port in their connect URL.
- * The ActiveMQ logging system (Log4J) outputs log message in the format specified in and to the destinations specified in the logging configuration file
- * Persistent messages are stored to the journal in the ActiveMQ Data Directory and periodically spooled to a remote database (database not shown in diagram)
-* Note that ActiveMQ uses its own threads; since WebLogic Express does not support J2EE Connectors, it is not possible for ActiveMQ to access a WebLogic thread pool without more extensive customization
-
-#### Building the ActiveMQ to WebLogic Integration WAR
-
-This section discusses the code, libraries, and configuration files necessary to build the ActiveMQ web application that will be deployed in WebLogic Express.
-
-##### Starting and Stopping ActiveMQ
-
-ActiveMQ needs to start when the web application is deployed or started, and stop when the web application is stopped or undeployed. The easiest way to do this is to a use the commonly available Spring listeners, which start a Spring context, which can point ActiveMQ to an XBean configuration file, which starts ActiveMQ. A little roundabout, but it works well in practice with very little configuration.
-
-**J2EE WEB-INF/web.xml**
-
-<?xml version="1.0" encoding="UTF-8"?>
-
-<web-app version="2.4"
- xmlns="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app\_2\_4.xsd" >
- <listener>
- <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
- </listener>
-</web-app>
-
-**Spring WEB-INF/applicationContext.xml**
-
-<?xml version="1.0" encoding="UTF-8" ?>
-<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
-<beans>
- <bean id="brokerService" class="org.apache.activemq.xbean.BrokerFactoryBean">
- <property name="config" value="classpath:activemq-config.xml"/>
- </bean>
-</beans>
-
-Again, the `web.xml` listener starts Spring and reads the Spring `META-INF/applicationContext.xml` file (the default location used by the `ContextLoaderListener`), and the `applicationContext.xml` indicates that the ActiveMQ configuration file should be read from the class path with the name `activemq-config.xml`. That file could be placed in `WEB-INF/classes` or in a directory on the file system that is added to the WebLogic class path (for ease of editing).
-
-With this approach, the normal WebLogic deployment tools, admin console, etc. can be used to deploy, start, stop, and restart ActiveMQ (packaged into a web application WAR).
-
-##### Required Libraries
-
-ActiveMQ required a number of JARs which should be included in the web application `WEB-INF/lib` directory.
-
-This list was generated for ActiveMQ 4.0.1:
-
-* `activemq-core` (basic ActiveMQ code)
-* `activemq-jaas` (ActiveMQ security code)
-* `activeio-core` (ActiveMQ networking layer)
-* `derby` (embedded DB for persistent messages)
-* `commons-logging` (logging abstraction library)
-* `log4j` (actual logging package used)
-* `backport-util-concurrent` (concurrency utility library)
-* `spring` (used to configure and start ActiveMQ)
-* `xbean-spring` (used to configure ActiveMQ)
-
-Additionally, to build the custom security plugins, the WebLogic `server/lib/weblogic.jar` is presently required at compile time.
-
-Of these, Derby could be omitted if ActiveMQ was configured to not use a database for persistence or to use a separate database (e.g. a WebLogic database pool) for persistence. The WebLogic JAR is needed only at build time (it's provided by the server at runtime). Spring could be omitted if a different strategy was used to start and stop ActiveMQ when the web app was started or stopped (a little custom code could replace this dependency). The rest are probably unavoidable, unless ActiveM [...]
-
-##### WebLogic Integration Code
-
-There are two custom classes used for this example. We'll show in a minute how to configure ActiveMQ to use these. Note that these are optional – if you don't want to leverage WebLogic's security realm, you can skip these.
-
-The first class makes ActiveMQ use the WebLogic security realm for authentication, and lets you specify a single WebLogic group to use for authorization (only members of that group can access ActiveMQ, though group members have full access to ActiveMQ).
-
-**ActiveMQToWebLogicSecurity.java**
-
-This class is an ActiveMQ "plugin", which installs two filters (authorization and authentication) which will be invoked on every request. This is similar to the default behavior provided by ActiveMQ's `JaasAuthenticationPlugin` and `AuthorizationPlugin`.
-
-/\*\*
- \* An ActiveMQ security plugin that installs two security filters
- \* (authentication and authorization) that use WebLogic security realms to
- \* handle the login and provide user and group principals.
- */
-public class ActiveMQToWebLogicSecurity implements BrokerPlugin {
- private String authorizedGroup;
-
- public Broker installPlugin(Broker broker) {
- // Install the first filter for authentication
- Broker first = new ActiveMQWebLogicAuthenticationFilter(broker);
- // Configure and install the second filter for authorization
- AuthorizationEntry entry = new AuthorizationEntry();
- Set acls = new HashSet();
- acls.add(new WLSGroupImpl(authorizedGroup));
- entry.setAdminACLs(acls);
- entry.setReadACLs(acls);
- entry.setWriteACLs(acls);
- DefaultAuthorizationMap map = new DefaultAuthorizationMap();
- map.setDefaultEntry(entry);
- //todo: if finer-grained access is required, add more entries to the authorization map
- Broker second = new AuthorizationBroker(first, map);
- return second;
- }
-
- public String getAuthorizedGroup() {
- return authorizedGroup;
- }
-
- /\*\*
- \* Called by XBean at configuration time to set the authorized group from a
- \* property in the main ActiveMQ configuration file.
- */
- public void setAuthorizedGroup(String authorizedGroup) {
- this.authorizedGroup = authorizedGroup;
- }
-}
-
-The second class is the authentication filter used by the class above to authenticate all logins against the WebLogic default security realm.
-
-**ActiveMQWebLogicAuthenticationFilter.java**
-
-/\*\*
- \* A broker filter that authenticates callers against WebLogic security.
- \* This is similar to the ActiveMQ JaasAuthenticationBroker except for two
- \* things:
- \* <ul>
- \* <li>Instead of reading a JAAS configuration file, it hardcodes the JAAS
- \* configuration to require authentication against WebLogic</li>
- \*
- \* <li>The SecurityContext implementation overrides the method used to
- \* compare actual and eligible principals in order to handle the fact
- \* that WebLogic principals (WLSGroupImpl in particular) do not seem
- \* to match according to equals and hashCode even if the principal class
- \* and principal name are the same (perhaps having to do with the
- \* signature data on the WLSAbstractPrincipal).</li>
- \* </ul>
- */
-public class ActiveMQWebLogicAuthenticationFilter extends BrokerFilter {
- private final static Configuration WEBLOGIC\_JAAS\_CONFIGURATION = new Configuration() {
- public AppConfigurationEntry\[\] getAppConfigurationEntry(String name) {
- return new AppConfigurationEntry\[\]{
- new AppConfigurationEntry("weblogic.security.auth.login.UsernamePasswordLoginModule",
- AppConfigurationEntry.LoginModuleControlFlag.REQUIRED, Collections.EMPTY_MAP)
- };
- }
-
- public void refresh() {
- }
- };
- private final CopyOnWriteArrayList securityContexts = new CopyOnWriteArrayList();
-
- public ActiveMQWebLogicAuthenticationFilter(Broker next) {
- super(next);
- }
-
- static class JaasSecurityContext extends SecurityContext {
-
- private final Subject subject;
-
- public JaasSecurityContext(String userName, Subject subject) {
- super(userName);
- this.subject = subject;
- }
-
- public Set getPrincipals() {
- return subject.getPrincipals();
- }
-
- /\*\*
- \* This is necessary because WebLogic uses extra logic when comparing principals,
- \* probably to check whether they are cryptographically signed (which WebLogic
- \* supports). We skip that test because ActiveMQ does not sign the principals
- \* it deals with.
- */
- public boolean isInOneOf(Set eligiblePrincipals) {
- for (Iterator it = getPrincipals().iterator(); it.hasNext();) {
- Principal test = (Principal) it.next();
- for (Iterator el = eligiblePrincipals.iterator(); el.hasNext();) {
- Principal eligible = (Principal) el.next();
- if(test.getName().equals(eligible.getName()) &&
- test.getClass().getName().equals(eligible.getClass().getName())) {
- return true;
- }
- }
- }
- return false;
- }
- }
-
- public void addConnection(ConnectionContext context, ConnectionInfo info) throws Exception {
- if( context.getSecurityContext()==null ) {
- // Do the login.
- try {
- LoginContext lc = new LoginContext("ActiveMQ", new Subject(),
- new URLCallbackHandler(info.getUserName(), info.getPassword()),
- WEBLOGIC\_JAAS\_CONFIGURATION);
- lc.login();
- Subject subject = lc.getSubject();
-
- SecurityContext s = new JaasSecurityContext(info.getUserName(), subject);
- context.setSecurityContext(s);
- securityContexts.add(s);
- } catch (Exception e) {
- throw (SecurityException)new SecurityException("User name or password is invalid.").initCause(e);
- }
- }
- super.addConnection(context, info);
- }
-
- public void removeConnection(ConnectionContext context, ConnectionInfo info, Throwable error) throws Exception {
- super.removeConnection(context, info, error);
- if( securityContexts.remove(context.getSecurityContext()) ) {
- context.setSecurityContext(null);
- }
- }
-
- /\*\*
- \* Previously logged in users may no longer have the same access anymore. Refresh
- \* all the logged into users.
- */
- public void refresh() {
- for (Iterator iter = securityContexts.iterator(); iter.hasNext();) {
- SecurityContext sc = (SecurityContext) iter.next();
- sc.getAuthorizedReadDests().clear();
- sc.getAuthorizedWriteDests().clear();
- }
- }
-}
-
-##### Sample ActiveMQ Configuration Files
-
-This section shows three sample ActiveMQ configuration files – one for a single broker with the security and management plugins listed above, and one for a network of two brokers with the security and management plugins listed above. If you want to skip the security and management plugins, you can remove those attributes from the main `<broker>` element and remove the `<bean>` definitions for them below.
-
-It also shows a Log4J configuration file, which controls the ActiveMQ log output.
-
-**Single Broker**
-
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://activemq.org/config/1.0">
- <!\-\- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
-
- <broker useJmx="true" brokerName="MyBroker" useShutdownHook="false"
- plugins="#WebLogicSecurity">
-
- <!\-\- Register all ActiveMQ MBeans with the WebLogic runtime MBeanServer -->
- <managementContext>
- <managementContext>
- <MBeanServer>
- <bean class="org.springframework.jndi.JndiObjectFactoryBean" xmlns="">
- <property name="jndiName" value="java:comp/env/jmx/runtime" />
- <property name="lookupOnStartup" value="true" />
- <property name="expectedType" value="javax.management.MBeanServer" />
- </bean>
- </MBeanServer>
- </managementContext>
- </managementContext>
-
- <persistenceAdapter>
- <!\-\- By default, use an embedded Derby database -->
- <journaledJDBC journalLogFiles="5"
- dataDirectory="/server/bea/weblogic920/domains/jms/activemq-data"/>
- <!\-\- Use this with the WebLogicDataSource below to use a WebLogic
- database connection pool instead of the embedded Derby database
- <journaledJDBC journalLogFiles="5"
- dataDirectory="/server/bea/weblogic920/domains/jms/activemq-data"
- dataSource="#WebLogicDataSource" />
-
- -->
- </persistenceAdapter>
-
- <transportConnectors>
- <transportConnector name="MyBrokerTCP" uri="tcp://0.0.0.0:61616" />
- </transportConnectors>
- </broker>
-
- <bean id="WebLogicSecurity"
- class="com.example.activemq.weblogic.ActiveMQToWebLogicSecurity">
- <property name="authorizedGroup" value="ActiveMQUsers" />
- </bean>
-
-<!\-\- Uncomment and configure this if you want to use a WebLogic database
- connection pool for persistent messages
- <bean id="WebLogicDataSource"
- class="org.springframework.jndi.JndiObjectFactoryBean">
- <property name="jndiName" value="db/pool/jndi/name"/>
- </bean>
--->
-</beans>
-
-**Network of Brokers (Broker 1/2)**
-
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://activemq.org/config/1.0">
- <!\-\- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
-
- <broker useJmx="true" brokerName="FirstBroker" useShutdownHook="false"
- plugins="#WebLogicSecurity">
-
- <!\-\- Register all ActiveMQ MBeans with the WebLogic runtime MBeanServer -->
- <managementContext>
- <managementContext>
- <MBeanServer>
- <bean class="org.springframework.jndi.JndiObjectFactoryBean" xmlns="">
- <property name="jndiName" value="java:comp/env/jmx/runtime" />
- <property name="lookupOnStartup" value="true" />
- <property name="expectedType" value="javax.management.MBeanServer" />
- </bean>
- </MBeanServer>
- </managementContext>
- </managementContext>
-
- <persistenceAdapter>
- <!\-\- By default, use an embedded Derby database -->
- <journaledJDBC journalLogFiles="5"
- dataDirectory="/server/bea/weblogic920/domains/jms/activemq-b1-data"/>
- <!\-\- Use this with the WebLogicDataSource below to use a WebLogic
- database connection pool instead of the embedded Derby database
- <journaledJDBC journalLogFiles="5"
- dataDirectory="/server/bea/weblogic920/domains/jms/activemq-b1-data"
- dataSource="#WebLogicDataSource" />
-
- -->
- </persistenceAdapter>
-
- <transportConnectors>
- <transportConnector name="FirstBrokerTCP" uri="tcp://0.0.0.0:60010" />
- </transportConnectors>
-
- <networkConnectors>
- <networkConnector name="Broker1ToBroker2"
- uri="static://(tcp://localhost:60011)" failover="true"
- userName="fixme" password="fixme"/>
- </networkConnectors>
- </broker>
-
- <bean id="WebLogicSecurity"
- class="com.example.activemq.weblogic.ActiveMQToWebLogicSecurity">
- <property name="authorizedGroup" value="ActiveMQUsers" />
- </bean>
-
-<!\-\- Uncomment and configure this if you want to use a WebLogic database
- connection pool for persistent messages
- <bean id="WebLogicDataSource"
- class="org.springframework.jndi.JndiObjectFactoryBean">
- <property name="jndiName" value="db/pool/jndi/name"/>
- </bean>
--->
-</beans>
-
-**Network of Brokers (Broker 2/2)**
-
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://activemq.org/config/1.0">
- <!\-\- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
-
- <broker useJmx="true" brokerName="SecondBroker" useShutdownHook="false"
- plugins="#WebLogicSecurity">
-
- <!\-\- Register all ActiveMQ MBeans with the WebLogic runtime MBeanServer -->
- <managementContext>
- <managementContext>
- <MBeanServer>
- <bean class="org.springframework.jndi.JndiObjectFactoryBean" xmlns="">
- <property name="jndiName" value="java:comp/env/jmx/runtime" />
- <property name="lookupOnStartup" value="true" />
- <property name="expectedType" value="javax.management.MBeanServer" />
- </bean>
- </MBeanServer>
- </managementContext>
- </managementContext>
-
- <persistenceAdapter>
- <!\-\- By default, use an embedded Derby database -->
- <journaledJDBC journalLogFiles="5"
- dataDirectory="/server/bea/weblogic920/domains/jms/activemq-b2-data"/>
- <!\-\- Use this with the WebLogicDataSource below to use a WebLogic
- database connection pool instead of the embedded Derby database
- <journaledJDBC journalLogFiles="5"
- dataDirectory="/server/bea/weblogic920/domains/jms/activemq-b2-data"
- dataSource="#WebLogicDataSource" />
-
- -->
- </persistenceAdapter>
-
- <transportConnectors>
- <transportConnector name="SecondBrokerTCP" uri="tcp://0.0.0.0:60011" />
- </transportConnectors>
-
- <networkConnectors>
- <networkConnector name="Broker2ToBroker1"
- uri="static://(tcp://localhost:60010)" failover="true"
- userName="fixme" password="fixme" />
- </networkConnectors>
- </broker>
-
- <bean id="WebLogicSecurity"
- class="com.example.activemq.weblogic.ActiveMQToWebLogicSecurity">
- <property name="authorizedGroup" value="activemq" />
- </bean>
-
-<!\-\- Uncomment and configure this if you want to use a WebLogic database
- connection pool for persistent messages
- <bean id="WebLogicDataSource"
- class="org.springframework.jndi.JndiObjectFactoryBean">
- <property name="jndiName" value="db/pool/jndi/name"/>
- </bean>
--->
-</beans>
-
-**Log4J Configuration File (`log4j.properties`)**
-
-\# Can change this to "INFO, out" or "INFO, out, stdout"
-\# to enable logging to the file defined down below
-log4j.rootLogger=INFO, stdout
-log4j.logger.org.apache.activemq.spring=WARN
-log4j.logger.org.springframework=WARN
-log4j.logger.org.apache.xbean.spring=WARN
-
-\# Configuration to log to stdout
-log4j.appender.stdout=org.apache.log4j.ConsoleAppender
-log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
-log4j.appender.stdout.layout.ConversionPattern=%-5p %-30.30c{1} - %m%n
-log4j.appender.stdout.threshold=INFO
-
-\# Configuration for a log file (in addition to or instead of stdout)
-log4j.appender.out=org.apache.log4j.RollingFileAppender
-log4j.appender.out.file=/server/bea/weblogic920/domains/test/activemq.log
-log4j.appender.out.maxFileSize=1024KB
-log4j.appender.out.maxBackupIndex=5
-log4j.appender.out.append=true
-log4j.appender.out.layout=org.apache.log4j.PatternLayout
-log4j.appender.out.layout.ConversionPattern=%d \[%-15.15t\] %-5p %-30.30c{1} - %m%n
-
-#### Installation Procedure
-
-This procedure makes the following assumptions:
-
-* The ActiveMQ configuration file and Log4J configuration file will be stored in a subdirectory of the WebLogic domain directory for ease of editing. They may be packaged into `WEB-INF/classes` in the WAR for ease of distribution instead.
-* The ActiveMQ JMX management features will be exposed via the WebLogic runtime JMX MBeanServer. This is not required, but it should allow existing WebLogic management scripts to see the ActiveMQ MBeans. _NOTE: Additional configuration is required if the Sun JVM JMX server or JRockit management server will be used instead, or if the embedded ActiveMQ JMX server will be used instead and more than one ActiveMQ instance will be run on the same server._
-* ActiveMQ will be installed on a single WebLogic instance or on two WebLogic instances in a Network-of-Brokers configuration.
- * In a (Network-of-Brokers) cluster, the two ActiveMQ instances will use specific URLs to locate each other, rather than attempting runtime discovery of arbitrary brokers that may be present on the network.
-* Either ActiveMQ security is disabled, or ActiveMQ logins are validated against the WebLogic default security realm and a login is required and any member of a designated WebLogic group can access ActiveMQ.
-
-Prerequisites
-
-* WebLogic Express 9.2 has been installed
-* A simple WebLogic domain has been created
-* If the JRockit VM will be used on Linux, the file handle limit of the user running WebLogic may be important (test with `ulimit -n`). A recommended value would be at least twice the expected maximum number of JMS clients.
-* The ActiveMQ web application WAR (`activemq-4.0.1-web.war`)
-* The ActiveMQ configuration file (`activemq-config.xml`)
-* The Log4J configuration file (`log4j.properties`)
-
-Installation Procedure
-
-1. Create a subdirectory of the WebLogic domain directory to hold ActiveMQ config files (e.g. `domain-dir/activemq/config`)
-2. Create a subdirectory of the WebLogic domain directory to hold ActiveMQ runtime data – persistent messages, etc. (e.g. `domain-dir/activemq/data`)
-3. Edit the `activemq-config.xml` to point to the correct runtime data directory created in step 2 (look for the part of the file that reads `dataDirectory="..."`)
-4. In `activemq-config.xml`, review the port for the current ActiveMQ server defined in the `<transportConnector .../>` line, if ActiveMQ clustering will be used, review the hostname and port for the other ActiveMQ server(s) in the cluster defined in the `<networkConnector .../>` line.
-5. If ActiveMQ clustering and security are both enabled, in `activemq-config.xml`, find (or add) the `userName` and `password` settings on the `<networkConnector .../>` and change them to valid values. (When security is enabled, the ActiveMQ brokers in a cluster require valid logins to connect to each other to form the cluster.)
-6. If security is enabled, in `activemq-config.xml`, find the `authorizedGroup` setting on the `WebLogicSecurity` bean and set that to the name of the WebLogic group whose members should be able to access ActiveMQ. Note that the account used by the network connectors in the previous step must be members of this group. (This entry in the config file is described in the previous section)
-7. (Optional) Update the `log4j.properties` file to save ActiveMQ logs to a file rather than just emitting to the WebLogic server's standard output (e.g. change the first line to `log4j.rootLogger=INFO, out, stdout` and change the destination file in the `log4j.appender.out.file=...` line)
-8. Save the `activemq-config.xml` and `log4j.properties` files to the ActiveMQ configuration directory created in step 1
-9. Edit the `startWebLogic.sh` file in the domain directory and add the following line to the top (immediately after the `DOMAIN_HOME=...` line), adjusting the line to use the directory created in step 1:
-
- export EXT\_POST\_CLASSPATH=${DOMAIN_HOME}/activemq/config
-
-10. Start WebLogic
-11. Deploy the `activemq-4.0.1-web.war` file, by copying it to the `domain-dir/autodeploy` directory or using the deployment tools in the WebLogic console.
-12. Verify that the WebLogic server standard output (or the ActiveMQ log file configured in step 5) shows that ActiveMQ started, with output like this:
-
- INFO BrokerService - ActiveMQ 4.0.1 JMS Message Broker (localhost) is starting
- INFO BrokerService - For help or more information please see:
- http://incubator.apache.org/activemq/
- INFO JDBCPersistenceAdapter - Database driver recognized: \[apache\_derby\_embedded\_jdbc\_driver\]
- INFO JournalPersistenceAdapter - Journal Recovery Started from: Active Journal: using 5 x 20.0 Megs at:
- /data/server/bea/weblogic920/domains/test/activemq-data/journal
- INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in transactions recovered.
- INFO TransportServerThreadSupport - Listening for connections at: tcp://0.0.0.0:60010
- INFO TransportConnector - Connector default Started
- INFO BrokerService - ActiveMQ JMS Message Broker
- (localhost, ID:remus-28763-1156532531109-1:0) started
-
-13. Test a management connection by running the `jconsole` tool distributed with Java 5, using an advanced connection, entering the URL `service:jmx:rmi:///jndi/iiop://localhost:7001/weblogic.management.mbeanservers.runtime` (adjusting `localhost:7001` to the WebLogic server hostname and port) and the WebLogic administrator username and password. Once connected, on the MBeans tab, there should be entries under `org/activemq`
-14. Test a security if desired by running the example producer and consumer from an ActiveMQ 4.0.1 distribution. Note that the connect URL is in `examples/build.xml` while the connect username and password need to be added to `examples/src/ConsumerTool.java` and `examples/src/ProducerTool.java` to connect successfully to a secure instance.
-15. If ActiveMQ clustering will be used, repeat this process for the other WebLogic/ActiveMQ instance in the cluster. This should set up the two ActiveMQ servers to connect to each other. Confirm this by looking for output like this once both brokers are running:
-
- INFO DemandForwardingBridge - Network connection between vm://FirstBroker#0 and
- tcp://localhost:63222(SecondBroker) has been established.
-
-
diff --git a/src/_documents/classic/Connectivity/Containers/zos.md b/src/_documents/classic/Connectivity/Containers/zos.md
deleted file mode 100644
index 3c4c505..0000000
--- a/src/_documents/classic/Connectivity/Containers/zos.md
+++ /dev/null
@@ -1,174 +0,0 @@
-Apache ActiveMQ ™ -- zOS
-
-[Connectivity](../../connectivity.md) > [Containers](../../Connectivity/containers.md) > [zOS](../../Connectivity/Containers/zos.md)
-
-
-Running ActiveMQ on z/OS
-========================
-
-It is relatively straightforward to run the ActiveMQ broker on z/OS.
-
-There are a couple of steps:
-
-1\. Copy ActiveMQ to z/OS
-2\. Modify the configuration
-3\. Run using JZOS
-4\. Test
-
-### Copy ActiveMQ to z/OS
-
-* Ensure that the 1.5 JVM is available on z/OS, together with the [JZOS](http://www.dovetail.com/docs/jzos/index.html) component.
-* Download the .zip version of ActiveMQ from Apache.
-* FTP the broker to a suitable directory in USS.
-* Log into USS using rlogin or whatever has been configured at your site to do a login into USS.
-* Extract the zip file using the command: jar -xvf apache-activemq-5.0.0.zip
-* This will extract the whole package in ASCII, so do not except any of the files to be viewable on z/OS, except using special editors suitable for ASCII.
-* Maybe rename the directory to which the files were extracted to something shorter or create a softlink for more convenient access.
-
-### Modify the configuration
-
-Currently, the Jetty plugin does not work on z/OS, so need to be disabled in the activemq.xml file.
-
-* FTP the activemq.xml file from the conf directory in the ActiveMQ installation to your PC in binary mode.
-* Edit the XML file using your XML editor or a text editor like Wordpad.
-* Search for "jetty" in the XML.
-* Change the comment block so that jetty is completely commented out.
-* Save the file.
-* FTP the file back into the location on z/OS it came from, again in binary mode, so that it is preserved as an ASCII file.
-
-### Run using JZOS
-
-I have renamed the lib/optional directory in USS and shortened some of the lib/optional jar names to make the JCL easier to handle. The JCL to run the ActiveMQ broker is then:
-
-**ACTIVEMQ.JCL**
-
-//ACTIVEMQ JOB (),
-// CLASS=A,
-// MSGCLASS=X,
-// MSGLEVEL=(1,1),
-// NOTIFY=&SYSUID,
-// REGION=0M,
-// TIME=1440
-//PROCLIB JCLLIB ORDER=<JZOS.SYS1.PROCLIB>
-//\*
-//\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
-//\*
-//\* Batch job to run Tomcat under JZOS
-//\*
-//\* Tailor the proc and job for your installation:
-//\* 1.) Modify the Job card per your installation's requirements
-//\* 2.) Modify the PROCLIB card to point to JZOS proclib
-//\* 3.) Set VERSION='14' for Java 1.4 or VERSION='50' for Java 5
-//\* 4.) Set JAVA_HOME to point the location of the Java SDK
-//\* 5.) Set CATALINA_HOME to point to the shared Tomcat install dir
-//\* 6.) (Optional) set CATALINA_BASE to point to instance specific
-//\* Tomcat base dir
-//\*
-//\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
-//\*
-//JAVA EXEC PROC=JVMPRC50,
-// LOGLVL='+D',
-// JAVACLS='org.apache.activemq.console.Main',
-// ARGS='start'
-//STDENV DD *
-\# This is a shell script which configures
-\# any environment variables for the Java JVM.
-\# Variables must be exported to be seen by the launcher.
-. /etc/profile
-export JAVA\_HOME=/space/javaV5\_31/J5.0
-AMQ_HOME=/home/user/activemq/amq
-ACTIVEMQ\_BASE="$AMQ\_HOME"
-
-export PATH=/bin:"${JAVA_HOME}"/bin:
-
-LIBPATH=/lib:/usr/lib:"${JAVA_HOME}"/bin
-LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/classic
-export LIBPATH="$LIBPATH":
-
-CLASSPATH="${JAVA_HOME}/lib/tools.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/conf"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/activemq-all-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/bin/run.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/bin/wrapper.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activation-1.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-console-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-core-5.0.0-tests.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-core-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-jaas-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-web-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/camel-core-1.2.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/camel-jms-1.2.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/camel-spring-1.2.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/commons-logging-1.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ\_HOME/lib/geronimo-j2ee-management\_1.0_spec-1.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ\_HOME/lib/geronimo-jms\_1.1_spec-1.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ\_HOME/lib/geronimo-jta\_1.0.1B_spec-1.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/jaxb-api-2.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/jaxb-impl-2.0.3.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/stax-1.2.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/stax-api-1.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/spring-2.0.6.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/xbean.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/jetty-6.1.4.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/jetty-util-6.1.4.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/activeio-core-3.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/geronimo-j2ee-connector.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/activeio-core-tests.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/geronimo-j2ee-jacc.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/activemq-optional-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/activemq-xmpp-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/jmdns-1.0-RC2.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-beanutils-1.6.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/log4j-1.2.14.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-collections-3.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/servlet-api-2.5-6.1.4.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-dbcp-1.2.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-httpclient-2.0.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-pool-1.2.jar"
-CLASSPATH="$CLASSPATH":"$AMQ\_HOME/lib/opt/xmlpull-1.1.3.4d\_b4_min.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/derby-10.1.3.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/xstream-1.1.2.jar"
-export CLASSPATH="$CLASSPATH":
-
-\# Set JZOS specific options
-\# Use this variable to specify encoding for DD STDOUT and STDERR
-#export JZOS\_OUTPUT\_ENCODING=IBM-1047
-\# Use this variable to prevent JZOS from handling MVS operator commands
-#export JZOS\_ENABLE\_MVS_COMMANDS=false
-\# Use this variable to supply additional arguments to main
-#export JZOS\_MAIN\_ARGS=""
-
-\# Configure JVM options
-\# Note that ActiveMQ requires default ASCII file.encoding
-IJO="-Xms64m -Xmx512m"
-IJO="$IJO -Dfile.encoding=ISO8859-1"
-IJO="$IJO -Dcom.sun.management.jmxremote"
-IJO="$IJO -Dorg.apache.activemq.UseDedicatedTaskRunner=true"
-IJO="$IJO -Dderby.system.home=${ACTIVEMQ_BASE}/data"
-IJO="$IJO -Dderby.storage.fileSyncTransactionLog=true"
-IJO="$IJO -Djavax.net.ssl.keyStorePassword=password"
-IJO="$IJO -Djavax.net.ssl.trustStorePassword=password"
-IJO="$IJO -Djavax.net.ssl.keyStore=${ACTIVEMQ_BASE}/conf/broker.ks"
-IJO="$IJO -Djavax.net.ssl.trustStore=${ACTIVEMQ_BASE}/conf/broker.ts"
-IJO="$IJO -Dactivemq.classpath=${CLASSPATH}"
-IJO="$IJO -Dactivemq.base=${ACTIVEMQ_BASE}"
-IJO="$IJO -Dactivemq.home=${AMQ_HOME}"
-IJO="$IJO -Djava.io.tmpdir=${ACTIVEMQ_BASE}/temp"
-
-\# Configure SDK5.0 to use shared classes (at group level)
-\# You must comment this out if you are not running SDK 5
-groupname=\`id -gn\`
-IJO="$IJO -Xshareclasses:name=$groupname,groupAccess"
-export IBM\_JAVA\_OPTIONS="$IJO "
-
-export JAVA\_DUMP\_HEAP=false
-export JAVA_PROPAGATE=NO
-export IBM\_JAVA\_ZOS_TDUMP=NO
-//
-
-### Test
-
-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.
-
-You can also gather information about the broker as usual using [jmx](../../Features/jmx.md).
-
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/activemq-c-development.md b/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/activemq-c-development.md
deleted file mode 100644
index dc355ee..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/activemq-c-development.md
+++ /dev/null
@@ -1,99 +0,0 @@
-Apache ActiveMQ ™ -- ActiveMQ C Development
-
-[Connectivity](../../../connectivity.md) > [Cross Language Clients](../../../Connectivity/cross-language-clients.md) > [ActiveMQ C++ Clients](../../../Connectivity/Cross Language Clients/activemq-c-clients.md) > [ActiveMQ C Development](Connectivity/Cross Language Clients/ActiveMQ C++ ClientsConnectivity/Cross Language Clients/ActiveMQ C++ Clients/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/activemq-c-development.md)
-
-
-ActiveMQ CPP Development Page
-=============================
-
-This page documents current and planned development of ActiveMQ CPP. The table below lists development tasks and their current status
-
-Development Activeity
-
-Status
-
-Openwire Support
-
-in-progress
-
-### Openwire Support
-
-This task adds support for the OpenWire protocol to ActiveMQ CPP. The tasks involves the addition of new code, the activities are listed below, as well as who is working on them and what the status of each is.
-
-Task Description
-
-Assigned to
-
-Status
-
-Task Info
-
-Openwire Command / Marshallers generation scripts
-
-Tim Bish
-
-In-Progress
-
-Loose Marshalling works, Tight still not working
-
-WireFormat Negotiation Framework
-
-Tim Bish
-
-Completed
-
-Mimic the DotNet version?
-
-Primitives Map
-
-Nate Mittler
-
-Completed
-
-Needs more testing for memory leaks and performance.
-
-Primitive Map Marshalling
-
-Tim Bish
-
-Completed
-
-Needs more testing, for leaks etc. Add nested maps, lists.
-
-BaseDataStreamMarshallers Port
-
-Tim Bish
-
-In-Progress
-
-Done, but serious unit testing is needed
-
-BooleanStream Port
-
-Tim Bish
-
-Completed
-
-Done
-
-OpenWire Connector Framework Classes
-
-Tim / Nate
-
-Completed
-
-Needs lots of testing
-
-DataInputStreams / DataOutputStreams
-
-Tim Bish
-
-Completed
-
-Done
-
-Outstanding Issues
-------------------
-
-This section document issues that are outstanding...TDB
-
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/building-activemq-cpp.md b/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/building-activemq-cpp.md
deleted file mode 100644
index 5bd78d8..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/building-activemq-cpp.md
+++ /dev/null
@@ -1,141 +0,0 @@
-Apache ActiveMQ ™ -- Building ActiveMQ CPP
-
-[Connectivity](../../../connectivity.md) > [Cross Language Clients](../../../Connectivity/cross-language-clients.md) > [ActiveMQ C++ Clients](../../../Connectivity/Cross Language Clients/activemq-c-clients.md) > [Building ActiveMQ CPP](Connectivity/Cross Language Clients/ActiveMQ C++ Clients/building-activemq-cpp.md)
-
-
-Dependencies
-------------
-
-### libuuid
-
-The build requires the **libuuid** library that is part of the e2fsprogs package and is available from [http://e2fsprogs.sourceforge.net/](http://e2fsprogs.sourceforge.net/) which is not always installed by default.
-
-### cppunit
-
-The package contains a complete set of cppunit tests. In order for you to build an run the tests, you will need to download and install the cppunit suite. See [http://cppunit.sourceforge.net/cppunit-wiki](http://cppunit.sourceforge.net/cppunit-wiki)
-
-or on Fedora type the following:
-
-sudo yum install cppunit
-
-Make sure that the paths to the installed cppunit library and includes are visible in your current shell before you try building the tests.
-
-Windows users will need to build the cppunit library using the CPPUnit MSVC project files. A discussion of the build process can be found on the CPPUnit wiki under [CPPUnit Platform build instructions](http://cppunit.sourceforge.net/cppunit-wiki/BuildingCppUnit1) this covers both MSVC along with many other platforms and tool suites.
-
-### GNU Build System (for building on *nix)
-
-To Generate the ./configure script use to create the Makefiles, you need the following software installed:
-
-Tool
-
-Recommended Version
-
-autoconf
-
->= 2.59
-
-automake
-
->= 1.9.6
-
-libtool
-
->= 1.5.22
-
-Building on *nix (Unix/Linux/OS X/Cygwin)
------------------------------------------
-
-This assumes you have all of the project dependencies installed. We're now ready to create the configure script. To do this, run:
-
-./autogen.sh
-
-You may see the following warnings when running this command:
-
-src/test-integration/Makefile.am:44: `CXXFLAGS' is a user variable, you should not override it;
-src/test-integration/Makefile.am:44: use `AM_CXXFLAGS' instead.
-src/test/Makefile.am:104: `CXXFLAGS' is a user variable, you should not override it;
-src/test/Makefile.am:104: use `AM_CXXFLAGS' instead.
-
-These can be ignored. We override CXXFLAGS in the makefiles for the unit and integration tests in order to suppress compiler warnings.
-
-This should be run the first time and anytime you change configure.ac or any of the Makefile.am files.
-
-Solaris 10 Note
-
-CPP_UNIT might not build until you correct the file libstdc++.la to contain the correct data, see this discussion.
-
-[http://forum.sun.com/jive/thread.jspa?threadID=73150](http://forum.sun.com/jive/thread.jspa?threadID=73150)
-
-The configure script will customize the way the software is built and installed into your system along with detecting the available libraries that have been installed. To use the default configuration just run:
-
-./configure
-
-For more help on how to customize the build configuration, run:
-
-./configure --help
-
-Once the configure script has run successfully, you are ready to build. Run:
-
-make
-
-This will build all of the core ActiveMQ CPP source code. To build and install the code into the system directories, run:
-
-make install
-
-You will have to become the superuser in order to be able to install the files.
-
-Doxygen
--------
-
-To generate the doxygen documentation for the project, just run:
-
-make doxygen-run
-
-Running Tests
--------------
-
-### Unit Tests
-
-In order to build and run the suite of unit tests, run:
-
-make check
-
-This will verify that the library is functioning correctly on the target platform. In addition, it will generate the integration tests binary.
-
-### Integration Tests
-
-The library also contains a set of tests that are run against a real AMQ broker. These allow you to validate this distribution of ActiveMQ CPP against your broker. Running these without a broker will result in failed tests. The tests currently hard-code the broker url to be tcp://localhost:61613 for stomp and tcp://localhost:61616 for openwire.
-
-The integration tests are built via "make check". To run them, first start a broker and then
-
-cd src/test-integration
-./activemq-test-integration
-
-This will take quite some time to complete, so be patient.
-
-Example
--------
-
-There is an example application that ships with the distribution in src/examples. The example is compiled by default with the "make" command, but can easily be compiled manually using the command:
-
-g++ -o main -pthread -I ../main main.cpp ../../out/libactivemq-cpp-0\_0\_2.a -luuid
-
-Notes for Windows users
------------------------
-
-We support using the GNU compiler on Windows, using the Cygwin package. However we also support using the MSVC compiler on Windows.
-
-There are a couple or things that you will need to setup to ensure that the MSVC compile succeeds.
-
-* You need to download and install the Platform SDK if you don't have it installed already.
-* Ensure that the path to you MSVC install is set in the PATH env variable. You can test this by typing cl.exe at the command line, if you get an error complaining that its not found, then you'll need to fix your PATH.
-* Set the INCLUDE env variable to include the path to your MSVC includes, and the platform SDK includes. For example:
-
- INCLUDE = D:\\Program Files\\Microsoft Visual Studio 8\\VC\\include;D:\\Program Files\\Microsoft Platform SDK\\Include\\*
-
-* Set the LIB env variable to include the path to your MSVC libs, and the Platform SDK libs. For example:
-
- LIB = D:\\Program Files\\Microsoft Visual Studio 8\\VC\\lib;D:\\Program Files\\Microsoft Platform SDK\\Lib
-
-* The Project files reference the CPPUnit libraries for the Integration and Unit tests builds. In order for these to build correctly you must either place the CPPUnit libraries in a directory listed in the project settings, or add a new location for your install of CPPUnit.
-
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/configuring-activemq-cpp.md b/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/configuring-activemq-cpp.md
deleted file mode 100644
index 2139f63..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/configuring-activemq-cpp.md
+++ /dev/null
@@ -1,242 +0,0 @@
-Apache ActiveMQ ™ -- Configuring ActiveMQ CPP
-
-[Connectivity](../../../connectivity.md) > [Cross Language Clients](../../../Connectivity/cross-language-clients.md) > [ActiveMQ C++ Clients](../../../Connectivity/Cross Language Clients/activemq-c-clients.md) > [Configuring ActiveMQ CPP](Connectivity/Cross Language Clients/ActiveMQ C++ Clients/configuring-activemq-cpp.md)
-
-
-The configuration of ActiveMQ is so slick, we decided to take a similar approach with ActiveMQ-CPP. All configuration is achieved via URI-encoded parameters, either on the connection or destinations. Through the URIs, you can configure virtually every facet of your ActiveMQ-CPP client. The tables below show the comprehensive set of parameters.
-
-**Connection URI Parameters**
------------------------------
-
-#### Example Configuration
-
-cf = new ActiveMQConnectionFactory(
- "tcp://localhost:61616?wireFormat=openwire&wireFormat.tightEncodingEnabled=true");
-
-### **Socket Options**
-
-Option Name
-
-Default
-
-Description
-
-inputBufferSize
-
-10000
-
-The number of bytes in the buffered input stream's buffer
-
-outputBufferSize
-
-10000
-
-The number of bytes in the buffered output stream's buffer
-
-soLinger
-
-0
-
-Socket SOLinger value
-
-soKeepAlive
-
-false
-
-Socket SOKeepAlive value
-
-soReceiveBufferSize
-
--1
-
-Socket receive buffer. If -1, use OS default.
-
-soSendBufferSize
-
--1
-
-Socket send buffer. If -1, use OS default.
-
-### **Transport Options**
-
-Option Name
-
-Default
-
-Description
-
-commandTracingEnabled
-
-false
-
-If true, enables tracing of incoming and outgoing transport commands
-
-tcpTracingEnabled
-
-false
-
-If true, enables tracing of raw network IO (in hex)
-
-useAsyncSend
-
-false
-
-If true, enables asynchronous sending of messages.
-
-### **Transaction Options**
-
-Option Name
-
-Default
-
-Description
-
-transaction.maxRedeliveryCount
-
-5
-
-Maximum number of redelivery attempts.
-
-### **Wire Format Protocol Options**
-
-Option Name
-
-Default
-
-Description
-
-wireFormat
-
-openwire
-
-Selects the wire format to use. Out of the box, can be either stomp or openwire.
-
-wireFormat.stackTraceEnabled
-
-false
-
-Should the stack trace of exception that occur on the broker be sent to the client? Only used by openwire protocol.
-
-wireFormat.cacheEnabled
-
-false
-
-Should commonly repeated values be cached so that less marshalling occurs? Only used by openwire protocol.
-
-wireFormat.tcpNoDelayEnabled
-
-false
-
-Does not affect the wire format, but provides a hint to the peer that TCP nodelay should be enabled on the communications Socket. Only used by openwire protocol.
-
-wireFormat.sizePrefixDisabled
-
-false
-
-Should serialized messages include a payload length prefix? Only used by openwire protocol.
-
-wireFormat.tightEncodingEnabled
-
-false
-
-Should wire size be optimized over CPU usage? Only used by the openwire protocol.
-
-**Destination URI Parameters**
-------------------------------
-
-#### Example Configuration
-
-d = session->createTopic("com.foo?consumer.prefetchSize=2000&consumer.noLocal=true");
-
-### **General Options**
-
-Option Name
-
-Default
-
-Description
-
-consumer.prefetchSize
-
-1000
-
-The number of message the consumer will [prefetch](../../../FAQ/Using Apache ActiveMQ/what-is-the-prefetch-limit-for.md).
-
-consumer.maximumPendingMessageLimit
-
-0
-
-Use to control if messages are dropped if a [slow consumer](../../../Features/Consumer Features/slow-consumer-handling.md) situation exists.
-
-consumer.noLocal
-
-false
-
-Same as the noLocal flag on a Topic consumer. Exposed here so that it can be used with a queue.
-
-consumer.dispatchAsync
-
-false
-
-Should the broker [dispatch messages asynchronously](../../../Features/Consumer Features/consumer-dispatch-async.md) to the consumer.
-
-consumer.retroactive
-
-false
-
-Is this a [Retroactive Consumer](../../../Features/Consumer Features/retroactive-consumer.md).
-
-consumer.selector
-
-null
-
-JMS Selector used with the consumer.
-
-consumer.exclusive
-
-false
-
-Is this an [Exclusive Consumer](../../../Features/Consumer Features/exclusive-consumer.md).
-
-consumer.priority
-
-0
-
-Allows you to configure a [Consumer Priority](../../../Features/Consumer Features/consumer-priority.md).
-
-### **OpenWire-only Options**
-
-Option Name
-
-Default
-
-Description
-
-consumer.browser
-
-false
-
-consumer.networkSubscription
-
-false
-
-consumer.optimizedAcknowledge
-
-false
-
-Enables an optimised acknowledgement mode where messages are acknowledged in batches rather than individually. Alternatively, you could use Session.DUPS\_OK\_ACKNOWLEDGE acknowledgement mode for the consumers which can often be faster. **WARNING** enabling this issue could cause some issues with auto-acknowledgement on reconnection
-
-consumer.noRangeAcks
-
-false
-
-consumer.retroactive
-
-false
-
-Sets whether or not retroactive consumers are enabled. Retroactive consumers allow non-durable topic subscribers to receive old messages that were published before the non-durable subscriber started.
-
-producer.dispatchAsyc
-
-false
-
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/downloading-activemq-cpp.md b/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/downloading-activemq-cpp.md
deleted file mode 100644
index 2c1c00e..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/downloading-activemq-cpp.md
+++ /dev/null
@@ -1,23 +0,0 @@
-Apache ActiveMQ ™ -- Downloading ActiveMQ CPP
-
-[Connectivity](../../../connectivity.md) > [Cross Language Clients](../../../Connectivity/cross-language-clients.md) > [ActiveMQ C++ Clients](../../../Connectivity/Cross Language Clients/activemq-c-clients.md) > [Downloading ActiveMQ CPP](Connectivity/Cross Language Clients/ActiveMQ C++ Clients/downloading-activemq-cpp.md)
-
-
-ActiveMQ CPP distributions are source-only. To get the source bundle for a particular release, go [here](OverviewOverview/Overview/download.md). Follow the instructions here only if you want the bleeding edge from trunk.
-
-Web Browsing of SVN
--------------------
-
-To browse via the web use the ViewVC interface:
-
-[http://svn.apache.org/viewvc/activemq/activemq-cpp/trunk/activemq-cpp](http://svn.apache.org/viewvc/activemq/activemq-cpp/trunk/activemq-cpp)
-
-Or to browse the source tree directly:
-
-[https://svn.apache.org/repos/asf/activemq/activemq-cpp/trunk/activemq-cpp](https://svn.apache.org/repos/asf/activemq/activemq-cpp/trunk/activemq-cpp)
-
-Checking out from SVN
-----------------------
-
-svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/trunk/
-
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/openwire-cpp-client.md b/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/openwire-cpp-client.md
deleted file mode 100644
index ffd89cd..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/openwire-cpp-client.md
+++ /dev/null
@@ -1,113 +0,0 @@
-Apache ActiveMQ ™ -- OpenWire CPP Client
-
-[Connectivity](../../../connectivity.md) > [Cross Language Clients](../../../Connectivity/cross-language-clients.md) > [ActiveMQ C++ Clients](../../../Connectivity/Cross Language Clients/activemq-c-clients.md) > [OpenWire CPP Client](Connectivity/Cross Language Clients/ActiveMQ C++ ClientsConnectivity/Cross Language Clients/ActiveMQ C++ Clients/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/openwire-cpp-client.md)
-
-
-OpenWire C++ Client
-===================
-
-Goals
------
-
-We want to be able to provide a C++ API to ActiveMQ that retains rough feature-parity with the Java API while at the same time allowing for more flexibility in application design by opening up lower levels of the event system. We have come up with an API / programming model that maximizes the ways in which the messaging library can adapt to the application using it, not the other way around. Specifically, our goals are:
-
-* Make no assumption about the threading constraints of the containing application (specifically, allow asynchronous receives within a single-threaded application)
-* Make no assumption about the event loop characteristics of the containing application
-* Make no assumption about libraries needed – i.e. dont enforce use of a particular library or smart pointer implementation
-* Offer tradeoffs in flexibility versus application complexity
-* Provide distinctly C++-friendly APIs for asynchronous event notification
-* Provide pluggable data transports
-* Maximize portability
-
-It makes no assumptions about the threading or event loop model of the containing application, and so puts no restrictions on C++ program design as inherent costs of doing asynchronous messaging. As a result of this flexible and pluggable design, this library is particularly easy to implement as a native layer to a high-level scripting language interface to ActiveMQ since it makes no assumptions about the threading capabilities of the language.
-
-When we use the term programming model, we are referring to the handling of the most complex part of asynchronous messaging APIs – message delivery to the application.
-
-JMS / Java programming model
-----------------------------
-
-JMS 1.1 provides two ways for an application to receive messages. One is by a blocking receive in the MsgConsumer class' receive() function. This will suspend the calling thread until a message is received. The other method is through callbacks in subclasses of MessageListener. The OnMessage function is called when a message is received on the topic or queue that the MessageListener was created for.
-
-To sum up – The JMS model imposes a threading structure on the application developer. Either they must use multiple threads each doing synchronous receive() calls, or rely on a separate thread to deliver messages to them. A single-threaded model is impossible.
-
-Where whats best for C++ and Java APIs diverge
-----------------------------------------------
-
-The JMS API enforces a particular model of threading on an application. This is fine and well-accepted in the Java programming space, since Java is designed for it to be easiest to multiplex communications with threads. Threads are very easy and well-supported in Java.
-
-However, in C++ the common practice is different. Most C++ programs that handle network communication in an event-driven fashion use an event loop. This is a thread that waits for activity on a number of file descriptors, relying on the OS to wake it up when one has data. File descriptors are the lingua franca of event-driven C and C++ programs, since the OS makes it easy to use them for any kind of event, as well as providing rich functionality to wait on multiple file descriptors at on [...]
-
-In conclusion, C++ developers expect a level of openness and flexibility when using libraries that can deliver events, so that they can integrate multiple sources of events together without resorting to multithreading. Most libraries that do this properly expose the underlying file descriptor of the network connection directly to the application – X11 does this for example – and we will start there with the actual design specification.
-
-C++s lower level nature presents many more inherent design decisions than does Java. In particular, one of the largest issues is that there is no standard smart pointer implementation. Boost is popular, but every enterprise has its own, and every developer has personal preference. It is for this reason that this library does not propose to use any particular smart pointer implementation, as it enforces a design decision on enterprises that have their own requirements in that space. Throu [...]
-
-We are proposing a three-tiered approach to provide the tradeoff between application simplicity and flexibility. The lowest level will do the least and allow the widest range of applications to use it, the next level will be much more functional, but with some design tradeoffs, and the highest we will leave up to enterprise-specific needs.
-
-Proposed C++ API Design
------------------------
-
-The design that we are proposing consists of two layers. The core library owns no threads and acts simply as a filter – taking data from the broker in and dispatching messages if necessary. This core layer of the library is exposed to allow those C++ developers who do not want any threads other than their own managing events, and/or want to use non-TCP methods of communication with the broker. The socket to the ActiveMQ broker is to be exposed to the application by the transport layer, a [...]
-There are shortcomings to this approach. If the application blocks on some other activity and data from the broker is never processed, the TCP socket will back up and messages will build up on the broker side. Also, the single-threaded nature of the library means that the application must do all the I/O work itself, and implement a separate thread in order to make meaningful use of the blocking receive.
-
-We can build a second layer (we call it BrokerSession) on top of the first that provides these features – still integrating into the applications existing event structure, but at the price of a background thread. The background thread handles data from ActiveMQ and passes it to the core library, putting any resulting messages into an internal message buffer (or potentially multiple – see details below). With this the library can provide a much simpler and more direct messaging interface [...]
-
-The second layer simply invokes an interior instance of the first to perform any ActiveMQ-related messaging tasks – no messaging-system-specific code is outside of the core lower level library. As a result, the second layer is a thin one – just the thread, interaction with the transport abstraction layer and functionality passthroughs to the core library.
-
-There is a third level – there is a need for higher-level, application framework libraries for messaging, that might take all control flow from the user and provide the simplest possible environment. The lower levels are designed to allow the most flexibility in the design and requirements of the third level, which is most often enterprise-specific and lies outside the scope of this document. An example of a library at this level would be one that provides a framework that makes it easy [...]
-
-Transport layer abstraction overview
-------------------------------------
-
-Similar to ActiveMQ itself, we provide a transport layer abstraction that manages connection and I/O on file descriptors. Initially only TCP socket support will be provided, but there is value in other implementations – in-process pipe, playing back from a file, UDP, etc. This layer provides logical connect, send, recv, and close operations. Transports are initialized with URIs in the same fashion that other ActiveMQ transports are.
-
-Core library overview
----------------------
-
-The core layer of the library provides a very simple interface – data in, messages out.
-
-
-
-When the returned file descriptor from the transport layer's connect() call reads active in the application's event loop, the application reads available data and passes that to the library. The library itself has an internal buffer that will deliver a message when one has been fully accumulated. The purpose of this disconnect is that the core library **will not make any blocking I/O calls – or any system calls at all for that matter**. This satisfies the portability goal, as well as ens [...]
-
-The end-to-end lifetime of an outgoing message using the core library is:
-
-* User calls "send" or "subscribe" etc.
-* The core library constructs the corresponding OpenWire command object
-* The core library marshals this object into a buffer and returns that buffer to the user
-
-The end-to-end lifetime of an incoming message using the core library is:
-
-* The user gets data from ActiveMQ, possibly by using the included transport library
-* This data is passed to the core library, which does one of two things:
-
-* if it isn't already receiving a message, it looks at the first few bytes and notes how large the incoming message is by examining OpenWire headers.
-* if it is, it adds the incoming buffer to an internal message buffer, and if this addition completes the incoming message it deserializes it into an OpenWire command object, and the appropriate action is taken.
-
-Notable here is the behavior of message receives - the core library is able to receive messages in piecemeal, and only deliver a message when it has been completely received.
-
-Publication and subscription work in the conventional ways, except that they return data to be sent by the transport layer instead of directly sending it. This allows a higher level to determine exactly how the data is sent – for example, it allows use of non-blocking I/O.
-
-The application is given two choices for message receipt. The library does this by means of one or more internal "message consumer" objects (similar to JMS MessageConsumer objects). There are two kinds – one for synchronous receives, and one for asynchronous. The synchronous consumer(BlockingMessageConsumer) offers a blocking receive that multiple threads can wait on for messages. The asynchronous message consumer uses an event-based interface, notifying the application that a message is [...]
-
-BrokerSession library overview
-------------------------------
-
-The higher level library's interface offers a much simpler and more direct API to the developer than the first layer, as a result of having an internal thread to process data from the ActiveMQ broker.
-
-
-
-Since the BrokerSession library contains a copy of the core library, ActiveMQ-specific code is kept encapsulated there. The code in the BrokerSession library does the legwork of managing the core library and broker communication for the application. The use of a background thread to do this and deliver incoming messages to the message consumers greatly simplifies application development.
-
-As in the core library, message dispatch is done explicitly by the application, not from the background thread. Neither library stores message callbacks – it is not required that they be used. This ensures that only threads that are known by the calling application execute application code – the result being that thread-safe programming is not enforced or required (satisfying the goal of not mandating a particular thread model). It is not unexpected that there will commonly be enterprise [...]
-
-This library allows both a JMS-like programming model of multiple threads waiting on message queues as well as an event-driven, select-loop model that is more common in C++ programs. This makes it adaptable to the varying requirements of new and existing C++ applications that have design constraints imposed by things other than the messaging library.
-
-Logging and error handling
---------------------------
-
-To fit with the goals of not enforcing particular dependencies and allowing easy enterprise integration, the libraries have a callback-based model for logging. The application registers a logger with the library to be called when log events occur - this logger has function callbacks for error logging, debug logging, etc. This allows the easiest integration with existing logging systems, as these callbacks can then call directly into the native logging environment (such as syslog) or log [...]
-
-Error handling is slightly different. The native C++ way of doing error handling is through exceptions. Exceptions work very well for something like the core library, so when an error occurs it will throw an instance of ActiveMQ::Exception to the caller. In the BrokerSession library, however, such exceptions may be caught by the background thread. In this case, that thread will call an application callback to pass along the exception. This ensures that all errors reach the application an [...]
-
-The default callback for exception handling simply print the relevant message to standard error.
-
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/C Integration/c-integration-scenarios.md b/src/_documents/classic/Connectivity/Cross Language Clients/C Integration/c-integration-scenarios.md
deleted file mode 100644
index cf9f756..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/C Integration/c-integration-scenarios.md
+++ /dev/null
@@ -1,52 +0,0 @@
-Apache ActiveMQ ™ -- C integration scenarios
-
-[Connectivity](../../../connectivity.md) > [Cross Language Clients](../../../Connectivity/cross-language-clients.md) > [C Integration](../../../Connectivity/Cross Language Clients/c-integration.md) > [C integration scenarios](../../../Connectivity/Cross Language Clients/C Integration/c-integration-scenarios.md)
-
-
-One way and RPC with C services
--------------------------------
-
-Its common for the C services to be the back end services. The 2 common use cases are
-
-* we send a message one-way to a C service
-* we send a message to a C-service and wait for the result, then reply back to the originator the result
-
-### Making one-ways reliable
-
-If we assume that the C-service is fairly atomic, it works or it doesn't and does not partially work, then for one-way handling we just need some code to...
-
-1. consume a message from some destination
-2. invoke the C service and wait until the service completes
-3. acknowledge the message
-
-If invoking the C service fails (such that we know it wasn't invoked), we could automatically retry a certain number of times before we acknowledge the message.
-
-The problem is if the above code were to be killed before the message is acknowledged, we'd invoke the service again.
-
-To get around this we could persist that we have invoked the service, so that if we are killed we would not invoke the service again but put the message on some dead letter queue for manual reconciliation.
-
-1. consume a message from some destination
-2. have we seen this message before - if so put on a dead letter queue for manual reconciliation
-3. persist that we have processed this message
-4. invoke the C service and wait until the service completes
-5. acknowledge the message
-
-Another approach could be for the C service to say whether or not it has successfully processed the message before. This just pushes the problem inside the C code requiring that it persists when things are invoked and when things complete so that it can know when duplicate messages are delivered.
-
-### making RPC reliable
-
-This scenario is as above but rather than just acknowledge the inbound message we wish to send a reply and acknowledge the inbound message. So this could be regarded as a small JMS transaction.
-
-1. consume a message from some destination
-2. have we seen this message before - if so put on a dead letter queue for manual reconciliation
-3. persist that we have processed this message
-4. invoke the C service and wait until the service completes
-5. send the reply with results from the C service
-6. commit the JMS transaction
-
-Again if the C service is capable of knowing if it has seen the message before then we can avoiid step 3.
-
-### connectivity to C
-
-We can link C into a Java process and invoke it directly via JNI. Another option is to wrap the C code as an Apache module and perform a HTTP POST to invoke a C service and extract the results of the service.
-
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/C Integration/compile-activemq-with-gcj.md b/src/_documents/classic/Connectivity/Cross Language Clients/C Integration/compile-activemq-with-gcj.md
deleted file mode 100644
index cfed76f..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/C Integration/compile-activemq-with-gcj.md
+++ /dev/null
@@ -1,255 +0,0 @@
-Apache ActiveMQ ™ -- Compile ActiveMQ with GCJ
-
-[Connectivity](../../../connectivity.md) > [Cross Language Clients](../../../Connectivity/cross-language-clients.md) > [C Integration](../../../Connectivity/Cross Language Clients/c-integration.md) > [Compile ActiveMQ with GCJ](../../../Connectivity/Cross Language Clients/C Integration/compile-activemq-with-gcj.md)
-
-
-You can use [GCJ](http://gcc.gnu.org/java/) to build ActiveMQ as a shared library you can reuse from C++.
-
-### Native compile ActiveMQ HOWTO
-
-#### Abstract
-
-This document describes how to native compile ActiveMQ for use in a C++ environment. The version of ActiveMQ used is 3.2 in this howto. To compile you'll need GCC 4.0.2, or later, with both Java, and C/C++ support.
-
-#### Tools Setup
-
-If you don't already have GCC 4.0.2 installed you need to download and build it. See GCC manuals for complete instructions on how to build GCC but below is a short descriptions of the steps involved. The GCC build steps assumes that you already have an older GCC compiler installed.
-
-* Unpack GCC into an arbitrary directory, for example /opt/gccbuild, and then create a separate output directory. Your directory structure should look similar to this;
-
- /opt/gccbuild/gcc-4.0.2
- /opt/gccbuild/output
-
-* Go to the output directory and run configure.
-
- cd /opt/gccbuild/output
- ../gcc-4.0.2/configure --prefix=/opt/gcc402
- --enable-shared
- --enable-threads=posix
- --enable-languages=c,c++,java
-
-* Run make.
-
- make bootstrap
- make install
-
-
-* Download ActiveMQ and copy the JARs to a new empty directory /opt/app, including
-
- activeio-1.1.jar
- activemq-core-3.2.jar
- commons-logging-1.0.3.jar
- concurrent-1.3.4.jar
- geronimo-spec-j2ee-jacc-1.0-rc4.jar
- geronimo-spec-j2ee-management-1.0-rc4.jar
- geronimo-spec-jms-1.1-rc4.jar
- geronimo-spec-jta-1.0.1B-rc4.jar
- log4j-1.2.8.jar
-
-
-#### Write the Glue Code
-
-Either access the ActiveMQ classes directly from C++ or write a facade object in Java that handles all startup and shutdown logic of ActiveMQ. Save the glue files in the same directory as for the ActiveMQ jars.
-
-An CNI example using a Java object starting the MQ.
-
-##### Bootstrap.cpp
-
-#include <gcj/cni.h>
-#include <iostream>
-#include <java/lang/System.h>
-#include <java/lang/Throwable.h>
-#include <java/io/PrintStream.h>
-#include "MQAdapter.h"
-
-using namespace std;
-
-int main(int argc, char* argv\[\])
-{
- cout << "Entering main" << endl;
- using namespace java::lang;
-
- try
- {
- // Create and startup Java VM
- JvCreateJavaVM(NULL) ;
- JvAttachCurrentThread(NULL, NULL) ;
-
- System::out->println(JvNewStringLatin1("Java println")) ;
-
- // Start ActiveMQ
- MQAdapter* pAdapter = new MQAdapter() ;
- pAdapter->start() ;
-
- // Send a message
- pAdapter->send(JvNewStringLatin1("Hello World!")) ;
-
- // Shutdown ActiveMQ
- pAdapter->stop() ;
-
- JvDetachCurrentThread() ;
- }
- catch( Throwable *t )
- {
- System::err->println(JvNewStringLatin1("Exception")) ;
- t->printStackTrace() ;
- }
-}
-
-##### MQAdapter.java
-
-import org.activemq.*;
-import java.util.Hashtable ;
-import javax.jms.*;
-import javax.naming.*;
-
-public class MQAdapter
-{
- private InitialContext jndiContext ;
- private QueueConnectionFactory factory ;
- private QueueConnection connection ;
- private QueueSession session ;
- private QueueSender sender ;
- private Queue queue ;
-
- public MQAdapter()
- {
- }
-
- public void start()
- {
- try
- {
- Hashtable props = new Hashtable() ;
- props.put(Context.INITIAL\_CONTEXT\_FACTORY, "org.activemq.jndi.ActiveMQInitialContextFactory") ;
- props.put(Context.PROVIDER_URL, "tcp://localhost:61616") ;
- props.put("queue.MyQueue", "example.MyQueue") ;
-
- jndiContext = new InitialContext(props) ;
-
- // Create and configure JMS connection factory
- factory = (QueueConnectionFactory)jndiContext.lookup("ConnectionFactory") ;
-
- // Lookup Queue
- queue = (Queue)jndiContext.lookup("MyQueue") ;
-
- // Create a JMS connection
- connection = (QueueConnection)factory.createQueueConnection() ;
- System.out.println("Created connection: " + connection) ;
-
- // Create a JMS session
- session = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE) ;
- System.out.println("Created session: " + session) ;
-
- // Create JMS sender
- sender = session.createSender(queue) ;
- }
- catch( Exception e )
- {
- e.printStackTrace() ;
-
- try
- {
- if( connection != null )
- connection.close() ;
- } catch( JMSException jmse )
- { /\* ignore */ }
- }
- }
-
- public void stop()
- {
- try
- {
- if( connection != null )
- connection.close() ;
- } catch( JMSException e )
- { /\* ignore */ }
- }
-
- public void send(String msg)
- {
- TextMessage message ;
-
- try
- {
- message = session.createTextMessage(msg) ;
- sender.send(message) ;
- }
- catch( JMSException e )
- {
- e.printStackTrace() ;
- }
- }
-}
-
-#### Compile the Java and C++ Code
-
-The Java code must be BC compiled to be able to dynamically link required classes as needed, see reference for more information on BC compilation. Use the suggested script to compile all ActiveMQ JARs and create a class map database.
-
-Note
-
-Using -Bsymbolic does not seem to work, use -symbolic instead.
-
- compile.sh:
-
- #!/bin/sh
-
- # Create new classmap database
- gcj-dbtool -n classmap.db
-
- for JAR_FILE in \`find -iname "*.jar"\`
- do
- echo "Compiling ${JAR_FILE} to native"
- gcj -shared -findirect-dispatch -fjni -fPIC -Wl,-symbolic -o ${JAR\_FILE}.so ${JAR\_FILE}
- gcj-dbtool -a classmap.db ${JAR\_FILE} ${JAR\_FILE}.so
- done
-
-* Run the above script and set environment property GCJ_PROPERTIES.
-
- ./compile.sh
- export GCJ_PROPERTIES="gnu.gcj.precompiled.db.path=/opt/app/classmap.db"
-
-
-* Java compile MQAdapter.java
-
- gcj --classpath=./geronimo-spec-jms-1.1-rc4.jar:./activemq-core-3.2.jar -C MQAdapter.java
-
-
-* Generate CNI header for MQAdapter.class
-
- gcjh MQAdapter
-
-
-* JAR the Java glue code
-
- fastjar cf MQAdapter.jar MQAdapter.class
-
-
-* Native compile the Java JAR into a shared library, add output directory to LD\_LIBRARY\_PATH.
-
- gcj -shared -findirect-dispatch -fjni -fPIC -Wl,-symbolic -o MQAdapter.so MQAdapter.jar
- export LD\_LIBRARY\_PATH=$LD\_LIBRARY\_PATH:/opt/app
-
-
-* Compile the C++ code
-
- g++ -c Bootstrap.cpp
-
-
-* Link Bootstrap with the Java code
-
- gcj -o Bootstrap Bootstrap.o -L /opt/app -lgcj -lstdc++ activeio-1.1.jar.so activemq-core-3.2.jar.so
- commons-logging-1.0.3.jar.so concurrent-1.3.4.jar.so geronimo-spec-jms-1.1-rc4.jar.so
- geronimo-spec-j2ee-management-1.0-rc4.jar.so geronimo-spec-j2ee-jacc-1.0-rc4.jar.so
- geronimo-spec-jta-1.0.1B-rc4.jar.so log4j-1.2.8.jar.so MQAdapter.so
-
-
-Now, if everything went ok you should be able to run the app. with ./Bootstrap.
-
-#### References
-
-[How to BC compile with GCJ](http://gcc.gnu.org/wiki/How%20to%20BC%20compile%20with%20GCJ)
-
-[The state of Java on Linux](http://www.redhat.com/magazine/012oct05/features/java/)
-
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/C Integration/openwire-c-client.md b/src/_documents/classic/Connectivity/Cross Language Clients/C Integration/openwire-c-client.md
deleted file mode 100644
index 3f9c50f..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/C Integration/openwire-c-client.md
+++ /dev/null
@@ -1,15 +0,0 @@
-Apache ActiveMQ ™ -- OpenWire C Client
-
-[Connectivity](../../../connectivity.md) > [Cross Language Clients](../../../Connectivity/cross-language-clients.md) > [C Integration](../../../Connectivity/Cross Language Clients/c-integration.md) > [OpenWire C Client](../../../Connectivity/Cross Language Clients/C Integration/openwire-c-client.md)
-
-
-This is the C library which is based on the [OpenWire](../../../Connectivity/Protocols/openwire.md) protocol.
-
-You can browse the code here
-
-[http://svn.apache.org/repos/asf/activemq/sandbox/openwire-c/](http://svn.apache.org/repos/asf/activemq/sandbox/openwire-c/)
-
-e.g. here's an example of it in use...
-
-[http://svn.apache.org/repos/asf/activemq/sandbox/openwire-c/src/examples/main.c](http://svn.apache.org/repos/asf/activemq/sandbox/openwire-c/src/examples/main.c)
-
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/activemq-c-clients.md b/src/_documents/classic/Connectivity/Cross Language Clients/activemq-c-clients.md
deleted file mode 100644
index ef8b400..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/activemq-c-clients.md
+++ /dev/null
@@ -1,10 +0,0 @@
-Apache ActiveMQ ™ -- ActiveMQ C++ Clients
-
-[Connectivity](../../connectivity.md) > [Cross Language Clients](../../Connectivity/cross-language-clients.md) > [ActiveMQ C++ Clients](../../Connectivity/Cross Language Clients/activemq-c-clients.md)
-
-
-ActiveMQ C++ Integration
-------------------------
-
-[CMS](http://activemq.apache.org/cms/) is an easy-to-use JMS 1.1-like API. Our implementation of CMS is called ActiveMQ-CPP, the architecture for which supports pluggable transport protocols, very much like the ActiveMQ broker itself.
-
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/c-integration.md b/src/_documents/classic/Connectivity/Cross Language Clients/c-integration.md
deleted file mode 100644
index 94eff11..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/c-integration.md
+++ /dev/null
@@ -1,22 +0,0 @@
-Apache ActiveMQ ™ -- C Integration
-
-[Connectivity](../../connectivity.md) > [Cross Language Clients](../../Connectivity/cross-language-clients.md) > [C Integration](../../Connectivity/Cross Language Clients/c-integration.md)
-
-
-It is very common for an organisation to have lots of legacy C code which needs integration into the message bus. The current available solutions are
-
-* [CMS](#) is an easy-to-use JMS 1.1-like API for C++. Our implementation of CMS is called ActiveMQ-CPP, the architecture for which supports pluggable transport protocols, very much like the ActiveMQ broker itself.
-* use the [OpenWire C Client](../../Connectivity/Cross Language Clients/C Integration/openwire-c-client.md) which is only available in ActiveMQ 4.x or later.
-* we are working on the [OpenWire CPP Client](Connectivity/Cross Language Clients/ActiveMQ C++ ClientsConnectivity/Cross Language Clients/ActiveMQ C++ Clients/Connectivity/Cross Language Clients/ActiveMQ C++ Clients/openwire-cpp-client.md)
-
-* use the [Stomp C Client](http://stomp.codehaus.org/C) for any version of ActiveMQ from 3.1 onwards. You can also use [Stomp](http://stomp.codehaus.org/) from many other languages like .Net, Python, Ruby, Perl etc.
-
-Other alternative mechanisms to communicate using.
-
-* use the [REST](../../Connectivity/Protocols/rest.md) API
-* use [WS-Notification](http://servicemix.org/WS+Notification) and generate C bindings to WS-Notification using a SOAP stack
-* use [.Net or Mono](../../FAQ/Using Apache ActiveMQ/how-do-i-access-activemq-from-csharp-or-dotnet.md) to use ActiveMQ insided .Net
-* [Compile ActiveMQ with GCJ](../../Connectivity/Cross Language Clients/C Integration/compile-activemq-with-gcj.md) to get a native C/C++ library
-* link to the ActiveMQ Java client using JNI
-* Use a Jabber client to talk to the ActiveMQ broker via the [XMPP](../../Connectivity/Protocols/xmpp.md) protocol
-
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/cms.md b/src/_documents/classic/Connectivity/Cross Language Clients/cms.md
deleted file mode 100644
index 78a9cab..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/cms.md
+++ /dev/null
@@ -1,169 +0,0 @@
-Apache ActiveMQ ™ -- CMS
-
-[Connectivity](../../connectivity.md) > [Cross Language Clients](../../Connectivity/cross-language-clients.md) > [CMS](../../Connectivity/Cross Language Clients/cms.md)
-
-[Download](OverviewOverview/Overview/download.md "Download") | [JavaDocs](http://activemq.apache.org/maven/5.7.0/activemq-core/apidocs/) [More...](Overview/javadocs.md "JavaDocs") | [Source](Developers/source.md "Source") | [Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums") | [Support](CommunityCommunity/Community/support.md "Support")
-
-
-
-**Moved Page**
-This page has moved [here](http://activemq.apache.org/cms/)
-
-### [Overview](overview.md "Overview")
-
-* [Index](index.html "Index")
-* [News](Overview/news.md "News")
-* [New Features](/Features/new-features.md "New Features")
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [FAQ](CommunityCommunity/Community/faq.md "FAQ")
-* [Articles](Community/articles.md "Articles")
-* [Books](CommunityCommunity/Community/books.md "Books")
-* [Download](OverviewOverview/Overview/download.md "Download")
-* [License](http://www.apache.org/licenses/)
-
-### Search
-
-
-
-
-### Sub Projects
-
-* [Apollo](http://activemq.apache.org/apollo "ActiveMQ Apollo")
-* [CMS](http://activemq.apache.org/cms/ "The C++ API for Messaging")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [Camel](http://camel.apache.org/ "POJO based Enterprise Integration Patterns with a typesafe Java DSL")
-
-### [Community](community.md "Community")
-
-* [Support](CommunityCommunity/Community/support.md "Support")
-* [Contributing](CommunityCommunity/Community/contributing.md "Contributing")
-* [Discussion Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums")
-* [Mailing Lists](Community/mailing-lists.md "Mailing Lists")
-* [IRC](irc://irc.codehaus.org/activemq)
-* [IRC Log](http://servlet.uwyn.com/drone/log/hausbot/activemq)
-* [Site](site.md "Site")
-* [Sponsorship](http://www.apache.org/foundationCommunity/sponsorship.md)
-* [Projects Using ActiveMQ](CommunityCommunity/Community/projects-using-activemq.md "Projects Using ActiveMQ")
-* [Users](CommunityCommunity/Community/users.md "Users")
-* [Team](CommunityCommunity/Community/team.md "Team")
-* [Thanks](http://www.apache.org/foundationIndexIndex/Index/thanks.md)
-
-### [Features](features.md "Features")
-
-* [Advisory Message](/Features/Message Features/advisory-message.md "Advisory Message")
-* [Clustering](/Features/clustering.md "Clustering")
-* [Cross Language Clients](Connectivity/cross-language-clients.md "Cross Language Clients")
-* [Enterprise Integration Patterns](/Features/enterprise-integration-patterns.md "Enterprise Integration Patterns")
-* [JMX](/Features/jmx.md "JMX")
-* [JMS to JMS Bridge](ConnectivityConnectivity/Connectivity/jms-to-jms-bridge.md "JMS to JMS Bridge")
-* [MasterSlave](/Features/ClusteringFeatures/Clustering/Features/Clustering/masterslave.md "MasterSlave")
-* [Message Groups](/Features/Consumer Features/message-groups.md "Message Groups")
-* [Networks of Brokers](/Features/Clustering/networks-of-brokers.md "Networks of Brokers")
-* [Performance](/Features/performance.md "Performance")
-* [Persistence](/Features/persistence.md "Persistence")
-* [Security](/Features/security.md "Security")
-* [Virtual Destinations](/Features/Destination Features/virtual-destinations.md "Virtual Destinations")
-* [Visualisation](/Features/visualisation.md "Visualisation")
-* [More ...](features.md "Features")
-
-### [Connectivity](connectivity.md "Connectivity")
-
-* [Ajax](Connectivity/ajax.md "Ajax")
-* [AMQP](Connectivity/Protocols/amqp.md "AMQP")
-* [Axis and CXF Support](axis-and-cxf-CommunityCommunity/Community/support.md "Axis and CXF Support")
-* [C Integration](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "C Integration")
-* [C++](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/activemq-c-clients.md "ActiveMQ C++ Clients")
-* [C# and .Net Integration](http://activemq.apache.org/nms/)
-* [CMS](http://activemq.apache.org/cms/)
-* [J2EE](Connectivity/Containers/j2ee.md "J2EE")
-* [JBoss Integration](Connectivity/ContainersConnectivity/Containers/Connectivity/Containers/jboss-integration.md "JBoss Integration")
-* [Jetty](http://docs.codehaus.org/display/JETTY/Integrating+with+ActiveMQ)
-* [JNDI Support](Connectivity/Containers/jndi-Community/support.md "JNDI Support")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [REST](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rest.md "REST")
-* [RSS and Atom](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rss-and-atom.md "RSS and Atom")
-* [Spring Support](Connectivity/Containers/spring-Community/support.md "Spring Support")
-* [Stomp](Connectivity/Protocols/stomp.md "Stomp")
-* [Tomcat](Connectivity/Containers/tomcat.md "Tomcat")
-* [Unix Service](/Features/Unix/unix-service.md "Unix Service")
-* [WebLogic Integration](weblogiConnectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "WebLogic Integration")
-* [XMPP](Connectivity/Protocols/xmpp.md "XMPP")
-* [More ...](connectivity.md "Connectivity")
-
-### [Using ActiveMQ 5](using-activemq-5.md "Using ActiveMQ 5")
-
-* [Getting Started](version-5-Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Version 5 Getting Started")
-* [Initial Configuration](version-5-Using ActiveMQ/initial-Community/FAQ/configuration.md "Version 5 Initial Configuration")
-* [Running a Broker](Using ActiveMQ 5/version-5-Using ActiveMQ/run-broker.md "Version 5 Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ 5/configuring-version-5-transports.md "Configuring Version 5 Transports")
-* [Examples](version-5-Using ActiveMQ/examples.md "Version 5 Examples")
-* [Web Samples](Using ActiveMQ 5Using ActiveMQ 5/Using ActiveMQ 5/version-5-Using ActiveMQ/web-samples.md "Version 5 Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](Using ActiveMQ 5/version-5-xml-Community/FAQ/configuration.md "Version 5 XML Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq-5.md "Using ActiveMQ 5")
-
-### [Using ActiveMQ 4](using-activemq.md "Using ActiveMQ")
-
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [Initial Configuration](Using ActiveMQ/initial-Community/FAQ/configuration.md "Initial Configuration")
-* [Running a Broker](Using ActiveMQ/run-broker.md "Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ/configuring-transports.md "Configuring Transports")
-* [Examples](Using ActiveMQ/examples.md "Examples")
-* [Web Samples](Using ActiveMQ/web-samples.md "Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](xml-Community/FAQ/configuration.md "Xml Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq.md "Using ActiveMQ")
-
-### [Tools](tools.md "Tools")
-
-* [Web Console](ToolsTools/Tools/web-console.md "Web Console")
-* [Hermes Jms](ToolsTools/Tools/hermes-Community/FAQ/jms.md "Hermes Jms")
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [JMeter](http://jakarta.apache.org/jmeter)
-
-### [Support](CommunityCommunity/Community/support.md "Support")
-
-* [Issues](http://issues.apache.org/jira/browse/AMQ)
-* [Roadmap](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
-* [Change log](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:changelog-panel)
-
-### Related Projects
-
-* [Apache ServiceMix](http://incubator.apache.org/servicemix/ "Distributed Enterprise Service Bus based on JBI")
-* [Lingo](http://lingo.codehaus.org/ "POJO Remoting using JMS")
-* [Jencks](http://jencks.codehaus.org/ "Message Driven POJOs and pooling for JMS and JDBC")
-* [Stomp](http://stomp.codehaus.org/ "A simple protocol for messaging middleware interop and the easy development of custom clients")
-* [Spring](http://www.springframework.org/)
-* [OpenEJB](http://openejb.apache.org)
-* [Geronimo](http://geronimo.apache.org/)
-
-### [Developers](developers.md "Developers")
-
-* [Source](Developers/source.md "Source")
-* [Building](Developers/building.md "Building")
-* [Developer Guide](DevelopersDevelopers/Developers/developer-guide.md "Developer Guide")
-* [Becoming a committer](Developers/becoming-a-committer.md "Becoming a committer")
-* [Code Overview](code-overview.md "Code Overview")
-* [Wire Protocol](Developers/wire-protocol.md "Wire Protocol")
-* [Release Guide](DevelopersDevelopers/Developers/release-guide.md "Release Guide")
-
-### Tests
-
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [Benchmark Tests](Developers/benchmark-tests.md "Benchmark Tests")
-* [JMeter System Tests](Developers/jmeter-system-tests.md "JMeter System Tests")
-* [JMeter Performance Tests](Developers/jmeter-performance-tests.md "JMeter Performance Tests")
-* [Integration Tests](Developers/integration-tests.md "Integration Tests")
-
-### Project Reports
-
-* [JUnit Reports](DevelopersDevelopers/Developers/junit-reports.md "JUnit Reports")
-* [Source XRef](Developers/source-xref.md "Source XRef")
-* [Test Source XRef](Developers/test-Developers/source-xref.md "Test Source XRef")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/delphi-and-freepascal.md b/src/_documents/classic/Connectivity/Cross Language Clients/delphi-and-freepascal.md
deleted file mode 100644
index 351d4a3..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/delphi-and-freepascal.md
+++ /dev/null
@@ -1,26 +0,0 @@
-Apache ActiveMQ ™ -- Delphi and FreePascal
-
-[Connectivity](../../connectivity.md) > [Cross Language Clients](../../Connectivity/cross-language-clients.md) > [Delphi and FreePascal](../../Connectivity/Cross Language Clients/delphi-and-freepascal.md)
-
-
-Delphi and FreePascal Client
-============================
-
-Habari ActiveMQ Client is a library for Delphi(tm) and Free Pascal. With Habari, applications can connect to Apache ActiveMQ servers, subscribe to queues and topics, send and receive messages and objects, and work with transactions.
-
-### Supported Communication Libraries
-
-* Internet Direct (Indy) 10.2
-* Synapse
-* OverByte ICS V6 (limited feature set)
-* TClientSocket (limited feature set)
-
-### Project Status
-
-Habari ActiveMQ Client 1.0 has been released on March 5, 2008. Demo applications, API documentation and source code examples are available for download.
-The API documentation is available at [http://www.mikejustin.com/habaridocs.md/index.html](http://www.mikejustin.com/habaridocs.md/index.html)
-
-### Project Home Page
-
-[http://www.mikejustin.com/](http://www.mikejustin.com/)
-
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/dot-net.md b/src/_documents/classic/Connectivity/Cross Language Clients/dot-net.md
deleted file mode 100644
index 36aea9b..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/dot-net.md
+++ /dev/null
@@ -1,166 +0,0 @@
-Apache ActiveMQ ™ -- dot Net
-
-[Connectivity](../../connectivity.md) > [Cross Language Clients](../../Connectivity/cross-language-clients.md) > [dot Net](../../Connectivity/Cross Language Clients/dot-net.md)
-
-[Download](OverviewOverview/Overview/download.md "Download") | [JavaDocs](http://activemq.apache.org/maven/5.7.0/activemq-core/apidocs/) [More...](Overview/javadocs.md "JavaDocs") | [Source](Developers/source.md "Source") | [Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums") | [Support](CommunityCommunity/Community/support.md "Support")
-
-Unable to render {include} Couldn't find a page to include called: nms
-
-### [Overview](overview.md "Overview")
-
-* [Index](index.html "Index")
-* [News](Overview/news.md "News")
-* [New Features](/Features/new-features.md "New Features")
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [FAQ](CommunityCommunity/Community/faq.md "FAQ")
-* [Articles](Community/articles.md "Articles")
-* [Books](CommunityCommunity/Community/books.md "Books")
-* [Download](OverviewOverview/Overview/download.md "Download")
-* [License](http://www.apache.org/licenses/)
-
-### Search
-
-
-
-
-### Sub Projects
-
-* [Apollo](http://activemq.apache.org/apollo "ActiveMQ Apollo")
-* [CMS](http://activemq.apache.org/cms/ "The C++ API for Messaging")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [Camel](http://camel.apache.org/ "POJO based Enterprise Integration Patterns with a typesafe Java DSL")
-
-### [Community](community.md "Community")
-
-* [Support](CommunityCommunity/Community/support.md "Support")
-* [Contributing](CommunityCommunity/Community/contributing.md "Contributing")
-* [Discussion Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums")
-* [Mailing Lists](Community/mailing-lists.md "Mailing Lists")
-* [IRC](irc://irc.codehaus.org/activemq)
-* [IRC Log](http://servlet.uwyn.com/drone/log/hausbot/activemq)
-* [Site](site.md "Site")
-* [Sponsorship](http://www.apache.org/foundationCommunity/sponsorship.md)
-* [Projects Using ActiveMQ](CommunityCommunity/Community/projects-using-activemq.md "Projects Using ActiveMQ")
-* [Users](CommunityCommunity/Community/users.md "Users")
-* [Team](CommunityCommunity/Community/team.md "Team")
-* [Thanks](http://www.apache.org/foundationIndexIndex/Index/thanks.md)
-
-### [Features](features.md "Features")
-
-* [Advisory Message](/Features/Message Features/advisory-message.md "Advisory Message")
-* [Clustering](/Features/clustering.md "Clustering")
-* [Cross Language Clients](Connectivity/cross-language-clients.md "Cross Language Clients")
-* [Enterprise Integration Patterns](/Features/enterprise-integration-patterns.md "Enterprise Integration Patterns")
-* [JMX](/Features/jmx.md "JMX")
-* [JMS to JMS Bridge](ConnectivityConnectivity/Connectivity/jms-to-jms-bridge.md "JMS to JMS Bridge")
-* [MasterSlave](/Features/ClusteringFeatures/Clustering/Features/Clustering/masterslave.md "MasterSlave")
-* [Message Groups](/Features/Consumer Features/message-groups.md "Message Groups")
-* [Networks of Brokers](/Features/Clustering/networks-of-brokers.md "Networks of Brokers")
-* [Performance](/Features/performance.md "Performance")
-* [Persistence](/Features/persistence.md "Persistence")
-* [Security](/Features/security.md "Security")
-* [Virtual Destinations](/Features/Destination Features/virtual-destinations.md "Virtual Destinations")
-* [Visualisation](/Features/visualisation.md "Visualisation")
-* [More ...](features.md "Features")
-
-### [Connectivity](connectivity.md "Connectivity")
-
-* [Ajax](Connectivity/ajax.md "Ajax")
-* [AMQP](Connectivity/Protocols/amqp.md "AMQP")
-* [Axis and CXF Support](axis-and-cxf-CommunityCommunity/Community/support.md "Axis and CXF Support")
-* [C Integration](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "C Integration")
-* [C++](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/activemq-c-clients.md "ActiveMQ C++ Clients")
-* [C# and .Net Integration](http://activemq.apache.org/nms/)
-* [CMS](http://activemq.apache.org/cms/)
-* [J2EE](Connectivity/Containers/j2ee.md "J2EE")
-* [JBoss Integration](Connectivity/ContainersConnectivity/Containers/Connectivity/Containers/jboss-integration.md "JBoss Integration")
-* [Jetty](http://docs.codehaus.org/display/JETTY/Integrating+with+ActiveMQ)
-* [JNDI Support](Connectivity/Containers/jndi-Community/support.md "JNDI Support")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [REST](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rest.md "REST")
-* [RSS and Atom](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rss-and-atom.md "RSS and Atom")
-* [Spring Support](Connectivity/Containers/spring-Community/support.md "Spring Support")
-* [Stomp](Connectivity/Protocols/stomp.md "Stomp")
-* [Tomcat](Connectivity/Containers/tomcat.md "Tomcat")
-* [Unix Service](/Features/Unix/unix-service.md "Unix Service")
-* [WebLogic Integration](weblogiConnectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "WebLogic Integration")
-* [XMPP](Connectivity/Protocols/xmpp.md "XMPP")
-* [More ...](connectivity.md "Connectivity")
-
-### [Using ActiveMQ 5](using-activemq-5.md "Using ActiveMQ 5")
-
-* [Getting Started](version-5-Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Version 5 Getting Started")
-* [Initial Configuration](version-5-Using ActiveMQ/initial-Community/FAQ/configuration.md "Version 5 Initial Configuration")
-* [Running a Broker](Using ActiveMQ 5/version-5-Using ActiveMQ/run-broker.md "Version 5 Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ 5/configuring-version-5-transports.md "Configuring Version 5 Transports")
-* [Examples](version-5-Using ActiveMQ/examples.md "Version 5 Examples")
-* [Web Samples](Using ActiveMQ 5Using ActiveMQ 5/Using ActiveMQ 5/version-5-Using ActiveMQ/web-samples.md "Version 5 Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](Using ActiveMQ 5/version-5-xml-Community/FAQ/configuration.md "Version 5 XML Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq-5.md "Using ActiveMQ 5")
-
-### [Using ActiveMQ 4](using-activemq.md "Using ActiveMQ")
-
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [Initial Configuration](Using ActiveMQ/initial-Community/FAQ/configuration.md "Initial Configuration")
-* [Running a Broker](Using ActiveMQ/run-broker.md "Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ/configuring-transports.md "Configuring Transports")
-* [Examples](Using ActiveMQ/examples.md "Examples")
-* [Web Samples](Using ActiveMQ/web-samples.md "Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](xml-Community/FAQ/configuration.md "Xml Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq.md "Using ActiveMQ")
-
-### [Tools](tools.md "Tools")
-
-* [Web Console](ToolsTools/Tools/web-console.md "Web Console")
-* [Hermes Jms](ToolsTools/Tools/hermes-Community/FAQ/jms.md "Hermes Jms")
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [JMeter](http://jakarta.apache.org/jmeter)
-
-### [Support](CommunityCommunity/Community/support.md "Support")
-
-* [Issues](http://issues.apache.org/jira/browse/AMQ)
-* [Roadmap](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
-* [Change log](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:changelog-panel)
-
-### Related Projects
-
-* [Apache ServiceMix](http://incubator.apache.org/servicemix/ "Distributed Enterprise Service Bus based on JBI")
-* [Lingo](http://lingo.codehaus.org/ "POJO Remoting using JMS")
-* [Jencks](http://jencks.codehaus.org/ "Message Driven POJOs and pooling for JMS and JDBC")
-* [Stomp](http://stomp.codehaus.org/ "A simple protocol for messaging middleware interop and the easy development of custom clients")
-* [Spring](http://www.springframework.org/)
-* [OpenEJB](http://openejb.apache.org)
-* [Geronimo](http://geronimo.apache.org/)
-
-### [Developers](developers.md "Developers")
-
-* [Source](Developers/source.md "Source")
-* [Building](Developers/building.md "Building")
-* [Developer Guide](DevelopersDevelopers/Developers/developer-guide.md "Developer Guide")
-* [Becoming a committer](Developers/becoming-a-committer.md "Becoming a committer")
-* [Code Overview](code-overview.md "Code Overview")
-* [Wire Protocol](Developers/wire-protocol.md "Wire Protocol")
-* [Release Guide](DevelopersDevelopers/Developers/release-guide.md "Release Guide")
-
-### Tests
-
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [Benchmark Tests](Developers/benchmark-tests.md "Benchmark Tests")
-* [JMeter System Tests](Developers/jmeter-system-tests.md "JMeter System Tests")
-* [JMeter Performance Tests](Developers/jmeter-performance-tests.md "JMeter Performance Tests")
-* [Integration Tests](Developers/integration-tests.md "Integration Tests")
-
-### Project Reports
-
-* [JUnit Reports](DevelopersDevelopers/Developers/junit-reports.md "JUnit Reports")
-* [Source XRef](Developers/source-xref.md "Source XRef")
-* [Test Source XRef](Developers/test-Developers/source-xref.md "Test Source XRef")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/perl.md b/src/_documents/classic/Connectivity/Cross Language Clients/perl.md
deleted file mode 100644
index cc981e6..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/perl.md
+++ /dev/null
@@ -1,177 +0,0 @@
-Apache ActiveMQ ™ -- Perl
-
-[Connectivity](../../connectivity.md) > [Cross Language Clients](../../Connectivity/cross-language-clients.md) > [Perl](../../Connectivity/Cross Language Clients/perl.md)
-
-[Download](OverviewOverview/Overview/download.md "Download") | [JavaDocs](http://activemq.apache.org/maven/5.7.0/activemq-core/apidocs/) [More...](Overview/javadocs.md "JavaDocs") | [Source](Developers/source.md "Source") | [Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums") | [Support](CommunityCommunity/Community/support.md "Support")
-
-Perl Support
-------------
-
-For Perl support we recommend the use of the [Stomp protocol](http://activemq.apache.orgConnectivity/Protocols/stomp.md).
-There are various Perl Stomp clients available, such as
-
-[Net::STOMP::Client Perl](http://search.cpan.org/dist/Net-STOMP-Client/)
-[Net::Stomp Perl](http://search.cpan.org/dist/Net-Stomp/)
-
-Both are hosted on [CPAN.org](http://www.cpan.org)
-
-A more exhausting list of Stomp client libraries for Perl is available on [stomp.github.com](http://stomp.github.com//implementations.html).
-
-### [Overview](overview.md "Overview")
-
-* [Index](index.html "Index")
-* [News](Overview/news.md "News")
-* [New Features](/Features/new-features.md "New Features")
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [FAQ](CommunityCommunity/Community/faq.md "FAQ")
-* [Articles](Community/articles.md "Articles")
-* [Books](CommunityCommunity/Community/books.md "Books")
-* [Download](OverviewOverview/Overview/download.md "Download")
-* [License](http://www.apache.org/licenses/)
-
-### Search
-
-
-
-
-### Sub Projects
-
-* [Apollo](http://activemq.apache.org/apollo "ActiveMQ Apollo")
-* [CMS](http://activemq.apache.org/cms/ "The C++ API for Messaging")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [Camel](http://camel.apache.org/ "POJO based Enterprise Integration Patterns with a typesafe Java DSL")
-
-### [Community](community.md "Community")
-
-* [Support](CommunityCommunity/Community/support.md "Support")
-* [Contributing](CommunityCommunity/Community/contributing.md "Contributing")
-* [Discussion Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums")
-* [Mailing Lists](Community/mailing-lists.md "Mailing Lists")
-* [IRC](irc://irc.codehaus.org/activemq)
-* [IRC Log](http://servlet.uwyn.com/drone/log/hausbot/activemq)
-* [Site](site.md "Site")
-* [Sponsorship](http://www.apache.org/foundationCommunity/sponsorship.md)
-* [Projects Using ActiveMQ](CommunityCommunity/Community/projects-using-activemq.md "Projects Using ActiveMQ")
-* [Users](CommunityCommunity/Community/users.md "Users")
-* [Team](CommunityCommunity/Community/team.md "Team")
-* [Thanks](http://www.apache.org/foundationIndexIndex/Index/thanks.md)
-
-### [Features](features.md "Features")
-
-* [Advisory Message](/Features/Message Features/advisory-message.md "Advisory Message")
-* [Clustering](/Features/clustering.md "Clustering")
-* [Cross Language Clients](Connectivity/cross-language-clients.md "Cross Language Clients")
-* [Enterprise Integration Patterns](/Features/enterprise-integration-patterns.md "Enterprise Integration Patterns")
-* [JMX](/Features/jmx.md "JMX")
-* [JMS to JMS Bridge](ConnectivityConnectivity/Connectivity/jms-to-jms-bridge.md "JMS to JMS Bridge")
-* [MasterSlave](/Features/ClusteringFeatures/Clustering/Features/Clustering/masterslave.md "MasterSlave")
-* [Message Groups](/Features/Consumer Features/message-groups.md "Message Groups")
-* [Networks of Brokers](/Features/Clustering/networks-of-brokers.md "Networks of Brokers")
-* [Performance](/Features/performance.md "Performance")
-* [Persistence](/Features/persistence.md "Persistence")
-* [Security](/Features/security.md "Security")
-* [Virtual Destinations](/Features/Destination Features/virtual-destinations.md "Virtual Destinations")
-* [Visualisation](/Features/visualisation.md "Visualisation")
-* [More ...](features.md "Features")
-
-### [Connectivity](connectivity.md "Connectivity")
-
-* [Ajax](Connectivity/ajax.md "Ajax")
-* [AMQP](Connectivity/Protocols/amqp.md "AMQP")
-* [Axis and CXF Support](axis-and-cxf-CommunityCommunity/Community/support.md "Axis and CXF Support")
-* [C Integration](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "C Integration")
-* [C++](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/activemq-c-clients.md "ActiveMQ C++ Clients")
-* [C# and .Net Integration](http://activemq.apache.org/nms/)
-* [CMS](http://activemq.apache.org/cms/)
-* [J2EE](Connectivity/Containers/j2ee.md "J2EE")
-* [JBoss Integration](Connectivity/ContainersConnectivity/Containers/Connectivity/Containers/jboss-integration.md "JBoss Integration")
-* [Jetty](http://docs.codehaus.org/display/JETTY/Integrating+with+ActiveMQ)
-* [JNDI Support](Connectivity/Containers/jndi-Community/support.md "JNDI Support")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [REST](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rest.md "REST")
-* [RSS and Atom](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rss-and-atom.md "RSS and Atom")
-* [Spring Support](Connectivity/Containers/spring-Community/support.md "Spring Support")
-* [Stomp](Connectivity/Protocols/stomp.md "Stomp")
-* [Tomcat](Connectivity/Containers/tomcat.md "Tomcat")
-* [Unix Service](/Features/Unix/unix-service.md "Unix Service")
-* [WebLogic Integration](weblogiConnectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "WebLogic Integration")
-* [XMPP](Connectivity/Protocols/xmpp.md "XMPP")
-* [More ...](connectivity.md "Connectivity")
-
-### [Using ActiveMQ 5](using-activemq-5.md "Using ActiveMQ 5")
-
-* [Getting Started](version-5-Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Version 5 Getting Started")
-* [Initial Configuration](version-5-Using ActiveMQ/initial-Community/FAQ/configuration.md "Version 5 Initial Configuration")
-* [Running a Broker](Using ActiveMQ 5/version-5-Using ActiveMQ/run-broker.md "Version 5 Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ 5/configuring-version-5-transports.md "Configuring Version 5 Transports")
-* [Examples](version-5-Using ActiveMQ/examples.md "Version 5 Examples")
-* [Web Samples](Using ActiveMQ 5Using ActiveMQ 5/Using ActiveMQ 5/version-5-Using ActiveMQ/web-samples.md "Version 5 Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](Using ActiveMQ 5/version-5-xml-Community/FAQ/configuration.md "Version 5 XML Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq-5.md "Using ActiveMQ 5")
-
-### [Using ActiveMQ 4](using-activemq.md "Using ActiveMQ")
-
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [Initial Configuration](Using ActiveMQ/initial-Community/FAQ/configuration.md "Initial Configuration")
-* [Running a Broker](Using ActiveMQ/run-broker.md "Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ/configuring-transports.md "Configuring Transports")
-* [Examples](Using ActiveMQ/examples.md "Examples")
-* [Web Samples](Using ActiveMQ/web-samples.md "Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](xml-Community/FAQ/configuration.md "Xml Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq.md "Using ActiveMQ")
-
-### [Tools](tools.md "Tools")
-
-* [Web Console](ToolsTools/Tools/web-console.md "Web Console")
-* [Hermes Jms](ToolsTools/Tools/hermes-Community/FAQ/jms.md "Hermes Jms")
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [JMeter](http://jakarta.apache.org/jmeter)
-
-### [Support](CommunityCommunity/Community/support.md "Support")
-
-* [Issues](http://issues.apache.org/jira/browse/AMQ)
-* [Roadmap](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
-* [Change log](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:changelog-panel)
-
-### Related Projects
-
-* [Apache ServiceMix](http://incubator.apache.org/servicemix/ "Distributed Enterprise Service Bus based on JBI")
-* [Lingo](http://lingo.codehaus.org/ "POJO Remoting using JMS")
-* [Jencks](http://jencks.codehaus.org/ "Message Driven POJOs and pooling for JMS and JDBC")
-* [Stomp](http://stomp.codehaus.org/ "A simple protocol for messaging middleware interop and the easy development of custom clients")
-* [Spring](http://www.springframework.org/)
-* [OpenEJB](http://openejb.apache.org)
-* [Geronimo](http://geronimo.apache.org/)
-
-### [Developers](developers.md "Developers")
-
-* [Source](Developers/source.md "Source")
-* [Building](Developers/building.md "Building")
-* [Developer Guide](DevelopersDevelopers/Developers/developer-guide.md "Developer Guide")
-* [Becoming a committer](Developers/becoming-a-committer.md "Becoming a committer")
-* [Code Overview](code-overview.md "Code Overview")
-* [Wire Protocol](Developers/wire-protocol.md "Wire Protocol")
-* [Release Guide](DevelopersDevelopers/Developers/release-guide.md "Release Guide")
-
-### Tests
-
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [Benchmark Tests](Developers/benchmark-tests.md "Benchmark Tests")
-* [JMeter System Tests](Developers/jmeter-system-tests.md "JMeter System Tests")
-* [JMeter Performance Tests](Developers/jmeter-performance-tests.md "JMeter Performance Tests")
-* [Integration Tests](Developers/integration-tests.md "Integration Tests")
-
-### Project Reports
-
-* [JUnit Reports](DevelopersDevelopers/Developers/junit-reports.md "JUnit Reports")
-* [Source XRef](Developers/source-xref.md "Source XRef")
-* [Test Source XRef](Developers/test-Developers/source-xref.md "Test Source XRef")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/php.md b/src/_documents/classic/Connectivity/Cross Language Clients/php.md
deleted file mode 100644
index 8bd9a29..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/php.md
+++ /dev/null
@@ -1,170 +0,0 @@
-Apache ActiveMQ ™ -- PHP
-
-[Connectivity](../../connectivity.md) > [Cross Language Clients](../../Connectivity/cross-language-clients.md) > [PHP](../../Connectivity/Cross Language Clients/php.md)
-
-[Download](OverviewOverview/Overview/download.md "Download") | [JavaDocs](http://activemq.apache.org/maven/5.7.0/activemq-core/apidocs/) [More...](Overview/javadocs.md "JavaDocs") | [Source](Developers/source.md "Source") | [Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums") | [Support](CommunityCommunity/Community/support.md "Support")
-
-PHP Support
------------
-
-For PHP support we recommend the PHP Stomp Client. A list of available clients for PHP is available [here](http://stomp.codehaus.org/implementations.html).
-Among others you can grab a stomp-php client from [here](http://stomp.fusesource.org/release/php/1.0/stomp-php-1.0.0.tar.gz)
-
-### [Overview](overview.md "Overview")
-
-* [Index](index.html "Index")
-* [News](Overview/news.md "News")
-* [New Features](/Features/new-features.md "New Features")
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [FAQ](CommunityCommunity/Community/faq.md "FAQ")
-* [Articles](Community/articles.md "Articles")
-* [Books](CommunityCommunity/Community/books.md "Books")
-* [Download](OverviewOverview/Overview/download.md "Download")
-* [License](http://www.apache.org/licenses/)
-
-### Search
-
-
-
-
-### Sub Projects
-
-* [Apollo](http://activemq.apache.org/apollo "ActiveMQ Apollo")
-* [CMS](http://activemq.apache.org/cms/ "The C++ API for Messaging")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [Camel](http://camel.apache.org/ "POJO based Enterprise Integration Patterns with a typesafe Java DSL")
-
-### [Community](community.md "Community")
-
-* [Support](CommunityCommunity/Community/support.md "Support")
-* [Contributing](CommunityCommunity/Community/contributing.md "Contributing")
-* [Discussion Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums")
-* [Mailing Lists](Community/mailing-lists.md "Mailing Lists")
-* [IRC](irc://irc.codehaus.org/activemq)
-* [IRC Log](http://servlet.uwyn.com/drone/log/hausbot/activemq)
-* [Site](site.md "Site")
-* [Sponsorship](http://www.apache.org/foundationCommunity/sponsorship.md)
-* [Projects Using ActiveMQ](CommunityCommunity/Community/projects-using-activemq.md "Projects Using ActiveMQ")
-* [Users](CommunityCommunity/Community/users.md "Users")
-* [Team](CommunityCommunity/Community/team.md "Team")
-* [Thanks](http://www.apache.org/foundationIndexIndex/Index/thanks.md)
-
-### [Features](features.md "Features")
-
-* [Advisory Message](/Features/Message Features/advisory-message.md "Advisory Message")
-* [Clustering](/Features/clustering.md "Clustering")
-* [Cross Language Clients](Connectivity/cross-language-clients.md "Cross Language Clients")
-* [Enterprise Integration Patterns](/Features/enterprise-integration-patterns.md "Enterprise Integration Patterns")
-* [JMX](/Features/jmx.md "JMX")
-* [JMS to JMS Bridge](ConnectivityConnectivity/Connectivity/jms-to-jms-bridge.md "JMS to JMS Bridge")
-* [MasterSlave](/Features/ClusteringFeatures/Clustering/Features/Clustering/masterslave.md "MasterSlave")
-* [Message Groups](/Features/Consumer Features/message-groups.md "Message Groups")
-* [Networks of Brokers](/Features/Clustering/networks-of-brokers.md "Networks of Brokers")
-* [Performance](/Features/performance.md "Performance")
-* [Persistence](/Features/persistence.md "Persistence")
-* [Security](/Features/security.md "Security")
-* [Virtual Destinations](/Features/Destination Features/virtual-destinations.md "Virtual Destinations")
-* [Visualisation](/Features/visualisation.md "Visualisation")
-* [More ...](features.md "Features")
-
-### [Connectivity](connectivity.md "Connectivity")
-
-* [Ajax](Connectivity/ajax.md "Ajax")
-* [AMQP](Connectivity/Protocols/amqp.md "AMQP")
-* [Axis and CXF Support](axis-and-cxf-CommunityCommunity/Community/support.md "Axis and CXF Support")
-* [C Integration](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "C Integration")
-* [C++](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/activemq-c-clients.md "ActiveMQ C++ Clients")
-* [C# and .Net Integration](http://activemq.apache.org/nms/)
-* [CMS](http://activemq.apache.org/cms/)
-* [J2EE](Connectivity/Containers/j2ee.md "J2EE")
-* [JBoss Integration](Connectivity/ContainersConnectivity/Containers/Connectivity/Containers/jboss-integration.md "JBoss Integration")
-* [Jetty](http://docs.codehaus.org/display/JETTY/Integrating+with+ActiveMQ)
-* [JNDI Support](Connectivity/Containers/jndi-Community/support.md "JNDI Support")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [REST](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rest.md "REST")
-* [RSS and Atom](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rss-and-atom.md "RSS and Atom")
-* [Spring Support](Connectivity/Containers/spring-Community/support.md "Spring Support")
-* [Stomp](Connectivity/Protocols/stomp.md "Stomp")
-* [Tomcat](Connectivity/Containers/tomcat.md "Tomcat")
-* [Unix Service](/Features/Unix/unix-service.md "Unix Service")
-* [WebLogic Integration](weblogiConnectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "WebLogic Integration")
-* [XMPP](Connectivity/Protocols/xmpp.md "XMPP")
-* [More ...](connectivity.md "Connectivity")
-
-### [Using ActiveMQ 5](using-activemq-5.md "Using ActiveMQ 5")
-
-* [Getting Started](version-5-Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Version 5 Getting Started")
-* [Initial Configuration](version-5-Using ActiveMQ/initial-Community/FAQ/configuration.md "Version 5 Initial Configuration")
-* [Running a Broker](Using ActiveMQ 5/version-5-Using ActiveMQ/run-broker.md "Version 5 Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ 5/configuring-version-5-transports.md "Configuring Version 5 Transports")
-* [Examples](version-5-Using ActiveMQ/examples.md "Version 5 Examples")
-* [Web Samples](Using ActiveMQ 5Using ActiveMQ 5/Using ActiveMQ 5/version-5-Using ActiveMQ/web-samples.md "Version 5 Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](Using ActiveMQ 5/version-5-xml-Community/FAQ/configuration.md "Version 5 XML Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq-5.md "Using ActiveMQ 5")
-
-### [Using ActiveMQ 4](using-activemq.md "Using ActiveMQ")
-
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [Initial Configuration](Using ActiveMQ/initial-Community/FAQ/configuration.md "Initial Configuration")
-* [Running a Broker](Using ActiveMQ/run-broker.md "Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ/configuring-transports.md "Configuring Transports")
-* [Examples](Using ActiveMQ/examples.md "Examples")
-* [Web Samples](Using ActiveMQ/web-samples.md "Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](xml-Community/FAQ/configuration.md "Xml Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq.md "Using ActiveMQ")
-
-### [Tools](tools.md "Tools")
-
-* [Web Console](ToolsTools/Tools/web-console.md "Web Console")
-* [Hermes Jms](ToolsTools/Tools/hermes-Community/FAQ/jms.md "Hermes Jms")
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [JMeter](http://jakarta.apache.org/jmeter)
-
-### [Support](CommunityCommunity/Community/support.md "Support")
-
-* [Issues](http://issues.apache.org/jira/browse/AMQ)
-* [Roadmap](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
-* [Change log](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:changelog-panel)
-
-### Related Projects
-
-* [Apache ServiceMix](http://incubator.apache.org/servicemix/ "Distributed Enterprise Service Bus based on JBI")
-* [Lingo](http://lingo.codehaus.org/ "POJO Remoting using JMS")
-* [Jencks](http://jencks.codehaus.org/ "Message Driven POJOs and pooling for JMS and JDBC")
-* [Stomp](http://stomp.codehaus.org/ "A simple protocol for messaging middleware interop and the easy development of custom clients")
-* [Spring](http://www.springframework.org/)
-* [OpenEJB](http://openejb.apache.org)
-* [Geronimo](http://geronimo.apache.org/)
-
-### [Developers](developers.md "Developers")
-
-* [Source](Developers/source.md "Source")
-* [Building](Developers/building.md "Building")
-* [Developer Guide](DevelopersDevelopers/Developers/developer-guide.md "Developer Guide")
-* [Becoming a committer](Developers/becoming-a-committer.md "Becoming a committer")
-* [Code Overview](code-overview.md "Code Overview")
-* [Wire Protocol](Developers/wire-protocol.md "Wire Protocol")
-* [Release Guide](DevelopersDevelopers/Developers/release-guide.md "Release Guide")
-
-### Tests
-
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [Benchmark Tests](Developers/benchmark-tests.md "Benchmark Tests")
-* [JMeter System Tests](Developers/jmeter-system-tests.md "JMeter System Tests")
-* [JMeter Performance Tests](Developers/jmeter-performance-tests.md "JMeter Performance Tests")
-* [Integration Tests](Developers/integration-tests.md "Integration Tests")
-
-### Project Reports
-
-* [JUnit Reports](DevelopersDevelopers/Developers/junit-reports.md "JUnit Reports")
-* [Source XRef](Developers/source-xref.md "Source XRef")
-* [Test Source XRef](Developers/test-Developers/source-xref.md "Test Source XRef")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/pike.md b/src/_documents/classic/Connectivity/Cross Language Clients/pike.md
deleted file mode 100644
index 9de6513..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/pike.md
+++ /dev/null
@@ -1,169 +0,0 @@
-Apache ActiveMQ ™ -- Pike
-
-[Connectivity](../../connectivity.md) > [Cross Language Clients](../../Connectivity/cross-language-clients.md) > [Pike](../../Connectivity/Cross Language Clients/pike.md)
-
-[Download](OverviewOverview/Overview/download.md "Download") | [JavaDocs](http://activemq.apache.org/maven/5.7.0/activemq-core/apidocs/) [More...](Overview/javadocs.md "JavaDocs") | [Source](Developers/source.md "Source") | [Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums") | [Support](CommunityCommunity/Community/support.md "Support")
-
-Pike Support
-------------
-
-For Pike support we recommend the [Pike Stomp Client](http://stomp.codehaus.org/Pike)
-
-### [Overview](overview.md "Overview")
-
-* [Index](index.html "Index")
-* [News](Overview/news.md "News")
-* [New Features](/Features/new-features.md "New Features")
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [FAQ](CommunityCommunity/Community/faq.md "FAQ")
-* [Articles](Community/articles.md "Articles")
-* [Books](CommunityCommunity/Community/books.md "Books")
-* [Download](OverviewOverview/Overview/download.md "Download")
-* [License](http://www.apache.org/licenses/)
-
-### Search
-
-
-
-
-### Sub Projects
-
-* [Apollo](http://activemq.apache.org/apollo "ActiveMQ Apollo")
-* [CMS](http://activemq.apache.org/cms/ "The C++ API for Messaging")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [Camel](http://camel.apache.org/ "POJO based Enterprise Integration Patterns with a typesafe Java DSL")
-
-### [Community](community.md "Community")
-
-* [Support](CommunityCommunity/Community/support.md "Support")
-* [Contributing](CommunityCommunity/Community/contributing.md "Contributing")
-* [Discussion Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums")
-* [Mailing Lists](Community/mailing-lists.md "Mailing Lists")
-* [IRC](irc://irc.codehaus.org/activemq)
-* [IRC Log](http://servlet.uwyn.com/drone/log/hausbot/activemq)
-* [Site](site.md "Site")
-* [Sponsorship](http://www.apache.org/foundationCommunity/sponsorship.md)
-* [Projects Using ActiveMQ](CommunityCommunity/Community/projects-using-activemq.md "Projects Using ActiveMQ")
-* [Users](CommunityCommunity/Community/users.md "Users")
-* [Team](CommunityCommunity/Community/team.md "Team")
-* [Thanks](http://www.apache.org/foundationIndexIndex/Index/thanks.md)
-
-### [Features](features.md "Features")
-
-* [Advisory Message](/Features/Message Features/advisory-message.md "Advisory Message")
-* [Clustering](/Features/clustering.md "Clustering")
-* [Cross Language Clients](Connectivity/cross-language-clients.md "Cross Language Clients")
-* [Enterprise Integration Patterns](/Features/enterprise-integration-patterns.md "Enterprise Integration Patterns")
-* [JMX](/Features/jmx.md "JMX")
-* [JMS to JMS Bridge](ConnectivityConnectivity/Connectivity/jms-to-jms-bridge.md "JMS to JMS Bridge")
-* [MasterSlave](/Features/ClusteringFeatures/Clustering/Features/Clustering/masterslave.md "MasterSlave")
-* [Message Groups](/Features/Consumer Features/message-groups.md "Message Groups")
-* [Networks of Brokers](/Features/Clustering/networks-of-brokers.md "Networks of Brokers")
-* [Performance](/Features/performance.md "Performance")
-* [Persistence](/Features/persistence.md "Persistence")
-* [Security](/Features/security.md "Security")
-* [Virtual Destinations](/Features/Destination Features/virtual-destinations.md "Virtual Destinations")
-* [Visualisation](/Features/visualisation.md "Visualisation")
-* [More ...](features.md "Features")
-
-### [Connectivity](connectivity.md "Connectivity")
-
-* [Ajax](Connectivity/ajax.md "Ajax")
-* [AMQP](Connectivity/Protocols/amqp.md "AMQP")
-* [Axis and CXF Support](axis-and-cxf-CommunityCommunity/Community/support.md "Axis and CXF Support")
-* [C Integration](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "C Integration")
-* [C++](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/activemq-c-clients.md "ActiveMQ C++ Clients")
-* [C# and .Net Integration](http://activemq.apache.org/nms/)
-* [CMS](http://activemq.apache.org/cms/)
-* [J2EE](Connectivity/Containers/j2ee.md "J2EE")
-* [JBoss Integration](Connectivity/ContainersConnectivity/Containers/Connectivity/Containers/jboss-integration.md "JBoss Integration")
-* [Jetty](http://docs.codehaus.org/display/JETTY/Integrating+with+ActiveMQ)
-* [JNDI Support](Connectivity/Containers/jndi-Community/support.md "JNDI Support")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [REST](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rest.md "REST")
-* [RSS and Atom](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rss-and-atom.md "RSS and Atom")
-* [Spring Support](Connectivity/Containers/spring-Community/support.md "Spring Support")
-* [Stomp](Connectivity/Protocols/stomp.md "Stomp")
-* [Tomcat](Connectivity/Containers/tomcat.md "Tomcat")
-* [Unix Service](/Features/Unix/unix-service.md "Unix Service")
-* [WebLogic Integration](weblogiConnectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "WebLogic Integration")
-* [XMPP](Connectivity/Protocols/xmpp.md "XMPP")
-* [More ...](connectivity.md "Connectivity")
-
-### [Using ActiveMQ 5](using-activemq-5.md "Using ActiveMQ 5")
-
-* [Getting Started](version-5-Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Version 5 Getting Started")
-* [Initial Configuration](version-5-Using ActiveMQ/initial-Community/FAQ/configuration.md "Version 5 Initial Configuration")
-* [Running a Broker](Using ActiveMQ 5/version-5-Using ActiveMQ/run-broker.md "Version 5 Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ 5/configuring-version-5-transports.md "Configuring Version 5 Transports")
-* [Examples](version-5-Using ActiveMQ/examples.md "Version 5 Examples")
-* [Web Samples](Using ActiveMQ 5Using ActiveMQ 5/Using ActiveMQ 5/version-5-Using ActiveMQ/web-samples.md "Version 5 Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](Using ActiveMQ 5/version-5-xml-Community/FAQ/configuration.md "Version 5 XML Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq-5.md "Using ActiveMQ 5")
-
-### [Using ActiveMQ 4](using-activemq.md "Using ActiveMQ")
-
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [Initial Configuration](Using ActiveMQ/initial-Community/FAQ/configuration.md "Initial Configuration")
-* [Running a Broker](Using ActiveMQ/run-broker.md "Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ/configuring-transports.md "Configuring Transports")
-* [Examples](Using ActiveMQ/examples.md "Examples")
-* [Web Samples](Using ActiveMQ/web-samples.md "Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](xml-Community/FAQ/configuration.md "Xml Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq.md "Using ActiveMQ")
-
-### [Tools](tools.md "Tools")
-
-* [Web Console](ToolsTools/Tools/web-console.md "Web Console")
-* [Hermes Jms](ToolsTools/Tools/hermes-Community/FAQ/jms.md "Hermes Jms")
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [JMeter](http://jakarta.apache.org/jmeter)
-
-### [Support](CommunityCommunity/Community/support.md "Support")
-
-* [Issues](http://issues.apache.org/jira/browse/AMQ)
-* [Roadmap](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
-* [Change log](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:changelog-panel)
-
-### Related Projects
-
-* [Apache ServiceMix](http://incubator.apache.org/servicemix/ "Distributed Enterprise Service Bus based on JBI")
-* [Lingo](http://lingo.codehaus.org/ "POJO Remoting using JMS")
-* [Jencks](http://jencks.codehaus.org/ "Message Driven POJOs and pooling for JMS and JDBC")
-* [Stomp](http://stomp.codehaus.org/ "A simple protocol for messaging middleware interop and the easy development of custom clients")
-* [Spring](http://www.springframework.org/)
-* [OpenEJB](http://openejb.apache.org)
-* [Geronimo](http://geronimo.apache.org/)
-
-### [Developers](developers.md "Developers")
-
-* [Source](Developers/source.md "Source")
-* [Building](Developers/building.md "Building")
-* [Developer Guide](DevelopersDevelopers/Developers/developer-guide.md "Developer Guide")
-* [Becoming a committer](Developers/becoming-a-committer.md "Becoming a committer")
-* [Code Overview](code-overview.md "Code Overview")
-* [Wire Protocol](Developers/wire-protocol.md "Wire Protocol")
-* [Release Guide](DevelopersDevelopers/Developers/release-guide.md "Release Guide")
-
-### Tests
-
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [Benchmark Tests](Developers/benchmark-tests.md "Benchmark Tests")
-* [JMeter System Tests](Developers/jmeter-system-tests.md "JMeter System Tests")
-* [JMeter Performance Tests](Developers/jmeter-performance-tests.md "JMeter Performance Tests")
-* [Integration Tests](Developers/integration-tests.md "Integration Tests")
-
-### Project Reports
-
-* [JUnit Reports](DevelopersDevelopers/Developers/junit-reports.md "JUnit Reports")
-* [Source XRef](Developers/source-xref.md "Source XRef")
-* [Test Source XRef](Developers/test-Developers/source-xref.md "Test Source XRef")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/python.md b/src/_documents/classic/Connectivity/Cross Language Clients/python.md
deleted file mode 100644
index 3808574..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/python.md
+++ /dev/null
@@ -1,171 +0,0 @@
-Apache ActiveMQ ™ -- Python
-
-[Connectivity](../../connectivity.md) > [Cross Language Clients](../../Connectivity/cross-language-clients.md) > [Python](../../Connectivity/Cross Language Clients/python.md)
-
-[Download](OverviewOverview/Overview/download.md "Download") | [JavaDocs](http://activemq.apache.org/maven/5.7.0/activemq-core/apidocs/) [More...](Overview/javadocs.md "JavaDocs") | [Source](Developers/source.md "Source") | [Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums") | [Support](CommunityCommunity/Community/support.md "Support")
-
-Python Support
---------------
-
-For Python support we recommend the [Python Stomp Client](http://stomp.github.com/implementations.html)
-
-Alternatively, you can try [pyactivemq](http://code.google.com/p/pyactivemq/), which is a Python wrapper for the ActiveMQ C++ Library. Because the ActiveMQ C++ library supports both Stomp and Openwire, pyactivemq does too.
-
-### [Overview](overview.md "Overview")
-
-* [Index](index.html "Index")
-* [News](Overview/news.md "News")
-* [New Features](/Features/new-features.md "New Features")
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [FAQ](CommunityCommunity/Community/faq.md "FAQ")
-* [Articles](Community/articles.md "Articles")
-* [Books](CommunityCommunity/Community/books.md "Books")
-* [Download](OverviewOverview/Overview/download.md "Download")
-* [License](http://www.apache.org/licenses/)
-
-### Search
-
-
-
-
-### Sub Projects
-
-* [Apollo](http://activemq.apache.org/apollo "ActiveMQ Apollo")
-* [CMS](http://activemq.apache.org/cms/ "The C++ API for Messaging")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [Camel](http://camel.apache.org/ "POJO based Enterprise Integration Patterns with a typesafe Java DSL")
-
-### [Community](community.md "Community")
-
-* [Support](CommunityCommunity/Community/support.md "Support")
-* [Contributing](CommunityCommunity/Community/contributing.md "Contributing")
-* [Discussion Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums")
-* [Mailing Lists](Community/mailing-lists.md "Mailing Lists")
-* [IRC](irc://irc.codehaus.org/activemq)
-* [IRC Log](http://servlet.uwyn.com/drone/log/hausbot/activemq)
-* [Site](site.md "Site")
-* [Sponsorship](http://www.apache.org/foundationCommunity/sponsorship.md)
-* [Projects Using ActiveMQ](CommunityCommunity/Community/projects-using-activemq.md "Projects Using ActiveMQ")
-* [Users](CommunityCommunity/Community/users.md "Users")
-* [Team](CommunityCommunity/Community/team.md "Team")
-* [Thanks](http://www.apache.org/foundationIndexIndex/Index/thanks.md)
-
-### [Features](features.md "Features")
-
-* [Advisory Message](/Features/Message Features/advisory-message.md "Advisory Message")
-* [Clustering](/Features/clustering.md "Clustering")
-* [Cross Language Clients](Connectivity/cross-language-clients.md "Cross Language Clients")
-* [Enterprise Integration Patterns](/Features/enterprise-integration-patterns.md "Enterprise Integration Patterns")
-* [JMX](/Features/jmx.md "JMX")
-* [JMS to JMS Bridge](ConnectivityConnectivity/Connectivity/jms-to-jms-bridge.md "JMS to JMS Bridge")
-* [MasterSlave](/Features/ClusteringFeatures/Clustering/Features/Clustering/masterslave.md "MasterSlave")
-* [Message Groups](/Features/Consumer Features/message-groups.md "Message Groups")
-* [Networks of Brokers](/Features/Clustering/networks-of-brokers.md "Networks of Brokers")
-* [Performance](/Features/performance.md "Performance")
-* [Persistence](/Features/persistence.md "Persistence")
-* [Security](/Features/security.md "Security")
-* [Virtual Destinations](/Features/Destination Features/virtual-destinations.md "Virtual Destinations")
-* [Visualisation](/Features/visualisation.md "Visualisation")
-* [More ...](features.md "Features")
-
-### [Connectivity](connectivity.md "Connectivity")
-
-* [Ajax](Connectivity/ajax.md "Ajax")
-* [AMQP](Connectivity/Protocols/amqp.md "AMQP")
-* [Axis and CXF Support](axis-and-cxf-CommunityCommunity/Community/support.md "Axis and CXF Support")
-* [C Integration](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "C Integration")
-* [C++](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/activemq-c-clients.md "ActiveMQ C++ Clients")
-* [C# and .Net Integration](http://activemq.apache.org/nms/)
-* [CMS](http://activemq.apache.org/cms/)
-* [J2EE](Connectivity/Containers/j2ee.md "J2EE")
-* [JBoss Integration](Connectivity/ContainersConnectivity/Containers/Connectivity/Containers/jboss-integration.md "JBoss Integration")
-* [Jetty](http://docs.codehaus.org/display/JETTY/Integrating+with+ActiveMQ)
-* [JNDI Support](Connectivity/Containers/jndi-Community/support.md "JNDI Support")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [REST](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rest.md "REST")
-* [RSS and Atom](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rss-and-atom.md "RSS and Atom")
-* [Spring Support](Connectivity/Containers/spring-Community/support.md "Spring Support")
-* [Stomp](Connectivity/Protocols/stomp.md "Stomp")
-* [Tomcat](Connectivity/Containers/tomcat.md "Tomcat")
-* [Unix Service](/Features/Unix/unix-service.md "Unix Service")
-* [WebLogic Integration](weblogiConnectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "WebLogic Integration")
-* [XMPP](Connectivity/Protocols/xmpp.md "XMPP")
-* [More ...](connectivity.md "Connectivity")
-
-### [Using ActiveMQ 5](using-activemq-5.md "Using ActiveMQ 5")
-
-* [Getting Started](version-5-Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Version 5 Getting Started")
-* [Initial Configuration](version-5-Using ActiveMQ/initial-Community/FAQ/configuration.md "Version 5 Initial Configuration")
-* [Running a Broker](Using ActiveMQ 5/version-5-Using ActiveMQ/run-broker.md "Version 5 Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ 5/configuring-version-5-transports.md "Configuring Version 5 Transports")
-* [Examples](version-5-Using ActiveMQ/examples.md "Version 5 Examples")
-* [Web Samples](Using ActiveMQ 5Using ActiveMQ 5/Using ActiveMQ 5/version-5-Using ActiveMQ/web-samples.md "Version 5 Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](Using ActiveMQ 5/version-5-xml-Community/FAQ/configuration.md "Version 5 XML Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq-5.md "Using ActiveMQ 5")
-
-### [Using ActiveMQ 4](using-activemq.md "Using ActiveMQ")
-
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [Initial Configuration](Using ActiveMQ/initial-Community/FAQ/configuration.md "Initial Configuration")
-* [Running a Broker](Using ActiveMQ/run-broker.md "Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ/configuring-transports.md "Configuring Transports")
-* [Examples](Using ActiveMQ/examples.md "Examples")
-* [Web Samples](Using ActiveMQ/web-samples.md "Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](xml-Community/FAQ/configuration.md "Xml Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq.md "Using ActiveMQ")
-
-### [Tools](tools.md "Tools")
-
-* [Web Console](ToolsTools/Tools/web-console.md "Web Console")
-* [Hermes Jms](ToolsTools/Tools/hermes-Community/FAQ/jms.md "Hermes Jms")
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [JMeter](http://jakarta.apache.org/jmeter)
-
-### [Support](CommunityCommunity/Community/support.md "Support")
-
-* [Issues](http://issues.apache.org/jira/browse/AMQ)
-* [Roadmap](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
-* [Change log](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:changelog-panel)
-
-### Related Projects
-
-* [Apache ServiceMix](http://incubator.apache.org/servicemix/ "Distributed Enterprise Service Bus based on JBI")
-* [Lingo](http://lingo.codehaus.org/ "POJO Remoting using JMS")
-* [Jencks](http://jencks.codehaus.org/ "Message Driven POJOs and pooling for JMS and JDBC")
-* [Stomp](http://stomp.codehaus.org/ "A simple protocol for messaging middleware interop and the easy development of custom clients")
-* [Spring](http://www.springframework.org/)
-* [OpenEJB](http://openejb.apache.org)
-* [Geronimo](http://geronimo.apache.org/)
-
-### [Developers](developers.md "Developers")
-
-* [Source](Developers/source.md "Source")
-* [Building](Developers/building.md "Building")
-* [Developer Guide](DevelopersDevelopers/Developers/developer-guide.md "Developer Guide")
-* [Becoming a committer](Developers/becoming-a-committer.md "Becoming a committer")
-* [Code Overview](code-overview.md "Code Overview")
-* [Wire Protocol](Developers/wire-protocol.md "Wire Protocol")
-* [Release Guide](DevelopersDevelopers/Developers/release-guide.md "Release Guide")
-
-### Tests
-
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [Benchmark Tests](Developers/benchmark-tests.md "Benchmark Tests")
-* [JMeter System Tests](Developers/jmeter-system-tests.md "JMeter System Tests")
-* [JMeter Performance Tests](Developers/jmeter-performance-tests.md "JMeter Performance Tests")
-* [Integration Tests](Developers/integration-tests.md "Integration Tests")
-
-### Project Reports
-
-* [JUnit Reports](DevelopersDevelopers/Developers/junit-reports.md "JUnit Reports")
-* [Source XRef](Developers/source-xref.md "Source XRef")
-* [Test Source XRef](Developers/test-Developers/source-xref.md "Test Source XRef")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
diff --git a/src/_documents/classic/Connectivity/Cross Language Clients/ruby.md b/src/_documents/classic/Connectivity/Cross Language Clients/ruby.md
deleted file mode 100644
index fd8317c..0000000
--- a/src/_documents/classic/Connectivity/Cross Language Clients/ruby.md
+++ /dev/null
@@ -1,185 +0,0 @@
-Apache ActiveMQ ™ -- Ruby
-
-[Connectivity](../../connectivity.md) > [Cross Language Clients](../../Connectivity/cross-language-clients.md) > [Ruby](../../Connectivity/Cross Language Clients/ruby.md)
-
-[Download](OverviewOverview/Overview/download.md "Download") | [JavaDocs](http://activemq.apache.org/maven/5.7.0/activemq-core/apidocs/) [More...](Overview/javadocs.md "JavaDocs") | [Source](Developers/source.md "Source") | [Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums") | [Support](CommunityCommunity/Community/support.md "Support")
-
-Ruby Support
-------------
-
-For Ruby support we recommend the [Ruby Stomp Client](http://stomp.codehaus.org/Ruby)
-
-### Ruby Stomp
-
-Here's the Ruby client for Stomp, written by Brian McCallister.
-
-Package: [http://rubyforge.org/projects/stomp/](http://rubyforge.org/projects/stomp/)
-Source: [http://svn.codehaus.org/stomp/ruby/trunk/](http://svn.codehaus.org/stomp/ruby/trunk/)
-
-Also package dup as a gem:
-
-gem install stomp
-
-ActiveMessaging
----------------
-
-If you are working with Rails you might want to check out [ActiveMessaging](http://dev.tirsen.com/trac/activemessaging).
-
-### [Overview](overview.md "Overview")
-
-* [Index](index.html "Index")
-* [News](Overview/news.md "News")
-* [New Features](/Features/new-features.md "New Features")
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [FAQ](CommunityCommunity/Community/faq.md "FAQ")
-* [Articles](Community/articles.md "Articles")
-* [Books](CommunityCommunity/Community/books.md "Books")
-* [Download](OverviewOverview/Overview/download.md "Download")
-* [License](http://www.apache.org/licenses/)
-
-### Search
-
-
-
-
-### Sub Projects
-
-* [Apollo](http://activemq.apache.org/apollo "ActiveMQ Apollo")
-* [CMS](http://activemq.apache.org/cms/ "The C++ API for Messaging")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [Camel](http://camel.apache.org/ "POJO based Enterprise Integration Patterns with a typesafe Java DSL")
-
-### [Community](community.md "Community")
-
-* [Support](CommunityCommunity/Community/support.md "Support")
-* [Contributing](CommunityCommunity/Community/contributing.md "Contributing")
-* [Discussion Forums](CommunityCommunity/Community/discussion-forums.md "Discussion Forums")
-* [Mailing Lists](Community/mailing-lists.md "Mailing Lists")
-* [IRC](irc://irc.codehaus.org/activemq)
-* [IRC Log](http://servlet.uwyn.com/drone/log/hausbot/activemq)
-* [Site](site.md "Site")
-* [Sponsorship](http://www.apache.org/foundationCommunity/sponsorship.md)
-* [Projects Using ActiveMQ](CommunityCommunity/Community/projects-using-activemq.md "Projects Using ActiveMQ")
-* [Users](CommunityCommunity/Community/users.md "Users")
-* [Team](CommunityCommunity/Community/team.md "Team")
-* [Thanks](http://www.apache.org/foundationIndexIndex/Index/thanks.md)
-
-### [Features](features.md "Features")
-
-* [Advisory Message](/Features/Message Features/advisory-message.md "Advisory Message")
-* [Clustering](/Features/clustering.md "Clustering")
-* [Cross Language Clients](Connectivity/cross-language-clients.md "Cross Language Clients")
-* [Enterprise Integration Patterns](/Features/enterprise-integration-patterns.md "Enterprise Integration Patterns")
-* [JMX](/Features/jmx.md "JMX")
-* [JMS to JMS Bridge](ConnectivityConnectivity/Connectivity/jms-to-jms-bridge.md "JMS to JMS Bridge")
-* [MasterSlave](/Features/ClusteringFeatures/Clustering/Features/Clustering/masterslave.md "MasterSlave")
-* [Message Groups](/Features/Consumer Features/message-groups.md "Message Groups")
-* [Networks of Brokers](/Features/Clustering/networks-of-brokers.md "Networks of Brokers")
-* [Performance](/Features/performance.md "Performance")
-* [Persistence](/Features/persistence.md "Persistence")
-* [Security](/Features/security.md "Security")
-* [Virtual Destinations](/Features/Destination Features/virtual-destinations.md "Virtual Destinations")
-* [Visualisation](/Features/visualisation.md "Visualisation")
-* [More ...](features.md "Features")
-
-### [Connectivity](connectivity.md "Connectivity")
-
-* [Ajax](Connectivity/ajax.md "Ajax")
-* [AMQP](Connectivity/Protocols/amqp.md "AMQP")
-* [Axis and CXF Support](axis-and-cxf-CommunityCommunity/Community/support.md "Axis and CXF Support")
-* [C Integration](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "C Integration")
-* [C++](Connectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/activemq-c-clients.md "ActiveMQ C++ Clients")
-* [C# and .Net Integration](http://activemq.apache.org/nms/)
-* [CMS](http://activemq.apache.org/cms/)
-* [J2EE](Connectivity/Containers/j2ee.md "J2EE")
-* [JBoss Integration](Connectivity/ContainersConnectivity/Containers/Connectivity/Containers/jboss-integration.md "JBoss Integration")
-* [Jetty](http://docs.codehaus.org/display/JETTY/Integrating+with+ActiveMQ)
-* [JNDI Support](Connectivity/Containers/jndi-Community/support.md "JNDI Support")
-* [NMS](http://activemq.apache.org/nms/ "NMS is the .Net Messaging API")
-* [REST](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rest.md "REST")
-* [RSS and Atom](Connectivity/ProtocolsConnectivity/Protocols/Connectivity/Protocols/rss-and-atom.md "RSS and Atom")
-* [Spring Support](Connectivity/Containers/spring-Community/support.md "Spring Support")
-* [Stomp](Connectivity/Protocols/stomp.md "Stomp")
-* [Tomcat](Connectivity/Containers/tomcat.md "Tomcat")
-* [Unix Service](/Features/Unix/unix-service.md "Unix Service")
-* [WebLogic Integration](weblogiConnectivity/Cross Language ClientsConnectivity/Cross Language Clients/Connectivity/Cross Language Clients/c-integration.md "WebLogic Integration")
-* [XMPP](Connectivity/Protocols/xmpp.md "XMPP")
-* [More ...](connectivity.md "Connectivity")
-
-### [Using ActiveMQ 5](using-activemq-5.md "Using ActiveMQ 5")
-
-* [Getting Started](version-5-Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Version 5 Getting Started")
-* [Initial Configuration](version-5-Using ActiveMQ/initial-Community/FAQ/configuration.md "Version 5 Initial Configuration")
-* [Running a Broker](Using ActiveMQ 5/version-5-Using ActiveMQ/run-broker.md "Version 5 Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ 5/configuring-version-5-transports.md "Configuring Version 5 Transports")
-* [Examples](version-5-Using ActiveMQ/examples.md "Version 5 Examples")
-* [Web Samples](Using ActiveMQ 5Using ActiveMQ 5/Using ActiveMQ 5/version-5-Using ActiveMQ/web-samples.md "Version 5 Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](Using ActiveMQ 5/version-5-xml-Community/FAQ/configuration.md "Version 5 XML Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq-5.md "Using ActiveMQ 5")
-
-### [Using ActiveMQ 4](using-activemq.md "Using ActiveMQ")
-
-* [Getting Started](Using ActiveMQUsing ActiveMQ/Using ActiveMQ/getting-started.md "Getting Started")
-* [Initial Configuration](Using ActiveMQ/initial-Community/FAQ/configuration.md "Initial Configuration")
-* [Running a Broker](Using ActiveMQ/run-broker.md "Run Broker")
-* [Embedded Brokers](Community/FAQ/Using Apache ActiveMQ/how-do-i-embed-a-broker-inside-a-connection.md "How do I embed a Broker inside a Connection")
-* [Command Line Tools](Community/FAQ/Using Apache ActiveMQ/activemq-command-line-tools-reference.md "ActiveMQ Command Line Tools Reference")
-* [Configuring Transports](Using ActiveMQ/configuring-transports.md "Configuring Transports")
-* [Examples](Using ActiveMQ/examples.md "Examples")
-* [Web Samples](Using ActiveMQ/web-samples.md "Web Samples")
-* [Monitoring the Broker](Community/FAQ/Using Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-can-i-monitor-activemq.md "How can I monitor ActiveMQ")
-* [Xml Configuration](xml-Community/FAQ/configuration.md "Xml Configuration")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
-* [More ...](using-activemq.md "Using ActiveMQ")
-
-### [Tools](tools.md "Tools")
-
-* [Web Console](ToolsTools/Tools/web-console.md "Web Console")
-* [Hermes Jms](ToolsTools/Tools/hermes-Community/FAQ/jms.md "Hermes Jms")
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [JMeter](http://jakarta.apache.org/jmeter)
-
-### [Support](CommunityCommunity/Community/support.md "Support")
-
-* [Issues](http://issues.apache.org/jira/browse/AMQ)
-* [Roadmap](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
-* [Change log](http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:changelog-panel)
-
-### Related Projects
-
-* [Apache ServiceMix](http://incubator.apache.org/servicemix/ "Distributed Enterprise Service Bus based on JBI")
-* [Lingo](http://lingo.codehaus.org/ "POJO Remoting using JMS")
-* [Jencks](http://jencks.codehaus.org/ "Message Driven POJOs and pooling for JMS and JDBC")
-* [Stomp](http://stomp.codehaus.org/ "A simple protocol for messaging middleware interop and the easy development of custom clients")
-* [Spring](http://www.springframework.org/)
-* [OpenEJB](http://openejb.apache.org)
-* [Geronimo](http://geronimo.apache.org/)
-
-### [Developers](developers.md "Developers")
-
-* [Source](Developers/source.md "Source")
-* [Building](Developers/building.md "Building")
-* [Developer Guide](DevelopersDevelopers/Developers/developer-guide.md "Developer Guide")
-* [Becoming a committer](Developers/becoming-a-committer.md "Becoming a committer")
-* [Code Overview](code-overview.md "Code Overview")
-* [Wire Protocol](Developers/wire-protocol.md "Wire Protocol")
-* [Release Guide](DevelopersDevelopers/Developers/release-guide.md "Release Guide")
-
-### Tests
-
-* [Maven2 Performance Plugin](/Features/Performance/activemq-performance-module-users-manual.md "ActiveMQ Performance Module Users Manual")
-* [Benchmark Tests](Developers/benchmark-tests.md "Benchmark Tests")
-* [JMeter System Tests](Developers/jmeter-system-tests.md "JMeter System Tests")
-* [JMeter Performance Tests](Developers/jmeter-performance-tests.md "JMeter Performance Tests")
-* [Integration Tests](Developers/integration-tests.md "Integration Tests")
-
-### Project Reports
-
-* [JUnit Reports](DevelopersDevelopers/Developers/junit-reports.md "JUnit Reports")
-* [Source XRef](Developers/source-xref.md "Source XRef")
-* [Test Source XRef](Developers/test-Developers/source-xref.md "Test Source XRef")
-* [Xml Reference](Using ActiveMQ/xml-reference.md "Xml Reference")
diff --git a/src/_documents/classic/Connectivity/Protocols/OpenWire/openwire-version-2-specification.md b/src/_documents/classic/Connectivity/Protocols/OpenWire/openwire-version-2-specification.md
deleted file mode 100644
index 7978b74..0000000
--- a/src/_documents/classic/Connectivity/Protocols/OpenWire/openwire-version-2-specification.md
+++ /dev/null
@@ -1,561 +0,0 @@
-Apache ActiveMQ ™ -- OpenWire Version 2 Specification
-
-[Connectivity](../../../connectivity.md) > [Protocols](../../../Connectivity/protocols.md) > [OpenWire](../../../Connectivity/Protocols/openwire.md) > [OpenWire Version 2 Specification](../../../Connectivity/Protocols/OpenWire/openwire-version-2-specification.md)
-
-
-OpenWire Version 2 is not the latest version.
-
-This article references OpenWire V2 which is no longer the latest version. The formatting and encoding rules in this article are still valid for later OpenWire versions, but later versions define additional fields in the OpenWire commands. The default settings shown in this article may not reflect the current defaults, see [this page](../../../Using ActiveMQ/Configuring Transports/ActiveMQ Connection URIs/configuring-wire-formats.md) for the latest default OpenWire settings.
-
-Overview
---------
-
-OpenWire is used to marshal objects to byte arrays and back. We will refer to the marshaled objects as commands.
-
-A TCP network connection would see multiple commands back to back on the stream. Commands are not delimited in anyway and are variable sized.
-
-\+\-\-\-\-\-\-\-\-\-\+ \+\-\-\-\-\-\-\-\-\-\+ +---------+
-| command | | command | .... | command |
-\+\-\-\-\-\-\-\-\-\-\+ \+\-\-\-\-\-\-\-\-\-\+ +---------+
-
-All data primitive types used in the encoded commands are encoded in big-endian/network byte order.
-
-primitive types and encoding:
- | | | | | |
-\+\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+
-| byte | | | char | | | short | | | int | | | long | | | float | | | double |
-\+\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+
-| 1 octect | | | 2 octects | | | 2 octects | | | 4 octects | | | 8 octects | | | 4 octects | | | 8 octects |
-\+\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+ | \+\-\-\-\-\-\-\-\-\-\-\-\+
- | | | | | |
-
-Wire Format Negotiation
------------------------
-
-OpenWire is an extensible in that it supports adding new encoding options while still being backward compatible with previous versions of the protocol. Every OpenWire protocol session initially starts with all encoding options turned off and at version 1 of command marshalers. An initial WIREFORMAT_INFO command is exchanged between the two nodes so that additional encoding features can be enabled. If both sides request an encoding feature to be enabled then it will be enabled. The comman [...]
-
-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \+\-\-\-\-\-\-\-\-\-\+ \+\-\-\-\-\-\-\-\-\-\+ +---------+
-| WIREFORMAT_INFO command | | command | | command | .... | command |
-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \+\-\-\-\-\-\-\-\-\-\+ \+\-\-\-\-\-\-\-\-\-\+ +---------+
-
-Command Encoding
-----------------
-
-Every command is encoded as follows:
-
-command encoding:
-\[=If SizePrefixDisabled =\]
-\[ option is not enabled. \]
-\[ \+\-\-\-\-\-\-\+ \] +------+-------------------------+
-\[ | size | \] | type | command-specific-fields |
-\[ \+\-\-\-\-\-\-\+ \] +------+-------------------------+
-\[ | int | \] | byte | (size-1) octects |
-\[ \+\-\-\-\-\-\-\+ \] +------+-------------------------+
-\[========================\]
-
-Field
-
-Description
-
-size
-
-Holds how many subsequent bytes are in the the command
-
-type
-
-Command type identifier
-
-command-specific-fields
-
-The data for the command. It is encoding depends on the type used
-
-If a command type does not have any command specific content, then size would be 1.
-
-Prefixing the size on every command is done to aid in non-blocking IO processing so that receiver can easily determine when a whole command has been received and can be processed. But finding out the size of command takes additional buffering on the sender size and is not needed if the receiver is doing blocking IO. If the SizePrefixDisabled option is enabled after the exchange of WIREFORMAT_INFO packets, then every subsequent command will not have the size prefixed.
-
-Command Types
--------------
-
-Type Identifier
-
-Command
-
-Description
-
-1
-
-WIREFORMAT_INFO
-
-2
-
-BROKER_INFO
-
-3
-
-CONNECTION_INFO
-
-4
-
-SESSION_INFO
-
-5
-
-CONSUMER_INFO
-
-6
-
-PRODUCER_INFO
-
-7
-
-TRANSACTION_INFO
-
-8
-
-DESTINATION_INFO
-
-9
-
-REMOVE\_SUBSCRIPTION\_INFO
-
-10
-
-KEEP\_ALIVE\_INFO
-
-11
-
-SHUTDOWN_INFO
-
-12
-
-REMOVE_INFO
-
-14
-
-CONTROL_COMMAND
-
-15
-
-FLUSH_COMMAND
-
-16
-
-CONNECTION_ERROR
-
-17
-
-CONSUMER_CONTROL
-
-18
-
-CONNECTION_CONTROL
-
-21
-
-MESSAGE_DISPATCH
-
-22
-
-MESSAGE_ACK
-
-23
-
-ACTIVEMQ_MESSAGE
-
-24
-
-ACTIVEMQ\_BYTES\_MESSAGE
-
-25
-
-ACTIVEMQ\_MAP\_MESSAGE
-
-26
-
-ACTIVEMQ\_OBJECT\_MESSAGE
-
-27
-
-ACTIVEMQ\_STREAM\_MESSAGE
-
-28
-
-ACTIVEMQ\_TEXT\_MESSAGE
-
-30
-
-RESPONSE
-
-31
-
-EXCEPTION_RESPONSE
-
-32
-
-DATA_RESPONSE
-
-33
-
-DATA\_ARRAY\_RESPONSE
-
-34
-
-INTEGER_RESPONSE
-
-40
-
-DISCOVERY_EVENT
-
-50
-
-JOURNAL_ACK
-
-52
-
-JOURNAL_REMOVE
-
-53
-
-JOURNAL_TRACE
-
-54
-
-JOURNAL_TRANSACTION
-
-55
-
-DURABLE\_SUBSCRIPTION\_INFO
-
-60
-
-PARTIAL_COMMAND
-
-61
-
-PARTIAL\_LAST\_COMMAND
-
-65
-
-REPLAY
-
-70
-
-BYTE_TYPE
-
-71
-
-CHAR_TYPE
-
-72
-
-SHORT_TYPE
-
-73
-
-INTEGER_TYPE
-
-74
-
-LONG_TYPE
-
-75
-
-DOUBLE_TYPE
-
-76
-
-FLOAT_TYPE
-
-77
-
-STRING_TYPE
-
-78
-
-BOOLEAN_TYPE
-
-79
-
-BYTE\_ARRAY\_TYPE
-
-90
-
-MESSAGE\_DISPATCH\_NOTIFICATION
-
-91
-
-NETWORK\_BRIDGE\_FILTER
-
-100
-
-ACTIVEMQ_QUEUE
-
-101
-
-ACTIVEMQ_TOPIC
-
-102
-
-ACTIVEMQ\_TEMP\_QUEUE
-
-103
-
-ACTIVEMQ\_TEMP\_TOPIC
-
-110
-
-MESSAGE_ID
-
-111
-
-ACTIVEMQ\_LOCAL\_TRANSACTION_ID
-
-112
-
-ACTIVEMQ\_XA\_TRANSACTION_ID
-
-120
-
-CONNECTION_ID
-
-121
-
-SESSION_ID
-
-122
-
-CONSUMER_ID
-
-123
-
-PRODUCER_ID
-
-124
-
-BROKER_ID
-
-### Command Field Encoding
-
-All OpenWire commands use the same algorithm when encoding their fields. The algorithm restricts commands to use fields that are of the following type:
-
-* Java primitive types
-* String
-* Byte Arrays
-* N Sized Byte Arrays
-* Throwable
-* Nested OpenWire commands
-* Nested OpenWire command arrays
-* Cached Nested OpenWire commands
-
-Notice that OpenWire commands can nest other OpenWire commands in it's fields. Care must be taken that only acyclic graphs of commands are marshaled.
-
-#### String Type Encoding
-
-Strings fields may be null. If it is null then it encodes to a single "0" byte.
-
-string encoding:
- \[=If not-null is 1===========\]
-\+\-\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \]
-| not-null | \[ | size | encoded-string | \]
-\+\-\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \]
-| byte | \[ | short | size octects | \]
-\+\-\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \]
- \[============================\]
-
-Field
-
-Description
-
-not-null
-
-1 if the string is not null, 0 if the string is null
-
-size
-
-The number of bytes of the UTF-8 Encoded string
-
-encoded-string
-
-The UTF-8 encoded form of the string
-
-### Byte Array Type Encoding
-
-Byte array fields may be null. If it is null then it encodes to a single "0" byte.
-
-byte-array encoding:
- \[=If not-null is 1========\]
-\+\-\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \]
-| not-null | \[ | size | data | \]
-\+\-\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \]
-| byte | \[ | int | size octects | \]
-\+\-\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \]
- \[=========================\]
-
-Field
-
-Description
-
-not-null
-
-1 if the byte array is not null, 0 if it is null
-
-size
-
-The number of bytes in the byte array
-
-data
-
-The data of the byte array
-
-### N Sized Byte Array Type Encoding
-
-Fixed Size Byte array fields may NOT be null and their length must be N length. Used for byte arrays that are always a fixed size.
-
-N-sized-byte-array encoding:
-+-----------+
-| data |
-+-----------+
-| N octects |
-+-----------+
-
-Field
-
-Description
-
-data
-
-The data of the byte array
-
-### Throwable Type Encoding
-
-Throwable fields may be null. If it is null then it encodes to a single "0" byte.
-
-throwable encoding:
- \[=If not-null is 1===========================================================================\]
- \[ \[=If StackTraceEnabled option is enabled.==================\] \]
- \[ \[ \[=Repeated size times======================\] \] \]
-\+\-\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \] \] \]
-| not-null | \[ | exception-name | message | \[ | size | \[ | class | method | file | line-number | \] \] \]
-\+\-\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \] \] \]
-| byte | \[ | string | string | \[ | short | \[ | string | string | string | int | \] \] \]
-\+\-\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \] \] \]
- \[ \[ \[============================================\] \] \]
- \[ \[==========================================================\] \]
- \[============================================================================================\]
-
-Field
-
-Description
-
-not-null
-
-1 if the Throwable not null, 0 if the Throwable is null
-
-exception-name
-
-The class name of the exception
-
-message
-
-The exception message
-
-size
-
-The number of stack frames in the stack trace
-
-class
-
-The name of the class in a stack frame
-
-method
-
-The name of the method in a stack frame
-
-file
-
-The name of the file in a stack frame
-
-line-number
-
-The line number in a stack frame
-
-If the StackTraceEnabled encoding option is enabled after the exchange of WIREFORMAT_INFO packets, then every Throwable filed will have stack trace data appended to it.
-
-### Nested Command Type Encoding
-
-Nested command fields may be null. If it is null then it encodes to a single "0" byte.
-
-nested-object encoding:
- \[=If not-null is 1===================\]
-\+\-\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \]
-| not-null | \[ | type | command-specific-fields | \]
-\+\-\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \]
-| byte | \[ | byte | variable sized | \]
-\+\-\-\-\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \]
- \[====================================\]
-
-Field
-
-Description
-
-not-null
-
-1 if the Throwable not null, 0 if the Throwable is null
-
-type
-
-Command type identifier
-
-command-specific-fields
-
-The data for the command. It is encoding depends on the type used
-
-### Cached Nested Command Type Encoding
-
-Nested Command types can be cached so that subsequent marshaling operations of the same object result in a smaller on the wire size. By default the CacheEnabled option is not enabled and therefore standard nested-object encoding is used.
-
-cached-object-encoding:
-\[=If CacheEnabled option is enabled=====================\]
-\[ \[=If new-value is 1===========\] \]
-\[ \+\-\-\-\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \] \]
-\[ | new-value | key | \[ | command-specific-fields | \] \]
-\[ \+\-\-\-\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \] \]
-\[ | byte | short | \[ | nested-object | \] \]
-\[ \+\-\-\-\-\-\-\-\-\-\-\-\+\-\-\-\-\-\-\-\+ \[ \+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \] \]
-\[ \[=============================\] \]
-\[=====================================================\] \]
-
-\[=If CacheEnabled option is disabled =\]
-\[ \+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \]
-\[ | command-specific-fields | \]
-\[ \+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \]
-\[ | nested-object | \]
-\[ \+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\+ \]
-\[=====================================\]
-
-Field
-
-Description
-
-new-value
-
-1 if the value is not in the cache, 0 if it already is in the cache
-
-key
-
-Key used to identify the value in the cache
-
-command-specific-fields
-
-The data for the command. It is encoding depends on the type used
-
-Loose Encoding
---------------
-
-The default encoding explained so far is called "loose encoding" and is the default encoding used when OpenWire if first initialized. Loose encoding is simple to implement does not add much CPU overhead to the marshaling/unmarshaling process. It is able to marshal an object graph in single pass of the object tree.
-
-Tight Encoding
---------------
-
-Another encoding option is supported by OpenWire which is called TightEncoding. When tight encoding is used, it uses bit streams to marshal all the boolean values that would have taken up a byte in loose encoding to a bit in the bit stream. To build the bit stream 2 passes through the object graph are taken so this is more CPU intensive marshaling process but it produces a smaller on the wire size.
-
diff --git a/src/_documents/classic/Connectivity/Protocols/amqp.md b/src/_documents/classic/Connectivity/Protocols/amqp.md
deleted file mode 100644
index ac2acb2..0000000
--- a/src/_documents/classic/Connectivity/Protocols/amqp.md
+++ /dev/null
@@ -1,353 +0,0 @@
-Apache ActiveMQ ™ -- AMQP
-
-[Connectivity](../../connectivity.md) > [Protocols](../../Connectivity/protocols.md) > [AMQP](../../Connectivity/Protocols/amqp.md)
-
-
-ActiveMQ supports the [AMQP 1.0](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=amqp) protocol which is an OASIS standard.
-
-Availability
-
-Available from ActiveMQ version [5.8](Overview/Download/activemq-580-release.md) onward.
-
-### Enabling the ActiveMQ Broker for AMQP
-
-To enable AMQP protocol support on the broker add the following transport connector configuration referencing the **`amqp`** scheme in its URI:
-
-<transportConnectors>
- <transportConnector name="amqp" uri="amqp://0.0.0.0:5672"/>
-</transportConnectors>
-
-It is enabled in the default ActiveMQ server configuration. For more help see [Run Broker](../../Using ActiveMQ/run-broker.md).
-
-### Security
-
-The AMQP implementation fully supports an [ActiveMQ security](../../Features/security.md) mechanism. This allows the broker to accept plain SASL authentication. Authorization policies are applied to a destination when it's accessed (read/write).
-
-SSL
-
-For additional security AMQP can be configured to run over SSL as described in the following section.
-
-### Enabling AMQP over NIO
-
-For better scalability (and performance) the AMQP protocol should be configured to use NIO, rather than the default of TCP. To use NIO use the transport scheme **`amqp+nio`** instead of **`amqp`**.
-
-Example:
-
-<transportConnector name="amqp+nio" uri="amqp+nio://localhost:5672"/>
-
-This transport uses the [NIO transport](http://activemq.apache.orgUsing ActiveMQ/configuring-transports.md#ConfiguringTransports-TheNIOTransport) underneath and will generally use much less threads than the standard connector. This connector can help if you want to use [large number of queues](http://activemq.apache.orgCommunity/FAQ/Configuration/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.md)
-
-### Enabling AMQP over SSL
-
-It's easy to configure ActiveMQ to use AMQP over a SSL connection. To use SSL use the transport scheme **`amqp+ssl`** instead of **`amqp`**.
-
-Example:
-
-<transportConnector name="amqp+ssl" uri="amqp+ssl://localhost:5671"/>
-
-For more details on using SSL with ActiveMQ, see the following article ([How do I use SSL](http://activemq.apache.orgCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache ActiveMQ/how-do-i-use-ssl.md)).
-
-### Working with Destinations with AMQP
-
-You should prefix destination address with **`queue://`** to use queue based destinations or **`topic://`** to use topic based destinations. The destination type defaults to queue when the destination prefix is omitted.
-
-### Prefetch Size and Credit
-
-When AMQP receiver connects to the broker it's mapped to the JMS consumer. This JMS consumer has to have appropriate [prefetch size](../../FAQ/Using Apache ActiveMQ/what-is-the-prefetch-limit-for.md) set. The broker will honor the credit set by the client or use the default value of **`1000`** if client doesn't set it.
-
-Example: tuning the default **`prefetch`** size:
-
-<transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600&transport.prefetch=10"/>
-
-In this case, client preference will be ignored and the configured value will be used.
-
-You can also tune broker-side **`amqp`** receiver link that handles incoming messages. It will use credit of **`1000`** messages by default, but you can override this by using **`producerCredit`** property, like
-
-<transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600&transport.producerCredit=10000"/>
-
-### Mapping to JMS
-
-There are three basic conversion strategies that can be used with AMQP and inter-operating with the JMS API.
-
-Strategy
-
-Description
-
-`native`
-
-(**Default**) Wraps the bytes of the AMQP message into a JMS **`BytesMessage`** and maps the headers of the AMQP message to headers on the JMS message.
-
-`raw`
-
-Wraps the bytes of the AMQP message into a JMS **`BytesMessage`**.
-
-`jms`
-
-Maps headers of the AMQP message to JMS message headers and the body of the AMQP message to the JMS body.
... 150054 lines suppressed ...