-
1. Performance issue in JBoss EAP 5 (log.trace)
peterj Apr 19, 2011 8:26 AM (in response to rnexerp)Wow! Not only is this code generating unnecessary string objects which are then thrown away without being used (if logging is off) and thus causing extra stress on the garbage collector, but it also unnecessaily (if logging is off) calls three functions which are stealing processor cycles from threads that are trying to do real work, and probably also generating all kinds of unnecessary garbage, thus straining the garbage collector even more. And this is in the "professional" version. Amazing!
-
2. Performance issue in JBoss EAP 5 (log.trace)
rnexerp Apr 19, 2011 8:49 AM (in response to peterj)Yes. And I got a "not my problem" reply when commenting on a similar issue https://issues.jboss.org/browse/JBPAPP-4850
-
3. Performance issue in JBoss EAP 5 (log.trace)
jaikiran Apr 19, 2011 8:53 AM (in response to peterj)Yeah, that's real ugly!
By the way, are those interceptors being invoked? I mean that piece of code looks outdated. Are you using EJB2.x in which case it might be used. I don't see them being used in EJB3.
-
4. Performance issue in JBoss EAP 5 (log.trace)
peterj Apr 19, 2011 9:06 AM (in response to rnexerp)Remi Nodet wrote:
Yes. And I got a "not my problem" reply when commenting on a similar issue https://issues.jboss.org/browse/JBPAPP-4850
To be fair, they did indicate that you should open a new JIRA issue rather than commenting on an old, closed issue.
-
6. Performance issue in JBoss EAP 5 (log.trace)
rnexerp Apr 19, 2011 9:42 AM (in response to jaikiran)Yes, those interceptors are used with EJB2.x, and there are plenty of applications that are using those. It is a "regression" from EAP 4.2 to EAP 5.0 (a "newly" introduced problem, as there was no PreSecurityInterceptor.java in EAP 4.2).
The actual performance problems using EJB2.x are actually not limited to this in EAP 5.0 but that was the easiest to spot. We have roughly experienced a 30% increase in CPU usage going from EAP 4.2 to EAP 4.2 with our EJB2.x application.
-
7. Performance issue in JBoss EAP 5 (log.trace)
jaikiran Apr 19, 2011 9:51 AM (in response to rnexerp)It's now fixed.