Project

General

Profile

Actions
Copy link

Bug #1881

closed

Error when use haproxy

Added by Marcio Sales over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
3.3.0
Start date:
04/29/2013
Due date:
% Done:

0%

Estimated time:

Description

when i start the service with haproxy this message appear: wthttp/async: remote_endpoint() threw: Transport endpoint is not connected

Files

wt_3_3_0_error_message_haproxy.png (114 KB) wt_3_3_0_error_message_haproxy.png Marcio Sales, 04/29/2013 01:49 PM
Actions
Copy link
 #2

Updated by Wim Dumon over 11 years ago

Hello Marcio,

Sometimes these messages don't cause harm, so I have to ask: Does the application work? Does it behave different than expected?

BR,

Wim.

Actions
Copy link
 #3

Updated by Marcio Sales over 11 years ago

Hey Wim,

the application work normaly.

BR

Marcio

Actions
Copy link
 #4

Updated by Wim Dumon over 11 years ago

  • Status changed from New to Feedback

Marcio,

The most likely cause for this message is that haproxy closes the connection after a request. The HTTP RFC allows it to do so, so our 'error' status is a little bit over the top. Maybe you can check haproxy's configuration to see if you can configure it to keep connections open?

BR,

Wim.

Actions
Copy link
 #5

Updated by Koen Deforche over 11 years ago

  • Status changed from Feedback to Closed
Actions
Copy link

Also available in: Atom PDF