-
-
Notifications
You must be signed in to change notification settings - Fork 747
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
java.lang.NullPointerException at org.apache.wicket.markup.html.form.Form.onComponentTag(Form.java:1520) during Atmosphere eventbus.post() if using WebSockets #1002
Comments
Can you try 1.0.13? I think this issue has been reported already. If you can find what in Atmosphere is broken that will help...trace the AtmosphereResponse.getXXX, I suspect the regression is from there. |
The issue was already reported here : https://issues.apache.org/jira/browse/WICKET-5084 |
Alhamdulillah I've upgraded the nginx on our server to 1.3.15, so now it fully supports WebSockets (not just comet)... and so far testing is working.. but still there's this issue. But I know if it still problematic I can just revert back to disabling WebSockets, simple :) Here's a demo : http://www.stg.cintalama.com/product/fgn2 then open a different browser (a different tab won't work..not sure why (?) is it Atmosphere issue or Wicket issue? ) on that page. now sign in (try via Facebook) then comment. your comment should appear instantly on the other browser from Indonesia (which is ~400ms latency to our server) the it takes about 1 sec to update. which is good :-) quite happy ^_^ now I can sleep :p Thanks @jfarcand :) I'll let you know when I've tried 1.0.13-SNAPSHOT.... |
I'm 100% sure this issue has been fixed by #949 when I look at the code. So marking as fixed. |
I can't build 1.0.13-SNAPSHOT. Is there a prebuilt repo ?
|
But since I only need atmosphere-runtime, which was built. So I tried and yes, it works ! So this issue is indeed resolved. Thank you ! However I'm still curious why Maven fails.... |
Originally reported here: https://issues.apache.org/jira/browse/WICKET-5134
I think this is Atmosphere bug because it works well with 1.0.8 and 1.0.9. But buggy with 1.0.10, 1.0.11, and 1.0.12.
If using WebSockets, it always throws the NPE below:
Another stacktrace:
This bug is always reproducible in my configuration.
It doesn't occur if comet/long-polling is used instead of websockets. Which means setting below will not trigger the bug:
The text was updated successfully, but these errors were encountered: