Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 080DF200B32 for ; Thu, 23 Jun 2016 21:32:13 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 06D5F160A59; Thu, 23 Jun 2016 19:32:13 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 74C36160A35 for ; Thu, 23 Jun 2016 21:32:12 +0200 (CEST) Received: (qmail 64708 invoked by uid 500); 23 Jun 2016 19:32:11 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 64698 invoked by uid 99); 23 Jun 2016 19:32:11 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Jun 2016 19:32:11 +0000 Received: from [192.168.23.9] (host86-152-79-120.range86-152.btcentralplus.com [86.152.79.120]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 1148E1A022A for ; Thu, 23 Jun 2016 19:32:10 +0000 (UTC) Subject: Re: Bug that spans tomcat and tomcat-native To: Tomcat Developers List References: From: Mark Thomas Message-ID: <2e6f56c1-32cb-28c6-3864-7425aa973069@apache.org> Date: Thu, 23 Jun 2016 20:32:02 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit archived-at: Thu, 23 Jun 2016 19:32:13 -0000 On 23/06/2016 20:28, Nate Clark wrote: > Hello, > > I encountered a performance issue when using the apr protocol. I > tracked it down to basically missing a piece of the integration with > openssl. I was able to fix the performance issue but it required a > change to both tomcat-native and tomcat. I was going to file a bug > with my patches but tomcat-native and tomcat are separate projects so > I was wondering the best way to handle that. File an issue in > tomcat-native and one in tomcat referencing the other bug? Or just use > this mailing list to discuss the issue? > > If you want details about the issue I am happy to provide them but > just didn't wan to duplicate explaining it in a bug and in an email > thread. To be honest, it doesn't really matter which product it is filed under. It is more important to get it filed. Even more so since a tc-native release is planned for tomorrow. Just file it under tc-native and someone will take a look. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org