Md cleanup

2007-april.md

@@ -0,0 +1,12 @@
+Apache ActiveMQ ™ -- 2007 April 
+
+[Developers](developers.html) > [Board Reports](board-reports.html) > [2007 April](2007-april.html)
+
+
+April 2007 Report
+-----------------
+
+*   [ActiveMQ 4.1.1 Released](#)
+*   voted in a new committer, John Heitmann
+*   the developer and user lists continue to be very active
+

40-rc-1-guide.md

@@ -0,0 +1,47 @@
+Apache ActiveMQ ™ -- 4.0 RC 1 Guide 
+
+[Developers](developers.html) > [Developer Guide](developer-guide.html) > [Release Plans](release-plans.html) > [4.0 RC 1 Guide](40-rc-1-guide.html)
+
+
+ActiveMQ 4.0-RC-1 Release Guide
+===============================
+
+General Release Information
+---------------------------
+
+*   [Current RoadMap](http://jira.activemq.org/jira/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
+*   [Release Guide](release-guide.html)
+*   [Signing Releases](http://wiki.apache.org/incubator/SigningReleases)
+*   [Apache Mirror Guidelines](http://apache.org/dev/mirrors.html)
+
+Release Manager
+---------------
+
+**Hiram Chirino**
+
+Special issues
+--------------
+
+We are still in the Incubator so need to ensure that all the proper disclaimers are in place and that the artifacts are all properly named **incubator-activemq**.
+
+Open Issues Holding up the Release
+----------------------------------
+
+JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
+
+JIRA Issues Macro: Macro params are invalid
+
+Issues Resolved for this Release
+--------------------------------
+
+JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
+
+JIRA Issues Macro: Macro params are invalid
+
+How to Help
+-----------
+
+Everyone in the ActiveMQ community can help with releases; users, developers, commmiters are all encouraged to test out a release and post any comments to the [activemq-dev@ mailing list](mailing-lists.html) or create a [JIRA](https://issues.apache.org/activemq/browse/AMQ) issue.
+
+ActiveMQ is available in both source and binary distributions. See [Getting Started](getting-started.html).
+

58-migration-guide.md

@@ -0,0 +1,54 @@
+Apache ActiveMQ ™ -- 5.8 Migration Guide 
+
+[Overview](overview.html) > [Download](download.html) > [ActiveMQ 5.8.0 Release](activemq-580-release.html) > [5.8 Migration Guide](58-migration-guide.html)
+
+
+There are some changes in 5.8 that may require some code change
+
+1.  New modules may effect your maven pom dependencies  
+    `activemq-core` has been replaced with `activemq-client` and `activemq-broker`. The various message stores have their own activemq-xx-store module. The uber module `activemq-all` remains.
+2.  Changed JMX Mbean ObjectNames will effect scripts or tools that directly reference Mbean names  
+    All mbeans now share the type=Broker attribute, which gives them containment. In this way, consumers hang off of destinations, which hang off the broker.  
+    The different Mbean types are identified by the presence of specific identifiers in their ObjectNames. The mapping from old to new ObjectName is as follows:
+
+    Type
+
+    Old Name
+
+    New Name
+
+    Broker
+
+    Type=Broker
+
+    type=Broker
+
+    Destination
+
+    Type=Queue|Topic,Destination=<destination identifier>
+
+    type=Broker,destinationType=Queue|Topic,destinationName=<destination identifier>
+
+    Connector
+
+    Type=Connector
+
+    type=Broker,connector=clientConnectors
+
+    NetworkConnector
+
+    Type=NetworkConnector
+
+    type=Broker,connector=networkConnectors
+
+    Connection
+
+    Type=Connection
+
+    type=Broker,connector=*,connectionViewType=remoteAddress|clientId
+
+3.  OSGi integration has changed. The full details are at [OSGi Integration](osgi-integration.html). In summary:
+    1.  There is a single uber OSGI bundle
+    2.  The broker and webconsole are now configured via config admin pid files through an OSGi managed service factory.
+4.  The ActiveMQ binary file `bin/run.jar` has been renamed to `bin/activemq.jar`.
+

59-migration-guide.md

@@ -0,0 +1,11 @@
+Apache ActiveMQ ™ -- 5.9 Migration Guide 
+
+[Overview](overview.html) > [Download](download.html) > [ActiveMQ 5.9.0 Release](activemq-590-release.html) > [5.9 Migration Guide](59-migration-guide.html)
+
+
+There are some changes in 5.9 that may require user intervention
+
+1.  Schema change to JDBC Persistence Adapter. XID column type change.
+
+*   If you use XA transactions you need to ensure there are no XA transactions pending completion before you upgrade. Some mode detail in [AMQ-4628](https://issues.apache.org/jira/browse/AMQ-4628)
+

HEADER.md

@@ -0,0 +1,6 @@
+Apache ActiveMQ XML Schemas
+===========================
+
+This site contains all the various versions of the XML Schema Documents for the [Apache ActiveMQ project](http://activemq.apache.org/)
+
+For details of how to use the XML Schema files, particularly with Spring, please see the [XML Reference](http://activemq.apache.org/xml-reference.html)

ReadMe.md

@@ -0,0 +1,6 @@
+Apache ActiveMQ XML Schemas
+===========================
+
+This site contains all the various versions of the XML Schema Documents for the [Apache ActiveMQ project](http://activemq.apache.org/)
+
+For details of how to use the XML Schema files, particularly with Spring, please see the [XML Reference](http://activemq.apache.org/xml-reference.html)

activation-spec-properties.md

@@ -0,0 +1,199 @@
+Apache ActiveMQ ™ -- Activation Spec Properties 
+
+[Connectivity](connectivity.html) > [Containers](containers.html) > [Resource Adapter](resource-adapter.html) > [Activation Spec Properties](activation-spec-properties.html)
+
+
+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](selectors.html) 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 the MessageListener and rollback if an exception is thrown.
+
+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](what-is-the-prefetch-limit-for.html) will end up [starving other consumers](i-do-not-receive-messages-in-my-second-consumer.html).
+
+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**
+

active-groups.md

@@ -0,0 +1,23 @@
+Apache ActiveMQ ™ -- Active Groups 
+
+[Features](features.html) > [Active Groups](active-groups.html)
+
+
+Active Groups is a dynamic collaboration framework so simplify message passing and shared state between members of the group. It is available in ActiveMQ 6.0
+
+Active Groups includes the following:
+
+*   Dynamic membership information
+*   broadcast messaging
+*   point-to-point
+*   in boxes
+*   Distributed state (Map)
+*   Map change listeners
+*   write locks
+*   lock expiration
+*   optional state and lock removal when a member leaves
+*   automatic state and lock replication and failover
+*   configurable heartbeats
+
+Active Groups is peer based collaboration only - though the underlying transport is JMS (which can be peer based too). Although any JMS provider can be used, ActiveGroups can use the membership information available through ActiveMQ to supplement its heart beat infrastructure.
+

active-groups.md:qq

@@ -0,0 +1,23 @@
+Apache ActiveMQ ™ -- Active Groups
+
+[Features](features.html) > [Active Groups](active-groups.html)
+
+
+Active Groups is a dynamic collaboration framework so simplify message passing and shared state between members of the group. It is available in ActiveMQ 6.0
+
+Active Groups includes the following:
+
+*   Dynamic membership information
+*   broadcast messaging
+*   point-to-point
+*   in boxes
+*   Distributed state (Map)
+*   Map change listeners
+*   write locks
+*   lock expiration
+*   optional state and lock removal when a member leaves
+*   automatic state and lock replication and failover
+*   configurable heartbeats
+
+Active Groups is peer based collaboration only - though the underlying transport is JMS (which can be peer based too). Although any JMS provider can be used, ActiveGroups can use the membership information available through ActiveMQ to supplement its heart beat infrastructure.
+