[
https://issues.jboss.org/browse/EJBTHREE-2110?page=com.atlassian.jira.plu...
]
Sergiu Pienar commented on EJBTHREE-2110:
-----------------------------------------
Is this patch embedded into JBoss 7 ?
Add flag to enable an optimization to skip
serialization/deserialization of Remote interfaces running locally
-------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-2110
URL:
https://issues.jboss.org/browse/EJBTHREE-2110
Project: EJB 3.0
Issue Type: Feature Request
Reporter: Ben Schofield
Assignee: Carlo de Wolf
Fix For: bom-eap5-0.1.3, depchain-1.0.0-alpha-2
Attachments: EJBTHREE-2110.patch
When an application uses a remote EJB3 interface the call is serialized and deserialized.
While mandated by spec this is unnecessary if the EJB is running in the same JVM as the
calling client. Having the option to skip serialization would bring JBoss inline with
other major JEE vendors. Performance tests on a transactional application that has all
business logic in stateless session bean methods is showing 20% cpu overhead just for the
serialization. Having 20% more production CPU capacity is more important than claiming
strict EJB3 compliance. JBoss AS response times are better too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira