I recently implemented lockType=VFP in my ColdFusion system that uses your DBF driver. This seemed to clear up most of the thread conflicts I was seeing. However, today we once again found a thread conflict (see below).
It looks as if it might be a table the driver is accessing that is not adhering to the lockType = VFP setting. The challenge seems to be specifically when two users run queries very close to the same time, especially if one table is doing an update.
Do you have any suggestions how we can prevent this Thread conflict?
The queries shown here were run within seconds of one another. One operation seems to be accessing an "i" resource that the other operation has already opened, the other operation then tries to access an "at" resource that the first thread is using (the log entries are output from Fusion Reactor):
Thread ID: 0xbb (187)
Thread Name: jrpp-24
Priority: 5
Hashcode: 14951475
State: BLOCKED
"jrpp-24" prio=5 waiting for monitor entry
com.hxtt.sql.dbf.i.a(null:???)
- waiting on <0xb5e5d7> (a com.hxtt.sql.dbf.i held by thread 186, jrpp-23)
---------------------------------------------------------
Thread ID: 0xba (186)
Thread Name: jrpp-23
Priority: 5
Hashcode: 29078772
State: BLOCKED
"jrpp-23" prio=5 waiting for monitor entry
com.hxtt.sql.at.a(null:???)
- waiting on <0xa329dc> (a com.hxtt.sql.at held by thread 187, jrpp-24)
com.hxtt.sql.at.a(null:???)
Thanks for your help.
|
>Do you have any suggestions how we can prevent this Thread conflict?
Thanks for your order. Please download the latest package.
|
I downloaded and installed the latest release of your DBFv4.1 driver.
The thread conflict is still occuring. Why is it happening? How can I prevent it?
Thx
Paul Hall
|
|
Please send us the detailed block error stack report.
|
Main
webmaster@hxtt.com