Your embedded configuration isn't running optimized calls. This is probably because Tomcat/JBoss is finding the same classes in both the war and the ear. If an interface is in both places, Tomcat will load it from the war and JBoss will load it from the ear (each with its own classloader) and the invoker will think that they're not the same class and will silently un-optimize.
hth, danch Михаил Скорик wrote: > Hello all, > > I've just tested my application in two JBoss 2.4.4 configurations: > 1) with both (web and EJB) modules embedded Tomcat 4.0.1 > 2) and with .war part deployed into standalone (run out-of-process) Tomcat > 4.0.1 taken from the same JBoss package. > > The results of measuring avg. responce time was very surprising - it seems that > embedded Tomcat is about 5% slower(!!!) than standalone one. > > Have anybody observed a similiar behaviour ? > Have anybody made special explorations of embedded Tomcat performance ? > > -- > Mike > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Dice - The leading online job board > for high-tech professionals. Search and apply for tech jobs today! > http://seeker.dice.com/seeker.epl?rel_code=31 > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
