Bug 1132270

Summary:	Stateful EJB instances use excessive memory
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	James Livingston <jlivings>
Component:	EJB	Assignee:	David M. Lloyd <david.lloyd>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Martiska <jmartisk>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.2.0	CC:	joallen, sdouglas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-03 04:18:11 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.