Solaris libsoftcrypto/ucrypto library added several new mechanisms and as a result, they re-ordered the mechanisms inside enum ucrypto_mech. As a result,

SHA1withRSA was 34, now it is 37
SHA256withRSA was 35, now it is 39
SHA384withRSA was 36, now it is 40
SHA512withRSA was 37, now it is 41
MD5withRSA was 33, now it's 36.

This leads to unexpected failures since OracleUcrypto still uses the old native mech values, i.e. uses 34 when java apps requests SHA1withRSA algo.