You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Rodrigo De Castro (JIRA)" <ji...@apache.org> on 2009/08/27 06:42:59 UTC
[jira] Commented: (WICKET-2437) Ajax requests are called serially
using only one channel (Channel busy - postponing...)
[ https://issues.apache.org/jira/browse/WICKET-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748258#action_12748258 ]
Rodrigo De Castro commented on WICKET-2437:
-------------------------------------------
It seems that a possible fix would be to specify the channel, at least for AjaxLazyLoadPanel, what would make these call execute in parallel. The channel could be the wicket ID for that panel. For the specific case of AjaxLazyLoadPanel, it may not matter if it's a stack or drop channel, as only one call is to be executed from that panel.
> Ajax requests are called serially using only one channel (Channel busy - postponing...)
> ---------------------------------------------------------------------------------------
>
> Key: WICKET-2437
> URL: https://issues.apache.org/jira/browse/WICKET-2437
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-extensions
> Affects Versions: 1.4.0
> Reporter: Rodrigo De Castro
> Assignee: Matej Knopp
>
> I have several lazy load panel that load DynamicImageResource objects. They are always loaded in serial mode. These are the debug messages:
> INFO: Initiating Ajax GET request on ../?wicket:interface=:3:tabpanel:panel:app_graph_panel:1:graph::IBehaviorListener:0:1&random=0.7774967316771
> INFO: Invoking pre-call handler(s)...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Received ajax response (2665 characters)
> After checking the code, it seems that every Ajax code in Wicket does not specify the channel when calling wicketAjaxGet. By doing that, all the requests end up in the default queue, being executed serially.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.