I have setup the agent to go through the proxy, but it doesn't seem to work what I have done
This is my Tomcat parameters
-Dsecurity.type=database -Xms768m -Xmx768m -XX:NewSize=400m -XX:MaxNewSize=400m -XX:PermSize=256m -XX:MaxPermSize=1256m -XX:SurvivorRatio=3 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=15 -XX:+HeapDumpOnOutOfMemoryError -Denvironment=kobus -Dcustom.logs.dir=C:/Util/apache-tomcat-7.0.41/logs -javaagent:C:/Util/AppServerAgent/javaagent.jar -Dappdynamics.http.proxyHost=blabla -Dappdynamics.http.proxyPort=blabla -Dappdynamics.http.proxyUser=bla\bla -Dappdynamics.http.proxyPasswordFile=C:/Uti/\AppServerAgent/pass.txt -Dappdynamics.http.proxyPassword=morebla
I use the same proxy in my browsers and dropbox app and I copied and pasted the username and password
From the logs
[AD Thread Pool-Global1] 24 Jul 2014 10:01:56,959 INFO ConfigurationChannel - Sending Registration request with: Application Name [XXX], Tier Name [Localhost], Node Name [Node 1 c512], Host Name [XXX] Node Unique Local ID [Node 1 c512], Version [Server Agent v3.8.4.0 GA #2014-06-30_13-26-26 r5dc2d8d219673e698b0b455657ac469bc8b59337 4-3.8.4.next]
[AD Thread Pool-Global1] 24 Jul 2014 10:01:57,153 ERROR ConfigurationChannel - HTTP Request failed: HTTP/1.1 407 Proxy Authentication Required
[AD Thread Pool-Global1] 24 Jul 2014 10:01:57,153 WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [flightcentrelimited.saas.appdynamics.com], port[80], exception [null]
[AD Thread Pool-Global1] 24 Jul 2014 10:01:57,153 ERROR ConfigurationChannel - Exception: NULL
My controller info
<controller-port>80</controller-port>
<controller-ssl-enabled>false</controller-ssl-enabled>
<tier-name>Localhost</tier-name>
<node-name>Node 1 c512</node-name>
<agent-runtime-dir></agent-runtime-dir>
<enable-orchestration>false</enable-orchestration>
<force-agent-registration>false</force-agent-registration>
Hi,
We apologize for delay in response, if issue still persists, let us know if the following information helps:
- Can you please locate us the doc link from which you captured the property ?
- If you have captured from AD docs the proxy properties, can you check the behavior without -D jvm arg -Dappdynamics.http.proxyPassword and also make sure the password in file located for property is -Dappdynamics.http.proxyPasswordFile is plain text
- from provided text we see the file location seems to be not valid as we see /\ slashes in the file path:
C:/Uti/\AppSe
Regards,
Arun