On Wed, 21 Feb 2007, Niels Bo wrote: > I am however *not* able to reproduce it with Sun jvm and/or when a debugger > is attached! > > I am running it in a clean/new/default WL 8.1 SP5 installation where Jrockit > is selected as JVM.
Do you mean that it doesn't happen even with JRockit, when a debugger is attached? Then it could have something to do with threading (or hyperthreading), optimizing or garbage collection, all of which JRockit might do differently from the other VM. Also the debugger might produce side effects (such as calling toString() on some objects) that would prevent the bug from happenning; I have run into this sometimes when debugging (a kind of a heisenbug). It would be a good idea to automate a test that would reproduce the bug in a consistent way, if you can manage this e.g. with a load tester. Then you could enable all possible logging and see if something happens differently on the different JVMs. Also you might want to try with yet another JVM (such as IBM's or some open source); this might help in deciding whether to look for solutions within Wicket or the JVM. Another possibility is to tweak the JVM settings. I think that by default JRockit works quite differently from Sun JVM (at least Sun's client JVM). And yet another one to file a case to BEA support with a reproducable test case. - Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
