Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 3 Apr 2013 11:17:15 +0000 (UTC)
From: "Christoffer Sawicki (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12640491.1364987720888.98720.1364987835521@arcas>
In-Reply-To: <JIRA.12640491.1364987720888@arcas>
References: <JIRA.12640491.1364987720888@arcas>
Subject: [jira] [Created] (AMQ-4433) Socket parameters are not validated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Christoffer Sawicki created AMQ-4433:
----------------------------------------

             Summary: Socket parameters are not validated
                 Key: AMQ-4433
                 URL: https://issues.apache.org/jira/browse/AMQ-4433
             Project: ActiveMQ
          Issue Type: Bug
            Reporter: Christoffer Sawicki
            Priority: Minor


Connect parameters are validated in every transport factory with a statement like this:

{noformat}
if (!options.isEmpty()) {
  throw new IllegalArgumentException("Invalid connect parameters: " + options);
}
{noformat}

Socket parameters (i.e. connect parameters prefixed with {{socket.}}) are however never validated.

They are put away at

{noformat}
SslTransportFactory(TcpTransportFactory).compositeConfigure(Transport, WireFormat, Map) line: 85	
{noformat}

and then set at

{noformat}
SslTransport(TcpTransport).initialiseSocket(Socket) line: 428
{noformat}

where there is no check that {{socketOptions}} is empty after the call.

I've attached a patch that rectifies this.

--
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