• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 95 subscribers
  • Views 1179 views
  • Users 0 members are here
Options
Related

Web Designer UI throwing connection timed out error but working fine while debugging

poripi8342
over 3 years ago

Hi,

We have a use case where user can request application access from UI having components created in Web Designer.

In Web Designer at a particular step ADSAccount collection is loaded which take 1-2 minutes time to load while debugging and then it resumes. But this same scenario is throwing connection timed out error after 6-7 minutes of loading in UI(Chrome, IE). The query used for loading collection takes only 1-2 seconds of execution time in SQL Server.

This issue is observed for users having large number of AD Accounts (usually more than 300 AD Accounts).

What is causing this issue and what can be done here?

Version - 8.0

Parents
  • 0 over 3 years ago

    Hi Poripi8342,

    so have you identified while debugging or by looking at the logs, which query takes that long? Then take a look at this query and optimize it.

    Or maybe you load all Accounts in interactive mode? Which is only needed if you want to change data, but not for simple list showing.

    Regards,

    Geraldine

  • 0 over 3 years ago in reply to Geraldine Hopf

    Hi Geraldine,

    This issue if identified on the basis of debugging. And yes I tried optimizing the query by adding some filters in where clause of the SQL query, and now I can see the performance is improved.

    But still I am unsure what was causing it to take so much of time earlier, as the non optimized query was not taking longer than 2 seconds when I ran it directly on the SQL Server database.

    Thanks,

Reply
  • 0 over 3 years ago in reply to Geraldine Hopf

    Hi Geraldine,

    This issue if identified on the basis of debugging. And yes I tried optimizing the query by adding some filters in where clause of the SQL query, and now I can see the performance is improved.

    But still I am unsure what was causing it to take so much of time earlier, as the non optimized query was not taking longer than 2 seconds when I ran it directly on the SQL Server database.

    Thanks,

Children