This type of issue can sometimes be resolved by cycling the Csam service on the WCC server. In order to cycle the Csam service, you must first stop the WCC services that are using it. Here are the steps...
Go to Services and stop CA-wcc-services and CA-wcc
Stop and restart the CA Connection Broker service
Run 'unisrvcntr stop CA-wcc-services' and then run ustat to ensure both CA-wcc-services and CA-wcc are stopped.
Run '/opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux stop'
Run '/opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux start'
Run 'ps -ef|grep csam' and ensure there is a csampmuxf process running
Run 'unisrvcntr start CA-wcc' and then run ustat to ensure both CA-wcc and CA-wcc-services are running.