Hi, One thing that I don't understand in your code: how the async servlet is notified to release its resources (async contexts and executor) when the user navigates to another Wicket page?
Have you considered using Wicket Native WebSocket or Wicket-Atmosphere instead of this custom solution ? Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Apr 22, 2016 at 11:11 PM, fachhoch <[email protected]> wrote: > I enabled log info org.apache.wicket.protocol.http.RequestLogger, logs show > different url in case of error. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/open-connection-to-async-servlet-and-initiate-wicket-ajax-request-results-ComponentNotFoundException-tp4674357p4674379.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
