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 2B0DAD414 for ; Tue, 30 Oct 2012 15:30:16 +0000 (UTC) Received: (qmail 34933 invoked by uid 500); 30 Oct 2012 15:30:15 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 34465 invoked by uid 500); 30 Oct 2012 15:30:14 -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 33833 invoked by uid 99); 30 Oct 2012 15:30:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Oct 2012 15:30:13 +0000 Date: Tue, 30 Oct 2012 15:30:13 +0000 (UTC) From: "Christian Posta (JIRA)" To: dev@activemq.apache.org Message-ID: <428091112.44949.1351611013514.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (AMQ-4145) IntrospectionSupport does not convert from primitive to Wrapper classes appropriately MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Christian Posta created AMQ-4145: ------------------------------------ Summary: IntrospectionSupport does not convert from primitive to Wrapper classes appropriately Key: AMQ-4145 URL: https://issues.apache.org/jira/browse/AMQ-4145 Project: ActiveMQ Issue Type: Bug Components: Transport Affects Versions: 5.7.0 Reporter: Christian Posta In the TcpTransportServer#handleSocket method, we see that the default values for certain options (among them, trace, maxInactivityDuration, soTimeout, etc) are converted to their wrapper equivalents. However in IntrospectionSupport#convert(Object value, Class to) the conversion is not done properly. It always throws the IllegalArgumentException. Found in this message trail, although can be seen in other attempts to set variables directly on the transport server. Possibly related to changes for AMQ-3797 ?? -- 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