https://issues.apache.org/bugzilla/show_bug.cgi?id=56608

            Bug ID: 56608
           Summary: WatchedResource configured in
                    $TomcatHome\conf\Catalina\localhost context XML file
                    not triggering context reload after working for
                    several days
           Product: Tomcat 6
           Version: 6.0.39
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
          Assignee: dev@tomcat.apache.org
          Reporter: rem...@gmail.com

Created attachment 31700
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=31700&action=edit
Log files for the day the error occurred and context reloading stopped being
automatic.  Context file for app in question included.

I have set up a context XML file within $TOMCAT_HOME\conf\Catalina\localhost
which has a docbase on a network fileshare.  I have set up a WatchedResource
for a handful of files on this fileshare so that whenever one of the files is
updated, the context is refreshed.  This works fine for sometime, but after a
while, I see an error in the logs saying "java.io.IOException: The semaphore
timeout period has expired" (Log file with full stack trace is uploaded).

After we notice this error, I had to start the context back via the Tomcat
manager (to be expected, since it appears that a short network unavailability
caused the issue).  However, once the application is started manually, the
WatchedResources being updated no longer force the context to reload.  We have
to reload the context manually until we do a full restart of the Tomcat
service.

-- 
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

Reply via email to