Wednesday, October 3, 2012

Webservice invocation failed, Unable to access the following endpoint(s) – Oracle SOA Suite 11g


Webservice invocation failed, Unable to access the following endpoint(s) – Oracle SOA Suite 11g:

Some of the time we used to receive the following exception while invoking the webservice endpoints in Oracle SOA 11g. There could be a multiple reason behind this exception.

This blog explains the different ways to narrow down the issue and to fix the issue.

An exception occured while invoking the webservice operation. Please see logs for more details.
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Unable to access the following endpoint(s): http://hostname:50000/XISOAPAdapter/MessageServlet?channel=:SalesForce:CC_Out_Soap_SFDC_order

Steps:

Ping the host name: 

    • If the host is alive then the connectivity looks fine

    •  If we received Unknown host error then verify whether the host entry is available in the server host  file for the host.



    •   If the host is configured to lookup by DNS server then verify the DNS server configuration.

Telnet to the server with the corresponding port:

    • If the telnet is success then the connectivity looks fine.
    •  If the telnet is failed then check the network connectivity between the server and the webservice host in that particular port

Check the webservice status:

    • If the network connectivity between the two servers are looks fine then check whether the webservice is up and running.
    • Some cases the status of the service in the target system shows as up and running but due to some internal errors with the service the source system may not able to connect to the target service . For e.g. sometime the client will not be able to connect to the Siebel services due to some internal table locking but the status of the service will be shown as up and running in Siebel system. 

Check the webservice authentication configured properly:

    • If the webservice up and running properly then check whether the service is protected with username/password. If the service is protected with username/password then check the username/password configuration in the composite.xml file. 
                    You will be receiving the same exception if the username/password is not configured properly.

Sometimes we used to get the exception in the em console

oracle.fabric.common.FabricInvocationException: Unable to access the following endpoint(s): https://sap.int.com/XISOAPAdapter/MessageServlet?channel=*:Markets_Siebel_QA:CC_Out_Soap_SalesOrder

But the actual exception in the server log

Caused By: javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target


Verify the certificate installed properly in the server and also the certificate not expired.



