https://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2016-06-16T20:25:26ZDataONE TasksJava Client - Bug #7830: Metacat reports The CnList has not been initialized after restarting tomcathttps://redmine.dataone.org/issues/7830?journal_id=277862016-06-16T20:25:26ZRobert Waltz
<ul><li><strong>Tracker</strong> changed from <i>Task</i> to <i>Bug</i></li></ul> Java Client - Bug #7830: Metacat reports The CnList has not been initialized after restarting tomcathttps://redmine.dataone.org/issues/7830?journal_id=282752016-12-08T21:01:58ZRob Nahfrnahf@epscor.unm.edu
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>30</i></li></ul><p>looked at this as part of minor refactor / code cleanup of D1Clients. Believe that the reason for the exception was communication problem with the CN to build the NodeLocator (from cn.listNodes).</p>
<p>The newer version should have more informative exception messages and logging.</p>
Java Client - Bug #7830: Metacat reports The CnList has not been initialized after restarting tomcathttps://redmine.dataone.org/issues/7830?journal_id=291522017-09-07T17:46:26ZChris Jonescjones@nceas.ucsb.edu
<ul></ul><p>This issue is still a problem, and since it is intermittent, multiple Tomcat reboots may be necessary for the CN list to initialize correctly. This affects both Metacat MNs and the CNs. </p>
<p>However, I'm not understanding why there is a CnList at all. As I understand this, the call to @D1Client.getCN()@ should always return the Round Robin CN entry in the node list (e.g. for production: @<a href="https://cn.dataone.org/cn/v2/node/urn:node:CN@">https://cn.dataone.org/cn/v2/node/urn:node:CN@</a>). The client should never be communicating with a CN directly (like @<a href="https://cn.dataone.org/cn/v2/node/urn:node:CNUCSB1@">https://cn.dataone.org/cn/v2/node/urn:node:CNUCSB1@</a>). Perhaps I'm missing something here though.</p>
Java Client - Bug #7830: Metacat reports The CnList has not been initialized after restarting tomcathttps://redmine.dataone.org/issues/7830?journal_id=292882017-12-14T17:18:28ZRob Nahfrnahf@epscor.unm.edu
<ul></ul><p>the fix for this is only in trunk, so hasn't been deployed yet. I am not sure why it would take multiple tomcat reboots to fix a state problem of a java class instance, so maybe there is something more than a bug in the code going on. </p>
Java Client - Bug #7830: Metacat reports The CnList has not been initialized after restarting tomcathttps://redmine.dataone.org/issues/7830?journal_id=292892017-12-14T17:42:29ZRob Nahfrnahf@epscor.unm.edu
<ul></ul><p>Regarding the cnList, this construct is used only in the more generalized NodeListNodeLocator - the implementation that just relies on a NodeList to map between nodeReference and baseUrl. (This implementation is used a lot in the integration tests, where we need to get behind the round-robin to test all CN instances). D1Client uses a subclass of NodeListNodeLocator (SettingsContextNodeLocator) that overrides that general behavior and does what we want, which is return the CNode using the baseurl found in the libclient.properties file.</p>
<p>Regarding how the Round Robin CN entry in the NodeList is used:<br>
* in NodeListNodeLocator: if it can determine that one of the CNs in the nodelist is a round robin CN, it is used. If there isn't one, the NodeListNodeLocator makes its own round-robin from the listed CNs.<br>
* in SettingsContextNodeLocator: it is not used at all - the baseURL from libclient.properties is used. libclient_java ships with the production RR url, but also the CNs change that property to point to themselves. </p>
Java Client - Bug #7830: Metacat reports The CnList has not been initialized after restarting tomcathttps://redmine.dataone.org/issues/7830?journal_id=294982018-01-17T03:55:10ZRob Nahfrnahf@epscor.unm.edu
<ul></ul><p>copied the changes into the 2.3 branch, so Metacat can use it for its next deployment.</p>
Java Client - Bug #7830: Metacat reports The CnList has not been initialized after restarting tomcathttps://redmine.dataone.org/issues/7830?journal_id=294992018-01-17T03:55:50ZRob Nahfrnahf@epscor.unm.edu
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Testing</i></li><li><strong>% Done</strong> changed from <i>30</i> to <i>50</i></li></ul><p>...off to sandbox testing</p>
Java Client - Bug #7830: Metacat reports The CnList has not been initialized after restarting tomcathttps://redmine.dataone.org/issues/7830?journal_id=296742018-01-19T21:39:04ZRob Nahfrnahf@epscor.unm.edu
<ul><li><strong>Target version</strong> changed from <i>CCI-2.4.0</i> to <i>CCI-2.3.7</i></li></ul> Java Client - Bug #7830: Metacat reports The CnList has not been initialized after restarting tomcathttps://redmine.dataone.org/issues/7830?journal_id=296752018-01-19T21:41:44ZRob Nahfrnahf@epscor.unm.edu
<ul><li><strong>% Done</strong> changed from <i>50</i> to <i>80</i></li><li><strong>Status</strong> changed from <i>Testing</i> to <i>In Review</i></li></ul> Java Client - Bug #7830: Metacat reports The CnList has not been initialized after restarting tomcathttps://redmine.dataone.org/issues/7830?journal_id=297122018-01-23T18:33:44ZRob Nahfrnahf@epscor.unm.edu
<ul><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li><li><strong>Status</strong> changed from <i>In Review</i> to <i>Closed</i></li></ul><p>Jing reports success in Metacat - it didn't break things, but he doesn't have specific tests.</p>