Thanks for the report - if you can think of a patch we can use it for
3.2.3. The reloading system has been almost completely rewritten for 3.3,
with far fewer accesses to the file system.
Have you tried with a different VM ? ( I don't think we can avoid
getCanonicalPath, is a very useful call and is very important for security
too )
Costin
On Fri, 15 Jun 2001, Brett M. Bergquist wrote:
> I just upgraded or application from Tomcat 3.1 to Tomcat 3.2.2 and
noticed a dramatic slowdown and increased CPU utilization. This is on
WinN 4.0 SP5. To figure out what was happening, I fired up OptimizeIT
and ook a look. I found that 68% time was being spent in
"org.apache.tomcat.core.ServletWrapper.handleReload" and of the time
within this method, 51% of the time was being spent in
"java.io.File.getCanonicalPath" and of the time spend within this method,
all of it was spent within "java.io.Win32FileSystem.canonicalize".
>
> My question is is this normal and what in the hell is taking so long in
"java.io.Win32FileSystem.canonacalize"? Once I disabled class reloading,
by performance and CPU utilization went back to what was present with
3.1.
>
> Thanks for any input.
>
> Brett M. Bergquist
> Canoga Perkins Corp.
>
