Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. 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

XMLWordPrintable

    • 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

      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

              flaviarnn Flavia Rainone
              spyrkob Bartosz Spyrko-Smietanko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: