I'm trying to implement a system that processes messages from the DLQ. I'm
installed activemq 5.3.1 and left all configuration to the default. When I
run a client and rollback the message 6 times (default) the message is never
sent to the ActiveMQ.DLQ queue. I never see this queue created at al
nk?
> What platform are you on?
> Did u make any changes like run against an external broker?
>
> On 13 May 2010 13:15, sbuster wrote:
>
>>
>> Gary,
>> Thanks for the response! I downloaded the JmsRollbackRedeliveryTest and
>> get
>> the same result
core/src/test/java/org/apache/activemq/
>
> On 11 May 2010 20:36, sbuster wrote:
>
>>
>> I'm the same probelm as the other user in terms of using a simple
>> transacted
>> client that tries to call session.rollback and get the following
>> exception
>>
I'm the same probelm as the other user in terms of using a simple transacted
client that tries to call session.rollback and get the following exception
in the log. Ultimately I want the message to end up in the DLQ but it never
gets directed there. attached is a simple client, my activemq config
I have tested this same functionality within a servlet using UserTransactions
and it works fine. Using the same managed resources referenced by the J2EE
container as the MDB uses. Any help would be apprecicated.
Thanks
sbuster wrote:
>
> I'm using ActiveMQ 5.2 with WebSphere
phil,
either you response didn't come through, or I just don't see it. Did
you have a suggestion?
sbuster wrote:
>
> I'm using ActiveMQ 5.2 with WebSphere 7.0 and Sun JavaDB 10.x. Pretty
> standard requirement, I have a message that arrives on a Queue, gets
&
I'm using ActiveMQ 5.2 with WebSphere 7.0 and Sun JavaDB 10.x. Pretty
standard requirement, I have a message that arrives on a Queue, gets pulled
off with Message Drive Bean and needs to be directly insert into JavaDB.
However, when I thrown an exception inside my MDB to test the rollback
capabi
How do you setup the JMS configuration details inside a J2EE container to
listen for multiple brokers such as the in the clustered queue consumer
scenario? I have the Message Driven Bean configured and working to one
broker, but I don't see anywhere where I would put the "failover:(...)"
string
