How to fix "[DM_SESSION_E_RPC_ERROR]error: "Server communication failure"; ERRORCODE: 100; NEXT: null"

Question

I've been trying to create a session from a SessionManager in order to perform some actions on the Documentum application. My application failed to connect to the server giving me a "Server communication failure" caused by javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure. I've looked in the logs of the application, realizing that there is a problem with my dfc.globalregistry (username, password and repository). Are there any default globalregistry values in order to create a connection with the server?

private static void createSession() throws Exception {
        DfClientX clientx = new DfClientX();
        IDfClient localClient = clientx.getLocalClient();
        sessionManager = localClient.newSessionManager();
                IDfLoginInfo loginInfo = clientx.getLoginInfo();
        loginInfo.setUser(USERNAME);
        loginInfo.setPassword(PASSWORD);
        if (sessionManager.hasIdentity(REPOSITORY)) {
            sessionManager.clearIdentity(REPOSITORY);
        }
        sessionManager.setIdentity(REPOSITORY, loginInfo);
        session = sessionManager.getSession(REPOSITORY);
}

This method is called and failes at session = sessionManager.getSession(REPOSITORY); Any suggestions?

Full stacktrace:

DfIOException:: THREAD: main; MSG: [DM_SESSION_E_RPC_ERROR]error:  "Server communication failure"; ERRORCODE: 100; NEXT: null
    at com.documentum.fc.client.DfIOException.newCommunicationFailureException(DfIOException.java:16)
    at com.documentum.fc.client.impl.connection.netwise.AbstractNetwiseRpcClient.sendMessage(AbstractNetwiseRpcClient.java:216)
    at com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.newSessionByAddr(NetwiseDocbaseRpcClient.java:102)
    at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.beginSession(DocbaseConnection.java:298)
    at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.open(DocbaseConnection.java:129)
    at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.<init>(DocbaseConnection.java:99)
    at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.<init>(DocbaseConnection.java:59)
    at com.documentum.fc.client.impl.connection.docbase.DocbaseConnectionFactory.newDocbaseConnection(DocbaseConnectionFactory.java:26)
    at com.documentum.fc.client.impl.connection.docbase.DocbaseConnectionManager.createNewConnection(DocbaseConnectionManager.java:180)
    at com.documentum.fc.client.impl.connection.docbase.DocbaseConnectionManager.getDocbaseConnection(DocbaseConnectionManager.java:110)
    at com.documentum.fc.client.impl.session.SessionFactory.newSession(SessionFactory.java:23)
    at com.documentum.fc.client.impl.session.PrincipalAwareSessionFactory.newSession(PrincipalAwareSessionFactory.java:44)
    at com.documentum.fc.client.impl.session.PooledSessionFactory.newSession(PooledSessionFactory.java:49)
    at com.documentum.fc.client.impl.session.SessionManager.getSessionFromFactory(SessionManager.java:134)
    at com.documentum.fc.client.impl.session.SessionManager.newSession(SessionManager.java:72)
    at com.documentum.fc.client.impl.session.SessionManager.getSession(SessionManager.java:191)
    at training.sessions.SessionTest.createSession(SessionTest.java:72)
    at training.sessions.SessionTest.main(SessionTest.java:29)
Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    at sun.security.ssl.Alerts.getSSLException(Unknown Source)
    at sun.security.ssl.Alerts.getSSLException(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)
    at sun.security.ssl.AppOutputStream.write(Unknown Source)
    at com.documentum.fc.impl.util.io.MessageChannel.writeSocket(MessageChannel.java:261)
    at com.documentum.fc.impl.util.io.MessageChannel.write(MessageChannel.java:219)
    at com.documentum.fc.client.impl.connection.netwise.AbstractNetwiseRpcClient.sendMessage(AbstractNetwiseRpcClient.java:211)
    ... 16 more

You might be right. I wondered if there are any default values for the globalregistry in order to connect to the server. The problem occurs when I try to get a new session — Razvan Dragos, Jul 10 '19 at 06:54
I assume the repository holds authentication data, but not the transport layer keystores/trustores — Kris, Jul 10 '19 at 06:57
The repository holds the repository name I'm trying to connect in order to do some actions and yes, it doesn't hold the transport layer keystores — Razvan Dragos, Jul 10 '19 at 06:59
Well the error is originating from the transport layer. So I think registry is not the place to fix it. — Kris, Jul 10 '19 at 07:01
Thanks @Kris I will keep trying to investigate into this problem. — Razvan Dragos, Jul 10 '19 at 07:02
Also it can be useful to obtain a docbroker map and print this out - that way you can eliminate dfc.properties configuration issues — Henning Winter, Sep 25 '19 at 08:55

How to fix "[DM_SESSION_E_RPC_ERROR]error: "Server communication failure"; ERRORCODE: 100; NEXT: null"

0 Answers0