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

ASF GitHub Bot commented on AMQ-6514:
-------------------------------------

GitHub user cschneider opened a pull request:

    https://github.com/apache/activemq/pull/214

    [AMQ-6514] Upgrade xbean-blueprint to 4.2 to fix issue with placeholders

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cschneider/activemq AMQ-6514

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq/pull/214.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #214
    
----
commit 0ba102b02d8615b79de718676b2dee2595af0a6e
Author: Christian Schneider <ch...@die-schneider.net>
Date:   2016-11-22T09:49:10Z

    [AMQ-6514] Upgrade xbean-blueprint to 4.2 to fix issue with placeholders

----


> Property placeholders do not work in blueprint activemq config
> --------------------------------------------------------------
>
>                 Key: AMQ-6514
>                 URL: https://issues.apache.org/jira/browse/AMQ-6514
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: OSGi/Karaf
>    Affects Versions: 5.14.1
>         Environment: OSGi, blueprint
>            Reporter: Christian Schneider
>             Fix For: 5.14.2
>
>
> User properties as a placeholder do not work in the blueprint activemq config.
> <policyEntry topic=">" optimizedDispatch="true" producerFlowControl="false" 
> memoryLimit="$example{perTopicMemoryLimit}">
> Java.lang.IllegalArgumentException: Could convert not to a memory size: 
> $example
> {perTopicMemoryLimit}
> at 
> org.apache.activemq.util.MemoryPropertyEditor.setAsText(MemoryPropertyEditor.java:63)[97:org.apache.activemq.activemq-osgi:5.10.0]
> See http://apaste.info/nSw3h
> This seems to be caused by an error in xbean-blueprint 3.x. Upgrading to 4.2 
> fixes the issue. I will create a PR for the change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to