Project

General

Profile

Task #7536

Bug #7523: D1Client no longer updates stale NodeList

fix D1Client so that it refreshes the nodelist if MN not found

Added by Rob Nahf almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_libclient_java
Start date:
2015-12-10
Due date:
% Done:

100%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

at the very least, D1Client should be refreshing the NodeList.

I added the logic to both v1 and v2 D1Clients in 2.0.0 branch and will merge to trunk.

The unit test with mock objects is not working, but an integration-style test works, and has been committed, although commented out. There is a weakness in the NodeLocator class hierarchy that doesn't work well with InMemoryCNodes, because a CNode is used to call CN.listNodes, but is then replaced with a new CNode for the CN.

This should be looked at later.

Associated revisions

Revision 17531
Added by Rob Nahf almost 6 years ago

fixes #7546, refs #7635, #7536. Refactored ObjectFormatCache to be thread safe, and not dependent on the shipped ObjectFormatList file. Refactored getInstance methods of CertificateManager and ObjectFormatCache for thread safety. Removed unnecessary dependency on a live CN in d1client.properties.

Revision 17531
Added by Rob Nahf almost 6 years ago

fixes #7546, refs #7635, #7536. Refactored ObjectFormatCache to be thread safe, and not dependent on the shipped ObjectFormatList file. Refactored getInstance methods of CertificateManager and ObjectFormatCache for thread safety. Removed unnecessary dependency on a live CN in d1client.properties.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)