[jira] [Created] (ARTEMIS-4950) MBeanGuard throws an NPE
Andy Taylor created ARTEMIS-4950: Summary: MBeanGuard throws an NPE Key: ARTEMIS-4950 URL: https://issues.apache.org/jira/browse/ARTEMIS-4950 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor HawtIO calls invoke with a null operationName as a coarse grained way of authenticating against all the operations on an mbean. This throws a null pointer on operationName later in this call which is swallowed by HawtIO. Since fine grained checks are carried out against every operation this was never an issue however the new console based on HawtIO 4 passes this exception back to the console which breaks it. Since it is just an optimisation it is fine to always return true. Note that the alternative ArtemisRbacInvocationHandler does allow the ability to restrict a whole mbean -- 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-4780) Artemis web console does not ever set 'artemisJmxDomain' in localStorage
[
https://issues.apache.org/jira/browse/ARTEMIS-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852437#comment-17852437
]
Andy Taylor commented on ARTEMIS-4780:
--
Having discussed this on the PR th fix is probably not the correct approach.
Can you not just overwrite the patch the globals.ts and build tour own version?
> Artemis web console does not ever set 'artemisJmxDomain' in localStorage
>
>
> Key: ARTEMIS-4780
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4780
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Josh Byster
>Assignee: Andy Taylor
>Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We relocate our artemis packages as part of our shading process.
> I did set up:
>
> {code:java}
> aActiveMQServer.getConfiguration().setJMXDomain("com.abc.shaded.org.apache.activemq.artemis");
> {code}
> However the web console does not show up. I noticed in the code it's because
> we try to read in localStorage['artemisJmxDomain'] but never actually set it
> as far as I can tell. Thus we always default to org.apache.activemq.artemis.
> Everything works properly when setting localStorage['artemisJmxDomain'] =
> "com.abc.shaded.org.apache.activemq.artemis"
--
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-4780) Artemis web console does not ever set 'artemisJmxDomain' in localStorage
[
https://issues.apache.org/jira/browse/ARTEMIS-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851579#comment-17851579
]
Andy Taylor commented on ARTEMIS-4780:
--
I have changed the new console to auto detect the domain by searching for
*{*}:broker={*}*. PR at
[https://github.com/apache/activemq-artemis-console/pull/18] . I will hopefully
release a 1.0.0 (that can be run standalone, very soon.
Regarding the current console, I don't see any point in changing it, It has
been like that for years but if you want to do something similar you could make
the changes and send a PR.
> Artemis web console does not ever set 'artemisJmxDomain' in localStorage
>
>
> Key: ARTEMIS-4780
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4780
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Josh Byster
>Assignee: Andy Taylor
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We relocate our artemis packages as part of our shading process.
> I did set up:
>
> {code:java}
> aActiveMQServer.getConfiguration().setJMXDomain("com.abc.shaded.org.apache.activemq.artemis");
> {code}
> However the web console does not show up. I noticed in the code it's because
> we try to read in localStorage['artemisJmxDomain'] but never actually set it
> as far as I can tell. Thus we always default to org.apache.activemq.artemis.
> Everything works properly when setting localStorage['artemisJmxDomain'] =
> "com.abc.shaded.org.apache.activemq.artemis"
--
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] [Assigned] (ARTEMIS-4780) Artemis web console does not ever set 'artemisJmxDomain' in localStorage
[
https://issues.apache.org/jira/browse/ARTEMIS-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Taylor reassigned ARTEMIS-4780:
Assignee: Andy Taylor
> Artemis web console does not ever set 'artemisJmxDomain' in localStorage
>
>
> Key: ARTEMIS-4780
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4780
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Josh Byster
>Assignee: Andy Taylor
>Priority: Minor
>
> We relocate our artemis packages as part of our shading process.
> I did set up:
>
> {code:java}
> aActiveMQServer.getConfiguration().setJMXDomain("com.abc.shaded.org.apache.activemq.artemis");
> {code}
> However the web console does not show up. I noticed in the code it's because
> we try to read in localStorage['artemisJmxDomain'] but never actually set it
> as far as I can tell. Thus we always default to org.apache.activemq.artemis.
> Everything works properly when setting localStorage['artemisJmxDomain'] =
> "com.abc.shaded.org.apache.activemq.artemis"
--
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] [Closed] (ARTEMIS-1827) Improve HA tests to use remote brokers and not invm
[ https://issues.apache.org/jira/browse/ARTEMIS-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor closed ARTEMIS-1827. Resolution: Invalid > Improve HA tests to use remote brokers and not invm > --- > > Key: ARTEMIS-1827 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1827 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > This could possibly be implemented using Arquillian which allows resource > life cycle control -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4680) Upgrade the console to use HawtIO 4
[ https://issues.apache.org/jira/browse/ARTEMIS-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825980#comment-17825980 ] Andy Taylor commented on ARTEMIS-4680: -- [~erwindon] I have made a few changes which I have force pushed to my branch so you might wasnt to refresh. I'll fix that type > Upgrade the console to use HawtIO 4 > --- > > Key: ARTEMIS-4680 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4680 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > The current console is based upon HawtIO 1 which in turn is built on > Bootstrap. Bootstrap is old and no longer actively being maintained. > > This improvement is to migrate the current console to use HawtIO 4 which i > based on Typescript, react and Patternfly. > > A WIP can be found > [here|https://github.com/andytaylor/activemq-artemis/tree/artemis-console-ng] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4680) Upgrade the console to use HawtIO 4
[ https://issues.apache.org/jira/browse/ARTEMIS-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-4680: - Description: The current console is based upon HawtIO 1 which in turn is built on Bootstrap. Bootstrap is old and no longer actively being maintained. This improvement is to migrate the current console to use HawtIO 4 which i based on Typescript, react and Patternfly. A WIP can be found [here|https://github.com/andytaylor/activemq-artemis/tree/artemis-console-ng] > Upgrade the console to use HawtIO 4 > --- > > Key: ARTEMIS-4680 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4680 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > The current console is based upon HawtIO 1 which in turn is built on > Bootstrap. Bootstrap is old and no longer actively being maintained. > > This improvement is to migrate the current console to use HawtIO 4 which i > based on Typescript, react and Patternfly. > > A WIP can be found > [here|https://github.com/andytaylor/activemq-artemis/tree/artemis-console-ng] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ARTEMIS-4680) Upgrade the console to use HawtIO 4
[ https://issues.apache.org/jira/browse/ARTEMIS-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor reassigned ARTEMIS-4680: Assignee: Andy Taylor > Upgrade the console to use HawtIO 4 > --- > > Key: ARTEMIS-4680 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4680 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4680) Upgrade the console to use HawtIO 4
Andy Taylor created ARTEMIS-4680: Summary: Upgrade the console to use HawtIO 4 Key: ARTEMIS-4680 URL: https://issues.apache.org/jira/browse/ARTEMIS-4680 Project: ActiveMQ Artemis Issue Type: Improvement Components: Web Console Reporter: Andy Taylor -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4643) Web console authentication with Keycloak 31 doesn't work
[ https://issues.apache.org/jira/browse/ARTEMIS-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818145#comment-17818145 ] Andy Taylor commented on ARTEMIS-4643: -- I have actually been working on this in th ebackground for several months now, its not complete yest there are some glitches and I havent applied full branding. Feel free to take a look, I will rebase on Monday when I get time. Hopefully i can send a PR in the next few weeks. [https://github.com/andytaylor/activemq-artemis/tree/artemis-console-ng] > Web console authentication with Keycloak 31 doesn't work > > > Key: ARTEMIS-4643 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4643 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Web Console >Affects Versions: 2.32.0 >Reporter: Nicolas De Amicis >Priority: Major > > Authentication with Keycloak for the ActiveMQ Artemis web console doesn't > work with recent Keycloak versions. Tested with Keycloak 22 and 23.0.6 > (latest). > I have tested Hawtio 2.17.7 (i.e. the version of the web console component of > ActiveMQ Artemis) and it doesn't work. I have also tested Hawtio 3.0.1 > (latest version available) and it works with Keycloak 31. > I think Hawtio needs to be upgraded to 3.0.1 in ActiveMQ Artemis. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4557) expose producer window size in clusterconnection JMX
Andy Taylor created ARTEMIS-4557: Summary: expose producer window size in clusterconnection JMX Key: ARTEMIS-4557 URL: https://issues.apache.org/jira/browse/ARTEMIS-4557 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4398) Support configuring Database with Broker Properties
Andy Taylor created ARTEMIS-4398: Summary: Support configuring Database with Broker Properties Key: ARTEMIS-4398 URL: https://issues.apache.org/jira/browse/ARTEMIS-4398 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ARTEMIS-4213) Add a reference for Broker properties
[ https://issues.apache.org/jira/browse/ARTEMIS-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor reassigned ARTEMIS-4213: Assignee: Andy Taylor > Add a reference for Broker properties > - > > Key: ARTEMIS-4213 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4213 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > update the docs to have some reference documentation for Broker Properties. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4213) Add a reference for Broker properties
[ https://issues.apache.org/jira/browse/ARTEMIS-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703581#comment-17703581 ] Andy Taylor commented on ARTEMIS-4213: -- I'll also improve the schema docs while I am on > Add a reference for Broker properties > - > > Key: ARTEMIS-4213 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4213 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > update the docs to have some reference documentation for Broker Properties. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4213) Add a reference for Broker properties
Andy Taylor created ARTEMIS-4213: Summary: Add a reference for Broker properties Key: ARTEMIS-4213 URL: https://issues.apache.org/jira/browse/ARTEMIS-4213 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor update the docs to have some reference documentation for Broker Properties. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3875) Improve consumer/producer metrics
[ https://issues.apache.org/jira/browse/ARTEMIS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3875: - Description: adding the following metrics: for the Consumer and the methods listAllConsumersAsJSON on server and queue mbeans: messagesInTransit - number of Messages out for delivery which have not yet been acknowledged messagesInTransitSize - The total size of Messages out for delivery which have not yet been acknowledged messagesDelivered - Number of messages delivered messagesDeliveredSize' - total size of messages delivered messagesAcknowledged - total number of Messages Acknowledged messagesAcknowledgedAwaitingCommit - Total number of messages in a transaction that are acknowledged but awaiting a commit lastDeliveredTime - The time in milliseconds of the last message delivered lastAcknowledgedTime - The time in milliseconds of the last message acknowledged for the Producer add to the listProducers and listproducersasJSON mbean methods msgSent - The number of messages sent by a producer msgSizeSent - The total size of messages sent by a producer lastUUIDSent - The UUID of the last message sent The producer views are currently quite broken, different protocols show different producer info and number of producers, this is because in core we add a single producer per session which means you get 2 for every core session. We also create a producer instance for every address sent to so anonymous producers dont show as a single producer, this was also a DOS issue so we limit the no of producers we track to 100. Im changing this to work as expected so every JMS producer created will show as a single producer, even anonymous producers to correctly show what producers exist at a client. The downside to changing this so much is that producer metrics will no longer be available for legacy clients. Other improvements * Consolidate the names used by the different methods to be more consistent and referenced by static variables. * use statics in all the tests * add tests for different message count scenarios was: adding the following metrics: for the Consumer and the methods listAllConsumersAsJSON on server and queue mbeans: messagesInTransit - number of Messages out for delivery which have not yet been acknowledged messagesInTransitSize - The total size of Messages out for delivery which have not yet been acknowledged messagesDelivered - Number of messages delivered messagesDeliveredSize' - total size of messages delivered messagesAcknowledged - total number of Messages Acknowledged messagesAcknowledgedAwaitingCommit - Total number of messages in a transaction that are acknowledged but awaiting a commit lastDeliveredTime - The time in milliseconds of the last message delivered lastAcknowledgedTime - The time in milliseconds of the last message acknowledged for the Producer add to the listProducers and listproducersasJSON mbean methods msgSent - The number of messages sent by a producer msgSizeSent - The total size of messages sent by a producer lastUUIDSent - The UUID of the last message sent The producer views are currently quite broken, different protocols show different producer info and number of producers, this is because in core we add a single producer per session which means you get 2 for ecey core session. Im changing this to be a producer for every address sent to. For normal producers this will now show s single producer for every protocol, for anon producers this will show a producer for every address sent to. For DOS protection this will max on 100 producers and they will also be torn down when the session is closed. Ive also move the use of targetAddressInfos into the server producer for consistencey. Other improvements * Consolidate the names used by the different methods to be more consistent and referenced by static variables. * use statics in all the tests * add tests for different message count scenarios > Improve consumer/producer metrics > - > > Key: ARTEMIS-3875 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3875 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 7h > Remaining Estimate: 0h > > adding the following metrics: > > for the Consumer and the methods listAllConsumersAsJSON on server and queue > mbeans: > messagesInTransit - number of Messages out for delivery which have not yet > been acknowledged > messagesInTransitSize - The total size of Messages out for delivery which > have not yet been acknowledged > messagesDelivered - Number of messages delivered > messagesDeliveredSize' - total size of messages delivered > messagesAcknowledged - total number of Messages Acknowledged >
[jira] [Updated] (ARTEMIS-3875) Improve consumer/producer metrics
[ https://issues.apache.org/jira/browse/ARTEMIS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3875: - Description: adding the following metrics: for the Consumer and the methods listAllConsumersAsJSON on server and queue mbeans: messagesInTransit - number of Messages out for delivery which have not yet been acknowledged messagesInTransitSize - The total size of Messages out for delivery which have not yet been acknowledged messagesDelivered - Number of messages delivered messagesDeliveredSize' - total size of messages delivered messagesAcknowledged - total number of Messages Acknowledged messagesAcknowledgedAwaitingCommit - Total number of messages in a transaction that are acknowledged but awaiting a commit lastDeliveredTime - The time in milliseconds of the last message delivered lastAcknowledgedTime - The time in milliseconds of the last message acknowledged for the Producer add to the listProducers and listproducersasJSON mbean methods msgSent - The number of messages sent by a producer msgSizeSent - The total size of messages sent by a producer lastUUIDSent - The UUID of the last message sent The producer views are currently quite broken, different protocols show different producer info and number of producers, this is because in core we add a single producer per session which means you get 2 for ecey core session. Im changing this to be a producer for every address sent to. For normal producers this will now show s single producer for every protocol, for anon producers this will show a producer for every address sent to. For DOS protection this will max on 100 producers and they will also be torn down when the session is closed. Ive also move the use of targetAddressInfos into the server producer for consistencey. Other improvements * Consolidate the names used by the different methods to be more consistent and referenced by static variables. * use statics in all the tests * add tests for different message count scenarios was: adding the following metrics: for the Consumer and the methods listAllConsumersAsJSON on server and queue mbeans: messagesInTransit - number of Messages out for delivery which have not yet been acknowledged messagesInTransitSize - The total size of Messages out for delivery which have not yet been acknowledged messagesDelivered - Number of messages delivered messagesDeliveredSize' - total size of messages delivered messagesAcknowledged - total number of Messages Acknowledged messagesAcknowledgedAwaitingCommit - Total number of messages in a transaction that are acknowledged but awaiting a commit lastDeliveredTime - The time in milliseconds of the last message delivered lastAcknowledgedTime - The time in milliseconds of the last message acknowledged for the Producer add to the listProducers and listproducersasJSON mbean methods msgSent - The number of messages sent by a producer msgSizeSent - The total size of messages sent by a producer lastUUIDSent - The UUID of the last message sent The producer views are currently quite broken, different protocols show different producer info and number of producers, this is because in core we add a single producer per session which means you get 2 for ecey core session. Im changing this to be a producer for every address sent to. For normal producers this will now show s single producer for every protocol, for anon producers this will show a producer for every address sent to. For DOS protection this will max on 100 producers and they will also be torn down when the session is closed. Other improvements * Consolidate the names used by the different methods to be more consistent and referenced by static variables. * use statics in all the tests * add tests for different message count scenarios > Improve consumer/producer metrics > - > > Key: ARTEMIS-3875 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3875 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 2h 50m > Remaining Estimate: 0h > > adding the following metrics: > > for the Consumer and the methods listAllConsumersAsJSON on server and queue > mbeans: > messagesInTransit - number of Messages out for delivery which have not yet > been acknowledged > messagesInTransitSize - The total size of Messages out for delivery which > have not yet been acknowledged > messagesDelivered - Number of messages delivered > messagesDeliveredSize' - total size of messages delivered > messagesAcknowledged - total number of Messages Acknowledged > messagesAcknowledgedAwaitingCommit - Total number of messages in a > transaction that are acknowledged but awaiting a commit > lastDeliveredTime - The time in
[jira] [Updated] (ARTEMIS-3875) Improve consumer/producer metrics
[ https://issues.apache.org/jira/browse/ARTEMIS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3875: - Description: adding the following metrics: for the Consumer and the methods listAllConsumersAsJSON on server and queue mbeans: messagesInTransit - number of Messages out for delivery which have not yet been acknowledged messagesInTransitSize - The total size of Messages out for delivery which have not yet been acknowledged messagesDelivered - Number of messages delivered messagesDeliveredSize' - total size of messages delivered messagesAcknowledged - total number of Messages Acknowledged messagesAcknowledgedAwaitingCommit - Total number of messages in a transaction that are acknowledged but awaiting a commit lastDeliveredTime - The time in milliseconds of the last message delivered lastAcknowledgedTime - The time in milliseconds of the last message acknowledged for the Producer add to the listProducers and listproducersasJSON mbean methods msgSent - The number of messages sent by a producer msgSizeSent - The total size of messages sent by a producer lastUUIDSent - The UUID of the last message sent The producer views are currently quite broken, different protocols show different producer info and number of producers, this is because in core we add a single producer per session which means you get 2 for ecey core session. Im changing this to be a producer for every address sent to. For normal producers this will now show s single producer for every protocol, for anon producers this will show a producer for every address sent to. For DOS protection this will max on 100 producers and they will also be torn down when the session is closed. Other improvements * Consolidate the names used by the different methods to be more consistent and referenced by static variables. * use statics in all the tests * add tests for different message count scenarios was: adding the following metrics: for the Consumer and the methods listAllConsumersAsJSON on server and queue mbeans: messagesInTransit - number of Messages out for delivery which have not yet been acknowledged messagesInTransitSize - The total size of Messages out for delivery which have not yet been acknowledged messagesDelivered - Number of messages delivered messagesDeliveredSize' - total size of messages delivered messagesAcknowledged - total number of Messages Acknowledged messagesAcknowledgedAwaitingCommit - Total number of messages in a transaction that are acknowledged but awaiting a commit lastDeliveredTime - The time in milliseconds of the last message delivered lastAcknowledgedTime - The time in milliseconds of the last message acknowledged Producer msgSent - The number of messages sent by a producer msgSizeSent - The total size of messages sent by a producer lastUUIDSent - The UUID of the last message sent > Improve consumer/producer metrics > - > > Key: ARTEMIS-3875 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3875 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 2h 50m > Remaining Estimate: 0h > > adding the following metrics: > > for the Consumer and the methods listAllConsumersAsJSON on server and queue > mbeans: > messagesInTransit - number of Messages out for delivery which have not yet > been acknowledged > messagesInTransitSize - The total size of Messages out for delivery which > have not yet been acknowledged > messagesDelivered - Number of messages delivered > messagesDeliveredSize' - total size of messages delivered > messagesAcknowledged - total number of Messages Acknowledged > messagesAcknowledgedAwaitingCommit - Total number of messages in a > transaction that are acknowledged but awaiting a commit > lastDeliveredTime - The time in milliseconds of the last message delivered > lastAcknowledgedTime - The time in milliseconds of the last message > acknowledged > > for the Producer add to the listProducers and listproducersasJSON mbean > methods > msgSent - The number of messages sent by a producer > msgSizeSent - The total size of messages sent by a producer > lastUUIDSent - The UUID of the last message sent > > The producer views are currently quite broken, different protocols show > different producer info and number of producers, this is because in core we > add a single producer per session which means you get 2 for ecey core > session. Im changing this to be a producer for every address sent to. For > normal producers this will now show s single producer for every protocol, for > anon producers this will show a producer for every address sent to. For DOS > protection this will max on 100 producers and they will also be torn down > when the
[jira] [Updated] (ARTEMIS-3875) Improve consumer/producer metrics
[ https://issues.apache.org/jira/browse/ARTEMIS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3875: - Description: adding the following metrics: for the Consumer and the methods listAllConsumersAsJSON on server and queue mbeans: messagesInTransit - number of Messages out for delivery which have not yet been acknowledged messagesInTransitSize - The total size of Messages out for delivery which have not yet been acknowledged messagesDelivered - Number of messages delivered messagesDeliveredSize' - total size of messages delivered messagesAcknowledged - total number of Messages Acknowledged messagesAcknowledgedAwaitingCommit - Total number of messages in a transaction that are acknowledged but awaiting a commit lastDeliveredTime - The time in milliseconds of the last message delivered lastAcknowledgedTime - The time in milliseconds of the last message acknowledged Producer msgSent - The number of messages sent by a producer msgSizeSent - The total size of messages sent by a producer lastUUIDSent - The UUID of the last message sent was: adding the following metrics: Consumer messagesInTransit - number of Messages out for delivery which have not yet been acknowledged messagesInTransitSize - The total size of Messages out for delivery which have not yet been acknowledged messagesDelivered - Number of messages delivered messagesDeliveredSize' - total size of messages delivered messagesAcknowledged - total number of Messages Acknowledged messagesAcknowledgedAwaitingCommit - Total number of messages in a transaction that are acknowledged but awaiting a commit lastDeliveredTime - The time in milliseconds of the last message delivered lastAcknowledgedTime - The time in milliseconds of the last message acknowledged Producer msgSent - The number of messages sent by a producer msgSizeSent - The total size of messages sent by a producer lastUUIDSent - The UUID of the last message sent > Improve consumer/producer metrics > - > > Key: ARTEMIS-3875 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3875 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 2h 50m > Remaining Estimate: 0h > > adding the following metrics: > > for the Consumer and the methods listAllConsumersAsJSON on server and queue > mbeans: > messagesInTransit - number of Messages out for delivery which have not yet > been acknowledged > messagesInTransitSize - The total size of Messages out for delivery which > have not yet been acknowledged > messagesDelivered - Number of messages delivered > messagesDeliveredSize' - total size of messages delivered > messagesAcknowledged - total number of Messages Acknowledged > messagesAcknowledgedAwaitingCommit - Total number of messages in a > transaction that are acknowledged but awaiting a commit > lastDeliveredTime - The time in milliseconds of the last message delivered > lastAcknowledgedTime - The time in milliseconds of the last message > acknowledged > > Producer > msgSent - The number of messages sent by a producer > msgSizeSent - The total size of messages sent by a producer > lastUUIDSent - The UUID of the last message sent -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3875) Improve consumer/producer metrics
[
https://issues.apache.org/jira/browse/ARTEMIS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Taylor updated ARTEMIS-3875:
-
Description:
adding the following metrics:
Consumer
messagesInTransit - number of Messages out for delivery which have not yet been
acknowledged
messagesInTransitSize - The total size of Messages out for delivery which have
not yet been acknowledged
messagesDelivered - Number of messages delivered
messagesDeliveredSize' - total size of messages delivered
messagesAcknowledged - total number of Messages Acknowledged
messagesAcknowledgedAwaitingCommit - Total number of messages in a transaction
that are acknowledged but awaiting a commit
lastDeliveredTime - The time in milliseconds of the last message delivered
lastAcknowledgedTime - The time in milliseconds of the last message acknowledged
Producer
msgSent - The number of messages sent by a producer
msgSizeSent - The total size of messages sent by a producer
lastUUIDSent - The UUID of the last message sent
was:
adding the following metrics:
_Consumer_
messagesInTransit - number of Messages out for delivery which have not yet been
acknowledges
messagesInTransitSize - The total size of Messages out for delivery which have
not yet been acknowledges
messagesDelivered - Number of messages delivered
\{id: 'messagesDeliveredSize', name: 'Messages Delivered Size'},
\{id: 'messagesAcknowledged', name: 'Messages Acknowledged'},
\{id: 'messagesAcknowledgedAwaitingCommit', name: 'Messages
Acknowledged awaiting Commit'},
\{id: 'lastDeliveredTime', name: 'Last Delivered Time'},
{id: 'lastAcknowledgedTime',
_Producer_
_Total Msgs Sent - number of messages sent by the producer_
_Total Size Sent - combined size of messages sent by the producer_
> Improve consumer/producer metrics
> -
>
> Key: ARTEMIS-3875
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3875
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Andy Taylor
>Assignee: Andy Taylor
>Priority: Major
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> adding the following metrics:
>
> Consumer
> messagesInTransit - number of Messages out for delivery which have not yet
> been acknowledged
> messagesInTransitSize - The total size of Messages out for delivery which
> have not yet been acknowledged
> messagesDelivered - Number of messages delivered
> messagesDeliveredSize' - total size of messages delivered
> messagesAcknowledged - total number of Messages Acknowledged
> messagesAcknowledgedAwaitingCommit - Total number of messages in a
> transaction that are acknowledged but awaiting a commit
> lastDeliveredTime - The time in milliseconds of the last message delivered
> lastAcknowledgedTime - The time in milliseconds of the last message
> acknowledged
>
> Producer
> msgSent - The number of messages sent by a producer
> msgSizeSent - The total size of messages sent by a producer
> lastUUIDSent - The UUID of the last message sent
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3875) Improve consumer/producer metrics
[
https://issues.apache.org/jira/browse/ARTEMIS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Taylor updated ARTEMIS-3875:
-
Description:
adding the following metrics:
_Consumer_
messagesInTransit - number of Messages out for delivery which have not yet been
acknowledges
messagesInTransitSize - The total size of Messages out for delivery which have
not yet been acknowledges
messagesDelivered - Number of messages delivered
\{id: 'messagesDeliveredSize', name: 'Messages Delivered Size'},
\{id: 'messagesAcknowledged', name: 'Messages Acknowledged'},
\{id: 'messagesAcknowledgedAwaitingCommit', name: 'Messages
Acknowledged awaiting Commit'},
\{id: 'lastDeliveredTime', name: 'Last Delivered Time'},
{id: 'lastAcknowledgedTime',
_Producer_
_Total Msgs Sent - number of messages sent by the producer_
_Total Size Sent - combined size of messages sent by the producer_
was:
adding the following metrics:
_Consumer_
_Msgs Sent - current number of messages sent to consumer which are not yet
acknowledged._
_Size Sent - combined size of unacknowledged messages sent to consumer._
_Last Sent - approximate time elapsed since last message was sent by the server
to the consumer._
_Last Akcd - approximate time elapsed since last time any message sent to the
consumer was acknowledged by consumer._
_Total Sent - total number of messages sent to consumer since it was created._
_Total Acked - total number of messages sent to the consumer and acknowledged
by consumer since it was created._
_Producer_
_Total Msgs Sent - number of messages sent by the producer_
_Total Size Sent - combined size of messages sent by the producer_
> Improve consumer/producer metrics
> -
>
> Key: ARTEMIS-3875
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3875
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Andy Taylor
>Assignee: Andy Taylor
>Priority: Major
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> adding the following metrics:
>
> _Consumer_
> messagesInTransit - number of Messages out for delivery which have not yet
> been acknowledges
> messagesInTransitSize - The total size of Messages out for delivery which
> have not yet been acknowledges
> messagesDelivered - Number of messages delivered
> \{id: 'messagesDeliveredSize', name: 'Messages Delivered
> Size'},
> \{id: 'messagesAcknowledged', name: 'Messages Acknowledged'},
> \{id: 'messagesAcknowledgedAwaitingCommit', name: 'Messages
> Acknowledged awaiting Commit'},
> \{id: 'lastDeliveredTime', name: 'Last Delivered Time'},
> {id: 'lastAcknowledgedTime',
>
> _Producer_
> _Total Msgs Sent - number of messages sent by the producer_
> _Total Size Sent - combined size of messages sent by the producer_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3875) Improve consumer/producer metrics
[ https://issues.apache.org/jira/browse/ARTEMIS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3875: - Summary: Improve consumer/producer metrics (was: expose more consumer/producer metrics) > Improve consumer/producer metrics > - > > Key: ARTEMIS-3875 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3875 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 2h 50m > Remaining Estimate: 0h > > adding the following metrics: > > _Consumer_ > _Msgs Sent - current number of messages sent to consumer which are not yet > acknowledged._ > _Size Sent - combined size of unacknowledged messages sent to consumer._ > _Last Sent - approximate time elapsed since last message was sent by the > server to the consumer._ > _Last Akcd - approximate time elapsed since last time any message sent to the > consumer was acknowledged by consumer._ > _Total Sent - total number of messages sent to consumer since it was created._ > _Total Acked - total number of messages sent to the consumer and acknowledged > by consumer since it was created._ > > _Producer_ > _Total Msgs Sent - number of messages sent by the producer_ > _Total Size Sent - combined size of messages sent by the producer_ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3932) replace addAddressSettings with JSON param
Andy Taylor created ARTEMIS-3932: Summary: replace addAddressSettings with JSON param Key: ARTEMIS-3932 URL: https://issues.apache.org/jira/browse/ARTEMIS-3932 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor Similar to what we did with createQueue deprecate the addAddressSettings in ServerControl and add a json version -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-3917) missing/incorrect getters on Configuration.java
[ https://issues.apache.org/jira/browse/ARTEMIS-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor resolved ARTEMIS-3917. -- Fix Version/s: 2.25.0 Resolution: Fixed > missing/incorrect getters on Configuration.java > --- > > Key: ARTEMIS-3917 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3917 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.24.0 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: 2.25.0 > > Time Spent: 20m > Remaining Estimate: 0h > > no method exists for getNodeManagerLockDirectory and getNetworkCheckNIC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work stopped] (ARTEMIS-3917) missing/incorrect getters on Configuration.java
[ https://issues.apache.org/jira/browse/ARTEMIS-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-3917 stopped by Andy Taylor. > missing/incorrect getters on Configuration.java > --- > > Key: ARTEMIS-3917 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3917 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.24.0 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > no method exists for getNodeManagerLockDirectory and getNetworkCheckNIC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (ARTEMIS-3917) missing/incorrect getters on Configuration.java
[ https://issues.apache.org/jira/browse/ARTEMIS-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-3917 started by Andy Taylor. > missing/incorrect getters on Configuration.java > --- > > Key: ARTEMIS-3917 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3917 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.24.0 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > no method exists for getNodeManagerLockDirectory and getNetworkCheckNIC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3917) missing/incorrect getters on Configuration.java
[ https://issues.apache.org/jira/browse/ARTEMIS-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3917: - Issue Type: Bug (was: Improvement) > missing/incorrect getters on Configuration.java > --- > > Key: ARTEMIS-3917 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3917 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.24.0 >Reporter: Andy Taylor >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > no method exists for getNodeManagerLockDirectory and getNetworkCheckNIC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3917) missing/incorrect getters on Configuration.java
[ https://issues.apache.org/jira/browse/ARTEMIS-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3917: - Description: no method exists for getNodeManagerLockDirectory and getNetworkCheckNIC (was: no method exists for getNodeManagerLockDirectory and getNetworCheckNIC) > missing/incorrect getters on Configuration.java > --- > > Key: ARTEMIS-3917 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3917 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Priority: Major > > no method exists for getNodeManagerLockDirectory and getNetworkCheckNIC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3917) missing/incorrect getters on Configuration.java
[ https://issues.apache.org/jira/browse/ARTEMIS-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3917: - Affects Version/s: 2.24.0 > missing/incorrect getters on Configuration.java > --- > > Key: ARTEMIS-3917 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3917 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.24.0 >Reporter: Andy Taylor >Priority: Major > > no method exists for getNodeManagerLockDirectory and getNetworkCheckNIC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3917) missing/incorrect getters on Configuration.java
[ https://issues.apache.org/jira/browse/ARTEMIS-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3917: - Description: no method exists for getNodeManagerLockDirectory and getNetworCheckNIC (was: no method exists for isEnabledAsyncConnectionExecution, getNodeManagerLockDirectory and getNetworCheckNIC) > missing/incorrect getters on Configuration.java > --- > > Key: ARTEMIS-3917 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3917 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Priority: Major > > no method exists for getNodeManagerLockDirectory and getNetworCheckNIC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3917) missing/incorrect getters on Configuration.java
Andy Taylor created ARTEMIS-3917: Summary: missing/incorrect getters on Configuration.java Key: ARTEMIS-3917 URL: https://issues.apache.org/jira/browse/ARTEMIS-3917 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor no method exists for isEnabledAsyncConnectionExecution, getNodeManagerLockDirectory and getNetworCheckNIC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3875) expose more consumer/producer metrics
Title: Message Title Andy Taylor created an issue ActiveMQ Artemis / ARTEMIS-3875 expose more consumer/producer metrics Issue Type: Improvement Assignee: Andy Taylor Created: 28/Jun/22 09:02 Priority: Major Reporter: Andy Taylor adding the following metrics: Consumer Msgs Sent - current number of messages sent to consumer which are not yet acknowledged. Size Sent - combined size of unacknowledged messages sent to consumer. Last Sent - approximate time elapsed since last message was sent by the server to the consumer. Last Akcd - approximate time elapsed since last time any message sent to the consumer was acknowledged by consumer. Total Sent - total number of messages sent to consumer since it was created. Total Acked - total number of messages sent to the consumer and acknowledged by consumer since it was created. Producer Total Msgs Sent - number of messages sent by the producer Total Size Sent - combined size of messages sent by the producer Add Comment
[jira] [Created] (ARTEMIS-3539) Allow a shared single connection in the Resource Adaptor
Andy Taylor created ARTEMIS-3539: Summary: Allow a shared single connection in the Resource Adaptor Key: ARTEMIS-3539 URL: https://issues.apache.org/jira/browse/ARTEMIS-3539 Project: ActiveMQ Artemis Issue Type: Improvement Components: Broker Reporter: Andy Taylor Assignee: Andy Taylor currently there is a 1 to 1 session with connection and session for MDB's, allow the use of a single connection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3493) expose the User ID in the send message tab in console
Andy Taylor created ARTEMIS-3493: Summary: expose the User ID in the send message tab in console Key: ARTEMIS-3493 URL: https://issues.apache.org/jira/browse/ARTEMIS-3493 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor this field in the core message is used to keep the JMS Message ID, it would be nice to have one auto generated if a checkbox is checked -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3474) Replace use of non-inclusive terms throughout source code, comments and documentation
Andy Taylor created ARTEMIS-3474: Summary: Replace use of non-inclusive terms throughout source code, comments and documentation Key: ARTEMIS-3474 URL: https://issues.apache.org/jira/browse/ARTEMIS-3474 Project: ActiveMQ Artemis Issue Type: Task Reporter: Andy Taylor this follows up on the ActiveMQ Jira at https://issues.apache.org/jira/browse/AMQ-7514 but for Artemis . The conversation is on this Jira and in the forum -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3426) MQTT retain large messages not copied correctly
Andy Taylor created ARTEMIS-3426: Summary: MQTT retain large messages not copied correctly Key: ARTEMIS-3426 URL: https://issues.apache.org/jira/browse/ARTEMIS-3426 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor Assignee: Andy Taylor A retain message when large is created as a normal message, it should also be large. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3423) recreated shared durable subscription is created as unshared
[ https://issues.apache.org/jira/browse/ARTEMIS-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3423: - Affects Version/s: 2.18.0 > recreated shared durable subscription is created as unshared > > > Key: ARTEMIS-3423 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3423 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.18.0 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > This is just in the AMQP layer, if a shared durable subscription is recreated > because of a change in message selector it gets created as unshared > (maxconsumers=1) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3423) recreated durable subscription is created as unshared
Andy Taylor created ARTEMIS-3423: Summary: recreated durable subscription is created as unshared Key: ARTEMIS-3423 URL: https://issues.apache.org/jira/browse/ARTEMIS-3423 Project: ActiveMQ Artemis Issue Type: Bug Components: AMQP Reporter: Andy Taylor Assignee: Andy Taylor This is just in the AMQP layer, if a durable subscription is recreated because of a change in message selector it gets created as unshared (maxconsumers=1) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3404) expose max retry interval on bridge mbean
Andy Taylor created ARTEMIS-3404: Summary: expose max retry interval on bridge mbean Key: ARTEMIS-3404 URL: https://issues.apache.org/jira/browse/ARTEMIS-3404 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3403) wrong debug level in ArtemisMBeanServerGuard
Andy Taylor created ARTEMIS-3403: Summary: wrong debug level in ArtemisMBeanServerGuard Key: ARTEMIS-3403 URL: https://issues.apache.org/jira/browse/ARTEMIS-3403 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor ActiveMQServerLogger.LOGGER.info(object + " " + operationName + " " + false); shuld be debug -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3398) message count incorrect when browsing messages with filter in console
[ https://issues.apache.org/jira/browse/ARTEMIS-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3398: - Description: This means that the message nnmay appear in an empty list and pagination means it can only seeen on a specific page. > message count incorrect when browsing messages with filter in console > - > > Key: ARTEMIS-3398 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3398 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > This means that the message nnmay appear in an empty list and pagination > means it can only seeen on a specific page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3398) message count incorrect when browsing messages with filter in console
[ https://issues.apache.org/jira/browse/ARTEMIS-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3398: - Summary: message count incorrect when browsing messages with filter in console (was: message count when browsing messages with filter in console) > message count incorrect when browsing messages with filter in console > - > > Key: ARTEMIS-3398 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3398 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3398) message count when browsing messages with filter in console
Andy Taylor created ARTEMIS-3398: Summary: message count when browsing messages with filter in console Key: ARTEMIS-3398 URL: https://issues.apache.org/jira/browse/ARTEMIS-3398 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor Assignee: Andy Taylor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3332) Console uses Consumer ID instead of Consumer count for searching
Andy Taylor created ARTEMIS-3332: Summary: Console uses Consumer ID instead of Consumer count for searching Key: ARTEMIS-3332 URL: https://issues.apache.org/jira/browse/ARTEMIS-3332 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor Assignee: Andy Taylor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3331) Improvements to Resource Adapter and example
[ https://issues.apache.org/jira/browse/ARTEMIS-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3331: - Issue Type: Improvement (was: Bug) > Improvements to Resource Adapter and example > > > Key: ARTEMIS-3331 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3331 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Several improvements to the Resource Adapter and the example after testing > with WebSphere, these include: > > # Add a flag to enable whether or not an outgoing connection uses the > current JTA TX when creating the session. This is for when the RA does not > have access to the Transaction Manager to discover this automatically. > # The RA logger uses getPackage() which returns null on Classloaders that > aren't a jar Classloader, such as the WebSphere Rar uploader. use getClass > which always returns not null. > # Added some missing setters/getters > # Added overloaded getters for boolean properties, this is because some > Application Servers (WebSphere) uses introspection on the Classes which will > include getFoo() but not isFoo() > # Fixed up the example ra.xml. > # Other small fixes to handle Introspection better such as avoiding Null > Pointers -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3331) Improvements to Resource Adapter and example
[ https://issues.apache.org/jira/browse/ARTEMIS-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3331: - Description: Several improvements to the Resource Adapter and the example after testing with WebSphere, these include: # Add a flag to enable whether or not an outgoing connection uses the current JTA TX when creating the session. This is for when the RA does not have access to the Transaction Manager to discover this automatically. # The RA logger uses getPackage() which returns null on Classloaders that aren't a jar Classloader, such as the WebSphere Rar uploader. use getClass which always returns not null. # Added some missing setters/getters # Added overloaded getters for boolean properties, this is because some Application Servers (WebSphere) uses introspection on the Classes which will include getFoo() but not isFoo() # Fixed up the example ra.xml. # Other small fixes to handle Introspection better such as avoiding Null Pointers was: Several improvements to the Resource Adapter and the example after testing with WebSphere, these include: # Add a flag to enable whether or not an outgoing connection uses the current JTA TX when creating the session. This is for when the RA does not have access to the Transaction Manager to discover this automatically. # The RA logger uses getPackage() which returns null on Classloaders that aren't a jar Classloader, such as the WebSphere Rar uploader. use getClass which always returns not null. # Added some missing setters/getters # Added overloaded getters for boolean properties, this is because some Application Servers (WebSphere) uses introspection on the Classes which will include getFoo() but not isF00() # Fixed up the example ra.xml. > Improvements to Resource Adapter and example > > > Key: ARTEMIS-3331 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3331 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > Several improvements to the Resource Adapter and the example after testing > with WebSphere, these include: > > # Add a flag to enable whether or not an outgoing connection uses the > current JTA TX when creating the session. This is for when the RA does not > have access to the Transaction Manager to discover this automatically. > # The RA logger uses getPackage() which returns null on Classloaders that > aren't a jar Classloader, such as the WebSphere Rar uploader. use getClass > which always returns not null. > # Added some missing setters/getters > # Added overloaded getters for boolean properties, this is because some > Application Servers (WebSphere) uses introspection on the Classes which will > include getFoo() but not isFoo() > # Fixed up the example ra.xml. > # Other small fixes to handle Introspection better such as avoiding Null > Pointers -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3331) Improvements to Resource Adapter and example
[ https://issues.apache.org/jira/browse/ARTEMIS-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3331: - Description: Several improvements to the Resource Adapter and the example after testing with WebSphere, these include: # Add a flag to enable whether or not an outgoing connection uses the current JTA TX when creating the session. This is for when the RA does not have access to the Transaction Manager to discover this automatically. # The RA logger uses getPackage() which returns null on Classloaders that aren't a jar Classloader, such as the WebSphere Rar uploader. use getClass which always returns not null. # Added some missing setters/getters # Added overloaded getters for boolean properties, this is because some Application Servers (WebSphere) uses introspection on the Classes which will include getFoo() but not isF00() # Fixed up the example ra.xml. was: Several improvements to the Resource Adapter and the example after testing with WebSphere, these include: # Add a flag to enable whether or not an outgoing connection uses the current JTA TX when creating the session. This is for when the RA does not have access to the Transaction Manager to discover this automatically. # The RA logger uses getPackage() which returns null on Classloaders that aren't a jar Classloader, such as the WebSphere Rar uploader. use getClass which always returns not null. > Improvements to Resource Adapter and example > > > Key: ARTEMIS-3331 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3331 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > Several improvements to the Resource Adapter and the example after testing > with WebSphere, these include: > > # Add a flag to enable whether or not an outgoing connection uses the > current JTA TX when creating the session. This is for when the RA does not > have access to the Transaction Manager to discover this automatically. > # The RA logger uses getPackage() which returns null on Classloaders that > aren't a jar Classloader, such as the WebSphere Rar uploader. use getClass > which always returns not null. > # Added some missing setters/getters > # Added overloaded getters for boolean properties, this is because some > Application Servers (WebSphere) uses introspection on the Classes which will > include getFoo() but not isF00() > # Fixed up the example ra.xml. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3331) Improvements to Resource Adapter and example
[ https://issues.apache.org/jira/browse/ARTEMIS-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3331: - Description: Several improvements to the Resource Adapter and the example after testing with WebSphere, these include: # Add a flag to enable whether or not an outgoing connection uses the current JTA TX when creating the session. This is for when the RA does not have access to the Transaction Manager to discover this automatically. # The RA logger uses getPackage() which returns null on Classloaders that aren't a jar Classloader, such as the WebSphere Rar uploader. use getClass which always returns not null. was: Several improvements to the Resource Adapter and the example after testing with WebSphere, these include: # Add a flag to enable whether or not an outgoing connection uses the current JTA TX when creating the session. This is for when the RA does not have access to the Transaction Manager to discover this automatically. > Improvements to Resource Adapter and example > > > Key: ARTEMIS-3331 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3331 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > Several improvements to the Resource Adapter and the example after testing > with WebSphere, these include: > > # Add a flag to enable whether or not an outgoing connection uses the > current JTA TX when creating the session. This is for when the RA does not > have access to the Transaction Manager to discover this automatically. > # The RA logger uses getPackage() which returns null on Classloaders that > aren't a jar Classloader, such as the WebSphere Rar uploader. use getClass > which always returns not null. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3331) Improvements to Resource Adapter and example
[ https://issues.apache.org/jira/browse/ARTEMIS-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3331: - Description: Several improvements to the Resource Adapter and the example after testing with WebSphere, these include: # Add a flag to enable whether or not an outgoing connection uses the current JTA TX when creating the session. This is for when the RA does not have access to the Transaction Manager to discover this automatically. > Improvements to Resource Adapter and example > > > Key: ARTEMIS-3331 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3331 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > Several improvements to the Resource Adapter and the example after testing > with WebSphere, these include: > > # Add a flag to enable whether or not an outgoing connection uses the > current JTA TX when creating the session. This is for when the RA does not > have access to the Transaction Manager to discover this automatically. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3331) Improvements to Resource Adapter and example
Andy Taylor created ARTEMIS-3331: Summary: Improvements to Resource Adapter and example Key: ARTEMIS-3331 URL: https://issues.apache.org/jira/browse/ARTEMIS-3331 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor Assignee: Andy Taylor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3295) Openwire advisories are clustered
Andy Taylor created ARTEMIS-3295: Summary: Openwire advisories are clustered Key: ARTEMIS-3295 URL: https://issues.apache.org/jira/browse/ARTEMIS-3295 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.17.0 Reporter: Andy Taylor Assignee: Andy Taylor These should not be clustered as they arent in ActiveMQ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3201) Configured Diverts aren't persisted
[ https://issues.apache.org/jira/browse/ARTEMIS-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3201: - Affects Version/s: 2.17.0 > Configured Diverts aren't persisted > --- > > Key: ARTEMIS-3201 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3201 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.17.0 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > only diverts created via management ops -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3201) Configured Diverts aren't persisted
[ https://issues.apache.org/jira/browse/ARTEMIS-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3201: - Issue Type: Bug (was: Improvement) > Configured Diverts aren't persisted > --- > > Key: ARTEMIS-3201 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3201 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > only diverts created via management ops -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3202) add flag to delete diverts removed from config
Andy Taylor created ARTEMIS-3202: Summary: add flag to delete diverts removed from config Key: ARTEMIS-3202 URL: https://issues.apache.org/jira/browse/ARTEMIS-3202 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3201) Configured Diverts aren't persisted
Andy Taylor created ARTEMIS-3201: Summary: Configured Diverts aren't persisted Key: ARTEMIS-3201 URL: https://issues.apache.org/jira/browse/ARTEMIS-3201 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor only diverts created via management ops -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3196) expose journal pool files in JMX
Andy Taylor created ARTEMIS-3196: Summary: expose journal pool files in JMX Key: ARTEMIS-3196 URL: https://issues.apache.org/jira/browse/ARTEMIS-3196 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3154) Add support for navigation/deleting messages while being browsed
Andy Taylor created ARTEMIS-3154: Summary: Add support for navigation/deleting messages while being browsed Key: ARTEMIS-3154 URL: https://issues.apache.org/jira/browse/ARTEMIS-3154 Project: ActiveMQ Artemis Issue Type: Improvement Components: Web Console Reporter: Andy Taylor Assignee: Andy Taylor While browsing a message in the new Broker console, controls are no longer provided to navigate between message (previous/next) or delete messages. These controls were previously available in the console prior to 7.8.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3130) filter fields broker in console
[ https://issues.apache.org/jira/browse/ARTEMIS-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3130: - Affects Version/s: 2.17.0 > filter fields broker in console > --- > > Key: ARTEMIS-3130 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3130 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.17.0 >Reporter: Andy Taylor >Priority: Major > > There are some filter fields that aren't working in the queues tab that cause > an error when used. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3130) filter fields broker in console
Andy Taylor created ARTEMIS-3130: Summary: filter fields broker in console Key: ARTEMIS-3130 URL: https://issues.apache.org/jira/browse/ARTEMIS-3130 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor There are some filter fields that aren't working in the queues tab that cause an error when used. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3129) add browse entry in RBAC
Andy Taylor created ARTEMIS-3129: Summary: add browse entry in RBAC Key: ARTEMIS-3129 URL: https://issues.apache.org/jira/browse/ARTEMIS-3129 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor It's not obvios when configuring rbac access for read only and the browse tab what is needed in the management.xml file. This adds the roles with a comment for clarity -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3129) add browse entry in RBAC
[ https://issues.apache.org/jira/browse/ARTEMIS-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3129: - Affects Version/s: 2.17.0 > add browse entry in RBAC > > > Key: ARTEMIS-3129 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3129 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.17.0 >Reporter: Andy Taylor >Priority: Minor > > It's not obvios when configuring rbac access for read only and the browse tab > what is needed in the management.xml file. This adds the roles with a comment > for clarity -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ARTEMIS-3072) Management methods check for null and not for empty strings
[ https://issues.apache.org/jira/browse/ARTEMIS-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor resolved ARTEMIS-3072. -- Assignee: Andy Taylor Resolution: Fixed > Management methods check for null and not for empty strings > --- > > Key: ARTEMIS-3072 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3072 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.16.0 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: 2.17.0 > > > This has been brought to light because of the new console as it passes an > empty string instead of null in some scenarios. We should add a belts and > braces to check for an empty string as well. > > FYI Ive followed up with the Hawtio team about this as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3072) Management methods check for null and not for empty strings
[ https://issues.apache.org/jira/browse/ARTEMIS-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3072: - Affects Version/s: 2.16.0 > Management methods check for null and not for empty strings > --- > > Key: ARTEMIS-3072 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3072 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.16.0 >Reporter: Andy Taylor >Priority: Major > > This has been brought to light because of the new console as it passes an > empty string instead of null in some scenarios. We should add a belts and > braces to check for an empty string as well. > > FYI Ive followed up with the Hawtio team about this as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3072) Management methods check for null and not for empty strings
[ https://issues.apache.org/jira/browse/ARTEMIS-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3072: - Fix Version/s: 2.17.0 > Management methods check for null and not for empty strings > --- > > Key: ARTEMIS-3072 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3072 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.16.0 >Reporter: Andy Taylor >Priority: Major > Fix For: 2.17.0 > > > This has been brought to light because of the new console as it passes an > empty string instead of null in some scenarios. We should add a belts and > braces to check for an empty string as well. > > FYI Ive followed up with the Hawtio team about this as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3072) Management methods check for null and not for empty strings
Andy Taylor created ARTEMIS-3072: Summary: Management methods check for null and not for empty strings Key: ARTEMIS-3072 URL: https://issues.apache.org/jira/browse/ARTEMIS-3072 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor This has been brought to light because of the new console as it passes an empty string instead of null in some scenarios. We should add a belts and braces to check for an empty string as well. FYI Ive followed up with the Hawtio team about this as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3043) improvements on new console
[ https://issues.apache.org/jira/browse/ARTEMIS-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3043: - Description: This is to cover several items missing from the initial migration to hawtIO 2, this includes: * Add back the JMX Context on mbean pages * Add back column selectors for each view tab * Add back ability to hide brokers and network connectors * add timestamp fix added to old console * fix navigation and JMX tree context navigation under certain scenarios * fix navigation and linking between views. * fix serverside ordering was: This is to cover several items missing from the initial migration to hawtIO 2, this includes: * Add back the JMX Context on mbean pages * Add back column selectors for each view tab * Add back ability to hide brokers and network connectors * add timestamp fix added to old console * fix navigation and JMX tree context navigation under certain scenarios * fix navigation and linking between views. > improvements on new console > --- > > Key: ARTEMIS-3043 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3043 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.16.0 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 2h 20m > Remaining Estimate: 0h > > This is to cover several items missing from the initial migration to hawtIO > 2, this includes: > > * Add back the JMX Context on mbean pages > * Add back column selectors for each view tab > * Add back ability to hide brokers and network connectors > * add timestamp fix added to old console > * fix navigation and JMX tree context navigation under certain scenarios > * fix navigation and linking between views. > * fix serverside ordering -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3043) improvements on new console
[ https://issues.apache.org/jira/browse/ARTEMIS-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3043: - Affects Version/s: 2.16.0 > improvements on new console > --- > > Key: ARTEMIS-3043 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3043 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.16.0 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > This is to cover several items missing from the initial migration to hawtIO > 2, this includes: > > * Add back the JMX Context on mbean pages > * Add back column selectors for each view tab > * Add back ability to hide brokers and network connectors > * add timestamp fix added to old console > * fix navigation and JMX tree context navigation under certain scenarios > * fix navigation and linking between views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3043) improvements on new console
Andy Taylor created ARTEMIS-3043: Summary: improvements on new console Key: ARTEMIS-3043 URL: https://issues.apache.org/jira/browse/ARTEMIS-3043 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor This is to cover several items missing from the initial migration to hawtIO 2, this includes: * Add back the JMX Context on mbean pages * Add back column selectors for each view tab * Add back ability to hide brokers and network connectors * add timestamp fix added to old console * fix navigation and JMX tree context navigation under certain scenarios * fix navigation and linking between views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3029) wrong heading on producers tab in console
Andy Taylor created ARTEMIS-3029: Summary: wrong heading on producers tab in console Key: ARTEMIS-3029 URL: https://issues.apache.org/jira/browse/ARTEMIS-3029 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.16.0 Reporter: Andy Taylor Assignee: Andy Taylor it says browse consumers not producers -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3022) add original queue to dlq/expiry queue
Andy Taylor created ARTEMIS-3022: Summary: add original queue to dlq/expiry queue Key: ARTEMIS-3022 URL: https://issues.apache.org/jira/browse/ARTEMIS-3022 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor Currently its difficult to see what the original queue was when browsing a dlq or expiry queue. Its cumbersome to click into the details and then back out to be able to retry the message, this would alleviate this by showing in the main browse page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work stopped] (ARTEMIS-3018) Console dlq pref doesn work with multiple dlq's
[ https://issues.apache.org/jira/browse/ARTEMIS-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-3018 stopped by Andy Taylor. > Console dlq pref doesn work with multiple dlq's > --- > > Key: ARTEMIS-3018 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3018 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.16.0 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > This is because it used the queue name instead of the address of the dlq -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3018) Console dlq pref doesn work with multiple dlq's
[ https://issues.apache.org/jira/browse/ARTEMIS-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-3018: - Affects Version/s: 2.16.0 > Console dlq pref doesn work with multiple dlq's > --- > > Key: ARTEMIS-3018 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3018 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.16.0 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > This is because it used the queue name instead of the address of the dlq -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (ARTEMIS-3018) Console dlq pref doesn work with multiple dlq's
[ https://issues.apache.org/jira/browse/ARTEMIS-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-3018 started by Andy Taylor. > Console dlq pref doesn work with multiple dlq's > --- > > Key: ARTEMIS-3018 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3018 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.16.0 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > This is because it used the queue name instead of the address of the dlq -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3018) Console dlq pref doesn work with multiple dlq's
Andy Taylor created ARTEMIS-3018: Summary: Console dlq pref doesn work with multiple dlq's Key: ARTEMIS-3018 URL: https://issues.apache.org/jira/browse/ARTEMIS-3018 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor Assignee: Andy Taylor This is because it used the queue name instead of the address of the dlq -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ARTEMIS-3000) Console browse message filter broken
[ https://issues.apache.org/jira/browse/ARTEMIS-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor reassigned ARTEMIS-3000: Assignee: Andy Taylor > Console browse message filter broken > > > Key: ARTEMIS-3000 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3000 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3000) Console browse message filter broken
Andy Taylor created ARTEMIS-3000: Summary: Console browse message filter broken Key: ARTEMIS-3000 URL: https://issues.apache.org/jira/browse/ARTEMIS-3000 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2973) JMS AMQP Shared global subscriber queue not deleted on unsubscribe
Andy Taylor created ARTEMIS-2973: Summary: JMS AMQP Shared global subscriber queue not deleted on unsubscribe Key: ARTEMIS-2973 URL: https://issues.apache.org/jira/browse/ARTEMIS-2973 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor Assignee: Andy Taylor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2908) Persist Divert Configuration in Bindings journal
Andy Taylor created ARTEMIS-2908: Summary: Persist Divert Configuration in Bindings journal Key: ARTEMIS-2908 URL: https://issues.apache.org/jira/browse/ARTEMIS-2908 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor Assignee: Andy Taylor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2902) expose at queue control messages held in a prepared tx
Andy Taylor created ARTEMIS-2902: Summary: expose at queue control messages held in a prepared tx Key: ARTEMIS-2902 URL: https://issues.apache.org/jira/browse/ARTEMIS-2902 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor Assignee: Andy Taylor Sometimes it's helpful to track down messages to be able to find if they are held as part of a prepared tx that needs committing or rolling back -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work stopped] (ARTEMIS-2838) Migrate Console to use Hawtio 2
[ https://issues.apache.org/jira/browse/ARTEMIS-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-2838 stopped by Andy Taylor. > Migrate Console to use Hawtio 2 > --- > > Key: ARTEMIS-2838 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2838 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The main concern here is upgrading HawtIO as version 1 is no longer > maintained and we need to reduce the chance of CVE's going forward. > > I've basically re written the console JavaScript using the new API's making > them as much as possible the same as the original. There are a few minor > changes but nothing that would warrant a loss is functionality. This also > has a new look and feel. Ive aslo improved some features, these include: > > # A new landing page that shows some basic broker state, uptime, cluster > status, address memory used. > # A HawtIO security mbean, this means that hawtIO will check at call time > whether or not the attribute or operation can be called, so rather than see > an error in the attributes stab when access isnt authorised it is handled > gracefully. This is also used to control whether a tab is available, so if a > user does not have access to the createqueue jmx method then the create queue > tab will not be available. > # Added a help button to most of the tabs > # A search facility for mbeans in the JMX tree -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (ARTEMIS-2838) Migrate Console to use Hawtio 2
[ https://issues.apache.org/jira/browse/ARTEMIS-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-2838 started by Andy Taylor. > Migrate Console to use Hawtio 2 > --- > > Key: ARTEMIS-2838 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2838 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The main concern here is upgrading HawtIO as version 1 is no longer > maintained and we need to reduce the chance of CVE's going forward. > > I've basically re written the console JavaScript using the new API's making > them as much as possible the same as the original. There are a few minor > changes but nothing that would warrant a loss is functionality. This also > has a new look and feel. Ive aslo improved some features, these include: > > # A new landing page that shows some basic broker state, uptime, cluster > status, address memory used. > # A HawtIO security mbean, this means that hawtIO will check at call time > whether or not the attribute or operation can be called, so rather than see > an error in the attributes stab when access isnt authorised it is handled > gracefully. This is also used to control whether a tab is available, so if a > user does not have access to the createqueue jmx method then the create queue > tab will not be available. > # Added a help button to most of the tabs > # A search facility for mbeans in the JMX tree -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2838) Migrate Console to use Hawtio 2
[ https://issues.apache.org/jira/browse/ARTEMIS-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-2838: - Fix Version/s: 2.16.0 > Migrate Console to use Hawtio 2 > --- > > Key: ARTEMIS-2838 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2838 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: 2.16.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The main concern here is upgrading HawtIO as version 1 is no longer > maintained and we need to reduce the chance of CVE's going forward. > > I've basically re written the console JavaScript using the new API's making > them as much as possible the same as the original. There are a few minor > changes but nothing that would warrant a loss is functionality. This also > has a new look and feel. Ive aslo improved some features, these include: > > # A new landing page that shows some basic broker state, uptime, cluster > status, address memory used. > # A HawtIO security mbean, this means that hawtIO will check at call time > whether or not the attribute or operation can be called, so rather than see > an error in the attributes stab when access isnt authorised it is handled > gracefully. This is also used to control whether a tab is available, so if a > user does not have access to the createqueue jmx method then the create queue > tab will not be available. > # Added a help button to most of the tabs > # A search facility for mbeans in the JMX tree -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2838) Migrate Console to use Hawtio 2
[ https://issues.apache.org/jira/browse/ARTEMIS-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-2838: - Description: The main concern here is upgrading HawtIO as version 1 is no longer maintained and we need to reduce the chance of CVE's going forward. I've basically re written the console JavaScript using the new API's making them as much as possible the same as the original. There are a few minor changes but nothing that would warrant a loss is functionality. This also has a new look and feel. Ive aslo improved some features, these include: # A new landing page that shows some basic broker state, uptime, cluster status, address memory used. # A HawtIO security mbean, this means that hawtIO will check at call time whether or not the attribute or operation can be called, so rather than see an error in the attributes stab when access isnt authorised it is handled gracefully. This is also used to control whether a tab is available, so if a user does not have access to the createqueue jmx method then the create queue tab will not be available. # Added a help button to most of the tabs # A search facility for mbeans in the JMX tree was:hawtIO 1 is no longer maintained so to avoid possible CVE's we should migrate > Migrate Console to use Hawtio 2 > --- > > Key: ARTEMIS-2838 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2838 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > The main concern here is upgrading HawtIO as version 1 is no longer > maintained and we need to reduce the chance of CVE's going forward. > > I've basically re written the console JavaScript using the new API's making > them as much as possible the same as the original. There are a few minor > changes but nothing that would warrant a loss is functionality. This also > has a new look and feel. Ive aslo improved some features, these include: > > # A new landing page that shows some basic broker state, uptime, cluster > status, address memory used. > # A HawtIO security mbean, this means that hawtIO will check at call time > whether or not the attribute or operation can be called, so rather than see > an error in the attributes stab when access isnt authorised it is handled > gracefully. This is also used to control whether a tab is available, so if a > user does not have access to the createqueue jmx method then the create queue > tab will not be available. > # Added a help button to most of the tabs > # A search facility for mbeans in the JMX tree -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2838) Migrate Console to use Hawtio 2
[ https://issues.apache.org/jira/browse/ARTEMIS-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-2838: - Issue Type: Improvement (was: Bug) > Migrate Console to use Hawtio 2 > --- > > Key: ARTEMIS-2838 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2838 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > hawtIO 1 is no longer maintained so to avoid possible CVE's we should migrate -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2838) Migrate Console to use Hawtio 2
Andy Taylor created ARTEMIS-2838: Summary: Migrate Console to use Hawtio 2 Key: ARTEMIS-2838 URL: https://issues.apache.org/jira/browse/ARTEMIS-2838 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor Assignee: Andy Taylor hawtIO 1 is no longer maintained so to avoid possible CVE's we should migrate -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ARTEMIS-2793) quorum logging implies it happens when single pair
[ https://issues.apache.org/jira/browse/ARTEMIS-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor reassigned ARTEMIS-2793: Assignee: Andy Taylor > quorum logging implies it happens when single pair > -- > > Key: ARTEMIS-2793 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2793 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > we should probably log something different so users know no voting occured -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2793) quorum logging implies it happens when single pair
Andy Taylor created ARTEMIS-2793: Summary: quorum logging implies it happens when single pair Key: ARTEMIS-2793 URL: https://issues.apache.org/jira/browse/ARTEMIS-2793 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor we should probably log something different so users know no voting occured -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2786) Timestamp in console is incorrect
[ https://issues.apache.org/jira/browse/ARTEMIS-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-2786: - Description: The month is 1 out, this is because the javascript getmonth method returns the position of the month. [https://www.w3schools.com/js/js_date_methods.asp] was:The month is 1 out, this is because the javascript getmonth method returns the position of the month. > Timestamp in console is incorrect > - > > Key: ARTEMIS-2786 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2786 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.13.0 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > The month is 1 out, this is because the javascript getmonth method returns > the position of the month. > > [https://www.w3schools.com/js/js_date_methods.asp] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2786) Timestamp in console is incorrect
Andy Taylor created ARTEMIS-2786: Summary: Timestamp in console is incorrect Key: ARTEMIS-2786 URL: https://issues.apache.org/jira/browse/ARTEMIS-2786 Project: ActiveMQ Artemis Issue Type: Improvement Affects Versions: 2.13.0 Reporter: Andy Taylor Assignee: Andy Taylor The month is 1 out, this is because the javascript getmonth method returns the position of the month. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ARTEMIS-2648) Improve the Audit logging capabilities
[ https://issues.apache.org/jira/browse/ARTEMIS-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor resolved ARTEMIS-2648. -- Fix Version/s: 2.13.0 Resolution: Fixed > Improve the Audit logging capabilities > -- > > Key: ARTEMIS-2648 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2648 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: 2.13.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > This will improve the current audit logging feature. currently there are 2 > loggers which are very verbose so this will add a 3rd which focus mainly > around access to resources that a console user or a jmx client may use. Also > currently no success/failure is logged only entry points in methods, this new > logger will log success or failure. > Here is a list of the improvements: > * New Resource logger added > ** This will log more resource related access from JMX/console mainly around > creation of resources and access to these resource > ** It will be enabled independently of the other loggers > * Message audit log will be changed to be configurable independently not > with base audit log, and the new resource logger will also be configurable > independently. > * Add the ability to capture the remote address of the calling client > whether it be through JMX/console or a normal Netty connection > * Add the ability to capture authentication success or failure from the > console > > * Add the ability to log failures to JMX mbeans in the authentication > process. > > Also tidy up the current logger codes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2749) Add control objects for non UDP broadcast groups
[ https://issues.apache.org/jira/browse/ARTEMIS-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-2749: - Description: Currently if you use any other type of broadcast group, Jgroups, then you get errors when viewing the attributes. we need to support multiple types. > Add control objects for non UDP broadcast groups > > > Key: ARTEMIS-2749 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2749 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > Currently if you use any other type of broadcast group, Jgroups, then you get > errors when viewing the attributes. we need to support multiple types. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2749) Add control objects for non UDP broadcast groups
Andy Taylor created ARTEMIS-2749: Summary: Add control objects for non UDP broadcast groups Key: ARTEMIS-2749 URL: https://issues.apache.org/jira/browse/ARTEMIS-2749 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (ARTEMIS-2648) Improve the Audit logging capabilities
[ https://issues.apache.org/jira/browse/ARTEMIS-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-2648 started by Andy Taylor. > Improve the Audit logging capabilities > -- > > Key: ARTEMIS-2648 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2648 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > This will improve the current audit logging feature. currently there are 2 > loggers which are very verbose so this will add a 3rd which focus mainly > around access to resources that a console user or a jmx client may use. Also > currently no success/failure is logged only entry points in methods, this new > logger will log success or failure. > Here is a list of the improvements: > * New Resource logger added > ** This will log more resource related access from JMX/console mainly around > creation of resources and access to these resource > ** It will be enabled independently of the other loggers > * Message audit log will be changed to be configurable independently not > with base audit log, and the new resource logger will also be configurable > independently. > * Add the ability to capture the remote address of the calling client > whether it be through JMX/console or a normal Netty connection > * Add the ability to capture authentication success or failure from the > console > > * Add the ability to log failures to JMX mbeans in the authentication > process. > > Also tidy up the current logger codes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2648) Improve the Audit logging capabilities
[ https://issues.apache.org/jira/browse/ARTEMIS-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-2648: - Description: This will improve the current audit logging feature. currently there are 2 loggers which are very verbose so this will add a 3rd which focus mainly around access to resources that a console user or a jmx client may use. Also currently no success/failure is logged only entry points in methods, this new logger will log success or failure. Here is a list of the improvements: * New Resource logger added ** This will log more resource related access from JMX/console mainly around creation of resources and access to these resource ** It will be enabled independently of the other loggers * Message audit log will be changed to be configurable independently not with base audit log, and the new resource logger will also be configurable independently. * Add the ability to capture the remote address of the calling client whether it be through JMX/console or a normal Netty connection * Add the ability to capture authentication success or failure from the console * Add the ability to log failures to JMX mbeans in the authentication process. Also tidy up the current logger codes. was: This will improve the current audit logging feature. currently there are 2 loggers which are very verbose so this will add a 3rd which focus mainly around access to resources that a console user or a jmx client may use. Also currently no success/failure is logged only entry points in methods, this new logger will log success or failure. Here is a list of the improvements: * New Resource logger added ** This will log more resource related access from JMX/console mainly around creation of resources and access to these resource ** It will be enabled independently of the other loggers * Message audit log will be changed to be configurable independently not with base audit log, and the new resource logger will also be configurable independently. * Add the ability to capture the remote address of the calling client whether it be through JMX/console or a normal Netty connection * Add the ability to capture authentication success or failure via an audit login module, something like: |_org.apache.activemq.artemis.spi.core.security.jaas.AuditLoginModule optional_ _debug=false;_| * Add the ability to log failures to specific JMX mbeans in the authentication process, this will be configurable in the management.xml file and will hapen when rbac occurs in the management layer. This is really to avoid over verbose logging, something like: |__ __ __ __ __ __ __ __| Also tidy up the currentl logger codes. > Improve the Audit logging capabilities > -- > > Key: ARTEMIS-2648 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2648 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > This will improve the current audit logging feature. currently there are 2 > loggers which are very verbose so this will add a 3rd which focus mainly > around access to resources that a console user or a jmx client may use. Also > currently no success/failure is logged only entry points in methods, this new > logger will log success or failure. > Here is a list of the improvements: > * New Resource logger added > ** This will log more resource related access from JMX/console mainly around > creation of resources and access to these resource > ** It will be enabled independently of the other loggers > * Message audit log will be changed to be configurable independently not > with base audit log, and the new resource logger will also be configurable > independently. > * Add the ability to capture the remote address of the calling client > whether it be through JMX/console or a normal Netty connection > * Add the ability to capture authentication success or failure from the > console > > * Add the ability to log failures to JMX mbeans in the authentication > process. > > Also tidy up the current logger codes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2648) Improve the Audit logging capabilities
[ https://issues.apache.org/jira/browse/ARTEMIS-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-2648: - Description: This will improve the current audit logging feature. currently there are 2 loggers which are very verbose so this will add a 3rd which focus mainly around access to resources that a console user or a jmx client may use. Also currently no success/failure is logged only entry points in methods, this new logger will log success or failure. Here is a list of the improvements: * New Resource logger added ** This will log more resource related access from JMX/console mainly around creation of resources and access to these resource ** It will be enabled independently of the other loggers * Message audit log will be changed to be configurable independently not with base audit log, and the new resource logger will also be configurable independently. * Add the ability to capture the remote address of the calling client whether it be through JMX/console or a normal Netty connection * Add the ability to capture authentication success or failure via an audit login module, something like: |_org.apache.activemq.artemis.spi.core.security.jaas.AuditLoginModule optional_ _debug=false;_| * Add the ability to log failures to specific JMX mbeans in the authentication process, this will be configurable in the management.xml file and will hapen when rbac occurs in the management layer. This is really to avoid over verbose logging, something like: |__ __ __ __ __ __ __ __| Also tidy up the currentl logger codes. > Improve the Audit logging capabilities > -- > > Key: ARTEMIS-2648 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2648 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > This will improve the current audit logging feature. currently there are 2 > loggers which are very verbose so this will add a 3rd which focus mainly > around access to resources that a console user or a jmx client may use. Also > currently no success/failure is logged only entry points in methods, this new > logger will log success or failure. > Here is a list of the improvements: > * New Resource logger added > ** This will log more resource related access from JMX/console mainly around > creation of resources and access to these resource > ** It will be enabled independently of the other loggers > * Message audit log will be changed to be configurable independently not > with base audit log, and the new resource logger will also be configurable > independently. > * Add the ability to capture the remote address of the calling client > whether it be through JMX/console or a normal Netty connection > * Add the ability to capture authentication success or failure via an audit > login module, something like: > |_org.apache.activemq.artemis.spi.core.security.jaas.AuditLoginModule > optional_ > _debug=false;_| > * Add the ability to log failures to specific JMX mbeans in the > authentication process, this will be configurable in the management.xml file > and will hapen when rbac occurs in the management layer. This is really to > avoid over verbose logging, something like: > |__ > _ operation="createAddress"/>_ > _ operation="deleteAddress"/>_ > _ operation="updateAddress"/>_ > _ operation="createQueue"/>_ > _ operation="updateQueue"/>_ > _ operation="destroyQueue"/>_ > __| > > Also tidy up the currentl logger codes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2648) Improve the Audit logging capabilities
Andy Taylor created ARTEMIS-2648: Summary: Improve the Audit logging capabilities Key: ARTEMIS-2648 URL: https://issues.apache.org/jira/browse/ARTEMIS-2648 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2554) Queue control browse broken with large messages
[ https://issues.apache.org/jira/browse/ARTEMIS-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor updated ARTEMIS-2554: - Affects Version/s: 2.10.1 > Queue control browse broken with large messages > --- > > Key: ARTEMIS-2554 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2554 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.10.1 >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > This only happens if the large message was compressed but then sent as a > normal message rather than a large message as it was < large message size. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2554) Queue control browse broken with large messages
Andy Taylor created ARTEMIS-2554: Summary: Queue control browse broken with large messages Key: ARTEMIS-2554 URL: https://issues.apache.org/jira/browse/ARTEMIS-2554 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Andy Taylor Assignee: Andy Taylor This only happens if the large message was compressed but then sent as a normal message rather than a large message as it was < large message size. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2480) Reloading configuration can kill broker
Andy Taylor created ARTEMIS-2480: Summary: Reloading configuration can kill broker Key: ARTEMIS-2480 URL: https://issues.apache.org/jira/browse/ARTEMIS-2480 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.10.0 Reporter: Andy Taylor Assignee: Andy Taylor In some cases if undeploying a queue or address fails during restart then the broker will die, we should log a warning and continue -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (ARTEMIS-2477) create quieter check dependencies warning
Andy Taylor created ARTEMIS-2477: Summary: create quieter check dependencies warning Key: ARTEMIS-2477 URL: https://issues.apache.org/jira/browse/ARTEMIS-2477 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Andy Taylor Assignee: Andy Taylor The current checkdependencies checks print a whole stack trace which is overkill if the Netty class isnt on the classpath, if its a class not found we should give more descriptive help -- This message was sent by Atlassian Jira (v8.3.2#803003)
