Andrew,

<< I know that  I sent it because I thought it might help you see where
the problem was. Also, I wanted to point out that the lock retry and wait
time setting were not being respected, due to the fact that it took 2 1/2
min to come back with an error message.  Shouldn't the max time be 1500ms
(100ms X 15 retries)? >>

It's a different type of lock altogether.  What you're looking at is the row
lock parameters, and this lock issue is a read/write table lock, which has a
much higher retry count and wait time.

--
Tim Young
Elevate Software
www.elevatesoft.com

Andrew,

<< Or not...here it is. >>

Thanks, it appears to be the same issue.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Andrew,

<< I know that  I sent it because I thought it might help you see where
the problem was. Also, I wanted to point out that the lock retry and wait
time setting were not being respected, due to the fact that it took 2 1/2
min to come back with an error message.  Shouldn't the max time be 1500ms
(100ms X 15 retries)? >>

It's a different type of lock altogether.  What you're looking at is the row
lock parameters, and this lock issue is a read/write table lock, which has a
much higher retry count and wait time.

--
Tim Young
Elevate Software
www.elevatesoft.com


Ok, I didn't realize it was a different lock.  How do I control that so my app doesn't
"freeze" for such a long time?  Or would this not normally happen?

Also, when do you think there will be an update to fix this problem?

Thanks!
Andrew

Andrew,

<< Ok, I didn't realize it was a different lock.  How do I control that so
my app doesn't "freeze" for such a long time?   Or would this not normally
happen? >>

It's a bug so no, it normally would not happen.

<< Also, when do you think there will be an update to fix this problem? >>

Sometime between Monday to Wednesday of next week.

--
Tim Young
Elevate Software
www.elevatesoft.com