You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2026/06/23 20:17:00 UTC
[jira] [Closed] (ARTEMIS-6110) json broker properties doesn't load arrays properly
[ https://issues.apache.org/jira/browse/ARTEMIS-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram closed ARTEMIS-6110.
-----------------------------------
> json broker properties doesn't load arrays properly
> ---------------------------------------------------
>
> Key: ARTEMIS-6110
> URL: https://issues.apache.org/jira/browse/ARTEMIS-6110
> Project: Artemis
> Issue Type: Bug
> Reporter: Thomas Lavocat
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.55.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> On origin/main, InsertionOrderedProperties.loadJsonObject parses JSON broker config files into flat key=value properties. Its switch handles OBJECT, STRING, NUMBER, TRUE, FALSE — and throws on anything else via default: throw new IllegalStateException("JSON value type not supported: " + jsonValueType).
> That means any JSON config file containing an array value causes a hard crash during broker startup. For example:
> {
> "incomingInterceptorClassNames": ["com.example.Interceptor1", "com.example.Interceptor2"],
> "addressConfigurations": {
> "orders": {
> "routingTypes": ["ANYCAST"]
> }
> }
> }
> This blows up on routingTypes, incomingInterceptorClassNames, staticConnectors, federationDownstreamAuthorization, etc. — any property that's naturally a list. The only workaround is to avoid arrays in JSON config and use the .properties format instead, which defeats the purpose of having JSON config support.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org