Major Description
Currently, provide does not persist the requester's new persistent id during shutdown but it does not send a message to indicate this. The requester could then request gii from the provider and then persists its new persistent id and assume the provider has persisted its new id. And then it is being shut down as well.
The end result is a requester could not be restarted if provider was recovered first (shut down all case), as provider does not know the requester's new persistent id and ConflictingPersistentDataException is raised.
Attachments
Issue Links
- links to
