Solved

IFS MWS Nodemanager is not starting

  • 29 June 2022
  • 4 replies
  • 484 views

Badge +14

Hi All,

Would it be possible to get your valuable ideas to fix this, please? 

IFS Services

Please find the following error that we can see when we start/ stop servers.

Exception in thread "main" java.lang.ExceptionInInitializerError
    at javax.crypto.Cipher.getInstance(Cipher.java:518)
    at sun.security.ssl.JsseJce.getCipher(JsseJce.java:189)
    at sun.security.ssl.SSLCipher.isTransformationAvailable(SSLCipher.java:483)
    at sun.security.ssl.SSLCipher.<init>(SSLCipher.java:472)
    at sun.security.ssl.SSLCipher.<clinit>(SSLCipher.java:81)
    at sun.security.ssl.CipherSuite.<clinit>(CipherSuite.java:67)
    at sun.security.ssl.SSLContextImpl.getApplicableSupportedCipherSuites(SSLContextImpl.java:345)
    at sun.security.ssl.SSLContextImpl.access$100(SSLContextImpl.java:46)
    at sun.security.ssl.SSLContextImpl$AbstractTLSContext.<clinit>(SSLContextImpl.java:577)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:264)
    at java.security.Provider$Service.getImplClass(Provider.java:1728)
    at java.security.Provider$Service.newInstance(Provider.java:1686)
    at sun.security.jca.GetInstance.getInstance(GetInstance.java:236)
    at sun.security.jca.GetInstance.getInstance(GetInstance.java:164)
    at javax.net.ssl.SSLContext.getInstance(SSLContext.java:156)
    at weblogic.security.SSL.jsseadapter.JaSSLSupport.getSupportedTLSProtocolsFromProvider(JaSSLSupport.java:80)
    at weblogic.security.SSL.jsseadapter.JaSSLSupport.<clinit>(JaSSLSupport.java:34)
    at weblogic.security.SSL.jsseadapter.JaSSLContextImpl.enforceConstraints(JaSSLContextImpl.java:309)
    at weblogic.security.utils.SSLContextWrapper.<init>(SSLContextWrapper.java:105)
    at weblogic.security.utils.SSLContextWrapper.getInstance(SSLContextWrapper.java:68)
    at weblogic.security.utils.SSLSetup.getSSLContext(SSLSetup.java:375)
    at weblogic.security.utils.SSLSetup.getSSLContext(SSLSetup.java:367)
    at weblogic.security.SSL.SSLSocketFactory.setSSLClientInfo(SSLSocketFactory.java:242)
    at weblogic.security.SSL.SSLSocketFactory.<init>(SSLSocketFactory.java:46)
    at weblogic.security.SSL.SSLSocketFactory.<init>(SSLSocketFactory.java:38)
    at weblogic.security.SSL.SSLSocketFactory.getDefault(SSLSocketFactory.java:66)
    at weblogic.nodemanager.client.DefaultSSLClient.createSocket(DefaultSSLClient.java:22)
    at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:695)
    at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:668)
    at weblogic.nodemanager.client.NMServerClient.getState(NMServerClient.java:52)
    at weblogic.nodemanager.client.DefaultSSLClient.getState(DefaultSSLClient.java:14)
    at com.ifsworld.mws.conf.NodeManagerClient.verifyCredentials(NodeManagerClient.java:377)
    at com.ifsworld.mws.conf.Domain.verifyCredentials(Domain.java:204)
    at com.ifsworld.mws.ActionImpl.verifyCredentials(ActionImpl.java:117)
    at com.ifsworld.mws.ActionImpl.getCredentials(ActionImpl.java:153)
    at com.ifsworld.mws.ServerActions.perform(ServerActions.java:58)
    at com.ifsworld.mws.ServerActions$ActionStart.perform(ServerActions.java:188)
    at com.ifsworld.mws.Actions.perform(Actions.java:38)
    at com.ifsworld.mws.ConsoleImpl.run(ConsoleImpl.java:30)
    at com.ifsworld.mws.ServerController.main(ServerController.java:12)
Caused by: java.lang.SecurityException: Can not initialize cryptographic mechanism
    at javax.crypto.JceSecurity.<clinit>(JceSecurity.java:93)
    ... 41 more
Caused by: java.lang.SecurityException: The jurisdiction policy files are not signed by the expected signer! (Policy files are specific per major JDK release.Ensure the correct version is installed.)
    at javax.crypto.JarVerifier.verifyPolicySigned(JarVerifier.java:336)
    at javax.crypto.JceSecurity.loadPolicies(JceSecurity.java:378)
    at javax.crypto.JceSecurity.setupJurisdictionPolicies(JceSecurity.java:323)
    at javax.crypto.JceSecurity.access$000(JceSecurity.java:50)
    at javax.crypto.JceSecurity$1.run(JceSecurity.java:85)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.crypto.JceSecurity.<clinit>(JceSecurity.java:82)
    ... 41 more

 

icon

Best answer by MitDenukN 29 June 2022, 21:39

View original

4 replies

Badge +14

Is there anything to do with the following?

‘Caused by: java.lang.SecurityException: The jurisdiction policy files are not signed by the expected signer! (Policy files are specific per major JDK release.Ensure the correct version is installed.)’

Badge +14

We tried a server reboot as well

Badge +14

We can’t reconfigure this because we are getting another error.

 

Badge +14

We had to delete the it from installer to fix this.

Reply