Re: [Wonder-disc] [5.2] Exception reporting lock up the app

[Jonathan 'W. R. <web...@re...>]

Greetings Anjo,

>I did a bit more testing and it seems like I can *not* reproduce the  
>error with -say- BugTracker. But I did manage to track it down a bit:  
>when I remove the WOCollapsible in the WOExceptionPage, then the error  
>gets reported and everything is OK. As soon as I add it, the app locks  
>up when it tries to report an error???

Reading the tea leaves (thread dump), it appears WOCollapsible generates 
a WOHyperlink, which asks WOContext for its WOSession, which currently 
has none. So WOContext calls WOApplication.restoreSessionWithID, which 
calls WOSessionStore.checkOutSessionWithID, which deadlocks because the 
session was already checked out?

It would be interesting to discover if you deadlock sooner in 
MyApplication.handleException by calling context.session() explicitly.

>What can I do? I can't really log this with the bugreporter "Yeah,  
>well, there is a deadlock in the session store that *I* can reproduce,  
>would you like to look at my 100k code"?

Sure, send it my way! Oh, make sure you put it under a BSD license first, 
please. (grin)

.......................................................
Jonathan 'Wolf' Rentzsch         jon at redshed dot net
Red Shed Software   http://redshed.net   (847) 584-7465
PGP: B2AF 1A09 F881 EBDE C9D6  C4D2 C04F A3C0 3EC5 D5F2

             "There are 10 types of people:
    those who count in binary, and those who don't"