Re: [Artemis 2.6.3] Multicast consumer via HTTP transport: AMQ212037 Connection failure has been detected

2018-10-15 Thread Justin Bertram
A 'git bisect' revealed that the issue was introduced via 775b1c78aa690872ef7775f97ccdea408ed3830c for ARTEMIS-1927 [1]. You can work around the issue by setting the 'confirmationWindowSize' on your URL in jndi.properties to something > 0, e.g.: connectionFactory.ConnectionFactory=tcp://localho

Re: [Artemis 2.6.3] Multicast consumer via HTTP transport: AMQ212037 Connection failure has been detected

2018-10-15 Thread Justin Bertram
Some quick testing indicates this failure was introduced in 2.6.2 which means if you use 2.6.1 it should work. Justin On Mon, Oct 15, 2018 at 12:54 PM Justin Bertram wrote: > This WARN message: > > AMQ212037: Connection failure has been detected: > io.netty.handler.codec.http.HttpObjectAggre

Re: [Artemis 2.6.3] Multicast consumer via HTTP transport: AMQ212037 Connection failure has been detected

2018-10-15 Thread Justin Bertram
This WARN message: AMQ212037: Connection failure has been detected: io.netty.handler.codec.http.HttpObjectAggregator$AggregatedFullHttpRequest cannot be cast to io.netty.buffer.ByteBuf [code=GENERIC_EXCEPTION] Indicates to me that you're hitting a bug. Out of curiosity, why are you using the H

[Artemis 2.6.3] Multicast consumer via HTTP transport: AMQ212037 Connection failure has been detected

2018-10-15 Thread thokuest
I just started using ActiveMQ Artemis and would like to check whether I'm doing something wrong or if I hit a bug. I want to consume messages from a multicast address via HTTP transport. I tweaked the http-transport example (apache-artemis-2.6.3/examples/features/standard/http-transport) for my pu

Re: [Artemis 2.6.2] AMQP messages going to expiry queue, redelivery off that queue is failing

2018-10-15 Thread Robbie Gemmell
To confirm, the broker issue had nothing to do with use of transactions specifically. You only saw any variation there due to difference in client behaviour altering the overall situation in the limited test. Master and 2.6.x now have some fairly different message handling in this area, so you sho

memory leak

2018-10-15 Thread vox_de_hg
Hi, I'm facing a strange memory leak on one of my production environment (others environments are ok) The Environment 1) AIX 7.1 2) IBM JVM 1.7 3) ActiveMQ broker 5.12.2 embedded in our java monitoring application 3) Client are either java client (embedded inside a front office war applicat

Re: ActiveMQ: producer flow control and temp store

2018-10-15 Thread art.licis
Hi Tim, Sorry, I'm a bit late with this :) It's great you like the idea! I'll do my quick research and I'd love to contribute, so I'll make a JIRA and hopefully a PR. - Art -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: ACTIVE MQ upgrade/Migration steps

2018-10-15 Thread art.licis
Hi, It depends on what do you mean by 'old' and 'new'. If you mean migration 5.x to Artemis, then these are two different systems and need a slightly different approach. Here's an extensive guide for that: https://activemq.apache.org/artemis/migration/index.html - Art -- Sent from: http://a