For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Jeff_Siegel_152's avatar
Jeff_Siegel_152
Icon for Nimbostratus rankNimbostratus
Jun 03, 2014

Thanks for your response. I realize the problem is a hard one, and I’m fishing for ideas on how to tackle in the future.

 

More details:

 

The sending App runs on SAP’s WebMethods. The receiving App runs on Oracle’s WebLogic/Fusion but in the end they are just web servers sending small XML messages wrapped in SOAP, with relatively low volume message burst of a few messages a minute. Our F5 handles many different customers making it hard to isolate data, however no one else complained during the timeout issues, so while we think this was isolated to that one service we aren’t sure. Does that help?

 

Before we increase default idea-timeout setting, or some such thing, is there something you described above that indicates timeouts are really happening on my network at all, and more specifically with the service in question?

 

Thanks,

 

Jeff

 

Jeff_Siegel_152's avatar
Jeff_Siegel_152
Icon for Nimbostratus rankNimbostratus
Jun 10, 2014
Standard HTTPS VS with SSL offload on the F5. The inbound network is the Internet, internally the network is a LAN. It should be high bandwidth and pretty reliable. We have just one real server. Client TCP timeout is the default, 5 minutes. Latency should not be more than a few seconds. Does any way to track this come to mind? Thanks, Jeff