Hi, I'm afraid that I've not used Maven and will need to do some background on
this before I can use the software supplied. I thought there was supposed to
be a pom.xml file, but couldn't locate one. This is something I need to address.
Anyway, I'm about 90% sure I know the general nature of the problem. I was
running glassfish on an AMD 64 bit dual-core chipset (Windows 7) and started to
get a bit paranoid that it was running a bit hot (which it was - 70C), so tried
running on an Intel quad core box (64 bit) instead. Though I thought it unlikely I
wanted to rule out any bizarre hardware problems or anything like that.
I reloaded onto the new box glassfish 3.0.1 (with Mojarra 2.0.2), JDK 6 u21, NetBeans, everything. The problem was no better even after a clean and build. This pretty much rules out any configuration or hardware anomalies. I also tried a
Mojarra 2.1NB with no improvement.
Then I thought to see if I could disable all but one cpu and try again. Miraculously
I then get stable results, so it looks like a lack of thread safety which is less
likely to manifest itself on a single cpu box.
Perhaps this would be worth investigating. I could imagine that even if running on
a multi-cpu sparc unix box that differences in the underlying implementations
(i.e. not intel, not windows), despite the jvm, could change the conditions under
which this problem occurs, or not? Anyway, it's definitely a big problem on a
multi-cpu windows box.
Regards,
Brendan.
[Message sent by forum member 'healeyb']
http://forums.java.net/jive/thread.jspa?messageID=481098