You probably mean JBoss 3.2.5 rather than JBoss 2.3.5, right? (IIOP support appeared for the first time in 3.0.0.)
Anyway, two IIOP-related changes may cause a performance decrease in 4.0: 1) jacorb.jar was updated to (a patched version of) JacORB 2.2. A performance decrease has been reported for JacORB 2.2. The degradation shows up when JacORB tries to access unset configuration properties: http://lists.spline.inf.fu-berlin.de/pipermail/jacorb-developer/2004-September/006777.html 2) Portable interceptors were added to deal with transaction context propagation and with security over IIOP (CSIv2). Usage of request interceptors in JacORB effectively disables the local call optimization that would otherwise happen on in-VM calls. This has a negative effect on the performance of applications that do in-VM calls to (remote interfaces of) IIOP-enabled EJBs. If you don't need transaction demarcation/propagation and security over IIOP, then you get rid of the negative effect by commenting out the tx and csiv2 interceptors in iiop-service.xml. Regards, Francisco View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858772#3858772 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3858772 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
