You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Emmanuel Hugonnet (JIRA)" <ji...@apache.org> on 2018/11/05 15:46:00 UTC
[jira] [Updated] (ARTEMIS-2163) Classloading issue if
artemis-commons is not in ther same classloader as artemis-client-* or
artemis-server
[ https://issues.apache.org/jira/browse/ARTEMIS-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Hugonnet updated ARTEMIS-2163:
---------------------------------------
Summary: Classloading issue if artemis-commons is not in ther same classloader as artemis-client-* or artemis-server (was: Classloading issue if artemis-commons is not in ther same classloader as artemis-client-* or artemis-server-*)
> Classloading issue if artemis-commons is not in ther same classloader as artemis-client-* or artemis-server
> -----------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2163
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2163
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Broker
> Affects Versions: 2.6.3
> Reporter: Emmanuel Hugonnet
> Priority: Major
>
> The class org.apache.activemq.artemis.utils.ClassLoadingUtil is defined in artemis-commons. In a jboss-modules environment this creates a loop to be able to load classes from another module.
> Setting the ThreadContext classloader to the calling class before invoking ClassLoadingUtil
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)