Bug ID 669021: Application Tunnel fails to start with the following message: Failed, Couldn't open proxy server.

Last Modified: May 14, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Jun 13, 2017
Severity: 3-Major

Symptoms

Application Tunnel fails to start, with the following message: Failed, Couldn't open proxy server. Also, logterminal.txt might contain multiple entries similar to the following: 2017-05-28,10:44:11:080, 2724,2500,HOST, 48, , 1801, CHostCtrl::OnTimer(), TUNNEL_SERVER_READY_CHECK - TunnelServer is ready 2017-05-28,10:44:11:095, 2724,2500,HOST, 48, , 1801, CHostCtrl::OnTimer(), TUNNEL_SERVER_READY_CHECK - TunnelServer is ready 2017-05-28,10:44:11:111, 2724,2500,HOST, 48, , 1801, CHostCtrl::OnTimer(), TUNNEL_SERVER_READY_CHECK - TunnelServer is ready

Impact

Application Tunnel does not start.

Conditions

Conditions are undefined. If a thread running in F5 components gets blocked by something such as Anti-Virus, WM_TIMER events might cause the Microsoft Windows message queue to overfill, resulting in unexpected behavior. Note: This is an intermittent issue. Such instances of congestion happen when a thread, typically the main thread, is blocked by some long-standing (blocking) operation and does not happen in general use.

Workaround

None.

Fix Information

Application Tunnel client functionality has been improved to implement a queue overfill protection to prevent possible problems when starting the app tunnel.

Behavior Change