ActiveMQ 5.13.4 发布,JMS 消息服务器 - 开源中国社区
ActiveMQ 5.13.4 发布,JMS 消息服务器
daxiaoming 2016年07月22日

ActiveMQ 5.13.4 发布,JMS 消息服务器

daxiaoming daxiaoming 发布于2016年07月22日 收藏 19

免费体验IBM Cloud,构建Iot应用 >>>  

ActiveMQ 5.13.4 已经发布。修复了30多个问题。

PS. 真的很想看到最近版本的 ActiveMQ, Artemis, Rabbitmq 的对比评测。

详细列表:

Bug

  • [AMQ-5426] - ActiveMQMessageConsumer could run into NPE due to concurrent access to internal state

  • [AMQ-5886] - AMQ accepts illegal MQTT protocol level (5, only 3 and 4 are defined)

  • [AMQ-6194] - Deleting a temporary queue creates a warning message in the broker

  • [AMQ-6271] - activemq-osgi defines wrong range for org.springframework.osgi...

  • [AMQ-6275] - Error when using ws transport connector

  • [AMQ-6285] - MessageDatabase doesn't properly cleanup the checkpoint scheduler on shutdown

  • [AMQ-6287] - Message ack rewrite task doesn't properly release index lock

  • [AMQ-6290] - JMS Pool reconnection logic not always reliable

    [AMQ-6291] - Thread unsafe code in TcpTransportServer can lead to NPE or other errors on start / stop

  • [AMQ-6298] - Incorrect Import-Package version range for org.springframework.osgi

  • [AMQ-6305] - AMQP: Drain requests can go unaswered in certain cases.

  • [AMQ-6310] - Certain VirtualTopic configurations no longer send messages to the correct queue

  • [AMQ-6325] - JMS Selector parsing will not fail if a valid selector is followed by invalid text

  • [AMQ-6334] - ActiveMQConnection triggered heap space out of memory error when used with org.apache.activemq.network.SimpleJmsQueueConnector

  • [AMQ-6340] - Queue order lost on consumer close in some cases

  • [AMQ-6343] - [MQTT] LWT doesn't work over a websocket connection

  • [AMQ-6345] - [MQTT] ping response without CONNECT

    [AMQ-6346] - Concurrent access to a MQTT Transport from WebSocket client can deadlock

  • [AMQ-6350] - PooledConnectionFactory throws 'IllegalStateException: Pool not open' after re-init

  • [AMQ-6352] - Temporary message store cursor does not track store message size properly

  • [AMQ-6353] - AMQP: Using JMS Transformer, preserve the type of the original CorrelationId

  • [AMQ-6356] - Processing a KahaUpdateMessageCommand can lead to wrong store size being reported

  • [AMQ-6357] - shutdown due to a local error: java.lang.ArithmeticException: / by zero

改进

  • [AMQ-6100] - Virtual topic message destination should be the target queue

  • [AMQ-6292] - ACK rewrite task does unnecessary syncs

  • [AMQ-6301] - Embed spring-dm in activemq-osgi to avoid loading spring-dm in Karaf

  • [AMQ-6304] - Container-id field blank on sending an AMQP 1.0 open frame to the client

  • [AMQ-6319] - AMQP: Make it easier to disable accepting non-SASL clients and add more tests.

  • [AMQ-6328] - Upgrade Camel to latest

新特性

  • [AMQ-6274] - Add option to composite destinations to set originalMessage header

本站文章除注明转载外,均为本站原创或编译。欢迎任何形式的转载,但请务必注明出处,尊重他人劳动共创开源社区。
转载请注明:文章转载自 开源中国社区 [http://www.oschina.net]
本文标题:ActiveMQ 5.13.4 发布,JMS 消息服务器
分享
评论(5)
最新评论
0
是的,如果小规模的消息处理不像淘宝等的海量的消息,ActiveMQ足够了,如果是海量的消息和高效的处理,那当然是 RabbitMQ 了。
0

引用来自“zhuxinyu”的评论

年初刚刚选择了activemq
用着也很不错
0
年初刚刚选择了activemq
0

引用来自“OSGi狂人”的评论

不用评测了,从近几年来的使用情况来看Rabbitmq比ActiveMQ多,评测结果已经不重要了
这个结论很多人都知道。我只是想看看 ActiveMQ 最近比之前有多少改进?新的 Artemis 因为更轻量,到底与 ActiveMQ 相比会是怎样?
0
不用评测了,从近几年来的使用情况来看Rabbitmq比ActiveMQ多,评测结果已经不重要了
顶部