Forum Discussion
KenJ_50171
Nimbostratus
Nimbostratusconflict with Adobe Connect Pro
We've hit a conflict between our BigIP and the application Adobe Connect Professional, which is a "virtual meeting" software package.
Users who "share" a file (such as a Powerpoint) from their user PC into a Meeting are hitting a problem where the file transfer hangs.
Analysis so far is that the Adobe package is not respecting the KeepAlives as the F5 tries to reuse connections. When Adobe uses two packets to close the connection, the user client & F5 have already started using the presumed-open connection, and BOOM as the packets cross.
Tweaking window and buffer sizes in the TCP profile have allowed us to toggle between first-file-hangs and first-file-OK-second-file-hangs.
Our next step involves trying to get Adobe to discuss why their package doesn't respect the KeepAlives (which seem to be essential for OneConnect to work, and the F5 deployment guide stresses the importance of OneConnect for this application.
A possible workaround would be to get the F5 to stop reusing connections. We toggled off OneConnection Translations in the HTTP profile and that did not seem to help.
We're grasping at straws here, so any insights would be appreciated. Our Adobe-using customers are not going to like being told we can't load-balance their application.
KenJ_50171Sometimes writing out the problem leads to the solution... a little Googling led to an Adobe page suggesting that for some types of connection flakiness one might need to put in an Adobe configuration line "KEEP_ALIVE=false". Preliminary testing indicates that this fixes the problem by stopping Adobe Connect from advertising that it will accept keep-alives. We're evaluating if we can live with the performance hit.