I'm using Gatling to run load tests against our REST services, and have run into an unexpected issue, given that the linux agents are configured with /etc/security/limits.conf:
@teamcity soft nofile 8192
@teamcity hard nofile 16384
When I run a simple build script to report ulimit -Hn and ulimit -Sn, it reports 4096 and 4096, respectively.
We even tried using a wildcard, instead of limiting it to the teamcity user.
Is TeamCity over-riding the ulimit somehow? Can I prevent or configure this over-ride?