Reference Panel throws timeout exception in AEM 6.3

samikshaa186672 16-01-2019

hi ,

While working on my translation project in AEM 6.3 , I use the references panel to update/promote language copies to other languages from EN and to Synchronize/Roll out the language copies to live copies , however for all the system users the References Panel does not load properly and throws an timeout error, however if I login with my  administrator credentials , it seems to work with much speed.

I am not sure if there is any difference in the response time on events for different user levels in AEM , particularly for queries like loading all References of pages in the JCR.

I have attached the screenshot of the error .


when we checked the browser debug tool , it shows this


also the link to that URL in network Tab.


Please help me figure out this issue also suggest some way to improve the performance of the tool .

Thank you,


Accepted Solutions (1)

Accepted Solutions (1)


Is this related to slow performance or with timeout/504 that happens intermittently?

If you suspect that admin users perform better than others, I would recommend to log the queries and related information for this use case for further debugging -

  1. Enable logging for and your code package - This would provide the query and time taken to execute the query. Compare the behavior & data for admin/non-admin users.
  2. Check what queries run and what is the response time, what indexes are applied to the query and is there a need to optimize the indexes? Does this use case run inappropriate queries that are not supposed to run? Compare it for both admin & non-admin users.
  3. Check the component timings on author in developer mode. Does this happen on publish server as well across environments or only a single environment?
  4. Check what kind of restrictions authors have on assets/referenced assets? Do you have a custom authorization or something related in-place that might be a potential bottleneck? Does your project use any specific customization for ACLs? Are you on latest service pack/CFP for the AEM version?
  5. Based on the setup check server logs - AEM logs, webserver logs, dispatcher logs etc. for warnings/errors that are related to this use case.
  6. Check the behavior of author standalone vs author with dispatcher vs author with dispatcher & LB and other proxies. As you've mentioned that bypassing dispatcher works fine, then check the dispatcher configurations and experiment with different configurations like increasing the timeout value. Open dispatcher.any file and change the value of /receiveTimeout to 0 for testing
  7. Isolate the application issues vs network issues vs hardware issues - you suspect issues with ACL within AEM but on the other side you've mentioned that bypassing dispatcher works fine which means that the root cause is probably outside AEM. It would be better to work with a debugging strategy for a quick turnaround.

I'm not sure what kind of data/information you can share in this thread. It would be difficult for anyone to comment on any specific functionality unless we've specific data points. Alternatively, you could open a ticket with customer care with your findings.

Dispatcher.any file renderer section -



# Hostname or IP of the render

/hostname "localhost"

# Port of the render

/port "4503"

# Connect timeout in milliseconds, 0 to wait indefinitely /timeout "5000"

/receiveTimeout "2000"




Answers (3)

Answers (3)

samikshaa186672 18-01-2019

hi ,

I am logged in with my office VPN. I see that most of our users work in the same network and face the same problem. However I have seen a significant improvement in the performance ( the reference load functionality) with admin users as compared to normal (author) users.

Does this have something to do with the access levels to files ?

Also whenever we try accessing the servers with IP address bypassing the dispatchers it works pretty fine consistently.

Please provide me a solution on this.

Thanking you in anticipation,



The screenshot shows 504 Gateway timeout error which means that the upstream server couldn't get timely response because of various reasons and got timed out. Your local machine's browser could not get a timely response and the server that your browser is connected to threw off the connection. Are you on a VM or a cloud server?

Get the network connection checked and traffic monitored for a period of time whenever this issue happens. Engage your IT-Network team to intercept the traffic via tools.

In addition to that, check the timeout on dispatcher and keep-alive on web server and other proxy servers that are a part of this network.

There shouldn't be any difference in the response times for normal user vs admin user.

This issue might be visible only on slow queries that run over the timeout limit specified in one of intermediary servers in the network.