Hi, you've reached the website of Mark Menard, Freemason, developer, businessman, photographer, motorcyclist and all around nice guy.
The main joy in my life is Sylva, my loving partner and friend. (You will see plenty of pictures of her. Also check out our site.) My professonal career is running a consulting firm concentrating on business automation and custom software. I enjoy software development, motorcycles, photography, dancing, freemasonry and travel.
Here you will find galleries of my latest photos, thoughts on software development, freemasonry, the occassional politics, and other things. Enjoy your time here.
Mark
An ongoing photographic study of Freemasonry.
To contact Mark send an email to mark@mjm.net. You will receive an auto response from my mail server to verify you're not a spammer.
© Mark Menard 2002-2007
OutOfMemoryException
Just came across this rather interesting post, and have been integrating the interceptor into one of my applications. An interesting point I believe (although have not yet encountered) is that the interceptor uses an internal map for managing conversations, however if enough users start a conversation but never finish it (say across 4 actions for example with the first creating the conversation model and the last being the 4th action will return true via isConversationFinished where the other three return false) and the user moves away to another page after action 1 or 2 then eventually the JVM will encounter an OutOfMemoryException as the map does not seem to release a pointer to the conversation model.
This is quite a valid assumption? Or am I going mad after a long day at work?