cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Controller (SaaS, On Premises)

Exception: customername.saas.appdynamics.com:443 failed to respond

Exception: customername.saas.appdynamics.com:443 failed to respond

I am trying to push some custom metrics into AppDynamics but without success so far. I discovered that, in order to push custom metrics (our blockchain metrics), I had to first push metrics from one of your agents. I decided to take the simple root and deploy a basic Hello World microservice in Python using Flask. It is publicly available at (https://helloflask.ocyan.cloud/) at the moment.

 

Despite doing that and following AppD documentation I still get the followin error:

 

14:19:00,000  WARN [AD Thread-Metric Reporter1] MetricHandler - Metric Reporter Queue full. Dropping metrics.
14:19:02,394  INFO [AD Thread Pool-Global0] ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:9, Name:appdynamics.ip.addresses, Value:10.0.2.143]
14:19:02,394  INFO [AD Thread Pool-Global0] ConfigurationChannel - Sending Registration request with: Application Name [cs-beta], Tier Name [hello-world], Node Name [node 103f], Host Name [3b564073aee2] Node Unique Local ID [node 103f], Version [Python Agent v4.5.2.0 (proxy v4.5.13.27004, agent-api v4.3.5.0)]
14:19:02,653 ERROR [AD Thread Pool-Global0] ConfigurationChannel - Fatal transport error while connecting to URL [/controller/instance/0/applicationConfiguration]: org.apache.http.NoHttpResponseException: customername.saas.appdynamics.com:443 failed to respond
14:19:02,653  WARN [AD Thread Pool-Global0] ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [customername.saas.appdynamics.com], port[443], exception [Fatal transport error while connecting to URL [/controller/instance/0/applicationConfiguration]]
14:19:02,653  WARN [AD Thread Pool-Global0] AgentErrorProcessor - Agent error occurred, [name,transformId]=[com.singularity.CONFIG.ConfigurationChannel - org.apache.http.NoHttpResponseException,2147483647]
14:19:02,653  WARN [AD Thread Pool-Global0] AgentErrorProcessor - 0 instance(s) remaining before error log is silenced
14:19:02,653 ERROR [AD Thread Pool-Global0] ConfigurationChannel - Exception: customername.saas.appdynamics.com:443 failed to respond
org.apache.http.NoHttpResponseException: customername.saas.appdynamics.com:443 failed to respond
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:141) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259) ~[httpcore-4.4.9.jar:4.4.9]
at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163) ~[httpcore-4.4.9.jar:4.4.9]
at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:165) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273) ~[httpcore-4.4.9.jar:4.4.9]
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) ~[httpcore-4.4.9.jar:4.4.9]
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:272) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72) ~[httpclient-4.5.4.jar:4.5.4]
at com.singularity.ee.util.httpclient.n.a(n.java:289) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.httpclient.n.a(n.java:204) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.rest.f.G(f.java:384) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.rest.f.F(f.java:337) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.rest.controller.request.b.F(b.java:130) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.rest.controller.request.c.a(c.java:36) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.agent.appagent.kernel.config.xml.p.a(p.java:1480) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.agent.appagent.kernel.config.xml.p.a(p.java:122) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.agent.appagent.kernel.config.xml.w.a(w.java:742) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.agent.appagent.kernel.config.xml.p.a(p.java:521) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.agent.appagent.kernel.config.xml.G.run(G.java:644) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.o.run(o.java:122) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_51]
at com.singularity.ee.util.javaspecific.scheduler.B.e(B.java:335) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.a.b(a.java:152) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.b.a(b.java:119) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.b.b(b.java:206) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.b.run(b.java:236) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.i.a(i.java:694) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.i.run(i.java:726) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]

 

Any idea how to fix that? Any help is appreciated!

 

Thanks,

 

Gabriele

 

^ Post edited by @Ryan.Paredez to remove Controller URL info. Please do not share your Controller URL in community posts for security and privacy reasons.

By replying you agree to the Terms and Conditions of the AppDynamics Community.
Exception: customername.saas.appdynamics.com:443 failed to respond
2 REPLIES 2
Bin.Hu
Creator

do you have a solution? I have a same issue 

Tags (1)
Venkata.Nandula
New Poster

Hi @Gabriele.Cacciola,

 

Did your issue got resolved? i am having the same issue with the DMZ servers.