Forum Discussion

Heidi_35827's avatar
Heidi_35827
Icon for Nimbostratus rankNimbostratus
Oct 10, 2012

SAP Note regarding HTTP timers issue w/ Web Dispatcher

Anyone familiar with the timers referred to in the SAP Note 1177035? I'm not sure where to look to check timers that are described in this note. Anyone come across this before?

 

 

Here is an excerpt from the SAP Note (Attaching the full PDF to this post)

 

“This issue was seen on some customers' systems already. The reason was that the customer had a system landscape with some 3rd party load balancer (the provider does not matter, this can happen on any) and the configuration was set up the way, that this load balancer has waited on the HTTP response for 30 seconds (is a setting option on load balancer), and if this was not completed (often in query execution case) the request was canceled and the same request was send again to BI Java server”

 

partner
sap

2 Replies

Sort By
  • Nojan_Moshiri_4's avatar
    Nojan_Moshiri_4
    Historic F5 Account
    Oct 10, 2012
    That is a very unclear Note. I've read it twice and I'm still not really sure what it's saying.

     

     

    1) It could be that there is a time out issue. This would be the TCP timeout, the amount of time BIG-IP is going to hold open a connection on either side (client or server) before closing it because of inactivity. You can change this setting from profiles--->TCP (create a tcp profile and adjust the idle timeout to a larger number). This is typically used is you are running a report that takes a long time to complete.

     

     

    2) The second thing I'm seeing in this note is that this could be a persistence issue. When it says "BI is a state full application". It sounds like perhaps the system they are referencing did not have persistence setup.

     

     

    So, on your side, if you are seeing this error, check the couple of things: 1) The TCP profile you have assigned to your virtual server. Adjust it above the 300 second default 2) Make sure you have a persistence profile on your virtual server.

     

     

    Hopefully this helps, if you provide additional information about what sAP system you're running and what you're seeing, we can provide additional guidance.

     

  • Heidi_35827's avatar
    Heidi_35827
    Icon for Nimbostratus rankNimbostratus
    Oct 11, 2012
    Thank you. I'm glad I'm not the only one who thought this Note was extremely vague.

     

     

    The TCP timer is the one I thought of as well. We adjusted it up to 900 seconds yesterday afternoon. I should know today if this fixes the issue. I'll follow up on persistence as well, as a possibility, if the timer doesn't resolve this.

     

     

    Thanks again!

     

    Heidi