Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-1443

Stateless session bean invocation takes 30% longer with Weld 2.0

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • 2.0.0.Final
    • Weld SPI
    • None
    • Hide

      1. Deploy an application with a stateless session bean (@Stateless annotation) with CDI 1.1 implicit behavior disabled, and invoke the application to exercise the session bean.

      2. Deploy an application with a stateless session bean (@Stateless annotation), and invoke the application to exercise the session bean.

      3. Measure the difference in performance between the two; It's significant.

      Show
      1. Deploy an application with a stateless session bean (@Stateless annotation) with CDI 1.1 implicit behavior disabled, and invoke the application to exercise the session bean. 2. Deploy an application with a stateless session bean (@Stateless annotation), and invoke the application to exercise the session bean. 3. Measure the difference in performance between the two; It's significant.

      Micro benchmarks on EJB local session beans have regressed by 30% because of implicit CDI.

      The problem is that the WeldListener requestInitialized() and requestDestroyed() methods are consuming large amounts of CPU. These are all simple requests to call a business method on a stateless bean.

            rhn-engineering-jharting Jozef Hartinger
            phil.zampino Phil Zampino (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: