Closed AlexandruCiobanu closed 1 year ago
Very interesting. Are you using an outbound proxy server?
It would be also interesting if you can add the output of java -version
of the failed version here
Below is the java version output for the dev machine which experiences the Tag mismatch issue
# java -version
openjdk version "11.0.20" 2023-07-18 LTS
OpenJDK Runtime Environment Corretto-11.0.20.8.1 (build 11.0.20+8-LTS)
OpenJDK 64-Bit Server VM Corretto-11.0.20.8.1 (build 11.0.20+8-LTS, mixed mode)
The prod machine does not experience it :
# java -version
openjdk version "11.0.20.1" 2023-08-22 LTS
OpenJDK Runtime Environment Corretto-11.0.20.9.1 (build 11.0.20.1+9-LTS)
OpenJDK 64-Bit Server VM Corretto-11.0.20.9.1 (build 11.0.20.1+9-LTS, mixed mode)
uhoh. There is a small diff. I will try updating java to match prod and let you know
Updated dev machine to
]$ java -version
openjdk version "11.0.21" 2023-10-17 LTS
OpenJDK Runtime Environment Corretto-11.0.21.9.1 (build 11.0.21+9-LTS)
OpenJDK 64-Bit Server VM Corretto-11.0.21.9.1 (build 11.0.21+9-LTS, mixed mode)
This seems to have done the trick. Thank you!
Ah excellent - thanks :) The miracles of Java version related issues....
Hi Phil, I am struggling with an odd error. I am on a linux machine using java 11.0.20 trying to signal to the SMK a new participant. I have a small wrapper that handles parameters passed in as arguments and calls the ManageParticipantIdentifierServiceCaller . I get an SSL exception saying tag mismatch and I cannot find out why. On another machine the same code works when connecting to the SML. So production works but test does not. I tried the same code on a windows machine connecting to the SMK and it was able to successfully connect. I am at a loss as to what the problem may be. It is not a firewall issue as it can access the SMK's certificate chain. could it be a cipher issue? Both linux machines use java 11.0.20 and openssl 1.0.2.
Thank you, Alex
Please find below the redacted log of the failing call