Hi, I'm doing pre-sales benchmarking of Weblogic Enterprise, a completely diferent product than Weblogic Server, although they're both heading toward J2EE features, they're coming from different starting points. WLE, is the older C++ tuxedo framework, with EJB container support and the EJB DD and tools borrowed from WLS. Unfortunately the corba functionality underneath WLE server side is quite old and at present only 2.2. For external corba clients, WLE does not provide org.omg.CORBA packages, they default to the JDK2's orb. This is where my problems start. Has anyone experienced capacity limitations in the JDK2 orb. My benchmarking client, uses threads (100's) to simulate multi-client use cases. The JDK2's Orb seems to have limitations that I'm hitting. I'm even seeing hung IIOP protocol on Stub.method() dispatching where the return never comes (or is never seen). The Jdk2's orb seemed to gain some capacity by giving the VM more RAM: -Xmx256m -Xoss64k To my suprise this helped. I not used to applications not throwing OUT_OF_MEMORY exceptions, and just limping along as observation suggests for the Orb???? My problems start occuring in the 70-100 thread / FactorFinder / Stub levels of stress. Still happens with jit turned off. So far Weblogic tech guys don't have insights. It seems they don't see customers writing threaded java clients like this... ;( Any thoughts on where to find other JDK2 Orb knowledgable folks. The javasoft list for IDL/Corba has died, no activity except the spammers. :) Thanks for the great EJB design thoughts here! cheers, curt Curt Smith Z-Tel email: [EMAIL PROTECTED] work: 404-237-1166 x182 FAX: 404-237-1167 =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
