Modified DumpJournal to track the #of errors when dumping the pages of an index and continue (unless interrupted or cancelled).

See #855 (AssertionError: Child does not have persistent identity)

git-svn-id: https://svn.code.sf.net/p/bigdata/code/branches/BIGDATA_RELEASE_1_3_0@7983 8f7bc0f5-282e-0410-95e3-8d296e9bb460
Modified DumpJournal.main() to catch Throwable and log @ ERROR rather than just catching RuntimeException.

git-svn-id: https://svn.code.sf.net/p/bigdata/code/branches/BIGDATA_RELEASE_1_3_0@7984 8f7bc0f5-282e-0410-95e3-8d296e9bb460
I have modified the DefaultNodeCoder in the 1.3.0 development and maintenance branch to explicitly look for a 0L in the valid childAddr slots and throw an exception.  This will prevent bad data from becoming durable.

I do not observe any problems in the local B+Tree test suite.  I am committing this change to CI for feedback from full CI runs.

See #855 (Child identity is not persistent).

git-svn-id: https://svn.code.sf.net/p/bigdata/code/branches/BIGDATA_RELEASE_1_3_0@7985 8f7bc0f5-282e-0410-95e3-8d296e9bb460
javadoc on the semantics of interrupting (a) the submission of a query; and (b) a running query.

See #864 and #707.

git-svn-id: https://svn.code.sf.net/p/bigdata/code/branches/BIGDATA_RELEASE_1_3_0@8005 8f7bc0f5-282e-0410-95e3-8d296e9bb460
Bug fix to the GRS to protect the index with an UnisolatedReadWriteIndex along all code paths. This is only a partial fix for the reported problem.  I am committing this change to CI for feedback before committing through the NSS specific modifications.

See #867 (NSS concurrency problem with list namespaces and create namespace)

git-svn-id: https://svn.code.sf.net/p/bigdata/code/branches/BIGDATA_RELEASE_1_3_0@8015 8f7bc0f5-282e-0410-95e3-8d296e9bb460