I'm experiencing an issue with the renewal of registrations using Java WS Core
version 4.0.3 + the Aggregator Framework. It seems that the ServiceGroup client
is not able to get the remote time from my aggregator service. 
By logging at debug level the client, I obtain the following messages:

2006-09-30 12:55:09,110 DEBUG client.ServiceGroupRegistrationClient
[Timer-4,status:474] Attempting to get current time, preferring remote.
2006-09-30 12:36:09,110 DEBUG client.ServiceGroupRegistrationClient
[Timer-4,status:474] No remote current time available. Getting from local clock
instead.

and I understand that there is a problem while it is trying to get the remote
time.
Then, by studying the source code of the ServiceGroupRegistrationClient class,
I see the following piece of code:
_____________________________________________________

/** Gets the current time, preferably from the remote resource
           specified, and failing that from local system. */
       private Calendar getCurrentTimePreferringRemote(  EndpointReferenceType
epr)         {
           ServiceGroupRegistrationClient.this.status(LOG_D,     "Attempting to
get current time, preferring remote.");

           Calendar now = null;

           if(epr!=null && maybeHasLifetime) {

               try {
               GetResourceProperty getRPPort =   
rpLocator.getGetResourcePropertyPort(epr);
               setSecurity((Stub)getRPPort);

               GetResourcePropertyResponse resp =   
getRPPort.getResourceProperty(WSRFConstants.CURRENT_TIME);
               } catch(InvalidResourcePropertyQNameFaultType e) {
                   /* this fault means that we can talk to the
                      resource but it does not have current time,
                      which implies that it does not support
                      WS-ResourceLifetime mechanisms */
                   maybeHasLifetime=false;
                   /* now fall through */
               } catch(Exception e) {
                   /* some other exception occurred. return null, but
                   don't change maybeHasLifetime */
                   ;
               }
                          }

           // if the above hasn't produced a time, then pull time from
           // local clock
           if(now == null) {
               ServiceGroupRegistrationClient.this.status(LOG_D,
                   "No remote current time available. Getting from local clock
instead.");
               now = Calendar.getInstance();
           }

           return now;
       }
_____________________________________________________

In my opinion, there is a bug in this code, because it does not extract the
time from the "resp" object  and it never sets the "now" object in the try
block. Therefore, the local time is alway used.
Since the machines that join the infrastructure of the project I'm working in
are located in different timezones, this causes sometimes that the
ServiceGroupEntries created by the Agggregator Framework and connected to my
Sinks are always out of date at creation time. So, the sweeper of the
Aggregator Framework immediately deletes them at its next execution. In fact,
the next renewal attempt always creates a new ServiceGroupEntry because, of
course, it fails to acquire to the removed resource.