Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D34D0D661 for ; Tue, 26 Feb 2013 22:14:13 +0000 (UTC) Received: (qmail 31132 invoked by uid 500); 26 Feb 2013 22:14:13 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 31082 invoked by uid 500); 26 Feb 2013 22:14:13 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 30959 invoked by uid 99); 26 Feb 2013 22:14:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 22:14:13 +0000 Date: Tue, 26 Feb 2013 22:14:13 +0000 (UTC) From: "Jim Gomes (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMQNET-415) Client with wrong credentials overloads server when using failover MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-415. ------------------------------ Resolution: Fixed > Client with wrong credentials overloads server when using failover > ------------------------------------------------------------------ > > Key: AMQNET-415 > URL: https://issues.apache.org/jira/browse/AMQNET-415 > Project: ActiveMQ .Net > Issue Type: Bug > Components: ActiveMQ, NMS > Affects Versions: 1.5.6 > Environment: ActiveMQ Broker 5.6.0 > Reporter: Jim Gomes > Assignee: Jim Gomes > Priority: Minor > Labels: authentication, failover > Fix For: 1.5.7 > > > If the ActiveMQ broker has been secured to enforce login credentials, the NMS client will continually attempt to authenticate against it if it is using the failover protocol. > Steps to Reproduce: > ---------------------- > 1. Configure the broker to require login credentials for connections. > 2. Configure the NMS client to use failover mode. > 3. Configure the NMS client with incorrect login credentials. > 4. Attempt to connect the NMS client to the server. > Results: > ---------------------- > The client reattempts login continuously without backing off, and has a significant impact on the performance of the server. > Expected: > ---------------------- > The client should not enter failover, because it never successfully connected, and it would never expect to connect. > Notes: > ---------------------- > This was experienced using the OpenWire client, but a similar bug may exist in the STOMP client's failover code. > The broker may also want to protect itself against this, as this is an easy attack vector for a DDoS. Just a couple of clients attempting to login with invalid credentials can dramatically impact the server's performance, not just the broker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira