Formspider Engine => "ORA-00060: deadlock detected while waiting for resource"

Question

Hello folks,

when switching app into stateless app, a below error started to occur in most of our forms.

Are we doing something incorrectly?

ERROR : 05-10-2015 10:21:16  (  ) :  =>  :  (  ) =>  Formspider Engine => "ORA-00060: deadlock detected while waiting for resource"

Thanks, Tomas

Answer 1

0

Hi Tomas,

Do you have any information regarding where the error is happening? Package, Line number?

Kind Regards,
Yalim

link

answered 05 Oct '15, 09:07

Yalim Gerger ♦♦
1.8k●5
accept rate: 15%

Hi Yalim,

unfortunately I don't have more information. It occurs when api_application.setStateful(in_stateful_yn=>'Y'); and at the end of procedure which finishes correctly.

Any idea how to get more info ?

Tomas

(23 Oct '15, 17:14) Tomeo

Actually this error starts to occur when a paging navigation button (in toolbar) is pressed and grid row changes. This error stops to display when in other form (screen) a different grid row data are refreshed.

(23 Oct '15, 17:23) Tomeo

A problem is that it occurs across whole application. Please see this short video example, when once a datasource paging is being used an error occurs until changing row in different datasource:

http://firma.agtransport.cz:8484/agftp/2015-10-23_2316.swf

(23 Oct '15, 17:34) Tomeo

And one more info, when I change application status to api_application.setStateful(in_stateful_yn=>'N'); then all works fine.

Please suggest what could be incorrectly set?

(23 Oct '15, 17:37) Tomeo

Answer 2

0

Hello folks,

any idea regarding this issue?

Removing pagination is not an option in this case.

Thanks, Tomas

link

answered 29 Oct '15, 05:12

Tomeo
162●16●70
accept rate: 3%

Hi Tomas,

No, nothing new on this issue yet.

Kind Regards,
Yalim

(30 Oct '15, 05:02) Yalim Gerger ♦♦

Hi Yalim,

Were you able to simulate this issue?

Is there any workout?

Thanks, Tomas

(30 Oct '15, 08:42) Tomeo

Answer 3

0	I'm having the same issue with pagination. Please advise. Thanks, Ilia link answered 05 Nov '15, 17:16 Ilia Sazonov 120●5●14 accept rate: 0%

Answer 4

Maybe this information from the trace log will help?

----- Current SQL Statement for this session (sql_id=0c0hsv4awnczs) -----
UPDATE T_BDF_PANELDTLINS SET SELECTEDRECORDS_TX = BDF_SUPPORT.CHECKNULL(:B2 ) WHERE BDF_PANELDTLINS_OID =     :B1
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
0x721e3830       514  package body FORMSPIDER.BDF_PANELDTLINS_API
0x721e3830       521  package body FORMSPIDER.BDF_PANELDTLINS_API
0x721e3830       526  package body FORMSPIDER.BDF_PANELDTLINS_API
0x7bc4cde0       136  package body FORMSPIDER.BDF_PANELDTL_MNG
0x7c838728       475  package body FORMSPIDER.BDF_RESPONSE_MNG
0x7c838728      2673  package body FORMSPIDER.BDF_RESPONSE_MNG
0x7d931798      1760  package body FORMSPIDER.BDF_ENGINE
0x7d931798      2164  package body FORMSPIDER.BDF_ENGINE
0x7d931798      2448  package body FORMSPIDER.BDF_ENGINE
0x801c23e0         1  anonymous block
==================================================

Thanks, Ilia