commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 36665] New: - [configuration] clarify ReloadingStrategy interface usage
Date Thu, 15 Sep 2005 08:31:16 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36665>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36665

           Summary: [configuration] clarify ReloadingStrategy interface
                    usage
           Product: Commons
           Version: 1.1 Final
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Configuration
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: ndeloof@capgemini.fr


I had some trouble creating a ReloadingStrategy implementation (based on a JMX
reload request) : 
reloadingRequired() is called several times AFTER first returning 'true' and
before reloadingPerformed() is called. In fact, reloading process requires
access to getProperty() that itself (re)enters reload. If reloadingRequired()
doens't return false at this time, a infinite recursice loop starts.

Perhaps it is a reload() bug, that may use a boolean flag to mark
processing-reload and avoid such infinite loop in the Thread runing he reload.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message