nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DataDeploy taking a long time to complete

NathansDIS

Has anyone ever had DataDeploy take a long time to complete successfully? We had a datadeploy take 3 minutes yesterday, when it usually only takes a split second. It kind of looks like it might have timed out, but a 3 minute retry? Can we configure the retry interval? We are using OD/DD 6.0 to talk to a SQL Server database. Here is the log for your viewing pleasure. Any insights, comments, etc are much appreciated.

Cheers,

Nathan
Washington State DIS
~~~

SerialDaemon dispatch
TWorkItem: Smiley Very Happy

oIt --- sock=2345 id=75
msg [myfilelist=E:/Interwoven/DIS/Logs/filelist/datadeploy_127629_filelist.txt iwdd=aw_ea_deploy mydatabase=dis_aw_newsIndex logfile=E:/Interwoven/DIS/Logs/filelist/datadeploy_127629_log.txt mystagingarea=/default/main/DIS/AW2/STAGING cfg=C:\iw-home\OpenDeployNG\conf\datadeploy\aw_ea_deploy.xml need-result=yes logfile=E:/Interwoven/DIS/Logs/filelist/datadeploy_127629_log.txt depuuid=bc206ba0-39b7-11d9-bd7e-df2fa8374e75 leglabel=database]
id=75 fDdArgs[0]=[myfilelist=E:/Interwoven/DIS/Logs/filelist/datadeploy_127629_filelist.txt]
id=75 fDdArgs[1]=[iwdd=aw_ea_deploy]
id=75 fDdArgs[2]=[mydatabase=dis_aw_newsIndex]
id=75 fDdArgs[3]=[logfile=E:/Interwoven/DIS/Logs/filelist/datadeploy_127629_log.txt]
id=75 fDdArgs[4]=[mystagingarea=/default/main/DIS/AW2/STAGING]
id=75 fDdArgs[5]=[cfg=C:\iw-home\OpenDeployNG\conf\datadeploy\aw_ea_deploy.xml]
id=75 fDdArgs[6]=[need-result=yes]
id=75 fDdArgs[7]=[logfile=E:/Interwoven/DIS/Logs/filelist/datadeploy_127629_log.txt]
id=75 fDdArgs[8]=[depuuid=bc206ba0-39b7-11d9-bd7e-df2fa8374e75]
id=75 fDdArgs[9]=[leglabel=database]
Database Vendor set to microsoft-inetuna
Max Identifier length set to 128 characters.
SQL datatype for column path is VARCHAR(255)
SQL datatype for column state is VARCHAR(255)
SQL datatype for column Headline is VARCHAR(255)
SQL datatype for column filename is VARCHAR(200)
SQL datatype for column release_date is DATETIME
SQL datatype for column publish_date is DATETIME
SQL datatype for column expire_date is DATETIME
SQL datatype for column indexType is VARCHAR(15)
# of columns: 8
# of primary key columns specified: 1
WARNING:Assuming group name as the table name for [PressReleases].
# of groups defined in <dbschema> element: 1
[Thu Nov 18 15:15:28 PST 2004] Begin executing aw_ea_deploy
Area VPath:/default/main/DIS/AW2/STAGING
Setting up TDbSchemaAgent.
Validating cached connection...
OpenDeploy server host: localhost, RMI registry port: 9173
OpenDeploy server host: localhost, RMI registry port: 9173
OpenDeploy server host: localhost, RMI registry port: 9173
OpenDeploy server host: localhost, RMI registry port: 9173
SQLException[TDS Driver]Read timed out
url : jdbc:inetdae:198.239.145.66:1435?database=AWNewsTOC&sql7=true
login : TSDisCM
login timeout=3
Connecting to the database...
Try connecting using jdbc:inetdae:198.239.145.66:1435?database=AWNewsTOC&sql7=true...

