Where do we even start to look for performance problems? Were there
any performance tests or analysis run between releases?
First of all, I'd recommend that you don't use the ServletWebserver, but
a real servlet engine. Second, how about creating a test suite that
allows to reproduce what you do? Finally, how about adding logging
statements to the servers code in order to analyze the output?
We tried to get it to run under a real servlet engine. We have to
use JBoss due to other server dependencies. We have not been able
to make that work yet following the example in the documentation -
it never seems to get deployed under JBoss and our client can't
connect to it.
We do have a test suite that allows us to reproduce it - that's how
we can so easily discover that there is a performance problem. I
was looking for insight as to where to put log statements since we
don't really know much about the 3.0 code and are just trying to use
it.
Randall
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
