[
https://issues.apache.org/jira/browse/JUDDI-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt T Stam closed JUDDI-426.
-----------------------------
Resolution: Fixed
Changes have been checked in in revision 1033007, which wrongly has juddi-423
in the commit message. The acceptable lagtime is now configurable, but still
defaulted to 500 ms. This should address this issue.
> Could disable the check for the lag time of the notification
> ------------------------------------------------------------
>
> Key: JUDDI-426
> URL: https://issues.apache.org/jira/browse/JUDDI-426
> Project: jUDDI
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.0.1
> Reporter: ShengTao Dong
> Assignee: Kurt T Stam
> Fix For: 3.0.5
>
>
> In the org.apache.juddi.subscription.SubscriptionNotifier class, there is
> this method:
> The value ACCEPTABLE_LAG_TIME is fixed in code and is 500ms, and could this
> be refactor to be a property that the user can set, and for some special
> value, for example '-1' will mean always notify.
> private boolean firedOnTime(long scheduleExecutionTime) {
> long lagTime = System.currentTimeMillis() - scheduleExecutionTime;
> if (lagTime <= ACCEPTABLE_LAG_TIME) {
> return true;
> } else {
> log.warn("NotificationTimer is lagging " + lagTime + " milli
> seconds behind. A lag time "
> + "which exceeds an acceptable lagtime of " +
> ACCEPTABLE_LAG_TIME + "ms indicates "
> + "that the registry server is under stress. We are
> therefore skipping this notification "
> + "cycle.");
> return false;
> }
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
