Great! Glad it worked. Thanks for letting me know.
--
This is the Droid you're looking for.
On Sep 19, 2011 3:59 PM, "zcduthie" wrote:
> I've left it running for a week and everything seems to be working fine.
> What a silly mistake!
>
> Thanks very much!
>
> --
> View this messag
Hello,
I have a scenario (Spring, ActiveMQ, PostgreSQL) where we want to configure
our messaging to provide automatic failover and no additional interaction on
bringing a failed master back online (like in pure-shared-nothing
master/slave).
as mentioned in ActiveMQ in action I just started multip
I read about those items and checked out my configuration. I don't have
anything in there that should cause this. here's the section that defines
the flow control:
Thanks for your help. Unfortunately, TRACE level doesnt show anything
relevant. However, i've been trying different things and it seems this
problem happens only after the first 10 seconds of the consumer's activity.
I mean, if i make all the process i explained really fast (i never did
before my f
Thanks for your help. Unfortunately, TRACE level doesnt show anything
relevant. However, i've been trying different things and it seems this
problem happens only after the first 10 seconds of the consumer's activity.
I mean, if i make all the process i explained really fast (i never did
before my f
It depends on whether the broker got the commit message or not. If it
did not, then the transaction rolls back on the broker when it sees
the the disconnect.
If you are using failover, the client will report an exception. It
sees a missing reply but can't know the outcome so it must alert the
clie
Amq5.5 is not compatible with logback 0.9.9.
It works well after using logback 0.9.15.
At 2011-09-20 17:17:02,"Dejan Bosanac" wrote:
>Try using slf4j 1.6 and higher
>
>Regards
>--
>Dejan Bosanac - http://twitter.com/dejanb
>-
>The experts in open source integration and messagi
There was no producer, broker or connection crash while the msg was in transit?
The msg does not have an expiration time?
Are you certain that no consumer has got the msg already?
You could turn on full logging inside the broker, it will log each msgs being
received. Might not be suitable for a
sounds like you may have a memory limit configured. Can you post your
xml configuration or read about broker limits and flow control and
message cursors.
On 19 September 2011 20:42, rpack78 wrote:
> I am bench marking ActiveMQ using Perl and Stomp+NIO. I have setup 3 queues
> and 4 topics, and a
you will get more information with TRACE level logging for FailoverTransport
There are a bunch of retry config options but the default is to
continue to retry for ever.
If you want to see what it does/can do, the source is at:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java
Hello,
I've just started using Activemq so please excuse me if this has been
already answered.
I'm using failover with two brokers, host1 and host2, and this connection
uri:
failover:(tcp://host1:61617,tcp://host2:61617)
So the consumer randomly connects to one of the brokers. When i stop tha
Is there anything that might cause a message to go missing? A producer sends a
persistent message to a topic but now and then, although no error is returned
from the broker, the message just disappears. It's not logged in the data store
and it's as if it never reached the broker but that would h
Try using slf4j 1.6 and higher
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
2011/9/20 SuoNayi
> Hi all ,ar
13 matches
Mail list logo
