https://issues.apache.org/bugzilla/show_bug.cgi?id=56640
Konstantin Kolinko <knst.koli...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #1 from Konstantin Kolinko <knst.koli...@gmail.com> ---
1. Exact version of Tomcat where this is observed = ?
2. Full stacktrace when the issue happens = ?
You can mask your own components names.
I'd guess that you may have non-async capable filters there.
3. Run with a debugger [1] and look where the "async not supported" condition
is coming from.
[1] http://wiki.apache.org/tomcat/FAQ/Developing#Debugging
Without a reproducing example it is up to you to provide necessary information.
> Note that there is a websocket connection active on the AtmosphereServlet
> when > the issue arise (I do see the WsFilter in the stack trace)
No. (WsFilter is always there when you have websocket
ServletContainerInitializer active. Details are discussed in issue 55855. You
may get rid of those by removing *websocket* JARs from Tomcat or by some
configuration.)
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
