Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-2110

Add flag to enable an optimization to skip serialization/deserialization of Remote interfaces running locally

    Details

      Description

      When an application uses a remote EJB3 interface the call is serialized and deserialized. While mandated by spec this is unnecessary if the EJB is running in the same JVM as the calling client. Having the option to skip serialization would bring JBoss inline with other major JEE vendors. Performance tests on a transactional application that has all business logic in stateless session bean methods is showing 20% cpu overhead just for the serialization. Having 20% more production CPU capacity is more important than claiming strict EJB3 compliance. JBoss AS response times are better too.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  wolfc Carlo de Wolf
                  Reporter:
                  dbschofield Ben Schofield
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: