Long delay when replying with a fault from a mediator

Question

Using version 11.1.1.3.0 --
I have a very simple Mediator, which executes in about 50ms as expected in non-fault cases, but when returning a fault, it consistently takes approx 6 seconds.
The Flow Trace shows the Mediator completing 6 seconds after the BPEL component completes, but the Mediator completes in 53ms in the Audit Trail. So where are the extra 6 seconds going?
Here is the mediator.mplan:
<?xml version = '1.0' encoding = 'UTF-8'?>
<!--Generated by Oracle SOA Modeler version 1.0 at [6/20/11 2:48 PM].-->
<Mediator name="Mediator1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" wsdlTargetNamespace="http://xmlns.oracle.com/SOASuiteSOAP12/SOASuiteSOAP12/Mediator1" xmlns="http://xmlns.oracle.com/sca/1.0/mediator">
   <operation name="execute" deliveryPolicy="AllOrNothing" priority="4" validateSchema="false">
      <switch>
         <case executionType="direct" name="BPELProcess1.bpelprocess1_client.process">
            <action>
               <assign>
                  <copy target="$out.payload/inp1:singleString" expression="$in.request/inp1:singleString"
                        xmlns:inp1="http://xmlns.oracle.com/singleString"/>
               </assign>
               <invoke reference="BPELProcess1.bpelprocess1_client" operation="process">
                  <onReply>
                     <assign>
                        <copy target="$out.reply/inp1:singleString" expression="$in.payload/inp1:singleString"
                              xmlns:inp1="http://xmlns.oracle.com/singleString"/>
                     </assign>
                     <reply/>
                  </onReply>
                  <onFault type="fault">
                     <assign>
                        <copy target="$out.fault/inp1:singleString" expression="$in.payload/inp1:singleString"
                              xmlns:inp1="http://xmlns.oracle.com/singleString"/>
                     </assign>
                     <fault type="fault"/>
                  </onFault>
               </invoke>
            </action>
         </case>
      </switch>
   </operation>
</Mediator>Edited by: GuyM on Jun 20, 2011 2:07 PM

Answer 1

Hi,
Please take your time to collect some information for troubleshooting:
Does this issue occurred on all outlook clients?
Please try to disable any anti-virus software to check this issue.
Are there any 3rd part mail scanning software?
Thanks,
Best Regards.