Bug #2303
CN.updateNodeCapabilities() call fails on cn-dev
100%
History
#1 Updated by Ben Leinfelder about 12 years ago
- Category set to d1_cn_node_registry
- Assignee set to Robert Waltz
While testing Metacat MN registration with cn-dev, Matt's CN.updateNodeCapabilities() call returned an error.
cn-dev logs showed the following stack trace for that call:
20120208-02:13:19: [DEBUG]: Could not complete request [org.springframework.web.servlet.DispatcherServlet]
java.lang.IllegalStateException: Unable to connect to cluster
at com.hazelcast.client.HazelcastClient.(HazelcastClient.java:91)
at com.hazelcast.client.HazelcastClient.(HazelcastClient.java:129)
at com.hazelcast.client.HazelcastClient.newHazelcastClient(HazelcastClient.java:265)
at org.dataone.cn.rest.web.node.NodeController.updateNodeCapabilities(NodeController.java:146)
Perhaps it's as simple as a Hazelcast misconfiguration? Or something more?
#2 Updated by Matthew Jones about 12 years ago
- Target version changed from Sprint-2012.03-Block.1.2 to Sprint-2012.05-Block.1.3
- Position deleted (
1) - Position set to 1
#3 Updated by Robert Waltz about 12 years ago
- Status changed from New to Closed
hzNode map was not available to the d1_cn_rest service because d1_processing was not running.
I have tested updateNodeCapabilities with nodeId r6K4 and confirmed that it did properly update the node
