Permissions error on startup of java agent.

[Graeme_Gilmour]

Hi all, I am using Java Agent v 4.2.8.0 to monitor WebSphere Application Server on Linux. I have configured the agent manually on two seperate nodes, in an identical manner, however on the second node, I get the following error upon startup (briefly summarised here, with full error attached)...

[Thread-0] 01 Nov 2016 16:17:50,252 WARN AgentErrorProcessor - Agent error occurred, [name,transformId]=[com.singularity.JavaAgent - java.security.AccessControlException,2147483647]
[Thread-0] 01 Nov 2016 16:17:50,253 WARN AgentErrorProcessor - 4 instance(s) remaining before error log is silenced
[Thread-0] 01 Nov 2016 16:17:50,258 ERROR JavaAgent - Could Not Start Java Agent, Disabling !!!!!
java.security.AccessControlException: access denied (java.lang.RuntimePermission getClassLoader)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:398)

On both nodes, the agent home directory is /apps/was/appdynamics/appagent/ with identical permissions / ownership on both, including...

drwxr-xr-x  3 websphere websphere      4096 Oct 28 14:34 appdynamics

                            drwxr-xr-x 4 websphere websphere 4096 Oct 28 14:38 appagent

                                               drwxr-xr-x 8 websphere websphere 4096 Oct 17 11:33 ver4.2.8.0

                                                                    drwxr-xr-x 5 websphere websphere  4096 Oct 31 11:46 conf

                                                                    drwxr-xr-x 3 websphere websphere 4096 Oct 31 11:29 logs

Both nodes' WAS home directory ( apps/was/ws8.5/inst01/ has(seemingly) identical permissions / ownership...

drwxr-xr-x 38 websphere websphere 4096 May 27 18:38 inst01

Both nodes' JRE java.policy and the JVMs' server.policy are identical. And so I'm currently at a loss as to what to try next in order to resolve.

[Jean-Baptiste_M]

Best is probably to speak to support in that case : help@appdynamics.com

JB

[Graeme_Gilmour]

Email sent JB....

[CommunityUser]

This is most likely down to permission requirements in the server.policy file. See the 4.2 documentation on instrumenting Websphere jvms here: https://docs.appdynamics.com/display/PRO42/IBM+WebSphere+and+InfoSphere+Startup+Settings

[Graeme_Gilmour]

Hi Raymond. Yeah we got past the problem with the server.policy amendment.