KB215599: "System call error....Find target process dead while waiting for reply" error is received when attempting to connect to a Composite 6.2 database

INTRODUCTION
Composite 6.2 is certified as a warehouse with Strategy 9.3.1 - 9.4.1. Refer to the required Strategy version readme for the full certification information. 
 
SYMPTOM
In Strategy 9.3.1 - 9.4.1, the following error is received when users attempt to connect to Composite 6.2 using the certified Composite 6.0.2 driver:

Error type: System call error. Error communicating with connection process. Find target process dead while waiting for reply. 

Also, it is seen that the database connection process crashes unexpectedly, resulting in a core file generation (if core file creation is enabled).
 
CAUSE
This error can be seen when the connectivity parameters are not setup correctly as specified in KB38539. When the connectivity is not setup correctly and an error is received, the error is not handled correctly by the driver library and results in the crash of the database connection. This in turn throws the generic error message instead of the actual error message received when attempting to connect to the Composite 6.2 database. 
 
ACTION
An issue has been logged with Composite to fix the issue with the driver. Contact Strategy Technical Support for additional information. A ticket number for Composite is not available at the time of writing this document. 
 
WORKAROUND
Implement the steps below to get details about the actual error message received when attempting to connect to the Composite 6.2 database. 
 
After configuring the DSN on the Linux client, look for the file:
<Composite_Home>/composite62.xml
(file name will vary based on the version of composite)
 
To enable debugging, edit this file and add the following option to the "host" element for the DSN that needs to be debugged. 'debug' gives the full verbosity protocol level details.

traceLevel="debug"

 
Here's an example of a trace-enabled DSN entry in the composite62.xml file:

<connection name="my_test"> 
<driver name="Composite 6.0" version="6.0.2.0" /> 
<host name="localhost" port="9401" uid="test" 
password="5EA27D000D0AB84D" datasource="ds" catalog="cat" 
domain="composite" traceLevel="debug" /> 
</connection>

NOTE: the string "traceLevel" is case sensitive.
 
After making a client connection through this DSN from a tool such as Strategy DB Query Tool or command line ODBC Test Tool, a new file 'CsOdbcDebug.txt' file will appear in the <Composite_Home> directory. This error log will have the detailed messages. An example log entry has been provided below: 

 11/5/2014 14:01:03 3e16.f747ab70 ====
 11/5/2014 14:01:03 3e16.f6effb70 < error 1 2 AuthenticationError
 11/5/2014 14:01:03 3e16.f6effb70 < field string Authentication failed for user "TEST" in domain "win32ad". [security-1900206]
 11/5/2014 14:01:03 3e16.f6effb70 < field string com.compositesw.common.security.CompositeSecurityException: Authentication failed for user "TEST" in domain "win32ad". [security-1900206]
  at com.compositesw.server.security.DefaultAuthenticationManager.handleAuthException(DefaultAuthenticationManager.java:487)............
 "Caused by: java.lang.Exception: Invalid domainName="win32ad" specified for authentication."