19 comments:

  1. but in my project requirement we don't hardcode the username and password values as shown like above. so, in that case what i have to do.

    ReplyDelete
  2. but iam still getting this error.

    ReplyDelete
  3. Post the exact error what you are receiving.

    Regards
    Albin I

    ReplyDelete
  4. Hi,

    I have a 2 node cluster of SOA AIA 11.1.1.5 and am getting Unable to access endpoint error very often. Here is what I see in the logs

    HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection reset

    I have very simple Process which query OID if user exists. This SOA Process is invoked by a java web service which is also deployed in the same domain.

    In a non-cluster environment same requests takes less than a second but in cluster environment it takes 10-12 seconds. Even though same instances pointing to same OID.

    Looks like all the requests in a cluster environment are very slow.

    Any idea what to look into to tune, what could be the reason for the slow processing of the requests. Currently have purged all the data in MDS but still no help. Have over 100 SOA Processes even made sure nother process is running when making this test but still it takes that long which results in the above errors. Any help is appreciated.

    Thanks

    ReplyDelete
  5. I guess the communication between the SOA nodes are happening via Load Balancer.

    The communication between the SOA nodes should be local.
    Refer the below post to verify whether the communication between the SOA nodes are local

    http://www.albinsblog.com/2012/09/configuring-local-optimization-in.html#.ULXgWO-caS0

    Regards
    Albin I

    ReplyDelete
  6. Hi Albin,
    I have an interface where my mediator consumer messages from a local queue and invokes a BPEL process. This BPEL process then invokes an external web service. Off late, the invoke activity on the BPEL process gets stuck (remains in yellow colour) and I get the following error in the em console audit trail: the transaction has been rolled back. The logs how ever show that the end system is not available and the following error:
    javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection reset
    Please note that this issue is happening intermittently. My JTA is 120 sec

    ReplyDelete
  7. Hi Subhashish

    There is tow possibilities,

    1. The process might be failing some where after the invoke activity and rolled backed to previous commit point - add check pint activity after the invoke activity(multiple places) to narrow down the issue.

    2. The process might be taking more time to complete and rolled backed to previous commit pint - Refer the following post for details on timeouts http://www.albinsblog.com/2012/05/weblogictransactioninternaltimedoutexce.html

    I hope this will help you.

    Regards
    Albin I

    ReplyDelete
  8. Hi Albin,
    Thanks for your inputs. I set the httpreadtimeout property in the mbean browser for the binding element in the composite and it worked out for me.

    ReplyDelete
  9. This comment has been removed by the author.

    ReplyDelete
  10. This comment has been removed by the author.

    ReplyDelete
  11. Hi Albin,
    I still got this error after configuring all the necessary step.
    <Unable to dispatch request to http://xxx.xxx.xx/xx due to exception
    oracle.fabric.common.FabricInvocationException: Waiting for response has timed out. The conversation id is urn:A2C893007C1811E3BF0DE3EDC1EFB657. Please check the process instance for detail.

    Please note we did the same thing for OSB and its working fine when invoking the web service call. But the new interface for AIA is not working properly.

    ReplyDelete
  12. An error that we observe;

    <Unable to dispatch request to https://yy.yy.yyy.yy/Test3 due to exception
    javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

    ReplyDelete
    Replies
    1. Verify the configuration of Keystores for the server from the console.

      Login to Weblogic Console and click on the corresponding server(e.g. AdminServer) and click on Keystores

      The certificate has to to be installed into the configured keystore - use keytool to verify the same

      Delete
  13. Hi Albin,

    I have a situation my osb instance is down and i need to handle this exception. and get the payload inserted into my audit table. how can we handle this exception and this exception fall under what time of system fault.

    ReplyDelete
  14. This scenario will throw the Remote Fault. Catch the fault with Catch Activity and perform the required actions.

    Refer the following url to get the payload - http://www.albinsblog.com/2011/10/oracle-soa-11g-retrieving-request.html#.Uu5vyPmSySo

    Regards
    Albin I

    ReplyDelete
  15. Hi,iam geting the samae issue:
    oracle.fabric.common.FabricInvocationException: Unable to access the following endpoint(s): http://testebs.bra.com.au:60/webservices/SOAProvider/plsql/xxwsh_trip_abcs_pkg/

    Can you pls guide me ?

    ReplyDelete
  16. This comment has been removed by the author.

    ReplyDelete
  17. Hi ,Albin .Iam facing issue,while we invoking EBS-SOA gateway webservice as below:

    1)


    JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "4,886,242",
    bpel engine can not proceed further without an active transaction.
    Please debug the invoked subsystem on why the transaction is not in active status.
    the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "4886242" for process "XXXBPEL" is supposed to be in an active jta transaction,
    the current transaction status is "MARKED_ROLLBACK", the underlying exception is
    "Unable to access the following endpoint(s): http://XXX.com.au:/webservices/SOAProvider/plsql/xx_abcs_pkg/" .
    Consult the system administrator regarding this error.

    2)
    [WLS_SOA1] [NOTIFICATION] [] [oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor] [tid: DaemonWorkThread: '211' of WorkManager: 'wm/SOAWorkManager'] [userId: ] [ecid: 3b581a8dd575328b:-4ce6fc59:14d0210b25e:-8000-00000000000e1175,0] [WSM_POLICY_NAME: oracle/wss_username_token_client_policy] [APP: soa-infra] [composite_name: XXXXABCS] [component_name: XXBPEL] [component_instance_id: 4921549] Recipient Alias property not configured in the policy. Defaulting to encrypting with signers certificate.
    [2015-04-29T13:34:25.051+10:00] [WLS_SOA1] [ERROR] [] [oracle.integration.platform.blocks.soap] [tid: DaemonWorkThread: '211' of WorkManager: 'wm/SOAWorkManager'] [userId: ] [ecid: 3b581a8dd575328b:-4ce6fc59:14d0210b25e:-8000-00000000000e1175,0] [APP: soa-infra] [composite_name: XXXXABCS] [component_name: XXXBPEL] [component_instance_id: 4921549] Unable to dispatch request to http://xxxxx:/webservices/SOAProvider/plsql/xx_abcs_pkg/ due to exception[[
    javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection reset

    Can anyone pls suggest on this

    ReplyDelete
    Replies
    1. Hi Ram,

      Please give a try below methods

      1) This problem is due to poor IP communication between back-end computers, possibly including the Web server at the site you are trying to visit. Please make sure it is up and running and if you see error log in more detail you will see 502 Proxy Error .

      2) If Webservice includes any policies then please use WSM_POLICY_NAME: oracle/wss_http_token_client_policy

      Delete