If a scheduled (in Wicket.Channel) callback fails for some reason (in my case because WicketAjaxDebug was not yet loaded) then the 'busy' flag for the channel remains 'true' until the page is reloaded.
It would be better to try/catch the execution of the callback and reset the flag in case of an error.
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||1.4.17 [ 12316219 ]|
|Fix Version/s||1.5-RC3 [ 12316220 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|11h 8m||1||Martin Grigorov||24/Mar/11 21:03|