On Tue, 2002-08-13 at 19:11, Robert Hannebauer wrote:
> Hello,
>
> > 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
Hello,
> 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
>
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
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
