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 <john.d.am...@gmail.com> wrote: > 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: [artemis-amqp-protocol]. Adding protocol support > for: AMQP > > 17:21:26,457 INFO [org.apache.activemq.artemis.core.server] AMQ221043: > Protocol module found: [artemis-hornetq-protocol]. Adding protocol support > for: HORNETQ > > 17:21:26,458 INFO [org.apache.activemq.artemis.core.server] AMQ221043: > Protocol module found: [artemis-mqtt-protocol]. Adding protocol support > for: MQTT > > 17:21:26,459 INFO [org.apache.activemq.artemis.core.server] AMQ221043: > Protocol module found: [artemis-openwire-protocol]. Adding protocol support > for: OPENWIRE > > 17:21:26,460 INFO [org.apache.activemq.artemis.core.server] AMQ221043: > Protocol module found: [artemis-stomp-protocol]. Adding protocol support > for: STOMP > > 17:21:26,540 INFO [org.apache.activemq.artemis.core.server] AMQ221003: > Trying to deploy queue incoming > > 17:21:26,600 INFO [org.apache.activemq.artemis.core.server] AMQ221003: > Trying to deploy queue jms.queue.DLQ > > 17:21:26,609 INFO [org.apache.activemq.artemis.core.server] AMQ221003: > Trying to deploy queue jms.queue.ExpiryQueue > > 17:21:26,614 WARN [org.apache.activemq.artemis.core.server] AMQ222203: > Classpath lacks a protocol-manager for protocol AMQP, Protocol being > ignored on acceptor TransportConfiguration(name=amqp, > factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyAcceptorFactory) > ?port=5672&host=0-0-0-0&protocols=AMQP > > 17:21:27,180 WARN [org.apache.activemq.artemis.core.server] AMQ222203: > Classpath lacks a protocol-manager for protocol HORNETQ, Protocol being > ignored on acceptor TransportConfiguration(name=hornetq, > factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyAcceptorFactory) > ?port=5445&host=0-0-0-0&protocols=HORNETQ,STOMP > > 17:21:27,181 WARN [org.apache.activemq.artemis.core.server] AMQ222203: > Classpath lacks a protocol-manager for protocol STOMP, Protocol being > ignored on acceptor TransportConfiguration(name=hornetq, > factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyAcceptorFactory) > ?port=5445&host=0-0-0-0&protocols=HORNETQ,STOMP > > 17:21:27,181 WARN [org.apache.activemq.artemis.core.server] AMQ222203: > Classpath lacks a protocol-manager for protocol MQTT, Protocol being > ignored on acceptor TransportConfiguration(name=mqtt, > factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyAcceptorFactory) > ?port=1883&host=0-0-0-0&protocols=MQTT > > 17:21:27,182 WARN [org.apache.activemq.artemis.core.server] AMQ222203: > Classpath lacks a protocol-manager for protocol STOMP, Protocol being > ignored on acceptor TransportConfiguration(name=stomp, > factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyAcceptorFactory) > ?port=61613&host=0-0-0-0&protocols=STOMP > > > Thus hung for a while, then eventually I got this > > > 17:22:59,335 WARN [org.apache.activemq.artemis.core.client] AMQ212037: > Connection failure has been detected: AMQ119014: Did not receive data from > null. It is likely the client has exited or crashed without closing its > connection, or the network between the server and client has failed. You > also might have configured connection-ttl and client-failure-check-period > incorrectly. Please check user manual for more information. The connection > will now be closed. [code=CONNECTION_TIMEDOUT] > > > John > > On Mon, Apr 11, 2016 at 5:09 PM John D. Ament <johndam...@apache.org> > wrote: > >> 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 < >> clebert.suco...@gmail.com> 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, 2016 at 4:24 PM, John D. Ament <johndam...@apache.org> >>> wrote: >>> > 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?period=500") >>> > .process(exchange -> { >>> > exchange.getIn().setBody("Boop "+new Date()); >>> > exchange.getOut().setBody("BoopOut "+new Date()); >>> > }) >>> > .to("amqp:queue:incoming"); >>> > >>> > After I terminate the client abruptly and restart it (for durability >>> > testing), I'm seeing the broker not deliver messages to the consumer. >>> > After I restart the broker (even when the client is still running), I >>> see >>> > the consumer start back up. >>> > >>> > I'm wondering if this is an issue w/ Artemis or with Qpid. Has anyone >>> seen >>> > something similar? >>> > >>> > John >>> >>> >>> >>> -- >>> Clebert Suconic >>> >>
