If you search for "page recorder locked" in the archives (for instance, http://marc.theaimsgroup.com/?l=tapestry-user), you'll find several postings about this. The usual approach is to make your custom Engine ignore the exception, or add javascript to your buttons to disable a button once it's clicked, or synchronize multiple requests from the same user in the ApplicationServlet.
----- Original Message ----- From: "Daniel M Garland" <[EMAIL PROTECTED]> To: "Tapestry Users" <[email protected]> Sent: Tuesday, July 19, 2005 5:19 AM Subject: Commit exception? > Hi there, > > I've found the following exception in my program, which only happens > sometimes: > > org.apache.tapestry.ApplicationRuntimeException Page recorder for page Product is locked after a commit(), but received a change to property x on page y. > > > Why is this happening? I can't debug it easily as it only happens every > so often, like once a day. > > Any ideas? > -- > Regards, > > *Dan Garland* > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > Tel: +44 (0) 207 803 1947 > Mob: +44 (0) 7979 770053 > ICQ: 120963437 > AIM: dmgarland1767 > > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
