1 of our finally blocks calls first a response.close() without try/catch around that and then unset the threadlocals, i think the response.close does somehow in some situations throws an exception, i dont know which one but i build a try catch around it.
On 4/17/08, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > we dont even know if it is something in wicket that is causing this > yet...johan what exactly did you find out? > > -igor > > > On Wed, Apr 16, 2008 at 4:34 PM, Ned Collyer <[EMAIL PROTECTED]> wrote: > > > > > > Edvin Syse wrote: > > > > > > No, it has not. Johan said he fixed a bug that might have been this > > > problem, but I haven't been able to confirm it yet, as the fix is in > > > 1.3-SNAPSHOT, and I ran into some issues when deploying with the > > > snapshot-version. > > > > > > I see this problem 10-20 times every day still.. > > > > > > -- Edvin > > > > > > > I hope we see a non snapshot release soon. This sounds like a doozy of a > > bug - show stopper for everyone! > > -- > > View this message in context: > http://www.nabble.com/Invoulentary-session-sharing-leakage-in-Wicket-1.3.x-tp16550360p16735844.html > > > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > > > > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
