Yes!!!
we did it by a DQL update:
Having same issue. Also having great difficulty in determining which method is failing. Unfortuantely, the content server log does not indicate the method that is timing out!
I also tried looking for the method by the posted timeout value, but there were multiple methods with that timeout value. I don't want to just bump up the method timeout, I want to figure out why it is timing out.
Any bright ideas how I might figure out which method is failing? I checked the session log for the referenced session in the error message; nothing there.
Checked the JMS logs, could not determine.
In my case, they were all associated with workflow events:
./mdasprd.log:Wed Mar 17 13:44:46 2010 494386 [DM_WORKFLOW_E_AGENT_LAUNCH]error: "Failed to launch 4a01435080080c79 due to an operating system error: JAVA_METHOD_SERVER ERROR : user: mdasprd session id: 010143508000000c message: Method timed out (Exceeded the allowed duration of 60 seconds)
So, thought I had a bright idea to look for dm_methods where a_special_app = 'Workflow' and the same timeout value, but got no results.
Steve,
have you checked if '4a01435080080c79' is the r_object_id of the method???
Best regards
If you want to have method invocation in the docbase log you need to set the trace launch attribute on the method