EPAgent with jetty enabled doesn't run in container with 48 CPUs

Document ID : KB000119992
Last Modified Date : 21/11/2018
Show Technical Document Details
Issue:
We have EPAgent running inside a kubernetes container. It has access to the 48 CPUs on the system.
We have jetty enabled, introscope.epagent.config.httpServerPort=8080 When
we attempt to make a call to http://localhost:8080/apm/metricFeed, we get the error that is mentioned in
https://docops.ca.com/ca-apm/10-5/en/implementing-agents/ep-agent/configure-the-epagent/configure-epagent-for-jetty/
Example:
2016-10-22 06:43:48.639:WARN:oeji.nio:Dispatched Failed! SCEP@200d65c6{l(/0:0:0:0:0:0:0:1:41308)<->r(/0:0:0:0:0:0:0:1:9080),s=-1,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=1r}-{AsyncHttpConnection@19fd1c54,g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-14,l=0,c=-3},r=32470} to org.eclipse.jetty.server.nio.SelectChannelConnector$ConnectorSelectorManager@1a43b86b
We have tried various configurations that are mentioned in the above link, but continue to get the Dispatched Failed error message. 
Resolution:
We checked and found these properties do not exist in the APM Release (10.5.1): 
introscope.epagent.config.HttpServer.minThreadCount 
introscope.epagent.config.HttpServer.maxThreadCount 

We found that this change was merged to APM 10.5.2 and APM 10.7. 

Based on this information we suggest to use the APM 10.5.2 EPAgent. 

There should be no issue APM 10.5.2 EPAgent reporting to APM EM 10.5.