oracle.fabric.common.FabricInvocationException: Unable to find the WSDL service defined for service name

I was working on an integration with siebel system .When I am trying to invoke their service,

it used throw the below mentioned error :

 <fault>
  <bpelFault>
    <faultType>0</faultType>
    <remoteFault>
      <part name="summary">
        <summary>oracle.fabric.common.FabricInvocationException: Unable to find
                 the WSDL service defined for service name
                 {http://abcd.com/}CC_spcDC_spcNotifications. Please make sure
                 that the port attribute for the binding defined in the
                 composite file is correct by checking the namespace and service
                 name in the #wsdl.endpoint element. In addition, check that the
                 WSDL associated with the binding namespace is imported and
                 currently reachable (check the import nodes at the top of the
                 composite file). Finally, validate any HTTP proxy settings for
                 the server.</summary>
      </part>
      <part name="detail">
        <detail>Unable to find the WSDL service defined for service name
                {http://abcd.com}CC_spcDC_spcNotifications. Please make sure
                that the port attribute for the binding defined in the composite
                file is correct by checking the namespace and service name in
                the #wsdl.endpoint element. In addition, check that the WSDL
                associated with the binding namespace is imported and currently
                reachable (check the import nodes at the top of the composite
                file). Finally, validate any HTTP proxy settings for the server.</detail>
      </part>
      <part name="code">
        <code>null</code>
      </part>
    </remoteFault>
  </bpelFault>
</fault>

How To Tackle This Problem :

1) First take out the wsdl file and put in xml spy  or any online validator to check whether structure is of correct format.

2) The wsdl file should have a structure called "service" at bottom like mentioned below.If its missing it throws out  mentioned error intermittently(ideally it should not) :

<service name="Notifications">

      <port binding="tns:spcNotifications" name="C_spcNotifications">

         <soap:address location="http://abcd.com"/>

      </port>

   </service

3) Check with target partner system whether their service is up or running.


4) Most Imp:


This  can be resolved temporarily by bouncing the SOA Server.Issue might come up again if same wsdl is uploaded again.

I have spent nights in resolving this issue....happy programming!! :)