Connection timeout setting for JDBC data source?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-17-2011 12:45 PM
Is there a user-configurable connection timeout for JDBC data sources, or other recommended workaround?
I am importing data for CMDB reconciliation and integration from a legacy asset database using JDBC. For some data sources, the first import attempt (either Test Load 20 Records or Load All Records) fails with: error: java.sql.SQLException: com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.io.EOFException
If I retry within a few minutes, the import succeeds. I suspect this is due to high initial latency on the legacy server. Possibly the problem will be resolved by increasing a timeout. But I don't see a connection.timeout option described for JDBC data sources.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-17-2011 09:31 PM
I don't believe timeout is configurable via the Data Source. Read this thread here:
Data source timeout for JDBC/SQLServer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-18-2011 05:46 AM
Thank you for the reference. Because this is (probably) an issue of initial latency, breaking the query into smaller pieces per suggested second workaround in the referred thread will probably not help.
I could put a null query ahead of the desired query. This raises another question. Scheduled data imports with LDAP can be chained, i.e. one import can be programmed to follow another. Is this possible with generic scheduled jobs or even scheduled data imports?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-18-2011 06:07 AM
In your case, the scripting option may be preferred as listed in that thread...rather than the broken up query. There is a good write up on scripting JDBC Probe calls here:
Using the JDBC Probe from scripts
(You will need the JDBC Integration plugin for that to work)
As to your next question, yes, you can have scheduled imports that run right after another import. See the screen shot of this scheduled JDBC Import:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-03-2012 01:32 PM
property to modify the jdbc timeout period, thanks to SN Support I have been able to create and use the following property to modify the timeout period to extend the timeout period for jdbc data sources in my instance.
Property Name: glide.jdbcprobeloader.retry
Type: Integer