how to debug "LPX-00664: VM Node-Stack overflow" ?

Question

query would yield 155331 rows (for later Excel-download). Maybe one of those query-rewrite errors?

ERROR : An error occured while initializating Panel 26129. 
ORA-06512: in "XDB.DBMS_XSLPROCESSOR", Zeile 392
ORA-06512: in "XDB.DBMS_XSLPROCESSOR", Zeile 418
ORA-06512: in "FORMSPIDER.BDF_RESPONSE_MNG", Zeile 3025
ORA-06512: in "FORMSPIDER.BDF_RESPONSE_MNG", Zeile 3064
ORA-06512: in "FORMSPIDER.BDF_RESPONSE_MNG", Zeile 3144
ORA-06512: in "FORMSPIDER.BDF_PANELDTL_MNG", Zeile 403
ORA-06512: in "FORMSPIDER.P_26307", Zeile 77
ORA-06512: in "FORMSPIDER.P_26307", Zeile 430
ORA-06512: in "FORMSPIDER.P_26129", Zeile 124
ORA-06512: in "FORMSPIDER.P_26129", Zeile 198
ORA-06512: in Zeile 1
ORA-06512: in "FORMSPIDER.BDF_PANEL_MNG", Zeile 125

ERROR : in_panel_oid :26129(init) errmsg : ORA-31011: XML-Parsing nicht erfolgreich
ORA-19202: Fehler bei XML-Verarbeitung 
LPX-00664: VM Node-Stack overflow. aufgetreten

Accepted Answer

Hi,

As your query returns 155k rows, Formspider tries to send all to client into one little grid. While converting this big data to XML, apparently this issue comes about. However, as you can tell showing this much data on a grid at once is not the best idea. Therefore, we can suggest you using "Infinite Scroll" or "Paging" for your datasource instead of "Fetch All".

The other thing regarding seeing the altered query: what you want to see is a fairly low-level Formspider-specific query. Thus, this wouldn't be very comprehensible for many people if it's not confusing. However, seeing these queries could be helpful on some specific issues as you rightly pointed out. To overcome, we may think to write down this information as a debug log into a debug table. Thank you very much for your feedback.

Regards,

Answer 2

0	Hi, Can you please share the query of your datasource? Regards link answered 10 Jan '15, 06:49 Serdar ♦♦ 100k●4 accept rate: 13%

Answer 3

select LZ_LK_ID,LZ_TEXT,LZ_LB_ID,LZ_MENGE_START,LZ_MENGE_ENDE,LZ_TAGE,LZ_BASIS,LZ_XAUS,LZ_DLBMENGE,LZ_UMSCHLAG
from LK_ZEILEN, lagerbestaende, artikel, lager
where lb_id= lz_lb_id
 and at_id= lb_at_id
and lg_id =lb_lg_id
and lz_lk_id = :lkid

This is a demo app which I'm trying to use to push FormSpider at my biggest customer. The LKID is the Tasknumber which stores the background data (start-date, end-date, warehouse-id, item-group-id) for which a batch job has calculated item-stocking key figures (avg. amount in stock, throughtput, etc..) There currently is only one LK_ID value. LK_Zeilen holds ~155.000 rows for that single task ID. I'd like to show the first couple of them LK_ZEILEN. The user (poweruser - decisionmaker) wants to download the rows into excel. The Datasource is default, e.g. "Fetch ALL", "Max. Row Fetch Size = All" I'm afraid that I have hit another case where FormSpider framed my query for pagination purposes.

I really would appreciate an info textarea where FormSpider shows at design time what it'll do to my query during runtime.

how to debug "LPX-00664: VM Node-Stack overflow" ?

Follow this question

Related questions