Hi JB,
I'll try to. We got two activemq servers working as a cluster!
The producer speak with the loadbalancer in front of both servers.
-> ActiveMQ A <-
Producer -> LB | | LB <- Consumer
-> ActiveMQ B <-
Mit freundlichen Grüßen / Best regards
Björn
-----Ursprüngliche Nachricht-----
Von: Jean-Baptiste Onofré [mailto:[email protected]]
Gesendet: Donnerstag, 19. September 2013 12:21
An: [email protected]
Betreff: Re: Loadbalancer Alive-Checks
Hi Bjoern
which kind of LB did you setup ? Could you quickly describe what you did ?
Thanks,
Regards
JB
On 09/19/2013 12:10 PM, [email protected] wrote:
> Hello,
>
> we're running activemq with a loadbalancer setup. The loadbalancer does TCP
> alive checks to port 61616 which causes many Warnings in the activemq log.
> Is there any way to ignore requests from the loadbalancers ip? It's important
> to don't denied the access for those ip addresses, we want that they don't
> disturb the application.
>
> 2013-08-30 12:39:11,038 | WARN | Transport Connection to:
> tcp://10.12.21.4:11583 failed: java.net.SocketException: Connection
> reset | org.apache.activemq.broker.TransportConnection.Transport |
> ActiveMQ Transport: tcp:///10.12.21.4:11583@61616 2013-08-30
> 12:39:11,429 | WARN | Transport Connection to: tcp://10.12.20.4:11198
> failed: java.net.SocketException: Connection reset |
> org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
> Transport: tcp:///10.12.20.4:11198@61616
>
> Thanks in advance!
>
> Mit freundlichen Grüßen / Best regards Björn
>
>
>
>
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