Connected to jdbc:inetdae:198.239.145.66:1435?database=AWNewsTOC&sql7=true
Driver i-net UNA 2000
Version 4.17
Connected to [198.239.145.66:1435?database=AWNewsTOC]
Table [PressReleases] exists.
Running deployment [aw_ea_deploy]
extraction type=full
tuple mode=wide
area=/default/main/DIS/AW2/STAGING
filelist=[E:/Interwoven/DIS/Logs/filelist/datadeploy_127629_filelist.txt]
/default/main/DIS/AW2/STAGING/web/news/2004/Nov/n20041018_3678.aspx
Generate DirectoryContents start:Thu Nov 18 15:18:27 PST 2004
Generate DirectoryContents end :Thu Nov 18 15:18:27 PST 2004
Generate TFullEAExtractor start:Thu Nov 18 15:18:27 PST 2004
Generate TFullEAExtractor end :Thu Nov 18 15:18:27 PST 2004
Building replicant order column information.
Building replicant order column information... Done.
TUPLE={TeamSite/Metadata/expire_date=11-18-2009, IWOV_PROC_FLAG=true, state=Original, TeamSite/Metadata/Headline=Gov. Gary Locke's statement on governor's race, TeamSite/Templating/PrimaryPT=awnews.tpl, TeamSite/Templating/PrimaryDocumentType=PressRelease/news, TeamSite/Metadata/publish_date=11-18-2004, TeamSite/Templating/Encoding=, TeamSite/Metadata/Indextype=agency, TeamSite/Metadata/Contenttype=Access_Washington_Press_Release, TeamSite/Metadata/filename=n20041018_3678.aspx, TeamSite/Templating/PrimaryDCR=2004\Nov\n20041018_3678, TeamSite/Metadata/time=06:00, TeamSite/Metadata/release_date=11-18-2004 06:00, path=web\news\2004\Nov\n20041018_3678.aspx}
TTableSchemaHelper object for [PressReleases] found in cache.
RowsExistForPath Smiley Frustrated

ELECT COUNT(*) FROM PressReleases WHERE path = ?
INSERT:INSERT INTO PressReleases(path,state,Headline,filename,release_date,publish_date,expire_date,indexType) VALUES (?,?,?,?,?,?,?,?)
Column: path, field: path, Index: 1,Converting 'web\news\2004\Nov\n20041018_3678.aspx' to VARCHAR
Column: state, field: state, Index: 2,Converting 'Original' to VARCHAR
Column: Headline, field: TeamSite/Metadata/Headline, Index: 3,Converting 'Gov. Gary Locke's statement on governor's race' to VARCHAR
Column: filename, field: TeamSite/Metadata/filename, Index: 4,Converting 'n20041018_3678.aspx' to VARCHAR
Column: release_date, field: TeamSite/Metadata/release_date, Index: 5,Converting '11-18-2004 06:00' to TIMESTAMP
Column: publish_date, field: TeamSite/Metadata/publish_date, Index: 6,Converting '11-18-2004' to TIMESTAMP
Column: expire_date, field: TeamSite/Metadata/expire_date, Index: 7,Converting '11-18-2009' to TIMESTAMP
Column: indexType, field: TeamSite/Metadata/Indextype, Index: 8,Converting 'agency' to VARCHAR
-- Inserted
Filelist walk done
Stat for group [PressReleases]:
-----------------------------------
Rows inserted : 1
Rows updated : 0
Rows deleted : 0
Rows failed : 0
Rows rolled back : 0
Rows skipped : 0
-----------------------------------
Committing database [198.239.145.66:1435?database=AWNewsTOC]...
DepUUID = bc206ba0-39b7-11d9-bd7e-df2fa8374e75 LegLabel= database
Topic Session not established. Event msg will not published.
Deployment[aw_ea_deploy]
-----------------------------------
Files with EAs inserted : 1
Files with EAs updated : 0
Files with EAs deleted : 0
Files with EAs failed : 0
Files with EAs rolled back : 0
Files with EAs skipped : 0
-----------------------------------
Started : Thu Nov 18 15:15:28 PST 2004
Finished: Thu Nov 18 15:18:28 PST 2004

