https://issues.apache.org/bugzilla/show_bug.cgi?id=48605
Summary: Files not closed quickly enough during deployment /
lack of recovery
Product: Tomcat 6
Version: 6.0.20
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
AssignedTo: dev@tomcat.apache.org
ReportedBy: grahamtri...@gmail.com
When deploying applications, new file resources (operating system level) are
being consumed faster than they are released.
In some cases (ie. starting Tomcat when there are many applications in the
webapps folder), this can lead to the maximum open file limits being breached -
resulting in class not found exceptions and 'incomplete' deployments.
Subsequently reloading an incompletely loaded application may or may not work -
file handles consumed during loading are being released, but it appears that
you can also run into the situation where the failure to load a class is
cached, and so it doesn't check again - but undeploying and redeploying the
application will cause it to be loaded correctly.
This can be worked around by increasing the maximum number of concurrently open
files in the operating system. But ideally, the container should be better at
gracefully recovering from an failure to load a class and trying again.
This also applies to Tomcat 5.5
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
