I've discussed this with the author of the Atmosphere Framework, and according to him, this is a bug in Jetty 7, which surfaces due to changes in Atmosphere. The problem is that the websocket request gets recycled by Jetty, even though it is still open.
Best regards, Emond On Mon, Jul 16, 2012 at 6:04 PM, Martin Grigorov <[email protected]> wrote: > I cannot log to Jira for some reason so I'll comment here ... > > > On Mon, Jul 16, 2012 at 4:42 PM, Emond Papegaaij (JIRA) <[email protected]> > wrote: >> >> [ >> https://issues.apache.org/jira/browse/WICKET-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415110#comment-13415110 >> ] >> >> Emond Papegaaij commented on WICKET-4656: >> ----------------------------------------- >> >> This seems to be caused by a bug in Jetty 7.6.3 (which is used for the >> examples), Jetty 8.1.3 works fine. > > I'm not sure that this is really a bug in Jetty. There is no change in > Jetty version since beta2 where this example seems to be worked. > The only change is the upgrade of Atmosphere. It seems there is > backward incompatible change. > >> >>> Atmosphere example doesn't work due to missing 'page' when creating >>> AjaxRequestTarget >>> ------------------------------------------------------------------------------------- >>> >>> Key: WICKET-4656 >>> URL: https://issues.apache.org/jira/browse/WICKET-4656 >>> Project: Wicket >>> Issue Type: Bug >>> Components: wicket-atmosphere >>> Affects Versions: 6.0.0-beta3 >>> Reporter: Martin Grigorov >>> Assignee: Emond Papegaaij >>> >>> Testing beta3 revealed this error when trying to use Wicket Atmosphere: >>> ERROR - DefaultExceptionMapper - Unexpected error occurred >>> java.lang.IllegalArgumentException: Argument 'page' may not be null. >>> at org.apache.wicket.util.lang.Args.notNull(Args.java:41) >>> at >>> org.apache.wicket.ajax.AjaxRequestHandler.<init>(AjaxRequestHandler.java:111) >>> at >>> org.apache.wicket.protocol.http.WebApplication$DefaultAjaxRequestTargetProvider.get(WebApplication.java:956) >>> at >>> org.apache.wicket.protocol.http.WebApplication$DefaultAjaxRequestTargetProvider.get(WebApplication.java:949) >>> at >>> org.apache.wicket.protocol.http.WebApplication.newAjaxRequestTarget(WebApplication.java:800) >>> at >>> org.apache.wicket.atmosphere.AtmosphereRequestHandler.respond(AtmosphereRequestHandler.java:65) >>> at >>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:814) >>> at >>> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64) >>> .... >> >> -- >> This message is automatically generated by JIRA. >> If you think it was sent incorrectly, please contact your JIRA >> administrators: >> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa >> For more information on JIRA, see: http://www.atlassian.com/software/jira >> >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com
