Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Write Table now available in Qlik Cloud Analytics: Read Blog
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Talend Jobs stop running for unknown reason

Hi, we are new to Talend. Recently we have deployed Talend (v 4.2.3) services to a windows 2003 server.
Everything was running well for about a week until our jobs stop running. Windows services status were seen "Started". The jobs resume after we restarted the services. However, such downtime is very disruptive for our company business.
Anyone could share what could have caused the problem?

administration log:
2012-05-11 01:40:18 WARN TalendJobStoreTX - Failed to override connection auto commit/transaction isolation.
org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL)
at org.h2.message.DbException.getJdbcSQLException(DbException.java:327)
at org.h2.message.DbException.get(DbException.java:167)
at org.h2.message.DbException.get(DbException.java:144)
at org.h2.message.DbException.get(DbException.java:133) at or

To see the whole post, download it here
Labels (5)
5 Replies
Anonymous
Not applicable
Author

Hi
Welcome to Talend Community!
Which version do you use, Commercial version or Community version?
It seems that you are using TAC and Job Server to deploy jobs.
Here are two issue which have been fixed on JIRA.
http://jira.talendforge.org/browse/TDI-9211
http://jira.talendforge.org/browse/TDI-9546
Regards.
Pedro
Anonymous
Not applicable
Author

Thanks for your quick response.
We are using commercial version TIS 4.2.3. Both the links do not really relate to the message logs above. Moreover these fix are in place in v4.2.2.
janhess
Creator II
Creator II

Did the server reboot after applying windows updates? Did the database serviced restart if it rebooted?
Anonymous
Not applicable
Author

There is no server reboot though there is one prompting for one.
Anonymous
Not applicable
Author

I think we have found the issue. There were some backup scripts that is causing some I/O problem.