Return-Path: 
 <dev-return-168344-apmail-tomcat-dev-archive=tomcat.apache.org@tomcat.apache.org>
X-Original-To: apmail-tomcat-dev-archive@www.apache.org
Delivered-To: apmail-tomcat-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 40E3E18C42
	for <apmail-tomcat-dev-archive@www.apache.org>;
 Tue, 24 Nov 2015 22:53:55 +0000 (UTC)
Received: (qmail 20770 invoked by uid 500); 24 Nov 2015 22:53:54 -0000
Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org
Received: (qmail 20685 invoked by uid 500); 24 Nov 2015 22:53:54 -0000
Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@tomcat.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@tomcat.apache.org>
List-Post: <mailto:dev@tomcat.apache.org>
List-Id: <dev.tomcat.apache.org>
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Delivered-To: mailing list dev@tomcat.apache.org
Received: (qmail 20674 invoked by uid 99); 24 Nov 2015 22:53:54 -0000
Received: from mail-relay.apache.org (HELO mail-relay.apache.org)
 (140.211.11.15)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Nov 2015 22:53:54 +0000
Received: from asf-bz1-us-mid.priv.apache.org (nat1-us-mid.apache.org
 [23.253.172.122])
	by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with
 ESMTPS id 95CEB1A0182
	for <dev@tomcat.apache.org>; Tue, 24 Nov 2015 22:53:54 +0000 (UTC)
Received: by asf-bz1-us-mid.priv.apache.org (ASF Mail Server at
 asf-bz1-us-mid.priv.apache.org, from userid 33)
	id B367F60473; Tue, 24 Nov 2015 22:53:53 +0000 (UTC)
From: bugzilla@apache.org
To: dev@tomcat.apache.org
Subject: [Bug 58646] NullPointerException in InternalNioOutputBuffer under
 traffic related to <async-supported> config.
Date: Tue, 24 Nov 2015 22:53:53 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Tomcat 8
X-Bugzilla-Component: Catalina
X-Bugzilla-Version: 8.0.28
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: knst.kolinko@gmail.com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dev@tomcat.apache.org
X-Bugzilla-Target-Milestone: ----
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-58646-78-fjxrxv6HyL@https.bz.apache.org/bugzilla/>
In-Reply-To: <bug-58646-78@https.bz.apache.org/bugzilla/>
References: <bug-58646-78@https.bz.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bz.apache.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0

https://bz.apache.org/bugzilla/show_bug.cgi?id=58646

--- Comment #3 from Konstantin Kolinko <knst.kolinko@gmail.com> ---
1)
> Nov 23, 2015 CST 08:34:58.115 PM org.apache.coyote.http11.Http11NioProcessor
> INFO: Error parsing HTTP request header
> Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.

The above logging is controlled by
org.apache.juli.logging.UserDataHelper.CONFIG system property [1].

The log message was likely written by "catch (Throwable t)" clause in
AbstractHttp11Processor.process(). That is the only place where UserDataHelper
is used in a processor.

Unfortunately, it does not log the stacktrace, even with debug logging. It can
be improved with a code change in AbstractHttp11Processor.java line 1058,

-                            getLog().debug(message);
+                            getLog().debug(message, t);

(An easy test case: I have seen such messages when erroneously trying to
connect with https:// to a http connector.)


2)
I do not see thread names in your log. It is likely that the two errors are
related (being just 3ms apart), but it is unclear whether the two errors
occurred in the same thread.

It is known that org.apache.juli.OneLineFormatter writes the thread names.


3) Usual advice with misbehaving requests/responses is to add the following
property into conf/catalina.properties file:  [2]

org.apache.catalina.connector.RECYCLE_FACADES=true

It should make your configuration more robust against common mistake of
accessing Request/Response objects outside of their life cycle.


4) BTW, Tomcat 8.0.29 was released several hours ago. I think that it will be
announced tomorrow.


[1] http://tomcat.apache.org/tomcat-8.0-doc/config/systemprops.html#Logging
[2]
http://tomcat.apache.org/tomcat-8.0-doc/security-howto.html#System_Properties

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org