[
https://issues.apache.org/jira/browse/AMQ-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446696#comment-13446696
]
Claus Ibsen commented on AMQ-3797:
----------------------------------
The issue would be if people run with multiple AMQ brokers in the same JVM, and
hot deploy or uninstall a single broker. Then this would affect existing
running brokers as the property editor becomes uninstalled.
In the comment before we hit an issue in the past in Camel, so we no longer use
property editors, and they are neither thread safe to use anyway.
> org.apache.activemq.util.StringArrayEditor causes classloader leaks
> -------------------------------------------------------------------
>
> Key: AMQ-3797
> URL: https://issues.apache.org/jira/browse/AMQ-3797
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.3
> Reporter: Mattias Jiderhamn
>
> A static block in org.apache.activemq.util.IntrospectionSupport registers
> org.apache.activemq.util.StringArrayEditor with
> java.beans.PropertyEditorManager. In a web application environment, this will
> cause classloader leaks, since java.beans.PropertyEditorManager keeps a
> strong reference to the editor class.
> ActiveMQ should at least provide a graceful means of deregistering
> org.apache.activemq.util.StringArrayEditor (by calling
> java.beans.PropertyEditorManager.registerEditor() again with editor class
> null).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
