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.
I have set the path to the AppD agent jar in the startWeblogic.cmd script like:
set JAVA_OPTIONS=%JAVA_OPTIONS% -javaagent:"%APPDHOME%\javaagent.jar"
just before the line for starting weblogic.
In the cmd output of WebLogic I can see that the javaoptions are set correctly and the AppD agent property is present but I don't see it running, so there are no messages on the console about actually starting the AppD agent at all. Also, no log files are generated.
What can I do to make the WebLogic start the AppD agent?
Still the same situation. Here is the java line:
r" -client -Xms512m -Xmx1536m -XX:MaxPermSize=128m -Dweblogic.Name=AdminServer
-Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:
\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testCon
sole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls
Can you confirm:
Is there anything relating to the AppDynamics agent in the WebLogic boot log?
I also note this is your WebLogic admin server you have instrumented. You are likely to get more interesting results from one of the managed servers where your app is running (unless this is a single server installation), although there is no reason that instrumenting the admin server should not work.
1. Yes, it is running fine - I don't see any issues with it.
2. No - no logs generated at all. Only way I can make it write something is if I run directly java with -javaagent but it exits immediately after start, of course.
I don't see anything related with AppD in the weblogic logs.
It is a single server installation. And also it is more like a test setup so I just need to get any data from the agent...