Apollo 1.0 Beta 4 Released
Posted by Hiram Chirino on Tuesday, June 29, 2010
The Apache ActiveMQ Project is pleased to announce the
availability of Apollo 1.0 Beta 4. ActiveMQ Apollo is a faster, more reliable, easier
to maintain messaging broker built from the foundations of the original ActiveMQ. It is
focused on being the fastest most reliable STOMP 1.1 and 1.0 server available.
Apollo Features:
Noteworthy changes since the last beta include:
- APLO-17 - Support message expiration
- APLO-39 - Apply configuration updates to a broker without needing a restart
- APLO-40 - Web interface should support editing all the apollo configuration files (log4j, jaas, etc.)
- APLO-41 - Expose JVM Status/Metrics via REST API
- APLO-43 - Create an XSD to validate the apollo.xml configuration file.
- APLO-45 - Support auto deleting idle queues and topics
- APLO-47 - Add connectioncounter, consumercounter, and producer_counter metrics to the management interface
- APLO-50 - Support pre-creating durable subscriptions via the broker config file
- APLO-55 - Add an option to enable strict validation of the configuration XML
- APLO-57 - Track desired service state so you can stop a service which is still starting
- APLO-60 - Support regular expressions in destination wildcards.
- APLO-42 - File based JAAS login modules should cache file contents until changed.
- APLO-44 - Eagerly create destinations which are explicitly defined in the server configuration file.
- APLO-46 - Include current/total page info when the REST interface returns a paged result set
Further information:
Feedback is always welcome!
Apollo 1.0 Beta 5 Released
Posted by Hiram Chirino on Tuesday, June 29, 2010
The Apache ActiveMQ Project is pleased to announce the
availability of Apollo 1.0 Beta 5. ActiveMQ Apollo is a faster, more reliable, easier
to maintain messaging broker built from the foundations of the original ActiveMQ. It is
focused on being the fastest most reliable STOMP 1.1 and 1.0 server available.
Apollo Features:
Noteworthy changes since the last beta include:
- APLO-67 - Support an
auto-delete:true
header on the STOMP subscribe frame to auto delete queues when the subscription ends
- APLO-70 - Add per-destination queue quota
- APLO-34 - Allow a STOMP subscription to control message flow using a credit window
- APLO-68 - Add support for TCP-level keepalive
- APLO-74 - Support setting the timestamp header on received messages
- APLO-75 - Support setting the redelivered header on redelivered messages
- APLO-56 - Change to a terser configuration scheme for ACL definitions
- APLO-81 - Include message counters on the producer/consumer links on the destination stats in the REST API.
- APLO-80 - Separate message statistics for durable subs from queues.
- APLO-82 - Add a new /dest-metrics REST route which collects the metrics for queues, topics and dsubs.
- APLO-83 - Apollo REST API should support cookie/session based authentication
- APLO-71 - Apollo plugins should be easy to configure
- APLO-77 - Provide connection aggregation in the REST API
- APLO-78 - Provide message statistics (for topics) in the REST API
Migration Notes:
The way access control is configured substantially changed sine the Beta 4 release. It's
recommend you generate a new apollo configuration if upgrade to this release.
Further information:
Feedback is always welcome!
Apollo 1.0 Beta 3 Released
Posted by Hiram Chirino on Tuesday, June 1, 2010
The Apache ActiveMQ Project is pleased to announce the
availability of Apollo 1.0 Beta 3. ActiveMQ Apollo is a faster, more reliable, easier
to maintain messaging broker built from the foundations of the original ActiveMQ. It is
focused on being the fastest most reliable STOMP 1.1 and 1.0 server available.
Apollo Features:
Noteworthy changes since the last beta include:
- APLO-6 - Alternative topic separators should be supported in Apollo, as in ActiveMQ
- APLO-11 - Support HTTPS access to the REST management API
- APLO-12 - Support finer grained security in the REST based admin API
- APLO-21 - Support a protocol interceptor plugins to allow policy enforcement
- APLO-22 - Support generic service plugins to on a broker so that admins can start/stop additional opaque services along /w the broker.
- APLO-26 - Support directly addressing durable subscription queues
- APLO-27 - Support finer grained selection of record and fields in the REST interface
- APLO-29 - Add a new broker security roll to control access to viewing the broker configuration.
- APLO-32 - Support Connector start/stop actions in the management interface
- APLO-33 - Support deleting queues from the management interface.
- APLO-35- - Support installing as a background windows service
- APLO-37- Update BDB store to use a single BTree for all queue entries and use variable encoding for the keys
Migration Notes:
It is recommended to you generate a new broker instance for this release. The 1.0 beta3 release uses a slightly
different default configuration (to create a https port for administration). If your were using the BDB store,
this new release uses a totally different storage layout so you should export the data from the previous
versions, wipe the data directory and then import it into the broker on the new release.
Further information:
Feedback is always welcome!
Apollo 1.0 Beta 2 Released
Posted by Hiram Chirino on Monday, May 3, 2010
The Apache ActiveMQ Project is pleased to announce the
availability of Apollo 1.0 Beta 2. ActiveMQ Apollo is a faster, more reliable, easier
to maintain messaging broker built from the foundations of the original ActiveMQ. It is
focused on being the fastest most reliable STOMP 1.1 and 1.0 server available.
This Beta release features:
Further information:
Feedback is always welcome!
Change since the last beta include:
- Enable the jvmassert scala compiler plugin so that asserts are disabled by default at runtime unless enabled with the JVM -ea flag.
- Reduce verbosity of the internal debug message.
- Used the latest release of the stomp JMS client.
- Don't assume all connectors will be AcceptingConnectors.
- If the user sets the
JVM_FLAGS
or JMX_OPTS
then, don't use our defaults.
- Source the
etc/apollo.profile
if it exists.
- Protect against NPE.
- Configure the receive buffer size on the server socket so that it get properly set on the sockets that get accepted.
- Doco: Adding more config details about transport protocols
- Doco: Better looking downloads page.
- Doco: Have the links look different than the headers.
- Rename the multi protocol to any since that reads better from the point of view of
config: protocol="any"
- Simpler tcp transport option setup.
- Make the stomp max allowed headers sizes and friends configurable.
- Only trim headers in STOMP 1.0
- Making more socket options configurable on the tcp transport.
- Delay shutting down on disconnect to allow the receipt to be sent back to the client.
- Implemented an
apollo-broker-service
script which can be used to start/stop and manage a broker that is run in the background.
- Fixes AMQ-3295 : better logging messages.
- Simplify setting up the session refiller.
- display the base dir.
- Simpler getting started guide.
- Report the apollo install location when starting up the broker.
- Better dispatch execution assertion checking to catch usage errors.
- Add a linked assertion check to provide a friendlier usage error message.
- Fixes /AMQ-3267 - Make it able run Apollo without setting env variables
- Fixes AMQ-3265 : Added a
Waiting for messages...
console message to all the listener examples.
- Fixes AMQ-3264 : Add an
bin/apollo --help
- Add a shutdown hook which stops the broker.
- Adding a toString method to queues of easier debugging.
- Display more DBD store stats: # of pending stores.
Apollo 1.0 Beta 1 Released
Posted by Hiram Chirino on Tuesday, April 6, 2010
The Apache ActiveMQ Project is pleased to announce the
availability of Apollo 1.0 Beta 1. ActiveMQ Apollo is a faster, more reliable, easier
to maintain messaging broker built from the foundations of the original ActiveMQ. It is
focused on being the fastest most reliable STOMP 1.1 server available.
This Beta release features:
Further information:
Feedback is always welcome!