ok, I can put a try-catch(Throwable t) around the service() and log that
together with the request-url.
But since it is a production server, I am not able to get it deployed until
tomorrow evening, and right now we are doing ok with the workaround.

Niels
 

Johan Compagner wrote:
> 
> if there was an error before that
> that should then be logged just before you log that there is a wrong state
> 
> The way you do it now is in reverse
> 
> the wrong state was already set in X number of request back
> so when you log it, You can;'t really tie it to a a specific request that
> did go wrong.
> 
> If you log it later after the service method. Then you know that it did
> happen for that request
> And most likely there should be some error before that.. Because i dont
> see
> another way
> how it would be possible when the normal flow without exceptions would
> happen.
> 
> johan
> 
> 
> On Wed, Apr 9, 2008 at 3:28 PM, Niels Bo <[EMAIL PROTECTED]> wrote:
> 
>>
>> Hi
>> How can I check/log if there are "error for that thread"?
>> Niels
>>
>>
>> Johan Compagner wrote:
>> >
>> > could you change that method that it checks this after the fact?
>> > and then see if there is an error for that thread before? for example
>> also
>> > log the url call so that we can see
>> > what kind of request did let one thread local be there?
>> >
>> > Which one is it by the way?
>> > is it app, session or request cycle?
>> >
>> > i just checked our code and we have finally blocks pretty much every
>> where
>> > in WicketFilter.doGet
>> > and in RequestCycle.steps
>> >
>> > And i have no idea how those can be jumped over.
>> >
>> > johan
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Invoulentary-session-sharing-leakage-in-Wicket-1.3.x-tp16550360p16585768.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]
>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Invoulentary-session-sharing-leakage-in-Wicket-1.3.x-tp16550360p16590574.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]

Reply via email to