Direct binding faults getting FabricInvocationException

Question

We have two BPEL composites. When one calls the other using SOAP, the caller receives a correct fault, but when I change to direct binding, the fault type is lost and I get a FabricInvocationException instead.
The called composite returns this fault:
<FaultVar>
  <part name="fault">
    <PInitWorkflowTransactionFault>
      <nppTxId>
        <nppTransactionId>633919050</nppTransactionId>
        <nppTimestamp>2011/06/13 17:53:14 GMT</nppTimestamp>
        <nppIsRetryFlag>false</nppIsRetryFlag>
      </nppTxId>
      <clientTxId>
        <clientUserId>XYZ</clientUserId>
        <transactionId>100001</transactionId>
        <isRetry>false</isRetry>
      </clientTxId>
      <error>
        <errorClass>1</errorClass>
        <errorCode>10221</errorCode>
        <systemType>WorkflowManager-ProvInit</systemType>
        <errorMessage>Dummy error message</errorMessage>
      </error>
    </PInitWorkflowTransactionFault>
  </part>
</FaultVar>In the SOAP version, caller sees this, which is correct:
<bpelFault>
  <faultType>1</faultType>
  <WFMFault>
    <part name="fault">
      <PInitWorkflowTransactionFault>
        <nppTxId>
          <nppTransactionId>633919050</nppTransactionId>
          <nppTimestamp>2011/06/13 17:53:14 GMT</nppTimestamp>
          <nppIsRetryFlag>false</nppIsRetryFlag>
        </nppTxId>
        <clientTxId>
          <clientUserId>XYZ</clientUserId>
          <transactionId>100001</transactionId>
          <isRetry>false</isRetry>
        </clientTxId>
        <error>
          <errorClass>1</errorClass>
          <errorCode>10221</errorCode>
          <systemType>WorkflowManager-ProvInit</systemType>
          <errorMessage>Dummy error message</errorMessage>
        </error>
      </PInitWorkflowTransactionFault>
    </part>
  </WFMFault>
</bpelFault>When I switch to direct binding, using the following reference in the composite.xml, we see the problem.
<reference name="ProvInitializeWorkflowService" wsdlLocation="NPPProvInitializingWorkflow.wsdl">
  <interface.wsdl interface="http://www.example.com/network/NPP/ProvInitWF#wsdl.interface(PInitWorkflowPortType)"/>
  <binding.direct address="soadirect:/default/ProvInitializingWorkflow!1.0/initprovisioningpayload_client_ep_direct"
                  connection-factory="oracle.soa.api.JNDIDirectConnectionFactory">
    <property name="java.naming.provider.url" type="xs:string" many="false">t3://localhost:8001/default/ProvInitializingWorkflow!1.0/initprovisioningpayload_client_ep_direct</property>
  </binding.direct>
</reference>Non-fault replies all work correctly, so we don't have a type mismatch.
Using direct binding, the caller sees this instead:
<bpelFault>
  <faultType>0</faultType>
  <remoteFault>
    <part name="summary">
      <summary>oracle.fabric.common.FabricInvocationException: oracle.fabric.common.FabricInvocationException:
               oracle.soa.api.invocation.FaultException: {http://www.example.com/network/NPP/ProvInitWF}WFMFault</summary>
    </part>
    <part name="detail">
      <detail>{http://www.example.com/network/NPP/ProvInitWF}WFMFault</detail>
    </part>
    <part name="code">
      <code>null</code>
    </part>
  </remoteFault>
</bpelFault>I would really like to use direct binding, but I can't if faults do not work. Help?!
Thanks.

Answer 1

Hello guys,
did you manage to get a patch for your issue?
We have the same one here, a FabricInvocationException at the BPEL layer,
and in the logs
java.lang.ClassCastException: [B cannot be cast to com.bea.wli.sb.transports.client.SOAMessage
     at com.bea.wli.sb.transports.direct.OSBDirectConnection.invoke(Unknown Source)
     at com.bea.wli.sb.transports.direct.OSBDirectConnection.request(Unknown Source)
[ I use SOA Suite 11.1.1.5 ]
thanx
ydes