Release Notes - HornetQ - Version 2.2.0.GA - HTML format

Feature Request

  • [HORNETQ-393] - add timeout code around JNDI lookup in JMSBridgeImpl to deal with network outages
  • [HORNETQ-412] - HornetQConnection getClientId/setClientId problems in conjunction with WebLogic
  • [HORNETQ-416] - Provide additional management attributes and methods to manage JMS resources
  • [HORNETQ-422] - Expose durable option on JMSServerControl for createQueue
  • [HORNETQ-428] - Add JDK 1.5 support on client libraries
  • [HORNETQ-445] - Version compatibility matrix
  • [HORNETQ-498] - Paging Improvements
  • [HORNETQ-510] - Unable to call setClientId after getClientId
  • [HORNETQ-515] - Differentiate XA and non XA class hierarchies on JMS
  • [HORNETQ-528] - Add JMSExpiration as valid JMS selector identifier
  • [HORNETQ-531] - Enable HornetQ for a cloud deployment
  • [HORNETQ-560] - Change Stomp default message priority to 4 instead of 0
  • [HORNETQ-586] - Consistent Consumer information should be returned back by topic and server mbeans
  • [HORNETQ-587] - Missing JMS JMX Management Operations
  • [HORNETQ-647] - ConnectionFactoryControl doesn't persist changes on either JNDI or Journal

Bug

  • [HORNETQ-343] - Management operation results can not be read from Stomp clients
  • [HORNETQ-369] - transaction.commit should throw RolledBackException or guarantee it's atomic on failover
  • [HORNETQ-400] - In Message Grouping, I cannot set autogroup by hornetq-jms.xml
  • [HORNETQ-410] - Delivery not prompted when consumer flow control is disabled
  • [HORNETQ-411] - FailoverManager needs Priviledged Block on ClassLoading operation
  • [HORNETQ-420] - HDR_OPERATION_SUCCEEDED not set to true when retrieving an attribute value
  • [HORNETQ-434] - Inaccurate wording in exception message, mentions JBoss but should rather say HornetQ
  • [HORNETQ-437] - stand-alone/non-clustered/hornetq-beans.xml should pick up port properties from run.sh script
  • [HORNETQ-439] - Streaming Consumer Receives Only 1 Message With 0 Client Buffer
  • [HORNETQ-441] - Enabling NIO on client side does not work without buffering
  • [HORNETQ-444] - Delivery spins with consumers with filters that don't match
  • [HORNETQ-450] - Extra messages when mixing receive() and receiveImmediate()
  • [HORNETQ-454] - HornetQ RHQ/Jopr plugin's descriptor incorrectly lists JBossAS 4.x server as parent type
  • [HORNETQ-460] - Unknown jndi port in jboss-as-4\clustered\jms-ds.xml
  • [HORNETQ-469] - Some messages are trapped in queue and a thread consumes 100% CPU
  • [HORNETQ-493] - Cleanup may remove reference to the file containing the tx.commit
  • [HORNETQ-495] - Transacted/XA deliveries acked after onMessage
  • [HORNETQ-501] - Bad roles due to spaces around commas ("roles" attributes of the permission entity) in hornetq-configuration.xml
  • [HORNETQ-506] - HornetQ "JMSServerManager" fails to start on startup with NullPointerException
  • [HORNETQ-518] - HornetQ testsuite does not work on Solaris OS
  • [HORNETQ-519] - HQ non-durable, non-transacted, topic receiver hangs if idle for more than some time.
  • [HORNETQ-520] - Messages missing in HornetQ after one node in a cluster gets killed.
  • [HORNETQ-521] - Error removing diverts through core server API
  • [HORNETQ-522] - Reconnection issue when failover to backup server
  • [HORNETQ-523] - Eventual Page of Order when address goes out of page in the middle of a transaction
  • [HORNETQ-524] - Connection factory <group-id> does not work
  • [HORNETQ-525] - Concurrency issue between HornetQConnection and HornetQSession
  • [HORNETQ-526] - STOMP connection does not support TTL
  • [HORNETQ-530] - Default JTA integration on JBoss AS doesn't work as expected
  • [HORNETQ-549] - Twitter Bridge no longer work with basic auth
  • [HORNETQ-555] - Failover not working with JCA in JBoss
  • [HORNETQ-557] - Lost message with Selector/Queue/Consumer.receive()
  • [HORNETQ-566] - Change JMS connection factories in server integration configuration to be of type XAConnectionFactory
  • [HORNETQ-571] - Cluster messages not redistributed after node hard kill
  • [HORNETQ-585] - ConsumerId from JMS Server mbean is always 0
  • [HORNETQ-595] - Unable to compile MultipleFailoverFailbackExample
  • [HORNETQ-598] - Cope with moving messages that have clashing duplicateIDs
  • [HORNETQ-604] - org.hornetq.core.client.impl.ClientMessageImpl.saveToOutputStream does not flush after writing to OutputStream
  • [HORNETQ-606] - Stuck messages when consuming scheduled messages using selector
  • [HORNETQ-609] - DeliveringCount can go negative during transaction recovery
  • [HORNETQ-615] - connection factory control missing attribute
  • [HORNETQ-616] - createConnectionFactory is not exposing compressLargeMessage
  • [HORNETQ-617] - Settings on CF created through Management are not preserved after restart
  • [HORNETQ-624] - Duplicate JNDI Bindings Can Be Created Via ConnectionFactoryControl.addJNDI()
  • [HORNETQ-625] - Use of org.hornetq:module=JMS,type=Server.destroyConnectionFactory Doesn't Survive Restarts
  • [HORNETQ-628] - Incorrect Message Counts when Paging Occurs
  • [HORNETQ-629] - JMS Topic MBean Operation DropAllSubscriptions will also delete the address
  • [HORNETQ-636] - Cluster Bridges are not Acking properly
  • [HORNETQ-641] - Entries are not removed from org.hornetq.core.server.impl.HornetQServerImpl.addressSettingsRepository when deleting a queue
  • [HORNETQ-654] - Redistribution information is lost in case of a server restart
  • [HORNETQ-659] - Memory leak in cluster implementation
  • [HORNETQ-660] - Infinite Delivery Records on the Journal in case of failed deliveries

Task

Sub-task

  • [HORNETQ-325] - Implement the possibility of paging at the Queue Level
  • [HORNETQ-447] - Make sure the code is optimized on LargeMessage
  • [HORNETQ-448] - Large message compression
  • [HORNETQ-500] - Add timed syncs on paging
  • [HORNETQ-538] - Change large message to reconstruct a regular buffer on the client
  • [HORNETQ-574] - Persist queue counters on paging

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.