[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 Remy Maucherat changed: What|Removed |Added Resolution|--- |FIXED

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #35 from Justin --- (In reply to Remy Maucherat from comment #34) > Created attachment 33247 [details] > Test patch > > With debug. Excellent, this patch has resolved the problem. I tested both HTTP and HTTPS. I

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 Remy Maucherat changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #33

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 Remy Maucherat changed: What|Removed |Added Attachment #33243|0 |1 is

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #27 from Justin --- Created attachment 33240 --> https://bz.apache.org/bugzilla/attachment.cgi?id=33240=edit Client exceptions for /trunk@1711734 Thanks for the patch! I exported, applied, built, ran. -- You

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #29 from Remy Maucherat --- The debug info is not there however. -- You are receiving this mail because: You are the assignee for the bug. - To

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 Remy Maucherat changed: What|Removed |Added Attachment #33234|0 |1 is

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 Justin changed: What|Removed |Added Attachment #33241|0 |1 is obsolete|

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #30 from Justin --- Created attachment 33242 --> https://bz.apache.org/bugzilla/attachment.cgi?id=33242=edit stderr for /trunk@1711734 with debug code Previous attachment was catalina.out. stdout has only: >

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 Justin changed: What|Removed |Added Attachment #32830|0 |1 is obsolete|

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #26 from Remy Maucherat --- Created attachment 33234 --> https://bz.apache.org/bugzilla/attachment.cgi?id=33234=edit Debug code If the exception does not occur, the code can be added to SecureNio2Channel. --

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #22 from Remy Maucherat --- Investigating another issue, it seems possible this one is caused by a timeout exception that gets swallowed, followed by a new read attempt. It is not really a Tomcat bug if the theory

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #23 from Justin --- (In reply to Remy Maucherat from comment #21) > This could use another trunk retest. Built, ran /trunk@1711357. Client now throws exception connected to non-SSL port too... 2015-10-29

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #25 from Remy Maucherat --- When I say in the channel read, I mean here for the debug code: org.apache.tomcat.util.net.Nio2Channel.read(Nio2Channel.java:133) -- You are receiving this mail because: You are the

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #24 from Remy Maucherat --- Hum, it's not trunk, it's branch 8 head. Anyway, the SSL thing was just coincidental, never mind. It would be nice in the channel read to capture the previous stack trace (throw and

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #21 from Remy Maucherat --- This could use another trunk retest. -- You are receiving this mail because: You are the assignee for the bug. - To

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 Yilong Li changed: What|Removed |Added CC|

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #19 from Robert M --- We are running into this same issue in our application and I just started to debug the problem. The one additional piece of information I can add is that I only get this error when I

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #20 from Mark Thomas --- (In reply to Robert M from comment #19) > We are running into this same issue in our application and I just started to > debug the problem. The one additional piece of information I can

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #17 from Mark Thomas ma...@apache.org --- (In reply to Remy Maucherat from comment #16) Without a relatively simple test case, I think this should be closed for the time being. There has to be some concurrency involved and the

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #18 from Justin cry...@yahoo.com --- Without a test case this is going to sit in the NEEDINFO state. Understandable. Regardless of whether there is a test case, there is a bug causing exceptions in Tomcat 8 latest. I may not be

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #14 from Justin cry...@yahoo.com --- Created attachment 32830 -- https://bz.apache.org/bugzilla/attachment.cgi?id=32830action=edit Exceptions -- You are receiving this mail because: You are the assignee for the bug.

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #15 from Justin cry...@yahoo.com --- Retested and reconfirmed problem with /trunk@1685924. Attached exceptions. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #16 from Remy Maucherat r...@apache.org --- Without a relatively simple test case, I think this should be closed for the time being. There has to be some concurrency involved and the framework really gets in the way. -- You are

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #13 from Mark Thomas ma...@apache.org --- Any update now 8.0.23 is released? Still waiting on a test case or steps to reproduce. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #12 from Remy Maucherat r...@apache.org --- Since there's no test case, it is worth retesting again [with trunk] since the previous fix caused a regression. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #11 from Justin cry...@yahoo.com --- (In reply to Remy Maucherat from comment #9) Also, testing on Tomcat trunk may not be useless. Same errors with Tomcat 8.0.21. When I build/run /trunk@1675728, I get: 23-Apr-2015 17:55:46.105

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #9 from Remy Maucherat r...@apache.org --- Also, testing on Tomcat trunk may not be useless. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #8 from Remy Maucherat r...@apache.org --- So the pending flag seems correct. The difference with non SSL is thus unexplained, and this needs a (simple) testcase. -- You are receiving this mail because: You are the assignee for

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #7 from Justin cry...@yahoo.com --- (In reply to Remy Maucherat from comment #6) Unrelated (but useful) fixes merged in Tomcat 8 as r1672626. I exported from ^/trunk@1672808, removed both throw ReadPendingException from

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #3 from Remy Maucherat r...@apache.org --- As part of the investigation I fixed some issues (r1672297) which will be backported to Tomcat 8, but I don't see any way for the read pending flag to have a bad state. Without some test,

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 Remy Maucherat r...@apache.org changed: What|Removed |Added OS||All --- Comment #1

[Bug 57799] MessageCreationException: Couldn't create SOAP message with Nio2 connector protocol

https://bz.apache.org/bugzilla/show_bug.cgi?id=57799 --- Comment #2 from Justin cry...@yahoo.com --- There are no such problems when dropping SSL. -- You are receiving this mail because: You are the assignee for the bug. - To