### IWDataDeploy DONE ###

### Sending result ###

Find more posts tagged with

Comments

Dwayne

Yes, the timeout is configurable. A sample entry from my database.xml with the timeout overridden:

<database name="CMS"
              db="MYSQLSERVER:1433?database=CMS"
              user="database user here"
              password="user's password here"
              vendor = "microsoft-inetuna"
              timeout = "3"
              delete-tracker = "yes"
              max-id-length = "128" />

This sets the timeout to 3 seconds

--

Current project: TS 5.5.2/6.1 W2K

NathansDIS

Thx for the info. Anyone have any idea what the default is for the timeout?

Dwayne

3 minutes (120 seconds) sounds about right, if I remember correctly. But I'm not at all certain of that.

Side note - I've got a case open with support right now related to the very error that you're seeing. You wouldn't by any chance be using an IWTupleFilter or and IWExternalData source to read from the database, would you? That's what's causing the error for me - I've ended up having to deploy my metadata one file per deployment, because I always get a timeout on the second file in the deployment.

--

Current project: TS 5.5.2/6.1 W2K

NathansDIS

I'm not sure how to check if we are using IWTupleFilter of IWExternalData explicitly, but I do know that all our DD job does is write one record to the DB. We don't read anything out of the database with OD/DD. I'd be happy to check for these calls if you will tell me where to look. Hope this helps.

-Nathan

Migrateduser

I was having a similar problem. Search this forum for "abyssmal performance". In my case, it turned out to be the event reporting DB that was killing me. Following Adam's advice, I disabled it and now things are moving along quite expeditiously.

NathansDIS

Yes, I had to disable the reporting database as well when we migrated from OpenDeploy 5.6 to OD 6.0. The reporting 'feature' was causing regular, non DD deployments to take an inordinate amount of time. Not only was it slow, the upper and lower OD panes were reporting different times for completion of the OD jobs. Official word from support was that the out of the box DB was for POC only, not intended for production use.

In case this rant wasn't clear, this reporting feature was disabled when the issue in this case occured.

-Nathan
Washington State DIS

NathansDIS

Hey Dwayne-

Well, we got the error again and this time I found info in the logs that confirmed my suspicion that DD was trying to use a pooled connection that had errored out, see below. Does anyone know how to configure DD or ODBC to not use the cached connection? I set the timeout to 2 as described in your post and will update this thread if the error happens again. Thanks again for the info!

-Nathan
Washington DIS

[Thu Nov 18 15:15:28 PST 2004] Begin executing aw_ea_deploy

Area VPath:/default/main/DIS/AW2/STAGING

Setting up TDbSchemaAgent.

<b>Validating cached connection...</b>

OpenDeploy server host: localhost, RMI registry port: 9173

OpenDeploy server host: localhost, RMI registry port: 9173

OpenDeploy server host: localhost, RMI registry port: 9173

OpenDeploy server host: localhost, RMI registry port: 9173

SQLException[TDS Driver]Read timed out

url : jdbc:inetdae:192.168.1.1:1435?database=DBNAME&sql7=true

login :USERNAME

login timeout=3

Connecting to the database...

Try connecting using jdbc:inetdae:192.168.1.1:1435?database=DBNAME&sql7=true...

Connected to jdbc:inetdae:192.168.1.1:1435?database=DBNAME&sql7=true

Driver i-net UNA 2000

Version 4.17

Connected to [192.168.1.1:1435?database=DBNAME]

Table [PressReleases] exists.

Running deployment [aw_ea_deploy]

NathansDIS

Hi Dwayne-

I tried setting the timeout to 3 seconds as you specified in your post, but the timeout still took 3 minutes. It looks like the timeout is in minutes and not seconds?!?! Does anyone else have any suggestions about this? I guess this is one reason to be glad our press release process is moving to rss and away from a db index.

Thx,

-Nathan
Washington State DIS