+++ This bug was initially created as a clone of Bug #624817 +++ Otherwise, EMS defaults to using /tmp for its temporary per-classloader copy of the ems-impl-XXX.jar, which is bad, because it makes it hard to define an access control policy for that jar. --- Additional comment from ian.springer on 2010-08-17 16:42:09 EDT --- Fixed in master (ed986ce) and release-3.0.0 (c450bad).
Test for JON2.4.1
Hi Ian, Can you please provide steps to test the bug and expected result?
Though this change was in the RHQ plugin container, it only changes behavior when the plugin container is deployed inside EmbJopr (i.e. the JBAS admin console); there is no change in behavior when deployed inside the RHQ Agent, so there's nothing to test on that end.
Ondrej Can you test that this bug is fixed in the EAP5.1 release of the console? Thanks
Charles, I'll need test instructions for this, thx.
Ian, can you provide repro steps?
REPRO STEPS ----------- 1) Start up EAP 5.1. 2) Log into admin console. 3) Select the JBoss AS Server resource in the admin console. 4) Look in JBOSS_HOME/server/default/tmp/embjopr/ and confirm that there's an org-mc4j-ems-implXXXXXX.jar file in there, e.g.: org-mc4j-ems-impl1256585583900479844.jar If you see that jarfile under /tmp instead, then the issue has not been fixed.
Verified on Jon241 build#35 Stated EAP5.1 and logged in to the admin console. After login observed that the directory JBOSS_HOME/server/default/tmp/embjopr gets created and it displays below file: org-mc4j-ems-impl2348731868522119396.jar The /tmp directory does not display above file. Marking this as verified.