he consumer will mostly throw an
> exception (as seen im AMQ-1710). However your behavior seems a but
> different, can you create a jira-issue and attach your test-case? I'd
> like to try in on my patched version and see what happens.
>
> --Mario
>
> On Wed, Sep 10, 2008
Below is the output from a unit test I wrote to demonstrate the problem.
here is the summary from what is highlighted:
14:34:28 - send "Hello, World!"
14:34:29 - receive "Hello, World!"
14:34:34 - remind myself to shutdown master broker, i.e. localhost:61626
14:34:40 - amq detects transport fail
Hi,
I am starting two brokers (tcp://localhost:61616 and tcp://localhost:61626)
with shared FS. One is locked out because journal is locked by the master as
it should be. Then I start my Spring base web app with a TransportListener
added to ActiveMQConnectionFactory. When spring is done with init
Is there a way to specify redeliveryPolicy per destination in AMQ 5.1.0?
I know how to do this per connectionFactory or connection.
If not, my approach would be to configure spring to use a connection per
listener and configure redelivery policy per connection.
thanks,
vadim
--
View this messag
I've answered question #2
ByteSequence byteSeq = amqMessage.getMarshalledProperties();
DataInputStream dataIn = new DataInputStream(new
ByteArrayInputStream(byteSeq));
Map properties =
MarshallingSupport.unmarshalPrimitiveMap(dataIn);
but the rest I am still struggling with.
vadim
va
Hi,
I've configured message redelivery via Spring 2.5 and ActiveMQ 5.1.0 to
redeliver messages on a runtime exception thrown by a listener. If
redelivered message still could not be handled, it is sent to DLQ.
After picking it from DLQ and I would like to have access to the original
message prope
