Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-18587

[GSS](7.2.z) REM3-352 - EJB client behaviour is different when deployed in a .war compared to a .ear and can result in a OOME

    XMLWordPrintable

Details

    • +
    • Hide

      see reproducer in customer case
      essentially you have an EJB deployed on EAP 6 and a .war or .ear deployed on EAP 7. The .war or .ear connects to the remote EJB and the behaviour is different. The .war gives poor performance and runs out of native memory
      .ear works ok, ok as in consistent with the EAP 6(ejb) : EAP 6 (.ear or .war)
      The customer has shown this on EAP 7.2.6 I see it on EAP 7.2.3

      or I could zip up my verification of it and attach it to the case

      Show
      see reproducer in customer case essentially you have an EJB deployed on EAP 6 and a .war or .ear deployed on EAP 7. The .war or .ear connects to the remote EJB and the behaviour is different. The .war gives poor performance and runs out of native memory .ear works ok, ok as in consistent with the EAP 6(ejb) : EAP 6 (.ear or .war) The customer has shown this on EAP 7.2.6 I see it on EAP 7.2.3 or I could zip up my verification of it and attach it to the case

    Description

      EAP 7 - EJB client behaviour is different when deployed in a .war compared to a .ear

      .war gives poor performance and runs out of native memory
      .ear works ok

      Attachments

        1. client-ear.ear
          14 kB
        2. OOM_Reproducer.zip
          67 kB
        3. server_6M_.log
          971 kB
        4. standalone-full-eap6.xml
          22 kB

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18661 [GSS](7.3.z) REM3-352 - EJB client behaviour is different when deployed in a .war compared to a .ear and can result in a OOME

          • 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.
          • Verified
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. REM3-352 ConnectionInfo.NotShared does not update state when new connection is created

          • 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
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-13060 EJB client behaviour is different when deployed in a .war compared to a .ear and can result in a OOME

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-18827 [GSS](7.2.z) Upgrade JBoss Remoting from 5.0.17-redhat-00001 to 5.0.18-redhat-00001

          • 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.
          • Closed
          links to

          Web Link KCS

          Activity

            People

              flaviarnn Flavia Rainone
              rhn-support-sappleton Shaun Appleton
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: