[DM_SESSION_E_RPC_ERROR]error: "Server communication failure"

LakeAlex

Hello All.

I work with DFS.

There is a function. It carries out a regular query to the server in cycle.

A lot of the queries are successful. After a number hours of working I get error: "QUERY" action failed.

In the logs I have found [DM_SESSION_E_RPC_ERROR]error:  "Server communication failure".

What are possible causes of it?

Thanks

lastnitescurry

do you close query collections?

do you release sessions or just let them timeout?

LakeAlex

Saying more exactly I work with web-service and WCF.

Here is the code:

BasicHttpBinding bhb = new BasicHttpBinding();

            bhb.Name = "QueryServicePortBinding";

            EndpointAddress endpointAddress = new EndpointAddress(address + "/core/QueryService");

            QueryServicePortClient querySvc = new QueryServicePortClient(bhb, endpointAddress);

            int nCounter = -1;

            using (OperationContextScope scope = new OperationContextScope(new OperationContext(querySvc.InnerChannel)))

            {

                // Use the ServiceContext

                ServiceContextHeader scx = new ServiceContextHeader();

                RepositoryIdentity repoId = new RepositoryIdentity();

                repoId.repositoryName = repository;

                repoId.userName = userName;

                repoId.password = password;

                repoId.domain = domain;

                scx.AddRepositoryIdentity(repoId);

                OperationContext.Current.OutgoingMessageHeaders.Add(scx);

                for (int i = 1; i < int.MaxValue; i++)

                {

                    String sTemp = sName;

                    sTemp = sTemp.Replace(sCounterDescription, i.ToString());

                    PassthroughQuery query = new PassthroughQuery();

                    if (sPath.Equals(String.Empty))

                        query.queryString = "select object_name from dm_document where object_name = '" + sTemp + "'";

                    else

                        query.queryString = "select object_name from dm_document where folder('"

                            + sPath + "') and object_name = '" + sTemp + "'";

                    query.repositories = new string[1];

                    query.repositories[0] = sDocbase;

                    QueryExecution queryEx = new QueryExecution();

                    queryEx.cacheStrategyType = CacheStrategyType.DEFAULT_CACHE_STRATEGY;

                    queryEx.maxResultCount = 100;  // Must specify this or query doesn't return any results

                    QueryResult queryResult = querySvc.execute(query, queryEx, null);

                    if (queryResult.dataPackage != null)

                    {

                        DataPackage resultDp = queryResult.dataPackage;

                        DataObject[] dataObjects = resultDp.DataObjects;

   

                        if (dataObjects.Length == 0)

                        {

                            nCounter = i;

                            break;

                        }

                    }

     

                }

            }

LakeAlex

I have found more information in server logs. Unfortunately, I found nothing useful in the Internet to resolve this issue.

Can anybody help me?

 

Tue Nov 30 01:34:26 2010 681000 [DM_SESSION_E_CANT_MAKE_TEMP_CONNECTION]error:  "Could not establish an internal, temporary database connection (database_name = db_documentum, docbase_owner = documentum, connection_string = DOCUMENTUMDB); database system error was:  STATE=S1T00, CODE=0, MSG=[Microsoft][ODBC SQL Server Driver]Timeout expired

ERROR(-1) "

Current Session ID: 01de75d180031571

Last SQL statement executed by DB was:

Current Session ID: 01de75d18002eb9a

Last SQL statement executed by DB was:

TID(2788) failure during processing of request: NewSessionByAddr_string.

TID(1840) failure during processing of request: NewSessionByAddr_string.

Tue Nov 30 01:34:28 2010 Documentum Internal Error: Assertion failure at line: 288 in file: \Content_Server\Main\dmnew\rpc\netwise\server\dmconn.cxx

Tue Nov 30 01:34:28 2010 Documentum Internal Error: Assertion failure at line: 288 in file: \Content_Server\Main\dmnew\rpc\netwise\server\dmconn.cxx

Jubedus

Hi LakeAlex,

            Are you able to run your application again after getting this error without restarting the Content Server and/or the Database?

            If yes then probably some of the queries are taking too much time to execute. I’d suggest logging the queries before they are executed. It’ll help you to identify the exact query that’s causing the problem. Then you’ll be to analyze the query and figure out how to improve it.

            Alternatively, you may also increase the query timeout for your database.

            Good luck!

LakeAlex

Thank you Jubedus,

I will try to use your advices.

LakeAlex

The problem is resolved by increasing RAM memory on server. 1.3 Gb was on server. Now 3 Gb is on server.

nemelk

I am seeing similar message - on content server I have:

