> > That said, our loadtests indicate that WAS on Linux is much > more reliable= > than > > JBoss with Sun JDK 1.4.x on Linux. So for production WAS might > not be suc= > h a > > bad idea after all. > >=20 > > I'd like to see that [...] > Furthermore, I'll be= > t > your value objects are created in your session bean rather than in the > ejbLoad.
Andy! frankly - why would I create value objects in the session bean? Of course they are created in ejbLoad. > Lastly, Was that WAS on IBM JDK and JBoss on Sun JDK? Sun's JDK > is probably the slowest and has a nasty classloading bug that you're very > likely to hit on JBoss 3.2.2 and below under load and might hit on 3.2.3. > (It is never fair to compare on two different VMs.) You are right, JBoss was runnning in a Sun JDK, WAS on the IBM JDK (both RedHat AS 3.0). And the main problem we had was excessive garbage collection that eventually lead to a crash (which made me advocate using a different JDK like JRockit or the IBM JDK - the tests just haven't happened yet). I didn't mean to badmouth either application server (at least not in this particular mail :). Both have their purpose and application. Basically I was just pleased to say that after all the hassle I had to go through, getting things to run on WebSphere, there were actually reasonable results. However - you got me interested in that classloading bug you mentioned. Would you care to elaborate or give me a pointer so that I can read it up? Thanks, -hendrik
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
