Troubleshooting
Problem
Deleting a model in IBM Rational Rhapsody Design Manager results in CRJZS5531E error: The server stopped the SPARQL query because it was taking too long to run and return results. For details, check the server log.
Symptom
com.ibm.team.jfs.sdk.common.OperationTimeoutException: CRJZS5531E The server stopped the SPARQL query because it was taking too long to run and return results. For details, check the server log.
at com.ibm.team.jfs.rdf.internal.jena.tdb.JenaTxTdbProvider.query(JenaTxTdbProvider.java:2191)
at com.ibm.team.jfs.sdk.query.internal.SparqlQueryService.performQuery(SparqlQueryService.java:413)
at com.ibm.team.jfs.sdk.query.internal.SparqlQueryService.execute(SparqlQueryService.java:225)
at sun.reflect.GeneratedMethodAccessor1194.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at com.sun.proxy.$Proxy3628.execute(Unknown Source)
at com.ibm.xtools.rmps.frontservice.jaf.sparql.internal.JfsSparqlServicePojo.executeQuery(JfsSparqlServicePojo.java:557)
at com.ibm.xtools.rmps.frontservice.jaf.sparql.internal.JfsSparqlServicePojo.internalExecuteSelectSparqlQuery(JfsSparqlServicePojo.java:470)
at com.ibm.xtools.rmps.frontservice.jaf.sparql.internal.JfsSparqlServicePojo.executeSelectSparqlQueryAsString(JfsSparqlServicePojo.java:227)
at com.ibm.xtools.rmps.frontservice.jaf.sparql.internal.JfsSparqlServicePojo.executeSelectSparqlQueryAsyncAsString(JfsSparqlServicePojo.java:175)
at com.ibm.rational.carter.queries.AbsQuery.runJfsQuery(AbsQuery.java:43)
at com.ibm.rational.carter.queries.QueryResources$GetModelResources.runAndGetDiagrams(QueryResources.java:624)
at com.ibm.rational.carter.resource.ModelResourceUtil.getModelResourcesAndDiagrams(ModelResourceUtil.java:112)
at com.ibm.rational.carter.tasks.InitDeleteTask.main(InitDeleteTask.java:44)
at com.ibm.rational.carter.tasks.AbstractTask.execute(AbstractTask.java:42)
at com.ibm.rational.carter.requests.AbstractRequest.actualCall(AbstractRequest.java:208)
at com.ibm.rational.carter.requests.AbstractRequest.actualCall(AbstractRequest.java:1)
at com.ibm.xtools.rmps.frontservice.jaf.common.internal.threads.DMCallable.call(DMCallable.java:30)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:790)
Cause
Large model or model publish was not previously completed.
Diagnosing The Problem
- In some case the model may be large, so you should check if this is an issue by increasing the timeout.
- The "Jena query operation logging time threshold" property is the limit
- If extending the timeout does not resolve the problem you should run the model validation checker:
that the query execution needs to exceed to be written to the log file.
So increasing this value will make it less likely that an error will be
logged before completing.
The "SPARQL Query abort timeout" prevents queries running forever and
using up system resources. So setting this to an excessively high value
may have a performance impact. The value we recommended shouldn't have
an adverse effect on performance, but if the delete query still times
out and a degraded performance is apparent, we might look at putting it
back to its default value.
- 1. Paste this in the browser address bar, substituting the <serverUrl>
for your own:
<serverUrl>/dm/admin#action=com.ibm.team.repository.admin.configureAdvan
ced
2. Change the following properties:
Jena query operation logging time threshold (in ms): 45000 --> 500000
SPARQL Query abort timeout (in ms) 300000 -----> 3000000
3. Hit Save at the top right of the page
4. Try the delete operation again.
- 1. Go to dm/admin page
2. click on the diagnostics link on the left
3. In the list of tests, select the "Model Validation Page"
4. From here you can select the project, which will tell you if there
are any problems with the model. Including dangling resources and
unresolved elements.
Resolving The Problem
Extend the timeout of delete queries or remove and republish depending on the results of the above diagnosis.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21989409