Loading...

XML

Word

Printable

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
QE Test Coverage:
+
Target Release:

7.2.z.GA
Git Pull Request:
https://github.com/jboss-remoting/jboss-remoting/pull/230
Steps to Reproduce:

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

clones

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

is caused by

REM3-352 ConnectionInfo.NotShared does not update state when new connection is created

is cloned by

WFLY-13060 EJB client behaviour is different when deployed in a .war compared to a .ear and can result in a OOME

is incorporated by

JBEAP-18827 [GSS](7.2.z) Upgrade JBoss Remoting from 5.0.17-redhat-00001 to 5.0.18-redhat-00001

links to

KCS