Tag Archives: ActiveMQ5.5

Release Notes – ActiveMQ – Version 5.5.0 – HTML format

Configure Release Notes

Bug

  • [AMQ-1035] – Problem with STOMP C++ Client connecting with a AMQ Broker having Authorization and Authentication Plugins installed
  • [AMQ-1604] – Please make the following configuration changes so releases into production are simpler
  • [AMQ-1780] – ActiveMQ broker does not automatically reconnect if the connection to the database is lost
  • [AMQ-1997] – Memory leak in broker – Temporary Queue related (relating to bug AMQ-1790)
  • [AMQ-2138] – Memory Leak in ActiveMQConnection
  • [AMQ-2171] – Browse queue hangs with prefetch = 0
  • [AMQ-2213] – Equals method return wrong result for TopicSession / QueueSession
  • [AMQ-2218] – Message delivery to consumer eventually pauses if consumer publishes to the same queue it receives from
  • [AMQ-2223] – Documentation References Advisory Messages which are not valid in xsd
  • [AMQ-2256] – Unnecessary TcpTransportFactory NumberFormatException and warning
  • [AMQ-2336] – Redeliveried messages stops consumers from going on consuming the rest of messages in the queue
  • [AMQ-2402] – SystemPropertiesConfiguration swaps JMX user / password
  • [AMQ-2496] – journaledJDBC not creating ACTIVEMQ_MSGS with MS SQL 2008
  • [AMQ-2633] – Missing documentation: http://activemq.apache.org/producer-flow-control.html
  • [AMQ-2662] – ActiveMQEndpointWorker.stop() sometimes is needing many minutes to shutdown
  • [AMQ-2673] – Producer started before consumer leads to a “javax.jms.JMSException: Unmatched acknowledege” (repro available)
  • [AMQ-2683] – Producer Flow Control Does Not Seem to Work with Topics
  • [AMQ-2718] – Copyright banner on page footer of ActiveMQ Console is outdated
  • [AMQ-2736] – KahaDB doesn’t clean up old files
  • [AMQ-2758] – rollback does not work on topic
  • [AMQ-2798] – Occaional hangs on ensureConnectionInfoSent
  • [AMQ-2852] – Memory leak when undeploying webapp with ActiveMQ client
  • [AMQ-2929] – Compressed text message received by consumer uncompressed
  • [AMQ-2944] – Failover transport always re-connects to the first configured transport instead of the original transport speficied in the connection url
  • [AMQ-2954] – NPE in JobSchedulerStore after restarts
  • [AMQ-2955] – Message getting stuck on queue, leading to KahaDB log files not being deleted and disk running out of space
  • [AMQ-2963] – JMSBridgeConnectors does not work with IBM MQ and ActiveMQ 5.4.0
  • [AMQ-2978] – FailoverTransport sometimes reconnects on Connection.close()
  • [AMQ-2981] – Connecting to broker using discovery protocol fails
  • [AMQ-3000] – Multiple Cron Scheduled Messages don’t fire every minute as configured
  • [AMQ-3006] – STOMP connector assigns wrong default priority to incoming messages
  • [AMQ-3015] – Javascript client does not establish session properly.
  • [AMQ-3026] – Statistics plugin sample hanging when switching to http transport protocol
  • [AMQ-3033] – BrokerService leaks threads when scheduler or jmx are enabled
  • [AMQ-3036] – Scheduled message CRON strings not parsed correctly
  • [AMQ-3038] – Possible Memory-Leak as ActiveMQTempDestinations don’t get deleted when ActiveMQConnection.close() is called
  • [AMQ-3040] – ConnectionState.getTempDesinations() should be renamed to ConnectionState.getTempDestinations()
  • [AMQ-3041] – TemporyQueue will never get unregisterd from JMX which leads to a memory leak
  • [AMQ-3056] – Exception when Redelivery ack is processed by topic subscription
  • [AMQ-3062] – “Deflater has been closed” exception when jms.useCompression=true and using ActiveMQBytesMessage
  • [AMQ-3067] – ActiveMQBlobMessage.copy(..) does not copy the name attribute
  • [AMQ-3068] – Error creating tables on Oracle jdbc store
  • [AMQ-3071] – ConcurrentModificationException thrown in PriorityNetworkDispatchPolicy
  • [AMQ-3075] – Auto-create database fails with PostgreSQL (Error in SQL: ‘drop primary key’)
  • [AMQ-3076] – spurious KahaDB warnings
  • [AMQ-3077] – ArraysIndexOutOfBoundsException : -32768 in “BrokerService[xxx] Task” thread
  • [AMQ-3081] – Durable subscriptions are not removed from mbean
  • [AMQ-3084] – Typo “DispachedCounter” in response when running activemq-admin
  • [AMQ-3085] – IndexOutOfBoundsException on FailoverTransport.updateURIs after: already known: java.net.UnknownHostException
  • [AMQ-3088] – ActiveMQ Web Console “Scheduled” Tab Invocation Fails and returns an unclear message.
  • [AMQ-3092] – Deleting a Queue from the console results in lost messages
  • [AMQ-3093] – Client should provide handling of JMSPriority messages outside of range 0-9.
  • [AMQ-3094] – ajax client does not receive all messages
  • [AMQ-3095] – Broker policyEntry DurableTopicPrefetch is ignored by default because of connection.optimizedMessageDispatch
  • [AMQ-3115] – reportInterval property ignored by DiscardingDLQBrokerPlugin
  • [AMQ-3119] – Proxy connector stop sending messages after failover
  • [AMQ-3120] – KahaDB error: “Could not locate data file”
  • [AMQ-3122] – Recovery after out of disk space (when space freed up) needs manual intervention
  • [AMQ-3124] – Failover transport client gets corrupted connectedBrokers data
  • [AMQ-3125] – updateClusterFilter/ClientsOnRemove broken when running JMX broker
  • [AMQ-3129] – Can only have one duplex networkConnection per transportConnection
  • [AMQ-3130] – ActiveMQ’s Activator not discovering other bundles with extensions.
  • [AMQ-3140] – Lost messages when scheduling messages concurrently
  • [AMQ-3141] – Messages may be lost when schedule them with a short delay
  • [AMQ-3142] – Prepare the upgrade to Karaf 2.2
  • [AMQ-3143] – JMX attribute change doesn’t affect store usage
  • [AMQ-3149] – concurrentStoreAndDispatchQueues when cache disabled can lead to skipped message dispatch, leaving message pending for some time
  • [AMQ-3153] – An expired message that is consumed and resent with an updated expiration never expires again.
  • [AMQ-3160] – ConcurrentModificationException in ActiveMQ Journal Checkpoint Worker
  • [AMQ-3161] – Race condition in ActiveMQ Journal Checkpoint worker thread cleanup leads to multiple running instances
  • [AMQ-3162] – ActiveMQ checkpoint worker makes unnecessary repeated calls to Journal.getFileMap(), leading to excessive memory usage
  • [AMQ-3165] – ActiveMQ 5.4.2 Admin – Accessing Scheduled.jsp giving an Exception in log file
  • [AMQ-3167] – possible skipped Queue messages in memory limited configuration with fast consumers
  • [AMQ-3176] – Potential deadlock in duplex network connector recreation, resulting in dangling connections
  • [AMQ-3180] – JMX Browse of BytesMessage fails with javax.management.openmbean.OpenDataException: Argument’s element itemValues[8]=”[B@de15a0″ is not a valid value for this item
  • [AMQ-3181] – ActiveMQConnectionFactory fails in an Applet enviroment
  • [AMQ-3182] – JAAS PropertiesLoginModule does not maintain internal validity state, so will commit in error after an invalid login attempt
  • [AMQ-3185] – Closing a VMTransport can cause all other VMTransports to be prematurely closed
  • [AMQ-3187] – IllegalMonitorStateException in default topic consumer of maven-activemq-perf-plugin
  • [AMQ-3190] – Durable Subscription – missing messages when selector matching sub resumes after broker restart
  • [AMQ-3193] – Consumers won’t get msgs after JMX operation removeMatchingMessages() was called on a queue.
  • [AMQ-3199] – CRON next scheduled time incorrectly calculated
  • [AMQ-3200] – Scheduled CRON jobs execute twice
  • [AMQ-3202] – Sending an Empty MapMessage over HttpTransport fails with exception
  • [AMQ-3206] – Unsubscribed durable sub can leave dangling message reference in kahaDB, visible after a restart
  • [AMQ-3209] – URISupport.createURIWithQuery() fails on some composite uris.
  • [AMQ-3211] – JMSXUserId Can be spoofed by client
  • [AMQ-3220] – Wildcards do not work with included destinations for network connectors.
  • [AMQ-3222] – Failover and SimpleDiscovery – query parameters getting dropped
  • [AMQ-3238] – Topic-Messages not redelivered to durable subscription after rollback and reconnect

Improvement

  • [AMQ-2492] – Microsoft SQL Server JDBC Driver 2.0 not recognized
  • [AMQ-2968] – Add Apache commons daemon (jsvc/procrun) start/stop support.
  • [AMQ-3045] – Add property maximumRedeliveryDelay in org.apache.activemq.RedeliveryPolicy
  • [AMQ-3078] – Copyright message is out of date in admin console
  • [AMQ-3105] – Require JDK 6
  • [AMQ-3134] – Add support of MS SQL JDBC driver (version 3.0)
  • [AMQ-3138] – The Camel ActiveMQComponent should default create ActiveMQConnectionFactory with the provided broker url
  • [AMQ-3139] – Remove queue and topic endpoints in Camel when they are removed in CamelEndpointLoader
  • [AMQ-3145] – cacheEnabled attribute should be exposed on the queueview via jmx
  • [AMQ-3146] – Add original destination to Stomp messages received from DLQ
  • [AMQ-3148] – LoggingBrokerPlugin addConnection(..) log output is meaningless
  • [AMQ-3150] – Please Update log4j to latest version (1.2.16)
  • [AMQ-3159] – Log file offset in addition to file location in checkpointUpdate()
  • [AMQ-3174] – ConsumerTool (in examples) should show how to do batch acknowledgement using either transacted session or CLIENT_ACKNOWLEDGE
  • [AMQ-3175] – Allow setting soTimeout for Http/Https transports
  • [AMQ-3178] – 5.3.x clients to 5.4 brokers always get updated cluster information in the broker info, this should be configurable
  • [AMQ-3184] – Upgrade to Camel 2.6.0
  • [AMQ-3188] – Full table scan for durable subs in jdbc store when priority enabled; very slow with large message backlog
  • [AMQ-3191] – Add setTrustStore() and setKeyStore() methods to ActiveMQSslConnectionFactory class
  • [AMQ-3192] – Add setTrustStore() and setKeyStore() methods to ActiveMQSslConnectionFactory class
  • [AMQ-3195] – NetworkConnector initialization should be backed by an executor
  • [AMQ-3196] – Speed up initial message delivery for offline durable sub with keepDurableSubsActive=true and JDBC store
  • [AMQ-3197] – Virtual destinations and wildcards
  • [AMQ-3198] – Allow JAAS GuestLoginModule to fail if users specify a password
  • [AMQ-3205] – Update ActivationSpec
  • [AMQ-3207] – Various improvements to features.xml possible with karaf-2.2
  • [AMQ-3218] – Mutlitple Exclusive Consumers: It is currently not possible to always ensure that a new exclusive consumer replaces any existing one
  • [AMQ-3231] – Stomp Frame should mask passcode header in toString output, so it does not pollute the log
  • [AMQ-3237] – FileLock.tryLock() doesn’t work well in all environments
  • [AMQ-3241] – “Unkown” is an incorrect spelling in ActiveMQMessageProducerSupport.java
  • [AMQ-3244] – Enable PropertiesLoginModule JAAS module to optionally cache values in memory

New Feature

  • [AMQ-3003] – Allow the option of a DLQ per durable subscription DeadLetterStrategy
  • [AMQ-3010] – ActiveMQInputStream should allow to specify a timeout like MessageConsumer.receive() does
  • [AMQ-3107] – Fire advisory when network bridge is starter/stopped
  • [AMQ-3108] – Show network bridges in web console
  • [AMQ-3109] – Show bridges created by duplex connectors in JMX
  • [AMQ-3177] – Switch to use slf4j as logger (instad of commons logging)
  • [AMQ-3183] – Set JMSXUserID value based on authenticated principal
  • [AMQ-3186] – Allow producer and consumer throttling in maven-activemq-perf-plugin
  • [AMQ-3204] – Support non-standard destination path separators
  • [AMQ-3219] – Enable MDC logging
  • [AMQ-3236] – In the case of DLQ processing due to an exception from onMessage, provide the exception string as a message property

ActiveMQ 5.5.0 released

Apache ActiveMQ is the most popular and powerful open source messaging and Integration Patterns provider.

Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License

Grab yourself a Download, try our Getting Started Guide, surf our FAQ or start Contributing and join us on our Discussion Forums.

Features

  • Supports a variety of Cross Language Clients and Protocols from Java, C, C++, C#, Ruby, Perl, Python, PHP
    • OpenWire for high performance clients in Java, C, C++, C#
    • Stomp support so that clients can be written easily in C, Ruby, Perl, Python, PHP, ActionScript/Flash, Smalltalk to talk to ActiveMQ as well as any other popular Message Broker
  • full support for the Enterprise Integration Patterns both in the JMS client and the Message Broker
  • Supports many advanced features such as Message Groups, Virtual Destinations, Wildcards and Composite Destinations
  • Fully supports JMS 1.1 and J2EE 1.4 with support for transient, persistent, transactional and XA messaging
  • Spring Support so that ActiveMQ can be easily embedded into Spring applications and configured using Spring’s XML configuration mechanism
  • Tested inside popular J2EE servers such as Geronimo, JBoss 4, GlassFish and WebLogic
    • Includes JCA 1.5 resource adaptors for inbound & outbound messaging so that ActiveMQ should auto-deploy in any J2EE 1.4 compliant server
  • Supports pluggable transport protocols such as in-VM, TCP, SSL, NIO, UDP, multicast, JGroups and JXTA transports
  • Supports very fast persistence using JDBC along with a high performance journal
  • Designed for high performance clustering, client-server, peer based communication
  • REST API to provide technology agnostic and language neutral web based API to messaging
  • Ajax to support web streaming support to web browsers using pure DHTML, allowing web browsers to be part of the messaging fabric
  • CXF and Axis Support so that ActiveMQ can be easily dropped into either of these web service stacks to provide reliable messaging
  • Can be used as an in memory JMS provider, ideal for unit testing JMS