Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-6831

EJB3 SFSB call from remote client slow - 40% degradation in EJB3 performance in EAP5

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Blocker
    • None
    • JBossAS-5.1.0.Beta1, JBossAS-5.1.0.CR1
    • EJB
    • None

    Description

      SFSB EJB3 perf test showing performance of remote EJB3 call is in the order of magnitude slower compared to EAP 4.3 / 4.2

      IMPORTANT!!!: QE is seeing a 40% degradation in EJB3 performance in EAP5 : http://hudson.qa.jboss.com/hudson/view/EAP%20Perf+Fail/job/eap-4.2-perf-ejb3-buddy-async/11/artifact/report/report.html

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. EJBTHREE-1896 Lifecycle callback interceptor generation happens multiple times for each bean context

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. EJBTHREE-1897 Improve handling of GUID as Fqn element in clustered SFSB

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-2572 EJB3 SFSB call from remote client slow - 40% degradation in EJB3 performance in EAP5

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Activity

            People

              rhn-engineering-cdewolf Carlo de Wolf
              dpospisil Dominik Pospisil (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: