Skip to main content
A
aleserrau
Participant
December 4, 2009
Question

Connection between fmsedge and apache with http tunneling

  • December 4, 2009
  • 1 reply
  • 565 views

I configured my FMS for listening on port 80 and redirect non-FMS requests to apache on port 8080 in the same server machine.

It works well, but I've noticed several tcp connections from fmsedge to apache in Established status (it is simple to see through "netstat -nap | grep 8080" command) that stay forever (until FMS stop or restart).

With a sniffer capture I seen that sometime the fmsedge requests to apache a tcp connection but it (fmsedge) doesn't use this connection. Then the apache server send a syn,ack tcp request and always fmsedge send a dup ack tcp response. So, the connection is active but not used, then apache doesn't close it.
The kind of requests for apache are http get to js or php files.

I don't understand why fmsedge create these connections.

Am I misteking some configuration? Or may be it is a bug of fmsedge? Anybody have the same problem? Anybody can help me?

    This topic has been closed for replies.

    1 reply

    Asa_-_FMS
    Adobe Employee
    Asa_-_FMS
    Adobe Employee
    December 4, 2009

    It's possibly a bug in the proxy connection that we make with Apache.  Is this causing an issue for your deployment, or just an annoyance/curiosity?  Your feedback affects how we approach the issue.

    A
    aleserrau1
    Participant
    December 9, 2009

    This is causing an issue for us: after a litle time, the server is blocked because too many connection are established. Any other new request to the service is not accepted and it is necessary to restart the server to resolve, but this action of course close all the active connection...

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices