How documentum method timeout performed?

Anton_R

I have documentum dm_method

create dm_method object

set object_name = 'xxxxxxxxxxx',

set method_verb = '****.yyy.Foo',

set method_type = 'java',

set launch_async = false,

set use_method_server = true,

set run_as_server = true,

set timeout_min = 60,

set timeout_max = 600,

set timeout_default = 500

It invoked via dm_job with period 600 second.

But my method can work more than 600 second (depend on size of input data, produced by users)

Whats happens whan max_timeout exceeded on dm_method implemented in java?

DFC job manager send Thread.interrupt()?

DFC waits for finishing job and only log warning?

I didn't find detailed description in Documentum documentation.

http://stackoverflow.com/questions/7763352/how-documentum-method-timeout-performed

Find more posts tagged with

Comments

aflowers001

If I recall right it will attempt to kill the running method, but how is dependant on how the method is running. If the method server is used for these then it will try to kill it in some manner, but if it uses an external java process (i.e. not method server) it will try to kill the running process.

I don't know the exact method inside the method server but would assume it is not pretty and could well be Thread.interrupt or something similar, all you need to know is that the server will try to stop it.

I say 'try' as if the method is doing something that cannot be interrupted I have seen them continue for a while.

bacham2

When you call the dm_method yourself (e.g. via apply method), you can specify a timeout value. The value must be between timeout_min and timeout_max of the dm_method object. If you don't specify a timeout value, the Content Server will use the timeout_default value. If the timeout is reached, Content Server will kill the method execution.

If your method is called from a dm_job, no timeout is specified so the timeout_default will apply. So if your method can run longer than 600 seconds, you need to adjust timeout_default to the maximum time it can run.

Hicham

mszurap

I've never seen that Content Server kills a method because of it's timeout. Of course you might be right and maybe I have too few experiences about this.

As long as I know when the timeout is reached only the status of the job will be set to "timed out", but the method will complete (or not in timely manner) in the background.

bacham2

Then you should definitely give a try. Everybody should have seen this once in his life (the Content Server killing a method that is)! I did

By the way, a method can also run without a job.

mszurap

Hi,

Can it be (that I have never seen the killing of a method) bacause we always write methods which run in Java Method Server? I assume it is feasible to kill a standalone process, but it is not an option for methods running in JMS? Or can it kill it in JMS also (maybe with a Thread.interrupt())?

bacham2

The Content Server shows no mercy: it kills all methods, regardless of where they run. Not sure how it does it on JMS but it does it.

bacham2

Actually, it's possible that the Java method will continue running in the JMS after timeout. However, the Content Server will already have closed the OutputStream where the method can write the response. So you will most likely see errors in the log, and also in the job object if the method was called by a job. Depending on what the method does, it might actually be able to complete whatever it needs to do.

However, you should try to set the default timeout to a value that will give your job enough time to complete cleanly.

mszurap

Thanks for the comments, I'll try it some day...