OpenDeploy issue

I have noticed an issue with OD 5.5.1. Basically, there are times when it seems to be running many java.exe processes. Yesterday, it had about 12 of those processes running and it kept running low on memory. Deployments were very slow because of this and many of them kept timing out hence failing.

I resolved this problem by rebooting the server.

Has anybody got any idea why this happens and how to stop it happening again?

Find more posts tagged with

Comments

Migrateduser

Are you seeing the problem on the sender or receiver system?

How are you starting the deployments, via command line or Admin UI?

Each iwodstart command runs as a Java process. Are you starting a number of deployments in close succession?

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

fbuno

Hi Todd,

the problem is with the main OpenDeploy base server (it receives deployments from the TeamSite server and then fans them out to our web farm)

We run deployments via workflows, GUI and occasionally command line. When this problem happened we did have a few deployments which were run in close succession. My only worry is that those Java processes were still running even after the deployments terminated.

One thing i have also noticed: if i run a deployment via the command line and want to stop it, it stops ok but the java process won't. Any idea why?

Migrateduser

When you run a deployment from the command line, the command line tool runs as a Java process. That Java process talks to the local OD Base Server via RMI. Unless you use the -async option, iwodstart (the Java process) will wait until the deployment completes before returning.

How are you stopping the deployment? It sounds like the deployment thread is terminating but the CLT process isn't.

The next release of OD will have a better "cancel" mechanism whereby you can request a deployment cancelation any time via the command line or Admin UI. OD will hold onto that cancel request until it is able to get to a safe state, and then it will cancel the job.

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

fbuno

I think that possibly explains why we had problems with the java processes. Some deployments were run from the command line and i know i did cancel a couple of deployments from there too.

What is the best way to cancel deployments then?

Migrateduser

In the current release (OD 551), there is a cancel button on the Admin UI. However, it is only visible during phases of deployment when canceling is possible. I don't think there is a good way to cancel deployments from the command line.

The good news is that the upcoming release of OD will improve things by allowing you to request cancellation of a deployment at any time, either through the Admin UI or the command line.

I posted an announcement yesterday for those interested in the upcoming beta. ;-)

Cheers.

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