000022467 - How to resolve 'handshake failed' errors that appear in RSA ClearTrust Dispatcher log

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000022467
Applies ToRSA ClearTrust 5.0.1
Sun Solaris 2.8
IssueHow to resolve "handshake failed" errors that appear in RSA ClearTrust Dispatcher log
The following errors appear in dispatcher.log when starting the dispatcher:
Event Type = ,Error,Event Description = ,Error handling client connection,Error = ,java.io.IOException: handshake failed, socket closed prematurely
Event Type = ,Error,Event Description = ,Error handling client connection,Error = ,java.io.IOException: handshake failed, An IOException occured while writing the serverKeyExchange message
ClearTrust Agents are unable to contact the Dispatcher for a list of available Authorization Servers.
CauseIn some Sun Solaris environments, the RSA ClearTrust Dispatcher may take up to 20 seconds to generate a key for inter-component communication. If the Agent's dispatcher_timeout value is set too low, the Agent will declare the Dispatcher "unreachable." If only one Dispatcher is set up in an environment, this will prevent ClearTrust from functioning properly.
ResolutionTo correct this issue, set the value of cleartrust.agent.dispatcher_timeout to 20 seconds or greater, then restart web servers and the RSA ClearTrust server components.
Legacy Article IDa29856

Attachments

    Outcomes