Authentication method : Ticket, client_host : bpl-jbossprod02, current_rpc : EXEC, db_session : 130, LibVersion : 7.2.0170.0165, listIndex : 497, Locale : (Linux :(8201), Version: Linux), CharSet: UTF-8, Language: , UTC Offset: 7200, Date Format, pid : 12940, reconnect : 0, shutdownflag : 0, tempdb_session : -1, temperature : 3, token : , typelockdb_session : -1, user : cretnikt, last_rpc : GET_ERRORS
TID(5932) Exception Stack Dump:
Exception 00000000C0000005 (ACCESS_VIOLATION) occurred at 00007FFA96ED8EAC.
RaiseException+6cRaiseException+6c 000000018066A4DA / 00000000087AD6A0
dmReaderWriter::DoShared+20a f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\common\compat\dmmontor.cxx:484 00000001802D8322 / 00000000087AD890
dmSafeCache::FindObject+82 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\compat\dmscache.cxx:652 00000001802D8C06 / 00000000087AD910
dmSafeCache::ParentFetch+86 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\compat\dmscache.cxx:313 0000000180629F47 / 00000000087ADBB0
dmNamedObjectCache::Fetch+e7 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\common\compat\dmhash.cxx:1193 000000018062AC3B / 00000000087ADC40
dmNamedObjectCache::FindObject+bb f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\common\compat\dmhash.cxx:1351 000000018065AF83 / 00000000087ADC80
dmCheckCache+53 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\common\object\dmgcache.cxx:58 00000001802E353D / 00000000087ADCC0
dmPTManager::FetchFromCache+4d f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\type\typemgr.cxx:4846 00000001802E4ED2 / 00000000087ADCF0
dmPTManager::FetchInternal+62 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\type\typemgr.cxx:4936 00000001802E0392 / 00000000087ADD30
dmPTManager::DoFetch+a2 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\type\typemgr.cxx:4916 00000001805BF4C1 / 00000000087ADD90
validate_type_name+61 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\query\doc_expr.cxx:2292 00000001805BCC96 / 00000000087ADE00
make_table_reference_clause+296 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\query\doc_expr.cxx:1023 00000001805BBB33 / 00000000087ADF50
make_from_clause+e3 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\query\doc_expr.cxx:1442 00000001805AE050 / 00000000087ADFF0
build_select+220 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\query\query_sp.cxx:1370 00000001805B475F / 00000000087AE190
make_query_specification+9f f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\query\query_sp.cxx:155 000000018059EA5C / 00000000087AE1F0
Process_Select_Stmt+31c f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\query\select.cxx:480 0000000180397B55 / 00000000087AE3F0
dm_ExecQuery+365 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\query\exec.cxx:390 000000018020B9B2 / 00000000087AE4A0
dmExecIt+e2 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\initial\dminit.cxx:1189 0000000180174BA9 / 00000000087AE510
dmSession::Apply+539 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\session\dmsess.cxx:668 000000018012613E / 00000000087AE670
DoApply+5ee f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\rpc\netwise\server\dmrpc.cxx:824 0000000180125250 / 00000000087AE8B0
ApplyInternal+1c0 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\rpc\netwise\server\dmrpc.cxx:864 00000001805F90A7 / 00000000087AEBA0
Apply_string+207 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\rpc\netwise\server\dmapply.cxx:1627 00000001805F5626 / 00000000087AEE30
iIXApply_string+46 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\rpc\netwise\server\stubs\sstubs.c:6444 000000018011A710 / 00000000087AEE80
nwvss_+230nwvss_+230 00000001805F16D3 / 00000000087AEF80
S_Apply_string+e3 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\rpc\netwise\server\stubs\sstubs.c:6502 000000018057C921 / 00000000087AF0D0
driver_Proc+931 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\rpc\netwise\server\stubs\bstubs.c:988 000000018026F594 / 00000000087AF6F0
dmNetwiseConnection::Dispatch+134 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\rpc\netwise\server\dmnwisew.cxx:806 000000018013171B / 00000000087AF7C0
dmSessionThreadStart+42b f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\rpc\netwise\server\dmconn.cxx:221 00000001801216E6 / 00000000087AFB90
threadMain+1b6 f:\perforce\depot\platform\contentserver\hfx\hfx_7.2_rc\dmnew\server\compat\dmthread.cxx:76 00007FFA900A4F7F / 00000000087AFEF0
beginthreadex+107beginthreadex+107 00007FFA900A5126 / 00000000087AFF20
endthreadex+192endthreadex+192 00007FFA997D13D2 / 00000000087AFF50
BaseThreadInitThunk+22BaseThreadInitThunk+22 00007FFA99A254F4 / 00000000087AFF80

TID(5932) failure during processing of request: Apply_string. Fri Jun 22 15:12:01 2018 NT Exception: Exception Address: 96ed8eac, ACCESS_VIOLATION at (Apply_string)
Fri Jun 22 15:12:01 2018 Documentum Internal Error: Assertion failure at line: 287 in file: ........\rpc\netwise\server\dmconn.cxx

David Sciuto

Can you help answer this question?

We have noticed this question is over 30 days old and hasn't received a response. We're turning to you, the community, to help answer it.

This generic response is intended to prompt discussion in this post. The question remains open to your answers, suggestions, and best practices.

If you posted this question, what additional information can you provide to help us respond to you? Were able to resolve the issue? Please share your solution here with others. If you still need additional help, though, please let us know. Your question and its resolution are important to us, and we want to help.

• Please note that questions to the developer network are typically peer-to-peer, best effort responses. If you are a customer of the product about which you're inquiring, please consider moving this post to the product forum where it may receive more attention from our experts.

• Additionally, note that posting questions to General may not be answered by a product expert. The General forum is for non-product questions. Please be sure to post your product-specific questions to the proper product forum.

Brian Dinneen

@nemelk it is not the same error! As you are on 7.2 deploy the latest patch on test and retest.

Please do not hijack old threads that have already been answered.
Please create your own and post links to similar threads to show you have researched and worked on your problem