KMA 2.3.1: Reporting Key Not Found And SOAP Errors (Doc ID 1550594.1)

Last updated on MAY 17, 2017

Applies to:

Oracle Key Manager - Version 2.0.0 to 2.5.2 [Release 2.0]
Information in this document applies to any platform.
Older KMA cluster with two nodes. Added another node recently.
First two nodes management networks are 100Mbytes/half duplex, service networks are 1000Mbytes/full duplex.
Third node, management network is at 1000Mbytes/full duplex, service network at 100Mbytes/full duplex

Symptoms

SOAP errors and "Key not found" errors coming from KMA3.  KMA1 and KMA2 are getting SOAP errors.

Lots of "close_waits" in the netstat.txt file from KMA3 and there are 13,667 keys less on KMA3

than in the cluster. Replication is not completing properly on KMA3.

Changes

 Third node added recently that was running with management network at 1000Mbyte/full duplex. Service network running at 100Mbytes/full duplex

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms