activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raul Kripalani <r...@evosent.com>
Subject Re: FailoverTransport - "Successfully connected to..." log messages
Date Mon, 10 Dec 2012 19:04:32 GMT
Hey Ben

The default idleTimeout of the PooledConnectionFactory is only 30
seconds. And physical connections are borrowed in a round-robin fashion.

So if it takes the application more than 30 seconds to cycle through the 5
connections, you'll start observing connection churn, which seems exactly
what's happening in your case.

Is it possible that 30 secs elapsed between subsequent uses of the
JmsTemplate in your scenario?

Hope that helps,

*Raúl Kripalani*
Apache Camel Committer
Enterprise Architect, Program Manager, Open Source Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk <http://twitter.com/raulvk>

On Mon, Dec 10, 2012 at 6:27 PM, boday <ben.oday@initekconsulting.com>wrote:

> thanks ceposta, so is this a bug with the FailoverTransport or an issue
> with
> my configuration?
>
> correct...I have 2 applications running on separate brokers (no network of
> brokers, etc).  one application sends messages to the other broker via a
> JMSTemplate...
>
> is there a better way to do this than what I described?
>
>
>
> ceposta wrote
> > Nope, that shouldn't be expected. It should only log that if the
> > connection
> > is first created:
> >
> >                             if (firstConnection) {
> >                                 firstConnection = false;
> >                                 LOG.info("Successfully connected to " +
> > uri);
> >                             } else {
> >                                 LOG.info("Successfully reconnected to " +
> > uri);
> >                             }
> >
> > Not sure what you mean here:
> >
> > "I have 2 AMQ 5.7 brokers, one sends messages to the other via a
> > JMSTemplate/PooledConnectionFactory/FailoverTransport. "
> >
> > 2 brokers and one sends to the other using JmsTemplate?
> >
> >
> > On Mon, Dec 10, 2012 at 10:38 AM, boday &lt;
>
> > ben.oday@
>
> > &gt;wrote:
> >
> >> String failoverBrokerUrl =
> >> "failover:tcp://localhost:61666?randomize=false&timeout=10000";
> >> ActiveMQConnectionFactory factory = new
> >> ActiveMQConnectionFactory(failoverBrokerUrl);
> >> PooledConnectionFactory pcf = new PooledConnectionFactory(factory);
> >> pcf.setMaximumActive(500);
> >> pcf.setMaxConnections(5);
> >> JMSTemplate jmsTemplate = new JmsTemplate(pcf);
> >> jmsTemplate.setSessionAcknowledgeMode(Session.CLIENT_ACKNOWLEDGE);
> >>
> >
> >
> >
> > --
> > *Christian Posta*
> > http://www.christianposta.com/blog
> > twitter: @christianposta
>
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/FailoverTransport-Successfully-connected-to-log-messages-tp4660444p4660447.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message