New Wicket release does not allow AJAX requests from disabled/non-visible components so I see "behavior not enabled; ignore call." warning in logs and "Access denied" on Page.
Hello I use Ajax Self Updating Timer Behavior on one tab and when switching to another tab I want to stop it.
I'm using Ajax Self Updating Timer Behavior for updating some progress bars with multiple file uploads (it's simulated with a Servlet), but when i try to upload for example 8 files the behaviour (which has been working and listening) stops listening for a while (the uploading continues but the listener isn't called , this listener is used for updating some panels with files uploading information). Why could a Ajax Self Updating Timer Behavior stops working for a while? Does the Wicket AJAX window in your browser show anything interesting?
The open "about:config" page and change the value of "max-connections-per-server" setting and try again.Also each tab supports contributors (you can add panels, fragments that can be auto refreshable).I think that will be better to stop/remove behaviors automatically on tab switch and not to force each contributor to do it. I mean to have the timer attached to a component that is a sibling of the tab.It first starts the behavior like this: INFO: Response parsed. INFO: Received ajax response (1627 characters) INFO: but when i upload many files it stops sending responses, like this: INFO: Response parsed. In particular I would look for "channel busy" messages, indicating that some other AJAX request is pending when a new one is triggered.Recently I've migrated from Wicket 1.4 to Wicket 1.5.
Best, Ernesto On Tue, Jun 8, 2010 at PM, Decebal Suiu Hello Ernesto, I resolved the problem.