View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000637Pgpool-IIBugpublic2020-08-20 13:362020-10-07 11:52
Reporterjayakumar Assigned Topengbo  
PriorityhighSeveritymajorReproducibilitysometimes
Status feedbackResolutionopen 
PlatformLinuxOSRedhat Linux 7.2OS VersionRedhat Linux 7.2
Product Version3.7.10 
Summary0000637: Unable to read the data from frontend
DescriptionWe are getting below errors in different times. At the time we are getting error users also unable to access postgres server with application through pgpool. It's like hanging mode. And after 10-15 minutes without any action/modifications application is working fine. It's not happening at particular time, but once in month or so. Some times this is happening in the night times also where the users are very less in number.

Error occurred at 9:27:50 AM
Error: Unable to read the data from frontend: Detail: Socket read failed with an error "Connection reset by peer"

Error occurred at 9:19:37 PM
Error: Unable to read the data from frontend: Detail: Socket read failed with an error "Connection Timed Out"

Please help in resolving the issue.
Steps To ReproduceNA
Additional InformationAt the same time while application user is unable to access postgres server through pgpool, we could able to access postgres directly to check the number of connections.

It's not happening at particular time, but once in month or so. Some times this is happening in the night times also where the users are very less in number.
TagsUnable to read the data from frontend

Activities

jayakumar

2020-08-20 13:36

reporter  

error1.png (61,329 bytes)   
error1.png (61,329 bytes)   
error2.png (66,022 bytes)   
error2.png (66,022 bytes)   

pengbo

2020-08-31 10:36

developer   ~0003534

Sorry for late response.

> Error occurred at 9:27:50 AM
> Error: Unable to read the data from frontend: Detail: Socket read failed with an error "Connection reset by peer"
>
> Error occurred at 9:19:37 PM
> Error: Unable to read the data from frontend: Detail: Socket read failed with an error "Connection Timed Out"

It seems that front disconnected the connection to pgpool, so pgpool couldn't read data from frontend.

Are you setting any connection timeout in your application?
Or are your application using Tomcat?

jayakumar

2020-09-08 20:26

reporter   ~0003557

In recent times we did not changed any timeout settings. Yes. Application is using Tomcat.

pengbo

2020-09-10 14:57

developer   ~0003559

if your are using Tomcat JDBC connection pool, Tomcat may create lots of persistent connections to Pgpool-II.

If Pgpool-II disconnects the connection after "client_idle_limit", your application will get an error message the next time Tomcat tries to send request to Pgpool-II.

Are you setting "client_idle_limit"?
Try to disable "client_idle_limit" or configure Tomcat parameters to clean up or validate idle connections.
Here is a blog of configuring Tomcat parameters to work with pgpool.

pengbo

2020-10-07 11:52

developer   ~0003580

Have you resolved this issue?
May I close this one?

Issue History

Date Modified Username Field Change
2020-08-20 13:36 jayakumar New Issue
2020-08-20 13:36 jayakumar File Added: error1.png
2020-08-20 13:36 jayakumar File Added: error2.png
2020-08-20 13:36 jayakumar Tag Attached: Unable to read the data from frontend
2020-08-24 11:17 pengbo Assigned To => pengbo
2020-08-24 11:17 pengbo Status new => assigned
2020-08-24 11:17 pengbo Description Updated
2020-08-24 11:17 pengbo Additional Information Updated
2020-08-31 10:36 pengbo Note Added: 0003534
2020-08-31 10:36 pengbo Status assigned => feedback
2020-09-08 20:26 jayakumar Note Added: 0003557
2020-09-08 20:26 jayakumar Status feedback => assigned
2020-09-10 14:57 pengbo Note Added: 0003559
2020-09-14 14:38 pengbo Status assigned => feedback
2020-10-07 11:52 pengbo Note Added: 0003580