I believe I may be doing somethings incorrect in my application because I just ran across an OutOfMemoryError and the steps involved were small.
I did increase the memory size to -Xms256m -Xmx512m which got me past the original issue...but I did notice that the application heap size continues to grow more than I thought it should. In other words, my app won't scale when I add more users beyond me :-| Where I think I am causing problems in my memory management is that I am passing Page references around. I do this so I can place a "Cancel" button and go back to the previous page rather than relying on the browser back button. Is this the wrong approach? If so, what should I do to achieve this behavior? or should I just remove the "Cancel" button and rely on the browser back button? Also, I don't "clean" anything up at all, i.e. pages. Should I? If so, when? and how? Thanks - Doug -- View this message in context: http://www.nabble.com/Best-practice-question-tf4732767.html#a13533032 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
