Re: Artemis - Cannot get scheduled messages to work with AMQP and Topic

Ok. I misinterpreted the explanations in "Protocols and Interoperability / AMQP scheduling message delivery". By the way: the section "Scheduled Messages" suggests using property _AMQ_SCHED_DELIVERY which has no effect at all. At least not with AMQP. Thanks for clarification

Re: Artemis - Cannot get scheduled messages to work with AMQP and Topic

This seems to be a qpid problem. I debugged through the code and my delivery time above gets overwritten. Currently you can only set it using producer.setDeliveryDelay(6); And then scheduled messages work. So sorry for the noise. 2017-10-18 15:49 GMT+02:00 Matthias Hanisch

Artemis - Cannot get scheduled messages to work with AMQP and Topic

ted at all? Or is it a problem using multi-cast? I am using artemis 2.4.0-SNAPSHOT from last week. Many thanks in advance, Matthias -- camLine GmbH 85238 Petershausen, Industriering 4a, Deutschland Amtsgericht München HRB 88821 Geschäftsführer: Heinz Linsmaier (CEO), Bernhard Jofer, Georg R

Re: How to put "properties" on a message so they are accessible later

creates a new message with the enriched context and uploads it back to the broker. This would duplicate a lot of messages and would impact performance. A more efficient way to realize this feature would be greatly appreciated. Best regards, Matthias P.S.: I just subscribed to this mailing list so I was

Re: ActiveMQ RAR - Logging

rlier. I posted my (lengthy) solution on StackOverflow ( http://stackoverflow.com/questions/18123656/slf4j-bindings-are-overwritten-by-other-applications-on-the-same-application-s). Regards Matthias On 08/12/2013 08:13 PM, Matthias wrote: Hi all I have deployed activemq-rar-5.8.0.rar to a

ActiveMQ RAR - Logging

for your time & help Matthias

slave broker forwarding dead master's messages to another broker?

The following scenario: Master and slave share a datastore. Master fails, slave takes over. Is it possible to define a forwarding connection from this slave to another (master) broker, with the result that the slave broker finds the stored messages sent to the failed master, and automatically send

activemq-jpa-store introcudes in activemq-all 5.1.0 causes exception on JBoss startup if JPA not used

nk/activemq-all/pom.xml] - whilst converting to use the shade plugin, activemq-jpa-store was added. Was this intentional? Is the persistence.xml correct in not defining any data source? Kind regards, Matthias -- View this message in context: http://www.nabble.com/activemq-jpa-store-introcudes-in-act