Context Service: Deregistration Fails

From DocWiki

Jump to: navigation, search

Context Service: Deregistration Fails

Problem Summary Deregistration from Context Service fails.
Error Message None
Possible Cause If the AW-HDS-DDS side A can access the key management system (KMS) but not the rest of Context Service, registration appears to succeed even if a proxy server URL was not configured. However, deregistration fails because the cluster was not created, which happens during the first heartbeat.
Recommended Action
  1. Look for the following in the Context Service log:
    0000000111: *.*.*.*: Aug 12 2016 10:46:59.835 -0400: %_Thread-25-6-com.cisco.thunderhead.RESTClient:
    Error on CREATE: https://hercules-a.wbx2.com/v1/connectors
    0000000112: *.*.*.*: Aug 12 2016 10:46:59.835 -0400: %_Thread-25-3-com.cisco.thunderhead.RESTClient:
    Error: try #1: Exception trying to connect=com.sun.jersey.api.client.ClientHandlerException: org.apache.http.conn.HttpHostConnectException:
    Connect to hercules-a.wbx2.com:443 [hercules-a.wbx2.com/*.*.*.*, hercules-a.wbx2.com/*.*.*.*] failed: Connection timed out: connect
  2. Configure a proxy server URL and try to register to Context Service again.
Release 11.5(1)
Associated CDETS # None



Rating: 0.0/5 (0 votes cast)

Personal tools