OpenDeploy deployment frozen

Opendeploy is frozen at this point:
ENG: 2003-05-01 08:38:35 EST GMT-05:00 Thread-164 After PRECOMMIT, res=0
ENG: 2003-05-01 08:38:35 EST GMT-05:00 Thread-164 exiting dotask
ENG: 2003-05-01 08:38:35 EST GMT-05:00 Thread-164 entering awaiting-commit

What could be causing this? Also, is there anyway to manually kill the process? Restarting opendeploy is the only succcess we have had.

Find more posts tagged with

Comments

Migrateduser

The only way to kill a deployment (without killing the OD base server or receiver) is via the Admin UI or the iwoddeploycancel command line tool. But these are restricted to only certain phases of the deployment. (See the OD 5.6 docs for more info.)

The commit phase of a deployment involves renaming staged files to the original file names, and removing the backed up (old) files. Make sure you don't have something like an index server running that might lock up these files during the deployment job. Another cause might also be that the network connection is faulty, and one side is waiting for the other side to communicate status.

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

johnjamesmarsh

I get the same errors on our server. We are using OpenDeploy 5.5.1 on Solaris. Every once in a while a deployment will start but hang. There is a cancel button but that seems to do nothing. Also doing a reset via the GUI does not fix it either. The only solution I have found is to get the UNIX admins to restart OpenDeploy.

I think this happens when using the GUI sometimes you get two clicks. In a normal web app the first click is thrown away and only the second one is used. In OpenDeploy both clicks are acted on and you get a conflict.

Very annoying. Is this fixed in 5.6?

John

Migrateduser

As I said, killing deployment threads is currently restricted to only certain phases of the deployment. That's why, for example, the cancel button may be unavailable at times.

Not sure what you mean by problems happening when you do two clicks. If you were to twice start a deployment, by default the first one would start and the second one would be rejected (assuming the first one is still running when you do the second click.) I believe there was bug corrected at some point where two like-named deployments started in extremely close succession would cause a problem, but I think that had to do with a program starting multiple deployments at the same time. Not sure one could click twice that quickly.

In any case, there is an open feature request for finer grained deployment termination: FR #36873. I encourage those who are interested in this feature to contact Tech Support to get attached to the request.

Cheers,

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com