Ironn Pagnaniban,
Did you ever figure out how to work around this? We started encountering this error when we installed the 9.3.0.6 service pack.
Anyone else figure out a work around?
We thought we had it resolved by setting the connection pool removeAbandonedTimeout to a very high number--that seemed to work in internal testing, but it failed on production. Also tried setting removeAbandoned=false. These appeared to work in some internal tests, but as soon as we deployed to production, it failed. The error arose in a Sync after merge step. The error in the pentaho.log looks like this:
Caused by: java.sql.SQLException: org.apache.commons.dbcp.DelegatingPreparedStatement with address: "sp_executesql SQL: ...
/* sql here */ " is closed.
So, somehow a prepared statement is getting opened and then immediately closed. So that by the time the prepared statement is actually invoked, it fails immediately.
When I raised this issue with Pentaho support, they identified it as a known bug "that will be fixed in a later service pack."
Unfortunately 9.3.0.7 is currently scheduled for March 2024--so I guess we roll our production and internal systems back to an earlier service pack.
------------------------------
John Craig
Systems Engineer
Henry Schein One
------------------------------
Original Message:
Sent: 09-23-2023 03:09
From: Ironn Panganiban
Subject: The connection is closed
An etl job always fails to execute even though the testing of the connection is successful.
The ETL job was previously working and we did not make any changes to the etl job.
database source: MSSQL server (CRM)
Here are the messages we encountered
Explore
Testing connection
Thank you,
Ironn Paulo
------------------------------
Ironn Panganiban
Systems Engineer
Nexus Technologies Inc
------------------------------