Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
PSanadi
Contributor II
Contributor II

Error in Talend job with oracle DB java.sql.SQLRecoverableException: Closed Connection

Hi All,

One of our Talend job failed with below error

Message :java.sql.SQLRecoverableException: Closed Connection: next

at oracle.jdbc.driver.InsensitiveScrollableResultSet.ensureOpen(InsensitiveScrollableResultSet.java:110)

at oracle.jdbc.driver.InsensitiveScrollableResultSet.next(InsensitiveScrollableResultSet.java:404)

Talend Data Integration 7.3.1 Oracle Database 19.3.0

Ojdbc - ojdbc8-19.3.0.0.jar

JDK - 11.0_18l64

We are using shared connections and before any DB input component we have a connection component to register the shared connection name.

All the operations are select. Please help to find root cause of this issue.

Labels (4)
18 Replies
jlolling
Creator III
Creator III

What do you expect? I have told you the problem is related to the job design and you do not want to show us your job design. So no progress is possible until you provide the information we need to help.

PSanadi
Contributor II
Contributor II
Author

The job is working fine with db2, so if it was related to design it could have failed in db2 as well. Also for multiple runs in oracle it worked fine. The design is pretty simple we use the connection component to register the shared connection and use in multiple jobs.​

jlolling
Creator III
Creator III

Yes but at some point your job closes the connection and I would like to find out where. But it is YOUR problem and not mine. I done with it here.

PSanadi
Contributor II
Contributor II
Author

Sorry if I have offended you in any manner. Only intention was to get help on this. It is not possible to add the job design. I have checked there is no close or commit component added in entire job. Appreciate your help.​

jlolling
Creator III
Creator III

Please check if you have database output components where "Die On Error" is not checked.

It could be a component dies silently and the next component trying to use the connection cannot do this until a rollback has performed. This way you will find out the actual problem.

PSanadi
Contributor II
Contributor II
Author

We are just generating file using select. There are no output components still I will cross check and confirm back.​

PSanadi
Contributor II
Contributor II
Author

We are not using any output component.

jlolling
Creator III
Creator III

Ok, I do not know your job design and no logs. How do you think we could help you?

Again, if you still not provide more information we cannot help.

TBates1683209008
Contributor
Contributor

Have you resolved it?