[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Commented] (AMQ-3797) org.apache.activemq.util.StringArrayEditor causes classloader leaks
From:       "Claus Ibsen (JIRA)" <jira () apache ! org>
Date:       2012-08-30 13:33:07
Message-ID: 2067257849.16474.1346333587665.JavaMail.jiratomcat () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/AMQ-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444950#comment-13444950 \
] 

Claus Ibsen commented on AMQ-3797:
----------------------------------

Yeah we hit an issue with AMQ reqistering a javax.jms.Destination property editor \
that played tricks. IMHO property editors in the JDK should not be used, as they are \
per JVM, and you can override each others editors etc.  
> 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


[prev in list] [next in list] [prev in thread] [next in thread]