Client found that the CA PAM Client was no longer functional after a CA PAM version upgrade. The main CA PAM service was functional for some but not for all. The end-users experiencing this issue saw high utilization with the PAM client as well as trying with IE11 (Java also reported high utilization).
It was noted that in all cases where high cpu utilization there was found a bind error that was displayed when CA PAM loaded
Release : 3.x
Component : CA PAM Client
This bind error directly leads to high cpu utilization which then caused a lack of functionality.
This error is being deemed a bug and will be addressed in future releases but a workaround is listed here to bypass this.
In an earlier release of CA PAM the ability to generalize the local ports in our TCP/UDP configuration to ensure only unused ports would be utilized when the service is loaded. This will allow for locally used ports on the system would not impact the CA PAM client.