This content has been marked as final. Show 2 replies
We upgraded our JBoss 4.2.1/java 5 to JBoss 5.1.0/java 6, both in suse 10 linux. Application is unchanged. There is one area of application, which has a wraper class wrapping a SFSB. One wraper method calling a wrapped sfsb method is called in a tight loop. The time it takes for the job in JBoss 5.1.0 is 3+ times of the one in JBoss 4.2.1.
We then compare the cpu profile in JProfiler. We recorded cpu when this loop was running for about 550K invocation. The results showed that in JBoss 5.1.0, the hotest cpu is java.lang.forName, which was called over 2 million times. The forName hotspot in JBoss 4.2.1 was way down at the bottom of the list.
We examined that CallByValue flag was set to off. What other configuration should we set? Is this a JBoss 5 bug?