Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
5.5
-
None
-
None
Description
ReplicationHandler has volatile class member snapShootDetails.
The variable is not reset on new submission.
Usecase:
On Core1 running a JVM1, submit a replication request.
I poll this thread to check the replication status invoking the handler passing "command=details".
Issue:
I submit request1 on core1 to create replication. Poll the status using details.
Once the replication is complete, i submit the replication request2 on core1 again. When when we poll using handler for replication details, it still has request1 details.
I think on new submission, the previous request details(request1 in this eg) should be reset (meaning snapshotdetails= null) on new request.
The getDetails should be returned the status of request2 instead of request1 details. This doesn't happen untill request2 either succeeds or fails.