Flow Trace Fails to Load with Numerous Correlated Composite Instances

(Doc ID 1344024.1)

Last updated on SEPTEMBER 23, 2013

Applies to:

Oracle SOA Suite - Version to [Release 11gR1]
Information in this document applies to any platform.


The flow trace in Oracle Enterprise Manager Fusion Middleware Control Console can fail to load in scenarios in which you have numerous correlated composite instances (for example, 100).

You may see an error similar to the following in your <SOA_Server>/logs/soa_server1-diagnostic.log file.

Exception occured while retrieving the Flowtrace XML for the Composite
Instance; ECID: ....
weblogic.rmi.extensions.RequestTimeoutException: RJVM response from
'weblogic.rjvm.RJVMImpl@1205e86f - id:
connect time: 'Wed Sep 01 01:41:57 PDT 2010'' for
'getAuditTrail(Ljava.lang.String;) 'timed out after: 60000ms.
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at oracle.soa.management.internal.ejb.impl.FacadeFinderBean_4vacyo_FacadeFinderBea
nImpl_1034_WLStub.getAuditTrail(Unknown Source)


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms