java.lang.IllegalArgumentException

Invalid trust file name of null

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web17621

  • via objectmix.com by Unknown author, 10 months ago
    Invalid trust file name of null
  • Invalid trust file name of null
  • via Google Groups by vara...@gmail.com, 1 year ago
    Invalid trust file name of null
  • Stack trace

    • java.lang.IllegalArgumentException: Invalid trust file name of null at com.ibm.ws.ssl.provider.AbstractJSSEProvider.getKeyTrustManagers(AbstractJSSEProvider.java:329) at com.ibm.ws.ssl.provider.AbstractJSSEProvider.getSSLContext(AbstractJSSEProvider.java:151) at com.ibm.ws.ssl.provider.AbstractJSSEProvider.getSSLSocketFactory(AbstractJSSEProvider.java:740) at com.ibm.websphere.ssl.JSSEHelper.getSSLSocketFactory(JSSEHelper.java:574) at com.ibm.websphere.ssl.protocol.SSLSocketFactory.<init>(SSLSocketFactory.java:87) at java.lang.Class.newInstanceImpl(Native Method) at java.lang.Class.newInstance(Class.java:1263) at javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:9) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at com.sun.jndi.ldap.Connection.createSocket(Connection.java:295) at com.sun.jndi.ldap.Connection.<init>(Connection.java:209) at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:133) at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1593) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2611) at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:298) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:190) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:208) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151) at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:81) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:679) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:259) at javax.naming.InitialContext.init(InitialContext.java:235) at javax.naming.InitialContext.<init>(InitialContext.java:209) at com.hi.ehouse.services.jndi.JNDIHelper.createInitialDirContext(JNDIHelper.java:300)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.