[
https://issues.apache.org/jira/browse/ARTEMIS-4552?focusedWorklogId=900465&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-900465
]
ASF GitHub Bot logged work on ARTEMIS-4552:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Jan/24 16:19
Start Date: 18/Jan/24 16:19
Worklog Time Spent: 10m
Work Description: gtully commented on PR #4729:
URL:
https://github.com/apache/activemq-artemis/pull/4729#issuecomment-1898798243
that looks good to me. it makes sense that the properties applier will auto
create default instances for any intermediary that it encounters while trying
to apply nested properties.
What we may need is a test for the case where w.x.y.z=1 is set and both getX
and getY can return null.
Issue Time Tracking
-------------------
Worklog Id: (was: 900465)
Time Spent: 2h 10m (was: 2h)
> Configure all connection-router settings by using broker properties
> -------------------------------------------------------------------
>
> Key: ARTEMIS-4552
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4552
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Domenico Francesco Bruscino
> Assignee: Domenico Francesco Bruscino
> Priority: Major
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Allow to configure all the connection-router settings by using the broker
> properties. The broker properties for the cache configuration cause a null
> pointer exception:
> {code}
> "connectionRouters.autoShard.cacheConfiguration.persisted=true"
> "connectionRouters.autoShard.cacheConfiguration.timeout=60000"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)