[AEM service freeze] Unable to parse response: Premature end in HTTP response, state = 0 | Adobe Higher Education
Skip to main content
July 19, 2017
Frage

[AEM service freeze] Unable to parse response: Premature end in HTTP response, state = 0

  • July 19, 2017
  • 2 Antworten
  • 1999 Ansichten

Hello, has anybody seen the following error? it has apparently been fixed by server reboot but I want to know the cause in order to prevent to happen again:

[Thu Jul 13 20:10:36 2017] [D] [11929] Found farm mypublish.com

[Thu Jul 13 20:10:36 2017] [D] [11929] checking [en/home.html]

[Thu Jul 13 20:10:36 2017] [D] [11929] cachefile does not exist: /mnt/var/www/html/mypublish.com/en/home.html

[Thu Jul 13 20:10:36 2017] [D] [11929] try to create new cachefile: /mnt/var/www/html/mypublish.com/en/home.html

[Thu Jul 13 20:10:36 2017] [D] [11929] cache-action for [mypublish.com/en/home.html]: CREATE

[Thu Jul 13 20:10:36 2017] [D] [11929] Connected to backend 0 (publish:4503)

[Thu Jul 13 20:10:36 2017] [D] [11929] Adding request header: user-agent

[Thu Jul 13 20:10:36 2017] [D] [11929] Adding request header: accept-encoding

[Thu Jul 13 20:10:36 2017] [D] [11929] Adding request header: accept-language

[Thu Jul 13 20:10:36 2017] [D] [11929] Adding request header: accept

[Thu Jul 13 20:10:36 2017] [D] [11929] Adding request header: host

[Thu Jul 13 20:10:36 2017] [D] [11929] Adding request header: cookie

[Thu Jul 13 20:10:36 2017] [D] [11929] Adding request header: REMOTE_USER

[Thu Jul 13 20:10:36 2017] [D] [11929] Adding request header: Via

[Thu Jul 13 20:10:36 2017] [D] [11929] Adding request header: X-Forwarded-For

[Thu Jul 13 20:10:36 2017] [D] [11929] Adding request header: Server-Agent

[Thu Jul 13 20:10:42 2017] [D] [25021] Unable to parse response: Premature end in HTTP response, state = 0

[Thu Jul 13 20:10:42 2017] [D] [25021] socket error detected

[Thu Jul 13 20:10:42 2017] [D] [25021] initializing retry, closing socket (bogus %p

After notice the error above on Dispatcher I have logged on Publish server and the AEM service were up but apparently freeze so I restarted the server and it started to run just fine.

It's an AEM 6.2 + SP2 CFP7 running on centOS.

I haven't found anything about that kind of behavior and  I really appreciate any help or clue, Thanks.

Dieses Thema wurde für Antworten geschlossen.

2 Antworten

smacdonald2008
Level 10
July 19, 2017

We are hosting an Ask the AEM Experts on Dispatcher next tues. You can attend and Ask the presenters if they have seen anything like this before -- Scott's Digital Community: Ask the AEM Community Experts for July 2017

I have never seen this error before.

July 19, 2017

Thanks a lot smacdonald2008, I really appreciate.