Deployment blocked on two targets

croot

We have an issue that occurs in our production environment when more than one deployment occurs concurrently.

We have a deployment script that deploys to two web servers (sam1 & chase1). When we begin more than one job in TeamSite (which kicks off a deployment) at the same time, the processes are blocked by each other. Essentially what we have is sam1 waiting for chase1, chase1 waiting for sam1 and any other deployments started are blocked by both. This makes concurrent deployment very difficult if users submit at the same time. (this happens when submitting different folders and when submitting the same folder)

Just for some more information, one deploment would say:

sam1: setup done
blocked
waiting
chase1: setting up
blocked

another deployment started at the same time says:
sam1: setting up
blocked
chase1: setup done
blocked
waiting

and additional deployments say:
sam1: setting up
blocked
chase1: setting up
blocked

Any help with this issue would be greatly apreciated. Thanks.

Adam Stoller

We have an issue that occurs in our production environment when more than one deployment occurs concurrently. We have a deployment script that deploys to two web servers (sam1 & chase1). When we begin more than one job in TeamSite (which kicks off a deployment) at the same time, the processes are blocked by each other. Essentially what we have is sam1 waiting for chase1, chase1 waiting for sam1 and any other deployments started are blocked by both. This makes concurrent deployment very difficult if users submit at the same time. (this happens when submitting different folders and when submitting the same folder) Just for some more information, one deploment would say: sam1: setup done blocked waiting chase1: setting up blocked another deployment started at the same time says: sam1: setting up blocked chase1: setup done blocked waiting and additional deployments say: sam1: setting up blocked chase1: setting up blocked Any help with this issue would be greatly apreciated. Thanks.

Read the OD manuals with respect to the '-inst' command line parameter for initiating deployments (and/or run: iwodcmd start -h)

Also - you didn't specify whether these are transactional or non-transactional deployments, nor what version(s) of OD you are using on your sending and receiving sides, nor the OS for the sender or receiver.