-
-
Notifications
You must be signed in to change notification settings - Fork 754
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPE with Jetty 9.3 #2154
Comments
Which specific version of Jetty 9.3? This doesn't appear to be an Upgrade Request (for HTTP/1.1 -> WebSocket). Is it a HTTP POST request? (or something else?) |
Curious, I thought I tested 9.3.0 and 9.3.9.M1 but it turns out that this works with 9.3.0 but does not work with 9.3.9.M1. Let me track down what works and what does not |
9.3.1.v20150714 works |
Right, we might be in the wrong issue tracker as it seems to be reproducible without Atmosphere also although it was encountered when using websockets. It's a normal POST request which fails during getParameter |
Added test to jetty/jetty.project#543, will close this as it seems unrelated to Atmosphere |
Not convinced this is a Jetty issue. The test case provided by @Artur- does not fail for me. |
This is a followup of #1998. I am unable to get Vaadin + Atmosphere 2.4.3 + Jetty 9.3 websockets to work properly together. Before #1998 was fixed, there was an NPE in getContentType. Now I see that initially the app works as expected, including websockets (both JSR-356 and native). However, after refreshing not one but two times, I see the following NPE
The same NPE then occurrs on all following refreshes. The exception is that if you open the same URL rapidly in multiple tabs, in that case one or a few tabs will open the app. Seems a bit like the request object somehow ends up in an invalid state and is reused for the following connections.
Test project: https://github.com/Artur-/push-jetty93 (mvn clean install jetty:run)
The text was updated successfully, but these errors were encountered: