nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

D6.5 SP1 Crash

dinodia

Hi All,

We have a Documentum 6.5 SP1 installation on Solaris. The server went down a couple of days back. There was no response when the URL of the core services WSDLs (ObjectService, SearchService etc) were hit. I tried stopping the method server which did not respond for close to 10 mins and then said connection timed out. The logs showed the following exceptions:

1. Request to the docbroker failed.

2. Server Communication failure.

3. Connection refused.

4. Authorization failed, Please review the identities provided in service context.

I had to kill the jboss process. Started the server after this and it is working fine.

We are in the process of doing a root cause analysis for this and need help. Please do.

Thanks in advance.

- Deepak.

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Button

Accepted answers

zhou_simonq

From the server.log, I can see that client cannot connect with Docbroker. All the failures are caused by "Connection refused" by Docbroker. This issue can be sorted out in server side and client side respectively.

For troubleshooting:

1) make sure the Dobroker myserver:1489 is running.

2) are you using SSL Docbroker? If it is, make sure SSL docbroker is running.

3) on server side, make sure the Docbroker is configured correctly in the repository. For more info, pls refer to the Administration Guide and Object Reference Manual.

4) on client side, make sure Docbroker is configured correctly in file dfc.properties. Usually, dfc.properties locates in two places. The first one is in directory ${Documentum}/config, usually this one can be shared among several applications. The second one resides in each appliation, such as ACS, DFS deployment, etc. Go to the deployment of corresponding application, find ${APP_HOME}/APP-INF/classes and find dfc.properties.

5) it seems that there is something wrong with the ACS configuration. Type http://server_name:9080/ACS/servlet/ACS to check whether ACS server is running. There is on the server side. go to $JBOSS_HOME}/server/DctmServer_MethodServer/deploy/acs.ear/APP-INF/classes/dfc.properties, make sure the Docbroker configuration is right. If there is no such configuration in this file, find file ${Documentum}/config/dfc.properties, make sure the Docbroker configuation is OK.

- simon

All comments

Francois Dauberlieu

Did you get any message in the Documentum logs as well as at the OS level ?

dinodia

hi francois,

I didnt find anything in the OS logs. It was only the documentum server logs. I could connect to the docbase from DA where as there was no response from the service URLs for the various services.

- Deepak.

zhou_simonq

sounds strange.

if you are using Windows and OOTB installation of DFS:

1) execute command "netstat -nao|findstr 1489" to make sure docbroker is running

2) execute command "netstat -nao|findstr 9080" to make sure the application server is running.

From the info you provided, it seems that there is something wrong with JBOSS, is there any log info for JBOSS?

can this issue be reproduced?

- simon

dinodia

Hi Simon,

The server is on a Solaris box. Attached are the logs. I am not sure if this can be reproduced. The server is in production from 2 months and this is the first time such a problem has occured.

-Deepak.

zhou_simonq

For troubleshooting:

1) make sure the Dobroker myserver:1489 is running.

2) are you using SSL Docbroker? If it is, make sure SSL docbroker is running.

3) on server side, make sure the Docbroker is configured correctly in the repository. For more info, pls refer to the Administration Guide and Object Reference Manual.

- simon

dinodia

This is Awesome information. Thanks Simon.

I require another help from you here. I need to create a report with the root cause analysis for this error. Could you figure out why this happened.

-Deepak.

zhou_simonq

For root cause analysis, I think my previous answer has given you enough info. I don't know exactly why your application failed. But you can get the reason by some analysis.

- simon

dinodia

Thanks a lot Simon