Topic
6 replies Latest Post - ‏2014-05-01T06:57:44Z by MalleshaBasavanna
JasonJava
JasonJava
69 Posts
ACCEPTED ANSWER

Pinned topic Data Power Connectivity Errors to a backend Websphere app server

‏2012-02-24T00:58:59Z |
Our flow is Client -> DP XI50 -> Two backend Websphere App Servers

We are sending around 3000 transactions within 1.5 hours and about 100 failure alerts from DataPower. then when they got requeued, it is fine.

  • 0x01130006: Failed to establish a backside connection
  • 0x01130011: Failed to process response headers

So we have about 96.6 % success rate on first hit. Our user is asking us to see if there is anything we can do some tuning of the system.
Welcome suggestions ! Is that a network issue or a threading issue of the backend server ?
Updated on 2013-04-02T20:39:12Z at 2013-04-02T20:39:12Z by SystemAdmin
  • HermannSW
    HermannSW
    4320 Posts
    ACCEPTED ANSWER

    Re: Data Power Connectivity Errors to a backend Websphere app server

    ‏2012-02-24T01:56:21Z  in response to JasonJava
    Hi,

    > ...
    > - 0x01130006: Failed to establish a backside connection
    > - 0x01130011: Failed to process response headers
    > ...
    >
    got to "Administration->Debug->View List of Event Codes" in WebGUI.

    Searching for "0x01130006"/"0x01130011" and clicking on "help" link in rightmost column explains:

    Event Code 0x01130006 - Failed to establish a backside connection

    A dynamic routing failure has occured. The backend host was successfully selected, but a network connection to it could not be established.

    Level: error

    Suggestion:

    No suggestion available



    Event Code 0x01130011 - Failed to process response headers

    The HTTP response headers received from the backside server for this transaction did not conform to RFC 2616 and could not be parsed.

    Level: error

    Suggestion:

    No suggestion available




    > Welcome suggestions ! Is that a network issue or a threading issue of the backend server ?

    For "0x01130006":
    Are you sure that the backend system was able to handle the load?
    I have seen situations in the past where the DataPower request volume was a DoS to some backend systems ...

    Just take packet captures and eg. Wireshark will tell you exactly who closes/drops connections, and probaly also why.

     
    Hermann<myXsltBlog/>
    • JasonJava
      JasonJava
      69 Posts
      ACCEPTED ANSWER

      Re: Data Power Connectivity Errors to a backend Websphere app server

      ‏2012-02-24T06:00:35Z  in response to HermannSW
      Thanks for the reply. Our admin suggested to increase the thread count max on the Websphere servers. We will give it a try with your tool suggestion.

      According to this IBM article, these two errors are thrown by the DataPower appliance when it is unable to establish or reuse a connection. Maybe we can do the retry in the datapower as it described.

      http://www-01.ibm.com/support/docview.wss?uid=swg21282678
      • minarez
        minarez
        3 Posts
        ACCEPTED ANSWER

        Re: Data Power Connectivity Errors to a backend Websphere app server

        ‏2012-11-16T15:40:54Z  in response to JasonJava
        Hi,

        I want to know if your problem has been solved by increasing the maximum number of threads in websphere server or in applying the IBM Article.

        Thanks in advance

        Amine
      • SystemAdmin
        SystemAdmin
        6772 Posts
        ACCEPTED ANSWER

        Re: Data Power Connectivity Errors to a backend Websphere app server

        ‏2013-04-02T20:39:12Z  in response to JasonJava
        I know this is an old post, but maybe some one will be able to answer since I am having the same problem. Will some one confirm if increasing the thread count max on the Websphere servers resolves this issue?
  • LionGod8
    LionGod8
    1 Post
    ACCEPTED ANSWER

    Re: Data Power Connectivity Errors to a backend Websphere app server

    ‏2014-02-12T12:30:59Z  in response to JasonJava

    The DataPower reuses open HTTP connection. So it can send multiple messages through the same connection.
    This is called Persistent Connections.
    Sometimes the backside server closes a connection, and the DataPower tries to use this connection before he knew that the connection was closed.
    Then one of the following errors can occur:

    • 0x01130011: Failed to process response headers
    • 0x01130006: Failed to establish a backside connection

    The second error is actually a timeout.

    This happens mainly when there are network problems or the network is slow.

    To fix the problem you can do one of the following:

    1. Catch the error and try to resend the message through a new connection as described here.
    2. Not using Persistent Connections. To do it go to Advanced tab (or Advanced Proxy Settings) in your gateway/proxy and disable Persistent Connections.

    Hope this information would help.
    It happened to me too and I started investigating and now I'm sharing with you my insights.
    Good luck!

    Updated on 2014-02-12T18:14:14Z at 2014-02-12T18:14:14Z by LionGod8
  • MalleshaBasavanna
    MalleshaBasavanna
    1 Post
    ACCEPTED ANSWER

    Re: Data Power Connectivity Errors to a backend Websphere app server

    ‏2014-05-01T06:57:44Z  in response to JasonJava

    Hi LionGod8,

    In case of wrong back end url configuration on DP, the control will go to infinte loop if we use the solution which you have proposed. Is there any way to give conditional check on match action so that error rule can be restricted to some count. Please suggest.

     

    Thanks,

    Mallesh