Skip to content
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

Atmosphere's HttpServletRequest.getRequestURI() must never return null in all circumstances #1246

Closed
ceefour opened this issue Aug 22, 2013 · 7 comments
Labels

Comments

@ceefour
Copy link
Contributor

ceefour commented Aug 22, 2013

Affects v1.0.13.

As the correct behavior is depended upon by on wicket-atmosphere https://issues.apache.org/jira/browse/WICKET-5282

@papegaaij noted that:

The NPE is caused by a null url returned by HttpServletRequest.getRequestURI. Atmosphere provides the implementation of this HttpServletRequest. It seems this implementation can return null under some circumstances, which is a violation of the spec. It is likely to be related to the 'Request is no longer valid' warning. This should probably be reported upstream.

If Atmosphere cannot handle getRequestURI() call properly, it should throw a "real" Exception instead of returning null.

@jfarcand
Copy link
Member

Which transport produce this NPE?

@ceefour
Copy link
Contributor Author

ceefour commented Aug 22, 2013

WebSocket using tomcat 7.0 on linux64.
Atmosphere-compat-tomcat7 is excluded from maven.
On Aug 22, 2013 7:55 PM, "Jeanfrancois Arcand" notifications@github.com
wrote:

Which transport produce this NPE?


Reply to this email directly or view it on GitHubhttps://github.com//issues/1246#issuecomment-23087578
.

@ceefour
Copy link
Contributor Author

ceefour commented Aug 27, 2013

Souvik Bhattacharya added a comment - 27/Aug/13 14:07

I am able to generate the error multiple time in my application. In my application I push through EventBus.post frequently(in every 3 seconds) and if second request come to @subscribe before the completion of first request then it's throwing error. If needed I can share my screen as well

@jfarcand
Copy link
Member

Looking today...

@jfarcand
Copy link
Member

jfarcand commented Sep 3, 2013

So far I can't reproduce tha issue using 1.0.16 :-( @ceefour can you try?

@jfarcand
Copy link
Member

jfarcand commented Sep 3, 2013

Ok I can see where it happens. Fix in process...

jfarcand added a commit that referenced this issue Sep 3, 2013
@ceefour
Copy link
Contributor Author

ceefour commented Sep 3, 2013

Thank you @jfarcand , so this will be in 1.0.17 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants