Hi Bruce,
> Well, if that's the case, then those reconnect messages might be part
> of the issue. Why would the producers be disconnected so often?
Having had a look at the FailoverTransport source, it doesn't look
like that log message is necessarily bad, so I think red herring
there.
Yeah, I'm wondering that as well. I'll see if I can do a little more
investigation... see if I can reproduce it in a different environment.
On Thu, Oct 1, 2009 at 3:26 PM, Bruce Snyder <bruce.sny...@gmail.com> wrote:
> On Thu, Oct 1, 2009 at 7:57 AM, Jamie McCrindle
> <jamiemccrin...@gmail.com> wrote:
>> Hi Bruce,
>>
>> Thanks for the response. Looking at JVM options is definitely a way to
>> go but I have a suspicion that that would be treating the symptoms. We
>> really don't have many destinations. The setup should _theoretically_
>> keep the number of connections low (pooledconnection factory for
>> producers, CACHE_CONSUMER in the consumers) but it looks like
>> something is generating a _lot_ connections regardless. The
>> FailoverTransport.doReconnect messages are suspicious but I don't know
>> for sure that they're bad...
>
> Well, if that's the case, then those reconnect messages might be part
> of the issue. Why would the producers be disconnected so often?
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> ActiveMQ in Action: http://bit.ly/2je6cQ
> Blog: http://bruceblog.org/
> Twitter: http://twitter.com/brucesnyder
>
