Bug 1132270 - Stateful EJB instances use excessive memory
Summary: Stateful EJB instances use excessive memory
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: David M. Lloyd
QA Contact: Jan Martiska
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-21 03:32 UTC by James Livingston
Modified: 2018-12-09 18:24 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-11-03 04:18:11 UTC
Type: Enhancement
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3754 0 Major Resolved EJB StatefulSessionComponentInstance methodMap includes final Object methods 2016-04-22 09:40:30 UTC

Description James Livingston 2014-08-21 03:32:54 UTC 
Stateful EJB instances use an excessive amount of server-side memory. 
There is 300-400 bytes bytes of memory used per business method per instance, which quickly adds up.

Part of this is caused by https://issues.jboss.org/browse/WFLY-3754 which treats public final java.lang.Object methods as business methods.

Another part is caused by a normal interceptor chain having 5 of the 8 interceptors not shared.
Comment 1 Stuart Douglas 2014-08-27 02:05:29 UTC 
Which version of EAP did you observe this? It should be fixed in EAP 6.3 which has the stateless interceptors patch.
Comment 2 James Livingston 2014-08-28 04:13:55 UTC 
I'd accidentally overwritten by "eap-6.3" directory with 6.2, so was running the older version. I've done some testing with 6.3 and it the memory usage is much lower. So the main memory usage I was looking at was resolved by bug 1022265.
Note You need to log in before you can comment on or make changes to this bug.