DOCBASE UNREACHABLE from WebLogic App server

rakhi_raveendran
edited February 23, 2017 in Documentum #1

Hi,

My docbase is up and running but my application server is not able to connect to docbase and is throwing the following error saying docbase is unreachable.

The docbroker ports(1489 and 1490) are open in content server and I am able to do telnet to the application server from content server and vice versa.

DfServiceException:: THREAD: [ACTIVE] ExecuteThread: '68' for queue: 'weblogic.kernel.Default (self-tuning)'; MSG: [DFC_SESSION_DOCBASE_UNREACHABLE] Docbase "xxxxxx" is unreachable; ERRORCODE: ff; NEXT: null

at com.documentum.fc.common.DfException.<init>(DfException.java:321)

at com.documentum.fc.client.DfDocbaseUnreachableException.<init>(DfDocbaseUnreachableException.java:14)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.establishNewRpcClient(DocbaseConnection.java:197)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.open(DocbaseConnection.java:112)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.<init>(DocbaseConnection.java:86)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.<init>(DocbaseConnection.java:54)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnectionFactory.newDocbaseConnection(DocbaseConnectionFactory.java:26)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnectionManager.getDocbaseConnection(DocbaseConnectionManager.java:42)

at com.documentum.fc.client.impl.session.SessionFactory.newSession(SessionFactory.java:29)

In addition to this, I'm seeing the below lines in the docbroker logs.

Documentum Docbroker: dispatcher failed (104) on line 980 -- non-fatal

Documentum Docbroker: dispatcher failed (104) on line 980 -- non-fatal

Documentum Docbroker: nl_close failed (533) on line 1066 -- fatal

Documentum Docbroker: dispatcher failed (104) on line 980 -- non-fatal

Documentum Docbroker: nl_close failed (533) on line 1066 -- fatal

I'm really clueless on what could be the issue.

Please help

Best Answer

  • rakhi_raveendran
    edited February 23, 2017 #2 Answer ✓

    Hi Johny/Ahmad,

    The issue got resolved. It was a network issue in the connectivity between app and content servers. Anyways,

    Thank you so much for your time.

    The connection was getting timed out with docbase port configured in /etc/services.

Answers

  • DCTM_Guru
    edited February 21, 2017 #3

    Have you restarted weblogic?  If you have restarted Content Server, you should always restart app server as well since some information gets cached.

    Are you using hostname or IP address in the dfc.properties file for you web app?

  • Haroon_A
    edited February 21, 2017 #4

    order or start.

    0. database

    1. docbroker

    2. docbase

    3. app server

    shutdown should be reverse

  • rakhi_raveendran
    edited February 21, 2017 #5

    Hi Johnny,

    Yes,we have restarted application server along with the content server and we have IP addresses in dfc.properties. It was working fine and suddenly we started facing this issue.

    Also, do you have any idea on what is the dispatcher error coming in docbroker logs.

    Regards,

    Rakhi

  • rakhi_raveendran
    edited February 22, 2017 #6

    Hi Ahmed,

    Thanks for your reply. We did not do database restart. But did complete restart of app and content servers in the correct order.

    regards,

    Rakhi

  • DCTM_Guru
    edited February 22, 2017 #7

    Did you restart docbroker?  Use the sequence that Ahmad has listed in order to avoid any caching issues.

  • rakhi_raveendran
    edited February 22, 2017 #8

    Hi Johny,

    Yes, we restarted in the mentioned order. Still facing the issue.

  • Haroon_A
    edited February 22, 2017 #9

    Rakhi,

    Before starting docbase, your docbroker MUST be running, in order for your docbase to project to your docbroker. Or else, your clients won't be able to find the docbase.

    Do a restart of your environment in proper sequence. Assuming, the firewall, connectivity isn't an issue and your dfc.properties are set properly at your client level.

  • rakhi_raveendran
    edited February 22, 2017 #10

    Hi Ahmad,

    Thank you  for your response. We did start it in the correct order. We are able to connect from Samson to docbase and also execute dfc codes from one of our windows servers using the same dfc properties that we are using at client level.

    This was working without any problem and suddenly we started getting this issue. Should be something with network but not able to find anything. Ports are open and telnet is happening between content and app servers.

    Any other suggestions to troubleshoot the issue?

  • rakhi_raveendran
    edited February 23, 2017 #11 Answer ✓

    Hi Johny/Ahmad,

    The issue got resolved. It was a network issue in the connectivity between app and content servers. Anyways,

    Thank you so much for your time.

    The connection was getting timed out with docbase port configured in /etc/services.