I have a pub/sub model where the subscriber is a grails client using Spring
configuration for the messaging. For some reason it seems to miss several
messages in our tests. Here's what I've tried :-
1. Start up the subscriber to a test topic.
2. Start up the publisher - this publishes simple
Sorry.
I just test the scenario manually .
It is difficult for me to write a junit test for the test scenario.
Gary Tully wrote:
can you package up your test case or ideally mash it into a junit test
case along the lines of some of the tests in:
Hi,
I use ActiveMQ as a broker to deliver messages. Theses messages are
intented to be written in a dabatase. Sometimes, the database is
unreachable or down. In that case, I want to rollback my message to
retry later this message and I want to continue reading other messages.
This code
Have a peek at https://issues.apache.org/activemq/browse/AMQ-2710
On Wednesday, July 28, 2010, Jean-Philippe Caruana
jeanphilippe1.caru...@orange-ftgroup.com wrote:
Hi,
I use ActiveMQ as a broker to deliver messages. Theses messages are intented
to be written in a dabatase. Sometimes, the
We're using the ActiveMQ maven plugin to run a broker in the
pre-integration-test phase of one module in a multi-module project. It
starts up fine when you build just that module, but if you go up to the
parent project and try to do a build of all modules, ActiveMQ fails to start
with a
I have seen on this forum other users complain about javax.jms.JMSException:
java.io.EOFException happening in the receiver, but it seems that my case is
in the different context.
I am using ActiveMQ 5.3.2.
Please look at my exception log below. The exception happens when I attempt
an innocent
Is there any possible concurrent access to that message?
On 28 July 2010 17:34, lilyevsky lilyev...@mooncapital.com wrote:
I have seen on this forum other users complain about javax.jms.JMSException:
java.io.EOFException happening in the receiver, but it seems that my case is
in the different
No, but I do process them asynchronously. The actual consumer saves the
message in the queue and ends the onMessage() call. Another thread picks it
up from the queue and does the actual processing.
Even if there was concurrent access, why should it be a problem? The message
on the receiving side
I've got some more clues, maybe they will help.
I actually have two consumers that listen to the same topic, but slightly
different selectors. They share a connection, but they have their own
sessions.
I traced an example of corrupt message, this is what happened.
The message was supposed to go
Given a queue and the assumption that messages are idempotent, I'm looking for
a way to have a given consumer go 'back in time', and re-play some period or
even all available messages prior to resuming normal consumption. Possibly as
much as the last 24 hours worth.
The trick is that the
We are using worker threads to process messages. So, onMessage() calls
simply return by delegating the processing to the worker thread. Once the
worker thread processes the message, worker thread calls
message.acknowledge(). So, if I set a prefetch buffer of 10, and 9 messages
are getting
11 matches
Mail list logo
