[ openjms-Bugs-755234 ] Discrepancy in LeaseManager configuration
"SourceForge.net" <[email protected]>
| Newsgroups | gmane.comp.java.openjms.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #755234, was opened at 2003-06-16 20:32 Message generated for change (Comment added) made by tanderson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474136&aid=755234&group_id=54559 Category: server Group: v0.7.6 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Tim Anderson (tanderson) >Assigned to: Tim Anderson (tanderson) Summary: Discrepancy in LeaseManager configuration Initial Comment: The LeaseManagerConfiguration/sleepTime defaults to "300" [1], yet the code expects the time to be in milliseconds [2]. So, when there are no messages to expire, the LeaseManager will wake up every 300 ms to do nothing. The openjms.xsd schema [3] doesn't specify the expected type - seconds or milliseconds. I'm inclined to make it seconds, and change LeaseManager.java to be consistent with the other time fields in the configuration. [1] see src/main/org/exolab/jms/config/openjms_defaults.xml [2] see src/main/org/exolab/jms/lease/LeaseManager.java [3] see src/main/org/exolab/jms/config/openjms.xsd ---------------------------------------------------------------------- >Comment By: Tim Anderson (tanderson) Date: 2003-06-25 11:34 Message: Logged In: YES user_id=557161 Fixed in CVS. The openjms.xsd schema has been changed so that the sleepTime is now specified in seconds. The openjms_defaults.xml file has been changed to: <LeaseManagerConfiguration sleepTime="60" /> Fix will be available in the 0.7.6 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474136&aid=755234&group_id=54559