Ok, I *think* I found the issue with master. I raised a PR if you want to
take a look
https://github.com/apache/activemq-artemis/pull/456
John
On Mon, Apr 11, 2016 at 5:24 PM John D. Ament
wrote:
> Nope, master doesn't work either. Looks worse actually
>
> 17:21:26,454 INFO [org.apache.acti
Nope, master doesn't work either. Looks worse actually
17:21:26,454 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-server]. Adding protocol support for: CORE
17:21:26,456 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found:
If that works (and building it locally) are there any plans to introduce a
1.2.1/1.3.0 soon?
John
On Mon, Apr 11, 2016 at 4:59 PM Clebert Suconic
wrote:
> I have fixed something similar to this on master (It was a dead lock).
>
>
> Can you try against master or a snapshot?
>
> On Mon, Apr 11, 2
I have fixed something similar to this on master (It was a dead lock).
Can you try against master or a snapshot?
On Mon, Apr 11, 2016 at 4:24 PM, John D. Ament wrote:
> I'm using Camel AMQP Component (which uses Qpid under the hood) to connect
> to Artemis. Both are running locally on my mac.
I'm using Camel AMQP Component (which uses Qpid under the hood) to connect
to Artemis. Both are running locally on my mac. My routes are simply:
from("amqp:queue:incoming").process(exchange -> {
System.out.println(exchange.getIn().getBody());
});
from("timer:incoming
