Discussion

Requestor timeout

Sporadically, especially when the load on the server increases, we've noticed the following error message in our logs. Unable to synchronize on Requestor XXXX within 120 seconds Users too report that "the page is getting stuck". While we understand the reasons behind why this lock happens, we would like to increase the lock time to greater than 120 seconds (for some of the requests might actually be long running processes). How does one control this timeout?

***Updated by moderator: Marissa to close post***

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

Pega
May 19, 2008 - 11:58am

This sounds like a condition that could trigger a PEGA0019 alert. Please see http://pdn.pega.com/DevNet/PRPCv5/KB/25356.asp for information on how to adjust the lock time threshold