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; } } }

Error when calling iwsubmit at the end of 32 concurrent DNR deployments.

paultongyoo

Hi all--

I'm running a deployment configuration with 32 deployment definitions executing concurrently within a transactional <deployment>. For each dnrDeployment I execute a Perl script after success state which executes, among other things, an iwsubmit to submit the contents of 32 temp workareas into their corresponding STAGING areas.

What I'm observing is that the iwsubmit call errors out (ERROR 02404: No submit performed) for SOME of the deployment tasks and fails the entire transactional deployment. However, if I execute the iwsubmit manually via command-line afterwards, the submission executes successfully.

Are there problems executing iwsubmit (or any TS command-line tool) concurrently like this? Each deployment definition copies files into completely separate branches so I'm assuming there is no issue with file collisions.

Paul

Find more posts tagged with

Comments

ISCBorisB

Are there problems executing iwsubmit (or any TS command-line tool) concurrently like this?

No, there is no problem executing submits on separate branches.

There are however tons of problems executing Submits on changing Files - and that's what you are probably doing.
Transactional Deployment creates *.old and *.new Files on the Target. "new" files are renamed on Commitment Phase,
"old" Files removal (Cleaning Phase) however can go after Receiver reported Deployment success. Thus, you may
be submitting *.old Files while they are being deleted, etc...

Take a look at OpenDeploy Installation Guide, Chapter "Specifying Alternate Locations for Temporary Deployment
Files". It *may* help. From the other hand, if you deploy same Files to various target Branches within same transaction
it may cause more harm than good

testbirt.rptdesign.zip

Adam Stoller

Also - if you're using 6.2 (perhaps one or two releases earlier) you can serialize "concurrent" transactional deployments targeted to the same area to prevent a lot of potential issues that can occur with concurrent transactional deployments.

paultongyoo

Hi guys, thanks for the responses.

@ISCBorisB: I am executing my postdeploy script as part of a DNR (when="after" state="success") command so I am assuming all temporary files would have been removed by then.

@ghoti: Though I am not trying to deploy into the same area (branch), I'd like to experiment with serializing the deployments anyway. I tried searching the OD Admin and Deployment Configuration Guides for the relevant commands but could not find .... would you be able to share what config elements/attributes I should be using?

Thank you again,
Paul

ISCBorisB

I am executing my postdeploy script as part of a DNR (when="after" state="success") command so I am assuming all temporary files would have been removed by then

I've already noted that this is the wrong assumption. OD Process may perform Final Clean-up Phase of the transactional
Deployment after it reported Success. Check your STAGING/Editions, you *may* have "*.old" Files there.

paultongyoo

Ah, thanks! Will do.

ExpandableCollapsibleSection.rptdesign

Adam Stoller

Hi guys, thanks for the responses.

@ISCBorisB: I am executing my postdeploy script as part of a DNR (when="after" state="success") command so I am assuming all temporary files would have been removed by then.

As has been pointed out - there are various stages within a transactional deployment, and being transactional you would have to verify whether your DNR is running within, or after, the transaction has completed (e.g.: dnrDeploymentJob can run after, or you can try specifying a particular triggerPoint for your dnrDeployment)

@ghoti: Though I am not trying to deploy into the same area (branch), I'd like to experiment with serializing the deployments anyway. I tried searching the OD Admin and Deployment Configuration Guides for the relevant commands but could not find .... would you be able to share what config elements/attributes I should be using?

Look for things like pathRegistryChecking in the manuals and "Serializing transactional deployments in OpenDeploy", KB 61497 - on the Support site for more details about this.

paultongyoo

Look for things like pathRegistryChecking in the manuals and "Serializing transactional deployments in OpenDeploy", KB 61497 - on the Support site for more details about this.

Thanks for the KB reference, ghoti. Do you think pathRegistryChecking would still be helpful even if each deploy definition is deploying to a separate branch?

Adam Stoller

Thanks for the KB reference, ghoti. Do you think pathRegistryChecking would still be helpful even if each deploy definition is deploying to a separate branch?

If you're allowing concurrent transactional deployments - you want pathRegistryChecking - just in case you get concurrent deployments to the same target root directory.

If you're deploying to different target root directories - the result should be unaffected by pathRegistryChecking being enabled (perhaps a few microseconds of a performance hit?)