I've just upgraded from beta1 to beta2, and my unit test suite now cannot
run. I can run all test classes individually, or even a package at a time.
But if I run all tests in my project, I eventually get an exception ("Caused
by: java.lang.OutOfMemoryError: Java heap space"), at a different point each
time. The same behaviour is observed in both maven & eclipse.
I've tried various config settings (changing the configuration type to
deployment, calling Objects.setObjectStreamFactory etc), but I'm clutching
at straws.
I noted that each individual test package (say 200 test cases) was running
twice as slow as before. I improved this dramatically by calling
"getDebugSettings().setComponentUseCheck(false);" in development mode (not
ideal), and this improved the running time of each individual test package
back to something like its previous value. But, when running the full suite
(several packages, in either Maven or Eclipse), the tests still get
progressively slower until the OutOfMemory error is raised.
I've no idea where to start looking, but would greatly appreciate any
helpful suggestions. I've just checked with 1.3.0-SNAPSHOT, and I still
observe the same broken behaviour...
Severian.
--
View this message in context:
http://www.nabble.com/Wicket-1.3.0-beta2---OutOfMemoryError-tf4073994.html#a11578399
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
