Its was a conflict with the BouncyCastle library used by a custom connector. Setting that library to the same version as the one present in lib-connector (jdk15on-164) resolved the issue.
so, verify if it is the same case for you as well: BouncyCastle jar conflict.
Please check for any duplicate or older dependency JARs after the upgrade and remove them if found. Also, review the 8.4P3 release notes for any related prerequisites or library changes. after removing older jar files. make sure to restart tomcat. don’t forget to take a backup of deleting files.
So it seems the TransportException method has been renamed in the latest version. Therefore the algorithm can’t be found. In order to fix this issue trace which package (.jar) is the function being referred to and update the method name.