Hello Nikola,
Machines are not identical, the fast machine has different specs (less memory, less disk space and less cpu) then the slow machine (this one has better specs).
Quite ironic.
One hint we've got is the carachter encoding in which the file is saved, but it seems to me this cannot be the problem...
It can be a problem, but not responsible for 20x degradation.
Sure, heavy artillery can be used, but i don't think that would lead us to a solution, also because the machine with lesser specs serves better, and we use the same tomcat version, same settings and same jdk version.
Agreed. The only thing you're left with is profiling. There were some posts on that subject. So far, we've heard of JProfiler and something from IBM. Borland's JBuilder has OptimizeIt Suite", but it costs $$$.
Nix.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
