First, thank you for this great piece of software. Now for my problem, which is surely linked to my particular setup, but could affect others too.
I am currently triing to implement a rather simple ETL task with mETL accessing (among others) a Sybase SQL Anywhere database through the Sybase jconn2.jar JDBC driver. While this works well under test conditions, whenever I use the scheduler, the RDBMS reader stops on the error "... JZ0C0:
Connection is already closed ...". I can reliably reprduce the error in a test environment by running this flow once, then waiting more then 30 minutes, then running the flow again. (running it sooner does not lead to the error). If I immediatly rerun it a third time, the flow works again.
I suspect, that there is a time-out-close-session issue between your connection pool, the sybase jdbc driver and the database server. I tried multiple "test connection" settings on the DB ressource, with no effect.
Is there a way to force the db connection to dissconnect and reconnect before running a flow?
best regards,
Alexander, Austria
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Alexander - You should be able to adjust your connection pool settings in the resources view. I might try to add a "Validation Query" and check "Test On Borrow"
Dear Metl Team!
First, thank you for this great piece of software. Now for my problem, which is surely linked to my particular setup, but could affect others too.
I am currently triing to implement a rather simple ETL task with mETL accessing (among others) a Sybase SQL Anywhere database through the Sybase jconn2.jar JDBC driver. While this works well under test conditions, whenever I use the scheduler, the RDBMS reader stops on the error "... JZ0C0:
Connection is already closed ...". I can reliably reprduce the error in a test environment by running this flow once, then waiting more then 30 minutes, then running the flow again. (running it sooner does not lead to the error). If I immediatly rerun it a third time, the flow works again.
I suspect, that there is a time-out-close-session issue between your connection pool, the sybase jdbc driver and the database server. I tried multiple "test connection" settings on the DB ressource, with no effect.
Is there a way to force the db connection to dissconnect and reconnect before running a flow?
best regards,
Alexander, Austria
Alexander - You should be able to adjust your connection pool settings in the resources view. I might try to add a "Validation Query" and check "Test On Borrow"
Our connection pool settings are a direct pass through to: https://commons.apache.org/proper/commons-dbcp/api-1.4/org/apache/commons/dbcp/BasicDataSource.html
If you need any other settings exposed we would be happy to expose them ...
Last edit: Chris Henson 2017-02-17
Chris - Thank you. I played around with the values, reduced the pool size, restarted the mETL server and now it works fine!
best regards,
Alexander, Austria