[jira] [Closed] (JUDDI-486) Notifier can miss changes due to issue with setting the lastNotification time

["Kurt T Stam (JIRA)" <ju...@ws.apache.org>]

     [ https://issues.apache.org/jira/browse/JUDDI-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt T Stam closed JUDDI-486.
-----------------------------


> Notifier can miss changes due to issue with setting the lastNotification time
> -----------------------------------------------------------------------------
>
>                 Key: JUDDI-486
>                 URL: https://issues.apache.org/jira/browse/JUDDI-486
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0.4
>            Reporter: Kurt T Stam
>            Assignee: Kurt T Stam
>             Fix For: 3.1.0
>
>
> The normal notification process is below:
> 1. Setup a executing time, we assume it's 1:00:10 .
> 2. Get the last notification time of the subscription, we assume it's 1:00:05.
> 3. Get all change services between 1:00:05 -- 1:00:10.
> 4. Notify these change services to client of this subscription.
> 5. If it's success, set the subscription's last notification time to be 'current time'.
> The problem is the step 5, the last notification is updated to be
> 'current time', not the 'executing time', but in step 2, juddi use the
> 'executing time' to be the end time of changed services.
> In some probability, the 'current time' is after 'executing time', then
> when next time notifying, the 'current time' will be used as start time
> at step 2,  all changed services between 'current time' and 'executing
> time' will be lost to notify.
> I changed the code in step 5, set the subscription's last notification
> time to be 'executing time' instead of 'current time', so this issue
> should not happened.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira