/rm/publish/resources/* takes a long time
Accepted answer
That publishing call is asking for all resources in the entire repository.
In your production environment, the server is probably very busy trying to return ALL resources and it struggles.
That publishing call had been identified as the cause for server instability. That is, slow downs and crashes.
In the RM log, we would typically see a very large DESCRIBE query that lists all the resource URLs in the repository.
You might see something like the following in your RM log.
[ jena.query.monitor] WARN com.ibm.team.jfs - CRJZS5541W Query _cpfG0FwbEeWN8Jalfvs5-Q has exceeded the configurable warning threshold of 45 seconds. It has 0 user contexts:
DESCRIBE <https://clm-server:9443/rm/resources/_nmfMEFQQEeSsOsbhirHRVA> <https://clm-server:9443/rm/resources/_pJfYdlQCEeSsOsbhirHRVA>
< ... a large number of URLs here ...>
WHERE
{}
I would advise not to use that particular query anymore and, instead, add some parameters to further filter the results.
