If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Contradicting Behaviour of LockTimeOut.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-04-03, 01:24
nitingm nitingm is offline
Registered User
 
Join Date: Jul 2003
Location: Austin, TX, USA
Posts: 278
Contradicting Behaviour of LockTimeOut.

Hi Sathyaram/Marcus,

First and foremost many thanks for your guidance, my problem has been resolved as I have moved to UR though personally I would have prefered to downgrade to RS with DB2_RR_TO_RS=YES and a good value for the MaxLocks and LockList Parameters.

However I found one contradicting behaviour with the LockTimeout variable with the definition of it's default value of -1 as given in the help. The value -1 says that it is infinite wait and 0 means no wait, however what I observed is that when I had set the same to -1 my transactions were being rolled back because of a timeout and on the contrary when I set the value to approx 45 secs the transactions went through, so does it mean that -1 is not infinite wait?? My observation seems so.

Please explain this to me. Any input from the other experts would also be valuable.

Regards

Nitin.

P.S. The detailed history of this case can be obtained from my previous posts.
Reply With Quote
  #2 (permalink)  
Old 11-05-03, 11:24
sathyaram_s sathyaram_s is offline
Super Moderator
 
Join Date: Aug 2001
Location: UK
Posts: 4,534
Re: Contradicting Behaviour of LockTimeOut.

-1 is infinite lock-wait ...

You will have to take snapshots and have event monitors on if you wish to analyze the actual cause of the behaviour you see ..

Sorry for not being of much help

Sathyaram

Quote:
Originally posted by nitingm
Hi Sathyaram/Marcus,

First and foremost many thanks for your guidance, my problem has been resolved as I have moved to UR though personally I would have prefered to downgrade to RS with DB2_RR_TO_RS=YES and a good value for the MaxLocks and LockList Parameters.

However I found one contradicting behaviour with the LockTimeout variable with the definition of it's default value of -1 as given in the help. The value -1 says that it is infinite wait and 0 means no wait, however what I observed is that when I had set the same to -1 my transactions were being rolled back because of a timeout and on the contrary when I set the value to approx 45 secs the transactions went through, so does it mean that -1 is not infinite wait?? My observation seems so.

Please explain this to me. Any input from the other experts would also be valuable.

Regards

Nitin.

P.S. The detailed history of this case can be obtained from my previous posts.
__________________
Visit the new-look IDUG Website , register to gain access to the excellent content.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On