Ok - well I think my post almost answered itself. I think our basic problem was calling create() and remove() on every EJB method invocation. If we had cached the EJB object stub, each remote call would have taken about 4ms (3ms with pooled invoker) which is pretty reasonable.
So, my remaining questions are: | * Is caching the EJB stub the correct way to handle things? Is this cross-app server compatible? Any effect on clustering? | * Does anyone have any idea why the EJB create() method on the home interface would occassionally take 2+ seconds to execute. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3898655#3898655 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3898655 ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
