Getting a deadlock while using api_datasource.executeQuery

Hello,

I'm having the same problem whenever two users are trying to access (read only) the same record. Here is a short abstract from the trace file -

Deadlock graph:
                                          ---------Blocker(s)--------  ---------Waiter(s)---------

Resource Name                             process session holds waits  process session holds waits
TX-00090004-00001836-00000000-00000000         74      27     X             74      27           X

session 27: DID 0001-004A-000050FA      session 27: DID 0001-004A-000050FA

Rows waited on:
  Session 27: obj - rowid = 0001897F - AAAYl/AAJAAAJUyAAR
  (dictionary objn - 100735, file - 9, block - 38194, slot - 17)

----- Information for the OTHER waiting sessions -----
----- End of information for the OTHER waiting sessions -----

Information for THIS session:

----- Current SQL Statement for this session (sql_id=7dqarh6jc9885) -----
UPDATE T_BDF_PANELDTLINS SET FIRSTROW_NR = :B3 , LASTROW_NR = :B2 WHERE BDF_PANELDTLINS_OID = :B1
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
0x721e3830      1112  package body FORMSPIDER.BDF_PANELDTLINS_API
0x7c838728       711  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
0x802ca640         1  anonymous block

Please help!

Thanks, Ilia

Hi Everyone,

We identified the bug and applied a solution. The solution is being tested by Quality Assurance. All of the deadlock issues seem to be related to each other. We were able to reproduce one of the deadlock errors by making a grid to show the next page of rows using the nextPage button and then selecting a row in the grid. Selecting a row caused the deadlock. (The grid must have a selection changed event). We did not even need a second user for this. The deadlock happened even if the application was used by one user.

So, it is pretty safe to say that this issue will be fixed in Formspider 1.10. We will send out a hot fix to our professional support customers as soon as the fix is approved by Quality Assurance.

Kind Regards, Yalim

Hi Yalim,

I'm using 1.10.1 and I get this error when I use pagination on a grid, in fact this is why I found this topic. The GUI model consists of a readonly grid + a toolbar which includes a clasical pagination panel. When a user double click a record in grid(or press an Edit button in toolbar) an edit record modal dialog is popuped. Do nothing but close this dialog(visible='N' and requery datasource). Do this two or three times and this deadock exception occurs.

Just comment out the inclusion of pagination panel in toolbar and you're free of deadlock exception.

Hope this info is useful to you!

Cezar