juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ShengTao Dong (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Commented: (JUDDI-426) Could disable the check for the lag time of the notification
Date Fri, 29 Oct 2010 03:29:23 GMT

    [ https://issues.apache.org/jira/browse/JUDDI-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926157#action_12926157

ShengTao Dong commented on JUDDI-426:

Thanks curt, in our environment, it cause every notification fail in a period time, for example,
in 5 minutes, all notification are ignored for they all late than right time, It's normal
once a notification is ignored, further notification will be ignored in a big possibility.

Our model is, there is a master juddi that is used to register, and there are many local juddi
those are used to be lookup, so the process is the services will register in master juddi
first, and then will be distributed to local juddi by notification. So if in 5 minutes, all
notification are ignored, all services those register in this 5 minutes will not be distributed,
and the client want to lookup in local juddi will fail.

That's the problem.   

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

View raw message