I get this error inside my custom checkout code. The mail list archives from a year ago suggest that it might be a Derby problem, so I got the latest version with the same result. Is it most likely still a Derby problem or is it because the code that I am calling, CheckoutHelper.processPayment is doing a query on the OrderHeader table inside of a transaction that has already locked OrderHeader? Is calling processPayment from a service a way to fix this? I realize that I could try various fixes, but I believe that situations like this are a great opportunity to share knowledge. So start sharing.
Thanks, -Al
