Scribd Logo
Upload

Welcome to Scribd!

  • HTTP Data Send Error - '12031' (TCP Connection Reset) After Clicking The 'Submit' Button To Send Sales Order To AIA. (Doc ID 966743.1)

    Uploaded by

    Alex Calado
    421 views3 pages
    HTTP Data Send error - '12031' (tcp connection reset) after clicking the 'Submit' button to send Sales Order to AIA. (Doc ID 966743.1)

    Original Title

    HTTP Data Send error - '12031' (tcp connection reset) after clicking the 'Submit' button to send Sales Order to AIA. (Doc ID 966743.1)

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    HTTP Data Send error - '12031' (tcp connection reset) after clicking the 'Submit' button to send Sales Order to AIA. (Doc ID 966743.1)

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    421 views3 pages

    HTTP Data Send Error - '12031' (TCP Connection Reset) After Clicking The 'Submit' Button To Send Sales Order To AIA. (Doc ID 966743.1)

    Uploaded by

    Alex Calado
    HTTP Data Send error - '12031' (tcp connection reset) after clicking the 'Submit' button to send Sales Order to AIA. (Doc ID 966743.1)

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 3

    6/23/2020 Document 966743.

    1
    Copy right (c) 2020, Oracle. A ll rights reserv ed. Oracle Confidential.

    HTTP Data Send error: '12031' (tcp connection reset) after clicking the "Submit" button to send Sales Order to AIA. (Doc ID 966743.1)

    APPLIES TO:

    Siebel CRM - Version 8.1.1 [21112] and later


    Oracle Communications Integration Pack for Order to Billing - Version 2.0.1 and later
    Oracle Solaris on SPARC (64-bit)

    SYMPTOMS

    Customer experienced with the data send error, showed in a popup window on the Siebel Order Items view, then the "Submit" button has been clicked to send the Sales Order to
    the Oracle SOA 10g instance. The Oracle AIA/BRM Web Service end-point: "ProcessSalesOrderSiebelJMSProducer" of the Oracle AIA Prepackaged Integration Processes for
    Communications had to be invoked.

    The essential part of the error message in Siebel UI was:

    Error invoking service 'ProcessSalesOrderSiebelJMSProducer', method 'process' at step 'Submit Order WS'.(SBL-BPR-00162)
    --
    HTTP Internet Exception during 'Data Send': 'The connection with the server was reset', code: '12031'(SBL-EAI-04116)

    The error happened sporadically and seems was not related to the application load.

    The same Sales Order could be successfully transmitted by next try of clicking the "Submit" button.

    The issue could be reproduced in Siebel Thin Client Business Service simulator view to run the " process
    " method of the " ProcessSalesOrderSiebelJMSProducer" Outbound WS proxy
    Business Service with some sample payload (instance of the " PDS Order - No Hierarchy
    " Integration Object), captured from a failed calls.

    Oracle SOA 10g logs did not show any related traces to this case.

    CAUSE

    https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=11cssutyni_52&id=966743.1 1/3
    6/23/2020 Document 966743.1
    The TCP traffic monitoring on Siebel side, identified, that the TCP connection, opened by the Siebel EAI HTTP Transport to the HTTP Apache Server of Oracle SOA 10g instance was
    unexpectedly closed by Apache (FIN, ACK received). This causes Siebel to fail at next HTTP call, when the Siebel HTTP Transport tried to re-use this previously opened TCP
    connection.

    Note, by default the Siebel EAI HTTP Transport uses the HTTP /1.1 feature of "persisted connections", to optimize the performance on data exchange between HTTP Client (Siebel
    CRM Application) and HTTP Server (external application, such as HTTP Apache Server).

    The "..The connection with the server was reset', code: '12031'... " error has been brought by the WinInet API program stack, indicating that the client tries to use TCP connection,
    which has been already closed by the server party.

    SOLUTION

    The reason for connection reset by SOA 10g was not clearly identified

    However, the following workaround did help to solve the reported behavior on Siebel side, achieving stable Sales Order submission:

    WORKAROUND:

    Purpose:
    prevent the EAI HTTP Transport to use the HTTP /1.1 "persisted session" feature

    ***

    Solution for Siebel Releases 8.1.1.x/8.2.2.x:

    Add following input arguments to each call of the affected outbound WS proxy BS method call:

    Name = Value pairs in the input property set:


    siebel_transport_header:Connection = close
    siebel_transport_param:HTTPMaxIdleSeconds = 0

    Note: To staticially (have no need to specify at each BS call) add the above mentioned parameters, one can amend definition of the proxy BS to provide these as user properties
    with exact same name and value pairs.

    REFERENCES

    NOTE:859382.1 - How To Control Parameters On Transport For Outbound Web Service, e.g. HTTPSleepTime (HTTP) Or SendUsername (JMS)
    NOTE:1076251.1 - Master Note For Siebel Web Services IP2016 , IP2017 and 18.x
    Didn't find what you are looking for?

    https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=11cssutyni_52&id=966743.1 2/3
    6/23/2020 Document 966743.1

    https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=11cssutyni_52&id=966743.1 3/3

    You might also like