Sorry but I haven't understood your question. Aren't the same thing the 'request that keeps the lock' and the ' lock keeping request'? What would you like to add to the current log information?
On Tue, May 7, 2024 at 1:19 PM Martijn Dashorst <martijn.dasho...@gmail.com> wrote: > Hi! > > I was looking at our exception reporting in our application(s), and noticed > that when the CouldNotLockPageException is thrown, it only logs the stack > elements of the request that keeps the lock. > > What I'd like to do is to construct an exception and fill that exception's > stack trace elements with the stack of the lock keeping request, and > setting that as the cause of the CouldNotLockPageException. > > While this is a bit esoteric in nature, I think it is functionally correct > in that the page that keeps the lock is actually the cause of the CNLPE. > > This would make debugging the occurrences of the CNLPE a bit better, as the > exception itself is not informative, and you're actually interested in the > cause. So this would alleviate the need to peruse the logs of one's > application, and you can just look in the reported exception itself. > > WDYT? > > Martijn > -- Andrea Del Bene. Apache Wicket committer.
