[jira] [Commented] (NIFI-3463) ExecuteSQL Errors on first use after long period of unuse

["Matt Burgess (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516126#comment-16516126 ] 

Matt Burgess commented on NIFI-3463:
------------------------------------

Did you enter a Validation Query into the DBCPConnectionPool? I'm tempted to close this as Not a Bug but would like to see if having a Validation Query makes the above error go away (it should).

> ExecuteSQL Errors on first use after long period of unuse
> ---------------------------------------------------------
>
>                 Key: NIFI-3463
>                 URL: https://issues.apache.org/jira/browse/NIFI-3463
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Nicholas Carenza
>            Priority: Trivial
>              Labels: ExecuteSQL
>
> I have a flow that runs ~ once a month and it gets this error for the first query each time it runs.
> ExecuteSQL[id=61f3179d-34f3-1986-ee27-134f425dfa18] Unable to execute SQL select query SELECT blah blah blah,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1486767996789-3396773, container=default, section=165], offset=619840, length=89131409],offset=57849490,name=filename,size=1566] due to org.apache.nifi.processor.exception.ProcessException: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 1,401,254,731 milliseconds ago.  The last packet sent successfully to the server was 1,401,254,731 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.; routing to failure: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)