dispatcher Error | Community
Skip to main content
A
Anonymous
October 16, 2015
Solved

dispatcher Error

  • October 16, 2015
  • 6 replies
  • 1768 views

Hi Guys,

I am getting a Strange error in the Apache Dispatcher Logs . We have an Apache server in front of  CQ Author. 

The html Page renders properly directly from Author IP but it throws a 500 Error when accessed from Apache.

Following is the Error message in Dispatcher logs

>>

Error while sending body: Broken pipe
"GET /content/test/home.html" 500 36103 1186ms

<<

 

Has anyone encountered this error before?.

 

Thanks,

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

    Thanks Sham and Ove for your Help.

    We identified the issue. Our Author Apache server was on HTTPS and the Web Service Call was being made on HTTP, So browsers were blocking the requests. We found the solution that either Force HTTP for that Path on Apache or change the Web service URL to load on HTTPS.

    Thanks Again

    6 replies

    O
    Ove_Lindström
    Level 6
    October 16, 2015

    I have seen the Broken pipe problems when the virtual host and the Author is not aligned. The Author needs to "think" that it is the same as the Dispatcher.

    What Dispatcher version do you use?

    What Apache HTTPD server?

    How is your VHOST configured?

    How does the author_dispatcher_new.any looks like?

     

    /Ove

    Sham_HC
    Sham_HC
    Level 10
    October 16, 2015

    This indicates the client closed the connection. Per your description client is Apache. check apache configs & network. 

    A
    Anonymous
    October 16, 2015

    Actually Page is loading properly but it seems like some Component (Which makes call to a GSA) of the Page is not loading fine and hence we are seeing 500 error in the Logs. Apache version is 2.2.15 and Dispatcher is 4.0.9

     

    Thanks,

    A
    Anonymous
    Accepted solution
    October 16, 2015

    Thanks Sham and Ove for your Help.

    We identified the issue. Our Author Apache server was on HTTPS and the Web Service Call was being made on HTTP, So browsers were blocking the requests. We found the solution that either Force HTTP for that Path on Apache or change the Web service URL to load on HTTPS.

    Thanks Again

      Scott_Brodersen
      Scott_Brodersen
      Level 8
      October 16, 2015

      Regardless of whether it would fix your current issue, your Dispatcher version is pretty old....consider updating to the current version (4.1.7) to benefit from bug fixes and new features https://www.adobeaemcloud.com/content/companies/public/adobe/dispatcher/dispatcher.html

      scott

      A
      Anonymous
      October 16, 2015

      Thanks Scott for sharing this Useful Link. I will check this Out.

      Terms & ConditionsAccessibility statement

      Loading footer...