[Axapta-Knowledge-Village] Re: Deadlocks and try/retry

[Irving]

--- In Axapta-Knowledge-Village@yahoogroups.com, ontariodiver 
[EMAIL PROTECTED] wrote:

Hi

I have had a similar situation/experience.
If you use ttsbegin/ttscommit, then check where you are using them. 
When you use a tryCatch construction together with 
ttsbegin/ttscommit and get a deadlock, you go to the first catch 
(exception::deadlock) OUTSIDE the outermost ttscommit. If your catch 
(exception::deadlock) is inside the outermost ttscommit, you will 
never pick up the catch.

Regards

Irving

 Hi all,
 
 I have a situation where it seems that deadlocks are not picked up 
by 
 catch. Any ideas? It looks similar to this
 
 class 1:
 Try
 {
 method in class 2
 }
 catch (exception::deadlock)
 {
 retry
 }
 
 class 2 method:
 {
 step 1:insert sales lines into invoice
 step 2:update custom status field in new table
 }
 
 What is happening is Oracle reports a deadlock and processing 
stops 
 at step 1. I would have thought class 1 would catch the deadlock 
and 
 do a retry, but it doesn't. Do i have to do the try/retry in class 
2 
 as well?
 
 I am using Axapta 3.0 SP3.







Sharing the knowledge on Axapta.
Visit www.frappr.com/axapta for axapta friends. 
Yahoo! Groups Links

* To visit your group on the web, go to:
http://groups.yahoo.com/group/Axapta-Knowledge-Village/

* To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]

* Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
 

[Axapta-Knowledge-Village] Re: Deadlocks and try/retry

[ontariodiver]

Thanks for the responses. One other thing i came across is the retry 
field in Axapta configuration (in database tab) which allows me to 
increase the retry timer. 

The code seems ok, so my next assumption is that the retry is done 3 
times but too quickly and the lock is not yet released. I couldn't find 
anywhere in Axapta config to change the number of retries from 3 to a 
higher value so i am changing the retry timer from default to 2 seconds 
to see if it resolves the issue.

 I have a situation where it seems that deadlocks are not picked up by 
 catch. Any ideas? It looks similar to this
 








Sharing the knowledge on Axapta.
Visit www.frappr.com/axapta for axapta friends. 
Yahoo! Groups Links

* To visit your group on the web, go to:
http://groups.yahoo.com/group/Axapta-Knowledge-Village/

* To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]

* Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/