Project

General

Profile

Statistics
| Revision:
Name Size Revision Age Author Comment
  nceas 7141 about 12 years ben leinfelder check for empty null (missing) node.subjectList...

Latest revisions

# Date Author Comment
7141 04/19/2012 01:50 PM ben leinfelder

check for empty null (missing) node.subjectList. This should probably be a required element in the D1 schema, but it appears not. (ORNL entry was missing subjects in cn-dev environment)

7140 04/19/2012 11:57 AM ben leinfelder

just use the e.getMessage() as e.getCause() may be null (seeing NPE when testing via the MN IT tester)

7139 04/18/2012 04:04 PM ben leinfelder

check for empty null (missing) node.subjectList. This should probably be a required element in the D1 schema, but it appears not. (ORNL entry was missing subjects in cn-dev environment)

7137 04/17/2012 03:15 PM ben leinfelder

no not record EML access rules that use the "denyFirst" permOrder.
https://redmine.dataone.org/issues/2614

7136 04/17/2012 09:20 AM ben leinfelder

needed to initialize the nodeList that stores matching nodes (by subject) -- this was the source of a NPE when we had a matching node subject.

7135 04/16/2012 05:38 PM ben leinfelder

do not create docid-guid mapping unless we are supposed to write access rules for the data to the dbase
https://redmine.dataone.org/issues/2572

7134 04/13/2012 04:40 PM Chris Jones

As Ben suggested, don't compare to the node list if there are no replicas listed. This reduces the number of calls to listNodes() on the CN.

7133 04/13/2012 04:32 PM Chris Jones

Minor logging change in throwing ServiceFailure when Hazelcast throws a RuntimeException.

7132 04/13/2012 04:07 PM Chris Jones

Modify getSystemMetadata() to allow nodes that are listed as replicas to access the system metadata. Use the Session.Subject to find a list of nodes from the CN that match the subject, and compare those node ids to the listed replica node ids. Add listNodesBySubject() helper method to do so.

7129 04/10/2012 10:42 AM ben leinfelder

save backup properties before attempting node registration/update so that we don't "forget" the user input

View revisions

Also available in: Atom