Known issues with Java method server

Some time some custom appliaction can cause Method Server to put heaver load on the content server. On further investigation we have found that if the application uses asynchronous server method invocations, then executeion agent can potentially launch hundered or more external method processes. This causes a very high load on the content server and Oracle.

The Tomcat server userd for the method server can be configured to reduce the number of simultaneous threads active. This coculd theoretically provide some flow control by limiting the number of methods that can simulatneously be executed. Unfortunately it appears error handlingin the Content Server for asynchronous methods is rather weak. If the Java Method Server is already processing all the simultaneous methods that it is capable of, all new requests get discarded. The application never knows that its method requests were discarded.

Please note asynchronous method execution can overload the server and may cause substantial delay in execution of the method.

When switching to synchronous mehotd execution there are still problems. Under heavy load the “DO_METHOD” calls will fail with a rather vague error message. It is up to the application to decide that the server is under heavy load and therefore should just keep retrying the method submission until the server has bandwidth to service it. As it stantds now the user requests simply fail when the server gets busy.

Related Posts

• Enable SQL Trace in Documentum
• Avoid Folder predicates
• DQL Tips
• Backup repository by oracle tools
• Install and Uninstall Lifecycle