After upgrade my APEX to 4.2.3 (remove 4.2.2 and fresh install 4.2.3) I have a lot of exception: AJAX call returned server error ORA-20876: Stop APEX Engine for chart5
But my charts display properly.
|0.04630||0.01950||Run APXWGT request||4|
|0.06582||0.02544||...Execute Statement: select round(avg(spalanie),1) value, round(max(spalanie)) max, round(min(spalanie)) lov, round(max(spalanie)) high from ( select spalanie, rank() over (order by data desc) as rank from autos_paliwo where id_auto = :autos_auto_id and spalanie is not null) where rank <= 10||4|
|0.09125||0.00182||Stop APEX Engine detected||4|
|0.09320||0.00010||......message: AJAX call returned server error ORA-20876: Stop APEX Engine for chart5.||4|
|0.09361||0.00009||......ora_sqlerrm: ORA-20876: Stop APEX Engine||4|
|0.09370||0.00048||......error_backtrace: ORA-06512: at "APEX_040200.WWV_FLOW", line 3253 ORA-06512: at "APEX_040200.WWV_FLOW_FLASH_CHART5", line 6941 ORA-06512: at "APEX_040200.WWV_FLOW_AJAX", line 293||4|
|0.09419||0.00052||...Execute Error Handling Callout defined on Page or Application Level||4|
|0.09471||0.00374||...Execute Statement: begin declare l_error wwv_flow_error_api.t_error; begin l_error := wwv_flow_error_api.g_error; wwv_flow_error_api.g_error_result := jau_apex_pkg.error_hand_fnc ( p_error => l_error ); end; end;||4|
|0.09845||0.00184||Stop APEX Engine detected||4|
|0.10028||0.00029||Stop APEX Engine detected||4|
I think you might have found a bug, there was a similar issue in APEX 4.1, Patrick Wolf suggested not to use the apex stop engine in APEX on demand processes, but I suspect, only suspect.. :-) that the APEX team might have done it anyway.
You can more information about this here:
It might be usefull if you can reproduce this on apex.oracle.com and notify the APEX dev team about this.
Thanks for reporting this error. As Joni has suggested, it is indeed a bug, which I've just logged (17540909). There's an unrequired call to stop the APEX engine, which is resulting in the misleading error message you see reported in the debug output. We'll ensure this issue is addressed in our next major release. In the meantime, as you've seen, your chart is displaying without issue so the error can be ignored.