• Replies 1 reply
  • Subscribers 136 subscribers
  • Views 382 views
  • Users 0 members are here
Options
Related

Query folders not loading in pub manager

Akheil Jain

Running into issues with query folders, they don't load in Publication Manager, and throw a timeout error, even after increasing the timeout to 300seconds. At the same time the query folders load in seconds using the web client.

Things I have tried so far with no luck are:-

1) Restarted SolrLucene service.

2) Deleted and reindexed the repo.

3) increased timeout to 300 seconds in pub manager.

4) Checked the logs they are clean.

SDL support hasn't been of much help with this issue, the first time we ran into it with timeout of 120 seconds they asked to up the timeout to 240.

Any help is appreciated.

We are on the latest version of pub manager Tridion Docs 14 SP4.

Added Tridion Docs version.
[edited by: Akheil Jain at 9:52 PM (GMT 1) on 26 Jul 2022]
emoji
Rate translation
×
Suggest better translation
×
Parents

  • Hi Akheil,

    Query Folders are technically implemented using the SQL database, so they have the same limitations as the DocumentObj25.Find API call. To be clear, Query Folders are not executed over the Search25.PerformSearch API endpoint so they do not use SolrLucene.

    So all your query folder filter criteria are passed to a SQL WHERE clause query. If those criteria are not filtering enough, you will get a massive data set. The short term answer for massive data sets is to increase the time out.

    If you have WebApp server access, you should be able to find something in the Web Services logging, like C:\InfoShare\Data\Logs\InfoShareWS_yyyyMMdd.log I expect that logging to hold your request and indicate the size of the result set - even if your Publication Manager timed out.

    Hope this clarifies something,
    Dave
    emoji
Reply

  • Hi Akheil,

    Query Folders are technically implemented using the SQL database, so they have the same limitations as the DocumentObj25.Find API call. To be clear, Query Folders are not executed over the Search25.PerformSearch API endpoint so they do not use SolrLucene.

    So all your query folder filter criteria are passed to a SQL WHERE clause query. If those criteria are not filtering enough, you will get a massive data set. The short term answer for massive data sets is to increase the time out.

    If you have WebApp server access, you should be able to find something in the Web Services logging, like C:\InfoShare\Data\Logs\InfoShareWS_yyyyMMdd.log I expect that logging to hold your request and indicate the size of the result set - even if your Publication Manager timed out.

    Hope this clarifies something,
    Dave
    emoji
Children
No Data