Re: how to fix this error in wicket app
Have you ever fixed this problem? We are seeing the same issues with our application. Thijs On 28-11-2012 0:03, saty wrote: continued from above... /wicket:panel/div div class=imxt-a imxt-nowrap0/div div class=imxt-a imxt-nowrap0.2001/div div class=imxt-a imxt-nowrap/div div class=imxt-a imxt-nowrap0.4771/div div class=imxt-a imxt-nowrap/divdiv wicket:id=item class=imxt-a imxt-nowrapwicket:panel ./wicket/resource/com.apollo.pricematrix.web.pricing.priceview.PriceIndicatorPanel/up-ver-1354055622963.gif?antiCache=1354056400520 nbsp; 0.2001 /wicket:panel/div div wicket:id=item class=imxt-a imxt-nowrapwicket:panel xmlns:wicket=http://wicket.apache.org; div class=imxt-select-container input type=checkbox wicket:id=checkbox onchange=return false class=imxt-select id=checkbox3e2/ /div /wicket:panel/div div class=imxt-a imxt-nowrap21/div div wicket:id=item class=imxt-a imxt-nowrapwicket:panel div wicket:id=label id=label43d3MO LIBOR IR CAP 8% 6/13/div /wicket:panel/div div class=imxt-a imxt-nowrap/divdiv class=imxt-a imxt-nowrapUSD/div div wicket:id=item class=imxt-a imxt-nowrapwicket:panel div wicket:id=detailsWindow id=detailsWindow43e style=display:nonewicket:panel xmlns:wicket=http://wicket.apache.org; /wicket:panel/div span wicket:id=label id=label43f # 1 ./wicket/resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/indicator-ver-1352317451197.gif /wicket:panel/div div class=imxt-a imxt-nowrap-0.0807/div div wicket:id=item class=imxt-a imxt-nowrapwicket:panel ./wicket/resource/com.apollo.pricematrix.web.pricing.priceview.DayChangePriceIndicatorPanel/up-ver-1354055622963.gif?antiCache=1354056400520 nbsp; 0.0807 /wicket:panel/div div class=imxt-a imxt-nowrap0/div div class=imxt-a imxt-nowrap0.0807/div div class=imxt-a imxt-nowrap/div div class=imxt-a imxt-nowrap0./div div class=imxt-a imxt-nowrap/divdiv wicket:id=item class=imxt-a imxt-nowrapwicket:panel ./wicket/resource/com.apollo.pricematrix.web.pricing.priceview.PriceIndicatorPanel/up-ver-1354055622963.gif?antiCache=1354056400520 nbsp; 0.0807 /wicket:panel/div /wicket:panel /div /div /fieldset/div div class=imxt-bottom-toolbar-container wicket:panel xmlns:wicket=http://wicket.apache.org; div class=imxt-navigator-toolbar style=overflow: hidden; _height: 1%; padding-right: 0.5em; padding-left: 0.5em; div style=float: left; padding-top: 0.2em; div wicket:id=navigationLabelShowing 1 to 78 of 78/div /div div style=float: right; div wicket:id=navigator id=navigator234wicket:panel div class=imxt-paging-navigator emlt;lt;/em em/em em1/em em/em emgt;gt;/em /div /wicket:panel/div /div /div /wicket:panel /div /div /wicket:panel/div]]/componentheader-contribution encoding=wicket1
Re: how to fix this error in wicket app
That's great! Thanks On 16/1/13 17:25, saty wrote: Yes, this has been fixed in wicket 6.4.0 See below for more on this fix. http://apache-wicket.1842946.n4.nabble.com/understanding-ajax-response-td4654310.html#a4654715 -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-fix-this-error-in-wicket-app-tp4653954p4655431.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: how to fix this error in wicket app
As I play with this to find a solution, I notice few interesting things, that
I am hoping someone would be able to decipher into root cause if this issue
and a fix.
I have a data grid on my page with several filters drop downs and each of
them are basically making the grid to refresh (with filtered data).
Below is the event handler for each filter:
OnChangeAjaxBehavior onChangeAjaxBehavior = new OnChangeAjaxBehavior()
{
private static final long serialVersionUID = 1L;
@Override
protected void onUpdate(AjaxRequestTarget target)
{
grid.setCurrentPage(0);
target.add(grid);
}
}
The grid is comprised of several plain data cells but some of the columns
have IndicatingAjaxLink to launch a model window that displays further
details which are implemented as another panel with another data grid.
I notice that if I remove all these model window cells, everything seems to
working fine.
If you see something here, please let me know.
The data grid that we are using is
com.inmethod.grid.datagrid.DefaultDataGrid
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/how-to-fix-this-error-in-wicket-app-tp4653954p4654271.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: how to fix this error in wicket app
My problem has become worse now, earlier i only had issues selecting all rows
on grid but now anything that refreshes the data table grid is giving me
error. Any help would be appreciated. I dont have too many Ajax calls in the
grid, i am not sure what causes the recursion that it is complaining.
see this on Firefox, debug
[14:37:28.174] Wicket.Ajax: FunctionsExecuter.processNext: Error
on wicket debug:
var submitStateCallback = function (columnState) {
var attrs =
{u:./?5-6.IBehaviorListener.1-homePageTabs-panel-pricingPropertyTabs-panel-fitlerGridPanel-snapshotGridForm-snapshotGrid,c:snapshotGrid827,dep:[function(attrs){return
{'columnState': attrs.columnState}}]^};
var params = {};
attrs.ep = params;
Wicket.Ajax.ajax(attrs);
}
InMethod.XTableManager.instance.register(snapshotGrid827, columns,
submitStateCallback);
})();
]]/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate
encoding=wicket1/evaluateevaluate
encoding=wicket1/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluateevaluate/evaluate/ajax-response
ERROR: Wicket.Ajax.Call.processEvaluation: Exception evaluating javascript:
InternalError: too much recursion, text:
Re: how to fix this error in wicket app
Hi,
Do you have idea how many target.appendJS/prependJS calls do you have for
this Ajax request ?
The error says that you have a lot of those in the ajax-response.
If you look closely at
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/ajax/res/js/wicket-ajax-jquery.js#L118
you'll
see that this method works with recursion until its 1000th call, then it
uses setTimeout(callMySelf) to restart the recursion in a new stack frame.
Few months ago I did some testing:
https://issues.apache.org/jira/browse/WICKET-4675?focusedCommentId=13426609page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13426609
and
Firefox 14 was able to do ~5200 recursive calls before filling the stack.
Which version of Firefox do you use ?
On Fri, Nov 16, 2012 at 8:51 PM, saty satya...@gmail.com wrote:
I have this additional info on wicket debug panel.
ERROR: Wicket.Ajax.Call.processEvaluation: Exception evaluating javascript:
InternalError: too much recursion, text:
Wicket.Ajax.ajax({f:forma,u:./?1-3.IBehaviorListener.1-homePageTabs-panel-pricingPropertyTabs-panel-fitlerGridPanel-snapshotGridForm-snapshotGrid-form-bodyContainer-body-row-147,e:click,c:id147682,pre:[function(attrs){return
InMethod.XTable.canSelectRow(attrs.event);}],ad:true,m:POST,dep:[function(attrs){return
{'column': Wicket.$(attrs.c).imxtClickedColumn}}]});
ERROR: FunctionsExecuter.processNext: InternalError: too much recursion
ERROR: FunctionsExecuter.processNext: [Exception... Component returned
failure code: 0x80004002 (NS_NOINTERFACE) [nsIObserverService.addObserver]
nsresult: 0x80004002 (NS_NOINTERFACE) location: JS frame ::
resource:///components/ConsoleAPI.js :: CA_init :: line 57 data: no]
I dont know why its complaining about too much recursion, if there is a way
to increase the limit, any help would be appreciated, thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/how-to-fix-this-error-in-wicket-app-tp4653954p4653956.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com http://jweekend.com/
how to fix this error in wicket app
[12:52:52.119] Wicket.Ajax: FunctionsExecuter.processNext: [Exception... Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsIObserverService.addObserver] nsresult: 0x80004002 (NS_NOINTERFACE) location: JS frame :: resource:///components/ConsoleAPI.js :: CA_init :: line 57 data: no] @ http://localhost:9080/wicket/resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-ajax-jquery-debug-ver-1352317451197.js:125 Subsequently this error means no Ajax events are processed unless page is refreshed. Channel '0' is busy - scheduling the callback to be executed when the previous requ Thanks -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-fix-this-error-in-wicket-app-tp4653954.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: how to fix this error in wicket app
On Fri 16.11.2012 10:51, saty wrote: I have this additional info on wicket debug panel. [ ... ] ERROR: FunctionsExecuter.processNext: InternalError: too much recursion ERROR: FunctionsExecuter.processNext: [Exception... Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsIObserverService.addObserver] nsresult: 0x80004002 (NS_NOINTERFACE) location: JS frame :: resource:///components/ConsoleAPI.js :: CA_init :: line 57 data: no] Seeing the last three lines, I would guess that this not a Wicket bug. It rather seems to be a Firefox Developer extension bug. -Timo - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
