TeamCity/Apache Tomcat
-
Hi all,
Does anybody have any experience of TeamCity and Apache Tomcat? Our developers are seeing an issue and I disagree with their findings.
So, developers local to our London office are able to download TeamCity files from the local VM in London running TeamCity using Tomcat as the webserver at 40 - 50 MB/s. Clients in Aberdeen over VPN are only able to get 2 - 3 MB/s. Now, they are saying something is wrong with the network or traffic shaping which I disagree with.
What we have done:
-
iperf, speeds between London and Aberdeen through the VPN are as expected.
-
Tested using a copy on Windows between the servers. Speeds were 40 - 50 MB/s as expected. (VM on a server in Aberdeen to the server in London over UI using copy/paste).
-
Setup an IIS webserver in London hosting the file, and can download the file from Aberdeen at 40 - 50 MB/s.
To me, this means the issue is with their Tomcat webserver or TeamCity. Same hardware/hosts/firewalls/tunnel, different webserver = better speeds.
Development built a proxy in London and can go to that proxy address from Aberdeen which sits between them and Tomcat and get 40 - 50 MB/s. They say this is proof of the traffic shaping/Network issue. Which makes no sense. The proxy is local to London, so just like clients is getting 40 -50 MB/s from Tomcat/server, and is able to successfully send to Aberdeen its self at 40/50. So, means the issue is still with Tomcat. Unless my logic is wrong?
Does anybody have any ideas here?
Cheers
-
-
@Jimmy9008 said in TeamCity/Apache Tomcat:
o me, this means the issue is with their Tomcat webserver or TeamCity. Same hardware/hosts/firewalls/tunnel, different webserver = better speeds.
Has anybody gone through the firewall configs and such to make sure there's not any traffic shaping happening?
-
Yes, my firewall guys have said we have the license available but do not use the feature.
-
There are multiple options, but by far the most likely is what they are saying - that there is something whether a traffic shaping rule, a bad packet size setting, a VPN config, or a proxy / web handler that is mangling things.
If you know that none of those things exist, then TeamCity must have some weird configuration that interacts poorly with the settings of the VPN tunnel that another proxy does not. But that's very, very unlikely.
Can you try moving the IP address of TeamCity to match that of the proxy that works? That's a quick test that, if it gets suddenly fast answers some questions, but if it remains the same tells us nothing.
