I was having the same problem, but I couldn't find any properties in the driver documentation that would help. This error, in my case, occurred to the detriment of the connection with the database breaking due to some reason of infrastructure or service failure. However, I noticed that it was possible to solve this problem in two ways using the controller service DBCPConnectionPool: - You can set a generic query in the Validation Query parameter. This way, at each new transaction with the database, the connection will be recreated executing this query. This can be a good alternative, however, if your flow performs many queries, it will slow down the processing slightly. - You can change the Max Connection Lifetime parameter, set a value other than -1 or 0. This value is the time interval in which your connection will be recreated with the database. For example, if you set 5 min, the connection will be recreated every five minutes. In my case the problem has been fixed, I hope I have helped.
... View more
Hello community, I am facing the following problem when using a JDBC Impala connection. Every time I restart Impala services, the following error message is displayed on clients that are connected using the JDBC driver: Failed to connect to server. Reason: java.net.sockettimeoutexception: Broke Pipe (Write Failed). I use Impala 3.2.0 and the Impala JDBC 4.1 driver. Doing some tests I noticed that the connection normalizes after forcing the manual restart of the connection with the server. Would there be any way or parameter that would make this reconnection automatically or some other solution for this problem?
... View more