Yes, I have seen this before when an error in appendToResponse of a
WOComponent prevented the session to get checked back into the
SessionStore at the end of the R-R loop.
To prevent the thread exiting and respawning and to get the error
stack trace, I used Wonder's
This would require my app to be Wonder-based right?
Unfortunately, this app is not Wonder-based yet. It will be in the
not to far distant future, just not yet. :-)
I noticed something interesting. I inserted this line of code right
before the line of code where the problem occurs:
On May 8, 2009, at 11:46 AM, Ricardo J. Parada wrote:
This would require my app to be Wonder-based right?
Unfortunately, this app is not Wonder-based yet. It will be in the
not to far distant future, just not yet. :-)
I noticed something interesting. I inserted this line of code right
You can always *examine* EXRApplication source and build a similar
sessionstoredeadlock trapping logic in your own non-Wonder app.
Ricardo, to start with Wonder, you only need ERExtensions and
ERJars . and by default they don't really change any of the
default WebObjects behaviour
