tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol
Date Mon, 02 Nov 2015 10:16:04 GMT

Remy Maucherat <> changed:

           What    |Removed                     |Added
             Status|NEEDINFO                    |NEW

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

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:
For additional commands, e-mail:

View raw message