readline: line too long got ...

Environment

Find more posts tagged with

Comments

The only time I have seen this was in a WF deployment from the STAGING area.

Senerio,

submit foo (size changes from X to Y)
deploy foo (from STAGING), with no delay, OD sees file size X.
Deployment starts now file is size Y

Is that possible ?

Andy

Adam Stoller

The only time I have seen this was in a WF deployment from the STAGING area.

Senerio,

submit foo (size changes from X to Y)
deploy foo (from STAGING), with no delay, OD sees file size X.
Deployment starts now file is size Y

Is that possible ?

Andy

Hmm - yes, it's possible, but in this case I think unlikely - there was only one file submitted and a full dir-diff deployment - the file that was submitted actually got deployed - and these errors occurred each time (and other errors occurred in the deployment itself - which was non-transactional) - I'm not on the project any more, but hopefully they'll have figured it out with IWOV Support assistance....

Adam Stoller

Hmm - yes, it's possible, but in this case I think unlikely - there was only one file submitted and a full dir-diff deployment - the file that was submitted actually got deployed - and these errors occurred each time (and other errors occurred in the deployment itself - which was non-transactional) - I'm not on the project any more, but hopefully they'll have figured it out with IWOV Support assistance....

Another aspect of the case in point which makes this seem less likely is that the TS server is on Windows - on Unix you have a caching and non-caching mount point in which deployments from the cached mount point exhibit the behavior you mentioned - but on Windows you only have one mount point (Y Smiley Happy

- and right now I cannot remember if that's cached or non-cached.