Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: dev@tomcat.apache.org
Subject: [Bug 57799] MessageCreationException: Couldn't create SOAP message
 with Nio2 connector protocol
Date: Mon, 02 Nov 2015 10:16:04 +0000
Message-ID: <bug-57799-78-o6fqYYiWEP@https.bz.apache.org/bugzilla/>
In-Reply-To: <bug-57799-78@https.bz.apache.org/bugzilla/>
References: <bug-57799-78@https.bz.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated
MIME-Version: 1.0

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

Remy Maucherat <remm@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW

--- Comment #33 from Remy Maucherat <remm@apache.org> ---
Ok, so this looks like legacy blocking code, which calls available() to be
smart.

Then it breaks because the input stream's available is really meant to be used
with isReady now (Servlet 3.1) and does a real async read. So maybe the
available action could use an added optional boolean parameter and do the async
read only if it is true (which would indicate Servlet 3.1 mode).

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