You can try to copy() the message before resending it and see if that helps.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Sat, Nov 7, 2009 at 5:48 AM,
Hi David,
it's all configured in your redeliveryPolicy, where you instructed the
broker to try resending the message indefinitely.
See http://activemq.apache.org/message-redelivery-and-dlq-handling.html for
more information how redelivery works and how you can use Dead letter
queues
Cheers
--
Just a though, with the latest 5.3.0 release, the wireformat version
is 5. Enable debug logging to validate the wireformat negotiation
between the brokers to see what is the problem. Possibly there is some
mix up in the classpath or something.
2009/11/9 hackingbear hackingb...@gmail.com:
Hi,
Think this is resolved by
https://issues.apache.org/activemq/browse/AMQ-2468 which is fixed on
trunk and the 5.3 branch. The pagedInPendingDispatch list which was
accumulating messages is now limited. This was highlighted by the jmx
purge operation but the same logic holds for the browse that is
Hi,
We are using Multicast Transport to broadcasting messages. We get
topicConnection successfully. But when it tries to get topicSession, it
receives timeout. Do we need to pass any particular options to the
connection or any other configuration might be wrong?
topicConnection =
Looks like AMQ-2468 does not resolve this as there is also an issue
with the message list. I have opened
https://issues.apache.org/activemq/browse/AMQ-2481 to track this and
already have a reproducible test case.
Thanks for the heads up.
2009/11/9 afei afei1...@126.com:
when a large of
I've troubles to deploy ActiveMQ 5.3.0 (and in 5.2.0 too) to zOS (Mainframe).
I know there is a description for 5.0.0 available
(http://activemq.apache.org/zos.html).
As it seems to be easy to deploy, we cannot start ActiveMq.
stdout: activemq_stdout.txt
ActiveMq-Log: activemq.log
config XML:
fyi: you can disable periodic message expiry processing using a
destination policy entry that sets expireMessagesPeriod = 0
2009/11/9 afei afei1...@126.com:
when a large of messages in queue,and no consumer or the consumer is very
slow, the OOM problem occur, because :
in
Hello,
We are having a problem when using Activemq-cpp (version 2.2.6). This
problem happens with Stomp and Openwire.
We create thousands of message groups dynamically : Create a message group,
send several messages, close message group. The producer is a C++
application, the consumer is two
Hello everybody!
I'm new to activemq and I have a question. I have a publisher and subcriber
to the topic, when I launch publisher it sends some messages to the topic,
then I close that publisher and start subscriber and he doesn't get
messages that publisher sended early. I have examples from
Hello again!
I resolved message redelivering problem, by following:
add to subscriber code:
IMessageConsumer consumer = session.CreateDurableConsumer(new
Apache.NMS.ActiveMQ.Commands.ActiveMQTopic(testing?consumer.retroactive=false),
testing listener, null, false);
and to config file:
I can't seem to find a way to listen for new producer and consumer
connections (or connection interrupts) in ActiveMQ (Java Version). I want to
be able to tell the consumers (or they can find out themselves) that the
producer's connection dropped. The other way around (the producer finding
out
Is it possible to make use of activemq bridge to forward the messages from a
remote queue on serverA to another remote queue on ServerB?
If yes, how should I configure the activemq? Thanks.
--
View this message in context:
http://old.nabble.com/activemq-bridge-tp26277790p26277790.html
Sent from
Forgot to mention that activemq is on another server which is independent
from ServerA and ServerB.
Both ServerA and ServerB use jboss messaging.
jeff yung wrote:
Is it possible to make use of activemq bridge to forward the messages from
a remote queue on serverA to another remote queue on
i test r831258,the problem still exist
Gary Tully wrote:
fyi: you can disable periodic message expiry processing using a
destination policy entry that sets expireMessagesPeriod = 0
2009/11/9 afei afei1...@126.com:
when a large of messages in queue,and no consumer or the consumer is
in addition,another problem of OOM.
Gary Tully wrote:
fyi: you can disable periodic message expiry processing using a
destination policy entry that sets expireMessagesPeriod = 0
2009/11/9 afei afei1...@126.com:
when a large of messages in queue,and no consumer or the consumer is very
16 matches
Mail list logo