[jira] [Closed] (ARTEMIS-4362) Produce a logger when consumers are holding too many messages not allowing depaging
[ https://issues.apache.org/jira/browse/ARTEMIS-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-4362. Resolution: Fixed > Produce a logger when consumers are holding too many messages not allowing > depaging > --- > > Key: ARTEMIS-4362 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4362 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.30.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > We should add a log.warn whenever the system can't read more messages because > consumers are holding too many messages in pending state. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org For additional commands, e-mail: issues-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
[jira] [Updated] (ARTEMIS-4362) Produce a logger when consumers are holding too many messages not allowing depaging
[ https://issues.apache.org/jira/browse/ARTEMIS-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic updated ARTEMIS-4362: - Summary: Produce a logger when consumers are holding too many messages not allowing depaging (was: Produce a logger when consumers are holding too many messages not allowing deposing) > Produce a logger when consumers are holding too many messages not allowing > depaging > --- > > Key: ARTEMIS-4362 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4362 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.30.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > We should add a log.warn whenever the system can't read more messages because > consumers are holding too many messages in pending state. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org For additional commands, e-mail: issues-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
[jira] [Reopened] (ARTEMIS-4362) Produce a logger when consumers are holding too many messages not allowing deposing
[ https://issues.apache.org/jira/browse/ARTEMIS-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic reopened ARTEMIS-4362: -- > Produce a logger when consumers are holding too many messages not allowing > deposing > --- > > Key: ARTEMIS-4362 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4362 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.30.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > We should add a log.warn whenever the system can't read more messages because > consumers are holding too many messages in pending state. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org For additional commands, e-mail: issues-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
[jira] [Resolved] (ARTEMIS-4803) Lost the lock according to the monitor, notifying listeners
[
https://issues.apache.org/jira/browse/ARTEMIS-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-4803.
-
Resolution: Information Provided
> Lost the lock according to the monitor, notifying listeners
> ---
>
> Key: ARTEMIS-4803
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4803
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.33.0
>Reporter: Ayla
>Assignee: Justin Bertram
>Priority: Major
> Attachments: Capture.JPG, broker.xml
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> We just installed 2.33.0 on a Windows server using with shared file storage.
> We have the situation that we in get endless loop with the following entry in
> the artemis log file:
> {noformat}
> WARN [org.apache.activemq.artemis.core.server.impl.FileLockNodeManager] Lost
> the lock according to the monitor, notifying listeners{noformat}
> We noticed that if we changed the config file to local disk the problem does
> not happen.
> We are using {*}Windows based clustered file shared storage and it is SMB not
> NFS{*}.
> SMB configuration properties are as below:
> {noformat}
> PS C:\Windows\system32> Get-SmbClientConfiguration
> ConnectionCountPerRssNetworkInterface : 4
> DirectoryCacheEntriesMax : 16
> DirectoryCacheEntrySizeMax : 65536
> DirectoryCacheLifetime : 10
> DormantFileLimit : 1023
> EnableBandwidthThrottling : True
> EnableByteRangeLockingOnReadOnlyFiles : True
> EnableInsecureGuestLogons : False
> EnableLargeMtu : True
> EnableLoadBalanceScaleOut : True
> EnableMultiChannel : True
> EnableSecuritySignature : True
> ExtendedSessionTimeout : 1000
> FileInfoCacheEntriesMax : 64
> FileInfoCacheLifetime : 10
> FileNotFoundCacheEntriesMax : 128
> FileNotFoundCacheLifetime : 5
> KeepConn : 600
> MaxCmds : 50
> MaximumConnectionCountPerServer : 32
> OplocksDisabled : False
> RequireSecuritySignature : True
> SessionTimeout : 60
> UseOpportunisticLocking : True
> WindowSizeThreshold : 1{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Commented] (ARTEMIS-4803) Lost the lock according to the monitor, notifying listeners
[
https://issues.apache.org/jira/browse/ARTEMIS-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17855122#comment-17855122
]
Justin Bertram commented on ARTEMIS-4803:
-
As far as I can tell this is an environmental issue and not a bug in the
broker. The exception clearly states:
{noformat}
...can not open file y:\AMQ\data\journal\server.lock... The system cannot find
the path specified{noformat}
> Lost the lock according to the monitor, notifying listeners
> ---
>
> Key: ARTEMIS-4803
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4803
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.33.0
>Reporter: Ayla
>Assignee: Justin Bertram
>Priority: Major
> Attachments: Capture.JPG, broker.xml
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> We just installed 2.33.0 on a Windows server using with shared file storage.
> We have the situation that we in get endless loop with the following entry in
> the artemis log file:
> {noformat}
> WARN [org.apache.activemq.artemis.core.server.impl.FileLockNodeManager] Lost
> the lock according to the monitor, notifying listeners{noformat}
> We noticed that if we changed the config file to local disk the problem does
> not happen.
> We are using {*}Windows based clustered file shared storage and it is SMB not
> NFS{*}.
> SMB configuration properties are as below:
> {noformat}
> PS C:\Windows\system32> Get-SmbClientConfiguration
> ConnectionCountPerRssNetworkInterface : 4
> DirectoryCacheEntriesMax : 16
> DirectoryCacheEntrySizeMax : 65536
> DirectoryCacheLifetime : 10
> DormantFileLimit : 1023
> EnableBandwidthThrottling : True
> EnableByteRangeLockingOnReadOnlyFiles : True
> EnableInsecureGuestLogons : False
> EnableLargeMtu : True
> EnableLoadBalanceScaleOut : True
> EnableMultiChannel : True
> EnableSecuritySignature : True
> ExtendedSessionTimeout : 1000
> FileInfoCacheEntriesMax : 64
> FileInfoCacheLifetime : 10
> FileNotFoundCacheEntriesMax : 128
> FileNotFoundCacheLifetime : 5
> KeepConn : 600
> MaxCmds : 50
> MaximumConnectionCountPerServer : 32
> OplocksDisabled : False
> RequireSecuritySignature : True
> SessionTimeout : 60
> UseOpportunisticLocking : True
> WindowSizeThreshold : 1{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] (ARTEMIS-4803) Lost the lock according to the monitor, notifying listeners
[ https://issues.apache.org/jira/browse/ARTEMIS-4803 ]
Justin Bertram deleted comment on ARTEMIS-4803:
-
was (Author: JIRAUSER305625):
Attaching Master broker.xml file[^broker.xml]
> Lost the lock according to the monitor, notifying listeners
> ---
>
> Key: ARTEMIS-4803
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4803
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.33.0
>Reporter: Ayla
>Assignee: Justin Bertram
>Priority: Major
> Attachments: Capture.JPG, broker.xml
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> We just installed 2.33.0 on a Windows server using with shared file storage.
> We have the situation that we in get endless loop with the following entry in
> the artemis log file:
> {noformat}
> WARN [org.apache.activemq.artemis.core.server.impl.FileLockNodeManager] Lost
> the lock according to the monitor, notifying listeners{noformat}
> We noticed that if we changed the config file to local disk the problem does
> not happen.
> We are using {*}Windows based clustered file shared storage and it is SMB not
> NFS{*}.
> SMB configuration properties are as below:
> {noformat}
> PS C:\Windows\system32> Get-SmbClientConfiguration
> ConnectionCountPerRssNetworkInterface : 4
> DirectoryCacheEntriesMax : 16
> DirectoryCacheEntrySizeMax : 65536
> DirectoryCacheLifetime : 10
> DormantFileLimit : 1023
> EnableBandwidthThrottling : True
> EnableByteRangeLockingOnReadOnlyFiles : True
> EnableInsecureGuestLogons : False
> EnableLargeMtu : True
> EnableLoadBalanceScaleOut : True
> EnableMultiChannel : True
> EnableSecuritySignature : True
> ExtendedSessionTimeout : 1000
> FileInfoCacheEntriesMax : 64
> FileInfoCacheLifetime : 10
> FileNotFoundCacheEntriesMax : 128
> FileNotFoundCacheLifetime : 5
> KeepConn : 600
> MaxCmds : 50
> MaximumConnectionCountPerServer : 32
> OplocksDisabled : False
> RequireSecuritySignature : True
> SessionTimeout : 60
> UseOpportunisticLocking : True
> WindowSizeThreshold : 1{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Comment Edited] (ARTEMIS-4803) Lost the lock according to the monitor, notifying listeners
[
https://issues.apache.org/jira/browse/ARTEMIS-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17854770#comment-17854770
]
Justin Bertram edited comment on ARTEMIS-4803 at 6/14/24 6:48 PM:
--
We enabled NFS on Windows server 2019 and created a share, used below mount
commands:
{noformat}
mount -o fileaccess=777 -o mtype=soft,noac -o timeout=50 -o retry=1
:/NFSTestFolder y:{noformat}
Attached you can find the [^broker.xml] for the master node, however the
Windows service keeps stopping with below errors:
{noformat}
2024-06-13 15:44:39,932 WARN [org.apache.activemq.artemis.core.server]
AMQ222141: Node Manager can not open file y:\AMQ\data\journal\server.lock
java.io.IOException: The system cannot find the path specified
at java.io.WinNTFileSystem.createFileExclusively0(Native Method) ~[?:?]
at java.io.WinNTFileSystem.createFileExclusively(WinNTFileSystem.java:645)
~[?:?]
at java.io.File.createNewFile(File.java:1043) ~[?:?]
at
org.apache.activemq.artemis.core.server.impl.FileBasedNodeManager.setUpServerLockFile(FileBasedNodeManager.java:145)
[artemis-server-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.setUpServerLockFile(FileLockNodeManager.java:111)
[artemis-server-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.start(FileLockNodeManager.java:102)
[artemis-server-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:696)
[artemis-server-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:610)
[artemis-server-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:66)
[artemis-cli-2.31.2.jar:2.31.2]
at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:130)
[artemis-cli-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:219)
[artemis-cli-2.31.2.jar:2.31.2]
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:165)
[artemis-cli-2.31.2.jar:2.31.2]
at
jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
~[?:?]
at java.lang.reflect.Method.invoke(Method.java:578) ~[?:?]
at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:157)
[artemis-boot.jar:2.31.2]
at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:64)
[artemis-boot.jar:2.31.2]
2024-06-13 15:44:39,948 ERROR [org.apache.activemq.artemis.core.server]
AMQ224097: Failed to start server
java.io.IOException: The system cannot find the path specified
at java.io.WinNTFileSystem.createFileExclusively0(Native Method) ~[?:?]
at java.io.WinNTFileSystem.createFileExclusively(WinNTFileSystem.java:645)
~[?:?]
at java.io.File.createNewFile(File.java:1043) ~[?:?]
at
org.apache.activemq.artemis.core.server.impl.FileBasedNodeManager.setUpServerLockFile(FileBasedNodeManager.java:145)
~[artemis-server-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.setUpServerLockFile(FileLockNodeManager.java:111)
~[artemis-server-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.start(FileLockNodeManager.java:102)
~[artemis-server-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:696)
~[artemis-server-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:610)
[artemis-server-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:66)
[artemis-cli-2.31.2.jar:2.31.2]
at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:130)
[artemis-cli-2.31.2.jar:2.31.2]
at
org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:219)
[artemis-cli-2.31.2.jar:2.31.2]
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:165)
[artemis-cli-2.31.2.jar:2.31.2]
at
jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
~[?:?]
at java.lang.reflect.Method.invoke(Method.java:578) ~[?:?]
at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:157)
[artemis-boot.jar:2.31.2]
at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:64)
[artemis-boot.jar:2.31.2]
2024-06-13 15:44:39,953 INFO [org.apache.activemq.artemis.core.server]
AMQ221002: Apache ActiveMQ Artemis Message Broker version 2.31.2 [null]
stopped, uptime 0.539 seconds{noformat}
was (Author: JIRAUSER305625):
We enabled NFS on Windows server 2019 and created a share, used below mount
commands:
mount -o fileaccess=777 -o mtype=soft,noac -o timeout=50 -o retry=1
[jira] [Updated] (ARTEMIS-4818) Improve support for multiple broker plugins from broker properties
[
https://issues.apache.org/jira/browse/ARTEMIS-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Domenico Francesco Bruscino updated ARTEMIS-4818:
-
Description: The broker support loading multiple broker plugins from the
broker properties only if they expose a getter/setter for the property name.
Could you support loading multiple broker plugins without a getter/setter for
the property name? (was: The broker support loading multiple broker plugins
from the broker properties only if they have a different class and expose a
getter/setter for the property name. Could you improve the broker property
syntax to define the class instance name in the key optionally? In this way,
users could add multiple instances of the same broker plugin even if it has no
getter/setter for the property name, i.e.
{code}
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-0.class".init=LOG_ALL_EVENTS=false
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-1.class".init=LOG_ALL_EVENTS=true
{code}
)
> Improve support for multiple broker plugins from broker properties
> --
>
> Key: ARTEMIS-4818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4818
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Domenico Francesco Bruscino
>Assignee: Domenico Francesco Bruscino
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The broker support loading multiple broker plugins from the broker properties
> only if they expose a getter/setter for the property name. Could you support
> loading multiple broker plugins without a getter/setter for the property name?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Work logged] (ARTEMIS-4818) Improve support for multiple broker plugins from broker properties
[
https://issues.apache.org/jira/browse/ARTEMIS-4818?focusedWorklogId=923462=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-923462
]
ASF GitHub Bot logged work on ARTEMIS-4818:
---
Author: ASF GitHub Bot
Created on: 14/Jun/24 08:32
Start Date: 14/Jun/24 08:32
Worklog Time Spent: 10m
Work Description: brusdev opened a new pull request, #4979:
URL: https://github.com/apache/activemq-artemis/pull/4979
…properties
Issue Time Tracking
---
Worklog Id: (was: 923462)
Remaining Estimate: 0h
Time Spent: 10m
> Improve support for multiple broker plugins from broker properties
> --
>
> Key: ARTEMIS-4818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4818
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Domenico Francesco Bruscino
>Assignee: Domenico Francesco Bruscino
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The broker support loading multiple broker plugins from the broker properties
> only if they have a different class and expose a getter/setter for the
> property name. Could you improve the broker property syntax to define the
> class instance name in the key optionally? In this way, users could add
> multiple instances of the same broker plugin even if it has no getter/setter
> for the property name, i.e.
> {code}
> brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-0.class".init=LOG_ALL_EVENTS=false
> brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-1.class".init=LOG_ALL_EVENTS=true
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Updated] (ARTEMIS-4818) Improve support for multiple broker plugins from broker properties
[
https://issues.apache.org/jira/browse/ARTEMIS-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Domenico Francesco Bruscino updated ARTEMIS-4818:
-
Description:
The broker support loading multiple broker plugins from the broker properties
only if they have a different class and expose a getter/setter for the property
name. Could you improve the broker property syntax to define the class instance
name in the key optionally? In this way, users could add multiple instances of
the same broker plugin even if it has no getter/setter for the property name,
i.e.
{code}
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-0.class".init=LOG_ALL_EVENTS=false
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-1.class".init=LOG_ALL_EVENTS=true
{code}
was:
The broker support loading multiple broker plugins from the broker properties
only if they have a different class and expose a getter/setter for the property
name. Could you improve the broker property syntax to define the class instance
name in the key optionally? In this way, users could add multiple instances of
the same broker plugin even if it has no getter/setter for the property name,
i.e.
{code}
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-0.class".init",
"LOG_ALL_EVENTS=false
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-1.class".init",
"LOG_ALL_EVENTS=true
{code}
> Improve support for multiple broker plugins from broker properties
> --
>
> Key: ARTEMIS-4818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4818
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Domenico Francesco Bruscino
>Assignee: Domenico Francesco Bruscino
>Priority: Major
>
> The broker support loading multiple broker plugins from the broker properties
> only if they have a different class and expose a getter/setter for the
> property name. Could you improve the broker property syntax to define the
> class instance name in the key optionally? In this way, users could add
> multiple instances of the same broker plugin even if it has no getter/setter
> for the property name, i.e.
> {code}
> brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-0.class".init=LOG_ALL_EVENTS=false
> brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-1.class".init=LOG_ALL_EVENTS=true
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Updated] (ARTEMIS-4818) Improve support for multiple broker plugins from broker properties
[
https://issues.apache.org/jira/browse/ARTEMIS-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Domenico Francesco Bruscino updated ARTEMIS-4818:
-
Description:
The broker support loading multiple broker plugins from the broker properties
only if they have a different class and expose a getter/setter for the property
name. Could you improve the broker property syntax to define the class instance
name in the key optionally? In this way, users could add multiple instances of
the same broker plugin even if it has no getter/setter for the property name,
i.e.
{code}
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-0.class".init",
"LOG_ALL_EVENTS=false
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-1.class".init",
"LOG_ALL_EVENTS=true
{code}
was:
The broker support loading multiple broker plugins from the broker properties
only if they have a different class and expose a getter/setter for the property
name. Could you improve the broker property syntax to define the class instance
name in the key optionally? In this way, users could add multiple instances of
the same broker plugin even if it has no getter/setter for the property name,
i.e.
{code}
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance.class".init",
"LOG_ALL_EVENTS=false
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance.class".init",
"LOG_ALL_EVENTS=false
{code}
> Improve support for multiple broker plugins from broker properties
> --
>
> Key: ARTEMIS-4818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4818
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Domenico Francesco Bruscino
>Assignee: Domenico Francesco Bruscino
>Priority: Major
>
> The broker support loading multiple broker plugins from the broker properties
> only if they have a different class and expose a getter/setter for the
> property name. Could you improve the broker property syntax to define the
> class instance name in the key optionally? In this way, users could add
> multiple instances of the same broker plugin even if it has no getter/setter
> for the property name, i.e.
> {code}
> brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-0.class".init",
> "LOG_ALL_EVENTS=false
> brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-1.class".init",
> "LOG_ALL_EVENTS=true
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Updated] (ARTEMIS-4818) Improve support for multiple broker plugins from broker properties
[
https://issues.apache.org/jira/browse/ARTEMIS-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Domenico Francesco Bruscino updated ARTEMIS-4818:
-
Summary: Improve support for multiple broker plugins from broker properties
(was: Support multiple broker plugins from broker properties)
> Improve support for multiple broker plugins from broker properties
> --
>
> Key: ARTEMIS-4818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4818
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Domenico Francesco Bruscino
>Assignee: Domenico Francesco Bruscino
>Priority: Major
>
> The broker support loading multiple broker plugins from the broker properties
> only if they have a different class and expose a getter/setter for the
> property name. Could you improve the broker property syntax to define the
> class instance name in the key optionally? In this way, users could add
> multiple instances of the same broker plugin even if it has no getter/setter
> for the property name, i.e.
> {code}
> brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance.class".init",
> "LOG_ALL_EVENTS=false
> brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance.class".init",
> "LOG_ALL_EVENTS=false
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Created] (ARTEMIS-4818) Support multiple broker plugins from broker properties
Domenico Francesco Bruscino created ARTEMIS-4818:
Summary: Support multiple broker plugins from broker properties
Key: ARTEMIS-4818
URL: https://issues.apache.org/jira/browse/ARTEMIS-4818
Project: ActiveMQ Artemis
Issue Type: Improvement
Reporter: Domenico Francesco Bruscino
Assignee: Domenico Francesco Bruscino
The broker support loading multiple broker plugins from the broker properties
only if they have a different class and expose a getter/setter for the property
name. Could you improve the broker property syntax to define the class instance
name in the key optionally? In this way, users could add multiple instances of
the same broker plugin even if it has no getter/setter for the property name,
i.e.
{code}
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance.class".init",
"LOG_ALL_EVENTS=false
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance.class".init",
"LOG_ALL_EVENTS=false
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
