You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (Jira)" <ji...@apache.org> on 2023/04/25 09:31:00 UTC
[jira] [Created] (ARTEMIS-4257) artemis run - allow isolation class loader to be disabled
Gary Tully created ARTEMIS-4257:
-----------------------------------
Summary: artemis run - allow isolation class loader to be disabled
Key: ARTEMIS-4257
URL: https://issues.apache.org/jira/browse/ARTEMIS-4257
Project: ActiveMQ Artemis
Issue Type: Improvement
Components: Broker
Affects Versions: 2.28.0
Reporter: Gary Tully
When using artemis with a jvm agent that needs to interact with the broker, the broker api classes need to be on the jvm classpath.
At the moment, the Artemis run command always executes the broker main with an isolating classloader that only peeks at the lib and lib/extra dirs. The only entry on the classpath is the boot jar. This makes sense in a shared environment, isolation is good.
In a container, where there is full control of the env, it makes sense to be able to trust the classpath, and a single classloader allows any agent dependencies to easily found/resolved.
The underlying use case is the jolokia jvm agent integrated with the artemis jaas callback handler, such that the agent can properly integrate with broker auth/authz
the ask is for a simple way to disable the isolation classloader, either a system property of command line option. The system property may be the simplest.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)