POST requests give connection time out error intermittently | Community
Skip to main content
A
asn11
Level 4
February 23, 2016

POST requests give connection time out error intermittently

  • February 23, 2016
  • 5 replies
  • 7844 views

We have a server which is serving content to users, we now have incorporated login- register - reset password functionalities in the existing site.

Most of the things releated to creation of new users, login work as OOTB i.e. geometrixx login,view/edit profile pages.

Everything was ok in our lower environments however now we have it on our higher env, 

Intermittently all POST requests i.e. creation of new user, reseti of password, edit of profile give me connection time out on screen.

I havent been able to identify any pattern till now, randomly some request go timed out.

What could be the best way to find out where the problem is?

The layers of server go like this:

akamai server-> webserver / dispatcher -> publish instance

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

5 replies

Jitendra_S_Toma
Jitendra_S_Toma
Level 10
February 23, 2016

Does request reach to publish instance?. You can check publish access log when time out request happens.

--

Jitendra

A
asn11Author
Level 4
February 29, 2016

HI Jitendra/Kautuk ,

I got access to logs and checked. The request does reach the publish server, still I get connection time out every time the POST goes beyond 60 seconds.If the POST request completes in 59 seconds also it works fine, however if post spans more than 60 sec I get connection timed out on page.On refreshing things work fine.

Please let me know how do I come around it?

I see there is a configuration

Day CQSE HTTP Service has got

"Connection Timeout, Connection timeout in milliseconds. This property applies to both HTTP and HTTPS connections. Defaults to 60 seconds. "

https://docs.adobe.com/docs/en/cq/5-6-1/deploying/osgi_configuration_settings.html

Would increasing this defaulted 60 sec help?

Thanks in advance.

Regards,

asn

smacdonald2008
smacdonald2008
Level 10
March 10, 2016

Hi Scott,

No We havent yet, its production server so cant change anything untill have a clear RCA.

Interestingly the connection time out does not appear when I directly access publish server (without the domain name or via web server).

But in any case 40-50 seconds is a long time.

Same happens in case of j_security_check as well.

Could it be the case of /home/user path getting locked in case of concurrent POST requests? Because POSTs to other paths seem to be working fine.

Thanks in advance for you help.

 

Regards


I recommend try to change this setting when you get permission. If that does not help, open a ticket, Support can go through a database of issues and see if this is a known one. 

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
February 24, 2016

Another Good article :- http://smallbusiness.chron.com/server-connection-timeout-mean-71381.html

Thanks and Regards

Kautuk Sahni

Kautuk Sahni
joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
April 5, 2016

Hi,

In your case you need to systematically test each layer if the request arrives in time and if the response goes out (and how many time it took in between); this is probably time-consuming, but everything else is just guesswork. The request.log of AEM is quite helpful, because it logs per request 2 lines: one when the request is received and one when the response is sent.

kind regards,
Jörg

Tuhin_Ghosh
Tuhin_Ghosh
Level 8
April 27, 2016

Why these simple things are taking 120 seconds? Have you checked the performance with the infra team? Please also check if there is any indexing needed for any heavyweight query that might be running.

Most importantly if this is solved mark it as solved and also share the solution for the community.

 

Thanks

Tuhin

A
asn11Author
Level 4
April 27, 2016

@srinivasc11017710 @Tuhin,

we have identified that

One of the possible causes could be Bundlecachesize 

  1. Checked repository.xml on  publish

There is no bundlecache given explicitly.so it is defaulted to 8MB

Its recommended that it is at least set up to 256MB. It should be in proportion to the xmx size given to JVM.

https://helpx.adobe.com/experience-manager/kb/performancetuningtips.html#TIP01

In our case its way below the recommended size.

Infra team is going to change the bundlecache to see if that helps.

@ srinivasc11017710  see if all POST requests show such behavior , for ex. you could try changing the page title of a page in siteadmin multiple times to establish the same.In your case count the exact time after which request goes timeout, IE developer tool shows that clearly.

Tuhin_Ghosh
Tuhin_Ghosh
Level 8
April 27, 2016

asn_177 wrote...

@srinivasc11017710 @Tuhin,

we have identified that

One of the possible causes could be Bundlecachesize 

  1. Checked repository.xml on  publish

There is no bundlecache given explicitly.so it is defaulted to 8MB

Its recommended that it is at least set up to 256MB. It should be in proportion to the xmx size given to JVM.

https://helpx.adobe.com/experience-manager/kb/performancetuningtips.html#TIP01

In our case its way below the recommended size.

Infra team is going to change the bundlecache to see if that helps.

@ srinivasc11017710  see if all POST requests show such behavior , for ex. you could try changing the page title of a page in siteadmin multiple times to establish the same.In your case count the exact time after which request goes timeout, IE developer tool shows that clearly.

 

 

Cheers. Then kindly mark it as fixed.

Thanks

Tuhin

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
April 27, 2016

Hi 

I would say you need to debug why it is taking so much of the time, some performance changes would be required.

Changing Connection Timeout is a workaround. And i am not in favor of it. No body would wait for 1 min to get into a page.

I would say you should try to debug the issue, if not able to undo this behavior then reach out to Support :- https://daycare.day.com/public/contact.html

Thanks and Regards

Kautuk Sahni

Kautuk Sahni
Terms & ConditionsAccessibility statement

Loading footer...