[jira] [Commented] (ARTEMIS-1809) Add example showing Virtual Topic Mapping
[ https://issues.apache.org/jira/browse/ARTEMIS-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443650#comment-16443650 ] Pat Fox commented on ARTEMIS-1809: -- Hi [~gaohoward], I don't seem to be able to assign issues to myself. Perhaps I don't have the correct permissions - not sure. Thanks Pat > Add example showing Virtual Topic Mapping > -- > > Key: ARTEMIS-1809 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1809 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: OpenWire >Affects Versions: 2.5.0 >Reporter: Pat Fox >Priority: Minor > > Add a simple example to demonstrate the use of > "virtualTopicConsumerWildcards" to map ActiveMQ 5.x virtual topic consumers > to use the Artemis Address model. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARTEMIS-1815) add "exclusive-queue" example
[ https://issues.apache.org/jira/browse/ARTEMIS-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441033#comment-16441033 ] Pat Fox commented on ARTEMIS-1815: -- PR to follow > add "exclusive-queue" example > -- > > Key: ARTEMIS-1815 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1815 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.5.0 >Reporter: Pat Fox >Priority: Minor > > add "exclusive-queue" example to the examples dir. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARTEMIS-1815) add "exclusive-queue" example
Pat Fox created ARTEMIS-1815: Summary: add "exclusive-queue" example Key: ARTEMIS-1815 URL: https://issues.apache.org/jira/browse/ARTEMIS-1815 Project: ActiveMQ Artemis Issue Type: Improvement Components: Broker Affects Versions: 2.5.0 Reporter: Pat Fox add "exclusive-queue" example to the examples dir. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARTEMIS-1809) Add example showing Virtual Topic Mapping
[ https://issues.apache.org/jira/browse/ARTEMIS-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439089#comment-16439089 ] Pat Fox commented on ARTEMIS-1809: -- PR to follow > Add example showing Virtual Topic Mapping > -- > > Key: ARTEMIS-1809 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1809 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: OpenWire >Affects Versions: 2.5.0 >Reporter: Pat Fox >Priority: Minor > > Add a simple example to demonstrate the use of > "virtualTopicConsumerWildcards" to map ActiveMQ 5.x virtual topic consumers > to use the Artemis Address model. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARTEMIS-1809) Add example showing Virtual Topic Mapping
Pat Fox created ARTEMIS-1809: Summary: Add example showing Virtual Topic Mapping Key: ARTEMIS-1809 URL: https://issues.apache.org/jira/browse/ARTEMIS-1809 Project: ActiveMQ Artemis Issue Type: Improvement Components: OpenWire Affects Versions: 2.5.0 Reporter: Pat Fox Add a simple example to demonstrate the use of "virtualTopicConsumerWildcards" to map ActiveMQ 5.x virtual topic consumers to use the Artemis Address model. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARTEMIS-1623) create an ActiveMQServerPlugin for logging various broker events
[ https://issues.apache.org/jira/browse/ARTEMIS-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332735#comment-16332735 ] Pat Fox commented on ARTEMIS-1623: -- PR with suggested implementation to follow > create an ActiveMQServerPlugin for logging various broker events > - > > Key: ARTEMIS-1623 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1623 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.4.0 >Reporter: Pat Fox >Priority: Minor > > create an implementation of ActiveMQServerPlugin for logging various broker > events , consumer created, message delivered etc. This should be configurable > to log only events user is interested in. > Similar functionality to the ActiveMQ 5.x loggingBrokerPlugin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARTEMIS-1623) create an ActiveMQServerPlugin for logging various broker events
Pat Fox created ARTEMIS-1623: Summary: create an ActiveMQServerPlugin for logging various broker events Key: ARTEMIS-1623 URL: https://issues.apache.org/jira/browse/ARTEMIS-1623 Project: ActiveMQ Artemis Issue Type: Improvement Components: Broker Affects Versions: 2.4.0 Reporter: Pat Fox create an implementation of ActiveMQServerPlugin for logging various broker events , consumer created, message delivered etc. This should be configurable to log only events user is interested in. Similar functionality to the ActiveMQ 5.x loggingBrokerPlugin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARTEMIS-1575) configuring custom brokerPlugins within the broker.xml
Pat Fox created ARTEMIS-1575:
Summary: configuring custom brokerPlugins within the broker.xml
Key: ARTEMIS-1575
URL: https://issues.apache.org/jira/browse/ARTEMIS-1575
Project: ActiveMQ Artemis
Issue Type: Improvement
Components: Broker
Affects Versions: 2.4.0
Reporter: Pat Fox
Priority: Minor
It would be nice to allow users to users configure their custom plugins within
the broker.xml, using key value properties like below:
{code}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1575) configuring custom brokerPlugins within the broker.xml
[
https://issues.apache.org/jira/browse/ARTEMIS-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305669#comment-16305669
]
Pat Fox commented on ARTEMIS-1575:
--
PR to follow
> configuring custom brokerPlugins within the broker.xml
> --
>
> Key: ARTEMIS-1575
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1575
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.4.0
>Reporter: Pat Fox
>Priority: Minor
>
> It would be nice to allow users to users configure their custom plugins
> within the broker.xml, using key value properties like below:
> {code}
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ARTEMIS-1563) added an example to demo Slow Consumer Policy KILL and NOTIFY
Pat Fox created ARTEMIS-1563: Summary: added an example to demo Slow Consumer Policy KILL and NOTIFY Key: ARTEMIS-1563 URL: https://issues.apache.org/jira/browse/ARTEMIS-1563 Project: ActiveMQ Artemis Issue Type: Improvement Components: Broker Affects Versions: 2.4.0 Reporter: Pat Fox Priority: Minor could not find example of using Slow Consumer policy. It would be good to have one in the examples. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1563) added an example to demo Slow Consumer Policy KILL and NOTIFY
[ https://issues.apache.org/jira/browse/ARTEMIS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292321#comment-16292321 ] Pat Fox commented on ARTEMIS-1563: -- adding a PR with suggested example > added an example to demo Slow Consumer Policy KILL and NOTIFY > - > > Key: ARTEMIS-1563 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1563 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.4.0 >Reporter: Pat Fox >Priority: Minor > > could not find example of using Slow Consumer policy. It would be good to > have one in the examples. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1534) adding openwire connection logging
[ https://issues.apache.org/jira/browse/ARTEMIS-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276808#comment-16276808 ] Pat Fox commented on ARTEMIS-1534: -- PR request to follow > adding openwire connection logging > --- > > Key: ARTEMIS-1534 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1534 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: OpenWire >Affects Versions: 2.4.0 >Reporter: Pat Fox >Priority: Minor > > The openwire connection on the broker side does not provide much logging, so > it is difficult to trace what openwire messages have arrived at the broker > side. > It would be nice to introduce logging (at a trace level) where the openwire > commands that are receive or sent by the broker will be logged. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ARTEMIS-1534) adding openwire connection logging
Pat Fox created ARTEMIS-1534: Summary: adding openwire connection logging Key: ARTEMIS-1534 URL: https://issues.apache.org/jira/browse/ARTEMIS-1534 Project: ActiveMQ Artemis Issue Type: Improvement Components: OpenWire Affects Versions: 2.4.0 Reporter: Pat Fox Priority: Minor The openwire connection on the broker side does not provide much logging, so it is difficult to trace what openwire messages have arrived at the broker side. It would be nice to introduce logging (at a trace level) where the openwire commands that are receive or sent by the broker will be logged. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ARTEMIS-1526) ActiveMQServerControl.listConsumers() can fail with NullPointer
Pat Fox created ARTEMIS-1526:
Summary: ActiveMQServerControl.listConsumers() can fail with
NullPointer
Key: ARTEMIS-1526
URL: https://issues.apache.org/jira/browse/ARTEMIS-1526
Project: ActiveMQ Artemis
Issue Type: Bug
Affects Versions: 2.4.0
Reporter: Pat Fox
Priority: Minor
race condition between ActiveMQServerControl.listConsumers() and closing client
sessions can cause the following NullPointer
{code}
java.lang.NullPointerException: null
at
org.apache.activemq.artemis.core.management.impl.view.ConsumerView.toJson(Unknown
Source)
at
org.apache.activemq.artemis.core.management.impl.view.ConsumerView.toJson(Unknown
Source)
at
org.apache.activemq.artemis.core.management.impl.view.ActiveMQAbstractView.getResultsAsJson(ActiveMQAbstractView.java:68)
at
org.apache.activemq.artemis.core.management.impl.ActiveMQServerControlImpl.listConsumers(ActiveMQServerControlImpl.java:1727)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
at
com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
{code}
The ActiveMQServerControl.listConsumers() retrieves the associated
ServerSession and this may be null if the session has been closed AFTER the
listConsumers() has been called but BEFORE the session is retrieved.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ARTEMIS-1524) ActiveMQServerControl.listAddresses() can fail with NullPointerException
[
https://issues.apache.org/jira/browse/ARTEMIS-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pat Fox updated ARTEMIS-1524:
-
Description:
race condition between ActiveMQServerControl.listAddresses() and
ActiveMQServerControl.deleteAddress() that can result in the following
NullPointerException
{code}
java.lang.NullPointerException: null
at
org.apache.activemq.artemis.core.management.impl.view.AddressView.toJson(Unknown
Source)
at
org.apache.activemq.artemis.core.management.impl.view.AddressView.toJson(Unknown
Source)
at
org.apache.activemq.artemis.core.management.impl.view.ActiveMQAbstractView.getResultsAsJson(ActiveMQAbstractView.java:68)
at
org.apache.activemq.artemis.core.management.impl.ActiveMQServerControlImpl.listAddresses(ActiveMQServerControlImpl.java:1743)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
{code}
The ActiveMQServerControl.listAddresses() retrieves the list of addresses and
then retrieves the detail of each one to build the Json representation. If the
ActiveMQServerControl.deleteAddress() is invoked after getting the list of
addresses but before retrieving the details - a NullPointerException is thrown.
was:
race condition between ActiveMQServerControl.listAddresses() and
ActiveMQServerControl.deleteAddress() that can result in the following
NullPointerException
{code}
java.lang.NullPointerException: null
at
org.apache.activemq.artemis.core.management.impl.view.AddressView.toJson(Unknown
Source)
at
org.apache.activemq.artemis.core.management.impl.view.AddressView.toJson(Unknown
Source)
at
org.apache.activemq.artemis.core.management.impl.view.ActiveMQAbstractView.getResultsAsJson(ActiveMQAbstractView.java:68)
at
org.apache.activemq.artemis.core.management.impl.ActiveMQServerControlImpl.listAddresses(ActiveMQServerControlImpl.java:1743)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
{code}
The listAddresses() retrieves the list of addresses and then retrieves the
detail of each one to build the Json representation. If the deleteAddress()
happens between getting the list and retrieving the details - a
NullPointerException is thrown.
> ActiveMQServerControl.listAddresses() can fail with NullPointerException
>
>
> Key: ARTEMIS-1524
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1524
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.4.0
>Reporter: Pat Fox
>Priority: Minor
>
> race condition between ActiveMQServerControl.listAddresses() and
> ActiveMQServerControl.deleteAddress() that can result in the following
> NullPointerException
> {code}
> java.lang.NullPointerException: null
> at
> org.apache.activemq.artemis.core.management.impl.view.AddressView.toJson(Unknown
> Source)
> at
> org.apache.activemq.artemis.core.management.impl.view.AddressView.toJson(Unknown
> Source)
> at
> org.apache.activemq.artemis.core.management.impl.view.ActiveMQAbstractView.getResultsAsJson(ActiveMQAbstractView.java:68)
> at
> org.apache.activemq.artemis.core.management.impl.ActiveMQServerControlImpl.listAddresses(ActiveMQServerControlImpl.java:1743)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> {code}
> The ActiveMQServerControl.listAddresses() retrieves the list of addresses and
> then retrieves the detail of each one to build the Json representation. If
> the ActiveMQServerControl.deleteAddress() is invoked after getting the list
> of addresses but before retrieving the details - a NullPointerException is
> thrown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ARTEMIS-1524) ActiveMQServerControl.listAddresses() can fail with NullPointerException
Pat Fox created ARTEMIS-1524:
Summary: ActiveMQServerControl.listAddresses() can fail with
NullPointerException
Key: ARTEMIS-1524
URL: https://issues.apache.org/jira/browse/ARTEMIS-1524
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Broker
Affects Versions: 2.4.0
Reporter: Pat Fox
Priority: Minor
race condition between ActiveMQServerControl.listAddresses() and
ActiveMQServerControl.deleteAddress() that can result in the following
NullPointerException
{code}
java.lang.NullPointerException: null
at
org.apache.activemq.artemis.core.management.impl.view.AddressView.toJson(Unknown
Source)
at
org.apache.activemq.artemis.core.management.impl.view.AddressView.toJson(Unknown
Source)
at
org.apache.activemq.artemis.core.management.impl.view.ActiveMQAbstractView.getResultsAsJson(ActiveMQAbstractView.java:68)
at
org.apache.activemq.artemis.core.management.impl.ActiveMQServerControlImpl.listAddresses(ActiveMQServerControlImpl.java:1743)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
{code}
The listAddresses() retrieves the list of addresses and then retrieves the
detail of each one to build the Json representation. If the deleteAddress()
happens between getting the list and retrieving the details - a
NullPointerException is thrown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1524) ActiveMQServerControl.listAddresses() can fail with NullPointerException
[
https://issues.apache.org/jira/browse/ARTEMIS-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265734#comment-16265734
]
Pat Fox commented on ARTEMIS-1524:
--
PR to follow
> ActiveMQServerControl.listAddresses() can fail with NullPointerException
>
>
> Key: ARTEMIS-1524
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1524
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.4.0
>Reporter: Pat Fox
>Priority: Minor
>
> race condition between ActiveMQServerControl.listAddresses() and
> ActiveMQServerControl.deleteAddress() that can result in the following
> NullPointerException
> {code}
> java.lang.NullPointerException: null
> at
> org.apache.activemq.artemis.core.management.impl.view.AddressView.toJson(Unknown
> Source)
> at
> org.apache.activemq.artemis.core.management.impl.view.AddressView.toJson(Unknown
> Source)
> at
> org.apache.activemq.artemis.core.management.impl.view.ActiveMQAbstractView.getResultsAsJson(ActiveMQAbstractView.java:68)
> at
> org.apache.activemq.artemis.core.management.impl.ActiveMQServerControlImpl.listAddresses(ActiveMQServerControlImpl.java:1743)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> {code}
> The listAddresses() retrieves the list of addresses and then retrieves the
> detail of each one to build the Json representation. If the deleteAddress()
> happens between getting the list and retrieving the details - a
> NullPointerException is thrown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ARTEMIS-1522) add date to timestamp in default logger
[
https://issues.apache.org/jira/browse/ARTEMIS-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pat Fox updated ARTEMIS-1522:
-
Description:
It would be good to include the date in the logging timestamp. I appreciate
this can be derived from the log file postfix but in scenarios where you are
only seeing snippets of log files or these log files are being manipulated
later; it makes it much easier if the date is printed with the log entry.
I understand people want to reduce log space but adding the date would avoid
any potential ambiguity.
current format
{code}
11:56:49,051 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server
is now live
{code}
Suggested new format
{code}
2017-11-24 15:24:11,803 INFO [org.apache.activemq.artemis.core.server]
AMQ221007: Server is now live
{code}
was:
It would be good to include the date in the logging timestamp. I appreciate
this can be derived from the log file prefix but in scenarios where you are
only seeing snippets of log files or these log files are being manipulated
later, it makes it much easier if the date is printed with the log entry.
I understand people want to reduce log space but adding the date would avoid
any potential ambiguity.
current format
{code}
11:56:49,051 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server
is now live
{code}
Suggested new format
{code}
2017-11-24 15:24:11,803 INFO [org.apache.activemq.artemis.core.server]
AMQ221007: Server is now live
{code}
> add date to timestamp in default logger
> ---
>
> Key: ARTEMIS-1522
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1522
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.4.0
>Reporter: Pat Fox
>Priority: Minor
>
> It would be good to include the date in the logging timestamp. I appreciate
> this can be derived from the log file postfix but in scenarios where you are
> only seeing snippets of log files or these log files are being manipulated
> later; it makes it much easier if the date is printed with the log entry.
> I understand people want to reduce log space but adding the date would avoid
> any potential ambiguity.
> current format
> {code}
> 11:56:49,051 INFO [org.apache.activemq.artemis.core.server] AMQ221007:
> Server is now live
> {code}
> Suggested new format
> {code}
> 2017-11-24 15:24:11,803 INFO [org.apache.activemq.artemis.core.server]
> AMQ221007: Server is now live
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1522) add date to timestamp in default logger
[
https://issues.apache.org/jira/browse/ARTEMIS-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265396#comment-16265396
]
Pat Fox commented on ARTEMIS-1522:
--
PR to follow
> add date to timestamp in default logger
> ---
>
> Key: ARTEMIS-1522
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1522
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.4.0
>Reporter: Pat Fox
>Priority: Minor
>
> It would be good to include the date in the logging timestamp. I appreciate
> this can be derived from the log file prefix but in scenarios where you are
> only seeing snippets of log files or these log files are being manipulated
> later, it makes it much easier if the date is printed with the log entry.
> I understand people want to reduce log space but adding the date would avoid
> any potential ambiguity.
> current format
> {code}
> 11:56:49,051 INFO [org.apache.activemq.artemis.core.server] AMQ221007:
> Server is now live
> {code}
> Suggested new format
> {code}
> 2017-11-24 15:24:11,803 INFO [org.apache.activemq.artemis.core.server]
> AMQ221007: Server is now live
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ARTEMIS-1522) add date to timestamp in default logger
Pat Fox created ARTEMIS-1522:
Summary: add date to timestamp in default logger
Key: ARTEMIS-1522
URL: https://issues.apache.org/jira/browse/ARTEMIS-1522
Project: ActiveMQ Artemis
Issue Type: Improvement
Components: Broker
Affects Versions: 2.4.0
Reporter: Pat Fox
Priority: Minor
It would be good to include the date in the logging timestamp. I appreciate
this can be derived from the log file prefix but in scenarios where you are
only seeing snippets of log files or these log files are being manipulated
later, it makes it much easier if the date is printed with the log entry.
I understand people want to reduce log space but adding the date would avoid
any potential ambiguity.
current format
{code}
11:56:49,051 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server
is now live
{code}
Suggested new format
{code}
2017-11-24 15:24:11,803 INFO [org.apache.activemq.artemis.core.server]
AMQ221007: Server is now live
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ARTEMIS-1520) Add connectionID to trace logging that deals with packet reading/writing
[ https://issues.apache.org/jira/browse/ARTEMIS-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Fox updated ARTEMIS-1520: - Affects Version/s: 2.4.0 Priority: Minor (was: Major) Description: There is some very good logging for tracking packet read/write operations in org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl and org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl .However it is difficult to distinguish which TCP connection a packet arrived on or was written to. It would be good to add a connection ID to that logging so it is easier to track the packet flow on an individual connection. Component/s: Broker > Add connectionID to trace logging that deals with packet reading/writing > - > > Key: ARTEMIS-1520 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1520 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.4.0 >Reporter: Pat Fox >Priority: Minor > > There is some very good logging for tracking packet read/write operations in > org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl > and org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl .However > it is difficult to distinguish which TCP connection a packet arrived on or > was written to. > It would be good to add a connection ID to that logging so it is easier to > track the packet flow on an individual connection. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1520) Add connectionID to trace logging that deals with packet reading/writing
[ https://issues.apache.org/jira/browse/ARTEMIS-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264341#comment-16264341 ] Pat Fox commented on ARTEMIS-1520: -- PR to follow > Add connectionID to trace logging that deals with packet reading/writing > - > > Key: ARTEMIS-1520 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1520 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.4.0 >Reporter: Pat Fox >Priority: Minor > > There is some very good logging for tracking packet read/write operations in > org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl > and org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl .However > it is difficult to distinguish which TCP connection a packet arrived on or > was written to. > It would be good to add a connection ID to that logging so it is easier to > track the packet flow on an individual connection. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ARTEMIS-1520) Add connectionID to trace logging that deals with packet reading/writing
Pat Fox created ARTEMIS-1520: Summary: Add connectionID to trace logging that deals with packet reading/writing Key: ARTEMIS-1520 URL: https://issues.apache.org/jira/browse/ARTEMIS-1520 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Pat Fox -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1502) [web console, address list] add memory size and paging info to the address list panel
[ https://issues.apache.org/jira/browse/ARTEMIS-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239997#comment-16239997 ] Pat Fox commented on ARTEMIS-1502: -- suggested implementation to follow in PR. > [web console, address list] add memory size and paging info to the address > list panel > -- > > Key: ARTEMIS-1502 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1502 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker, Web Console >Affects Versions: 2.4.0 >Reporter: Pat Fox >Priority: Minor > > In the webconsole where addresses are listed and can be filtered, it would be > nice to have the > addressMemorySize, isPaging, numberOfPages, BytesPerPage listed for each > address. > This would be useful as we could then filter on the above attributes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ARTEMIS-1502) [web console, address list] add memory size and paging info to the address list panel
Pat Fox created ARTEMIS-1502: Summary: [web console, address list] add memory size and paging info to the address list panel Key: ARTEMIS-1502 URL: https://issues.apache.org/jira/browse/ARTEMIS-1502 Project: ActiveMQ Artemis Issue Type: Improvement Components: Broker, Web Console Affects Versions: 2.4.0 Reporter: Pat Fox Priority: Minor In the webconsole where addresses are listed and can be filtered, it would be nice to have the addressMemorySize, isPaging, numberOfPages, BytesPerPage listed for each address. This would be useful as we could then filter on the above attributes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ARTEMIS-1436) update CLI StatQueue to allow greater_than/less_than operations
Pat Fox created ARTEMIS-1436: Summary: update CLI StatQueue to allow greater_than/less_than operations Key: ARTEMIS-1436 URL: https://issues.apache.org/jira/browse/ARTEMIS-1436 Project: ActiveMQ Artemis Issue Type: Improvement Components: Broker Affects Versions: 2.3.0 Reporter: Pat Fox Priority: Minor the cli command StatQueue should now allow greater_than/less_than in its operation filter. This exposes the added functionality of ARTEMIS-1423 to the CLI -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1433) expose total Address memory usage in JMX
[ https://issues.apache.org/jira/browse/ARTEMIS-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176519#comment-16176519 ] Pat Fox commented on ARTEMIS-1433: -- adding a pull request with a potential implementation > expose total Address memory usage in JMX > > > Key: ARTEMIS-1433 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1433 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.3.0 >Reporter: Pat Fox >Priority: Minor > > activemq 5.x had a MemoryPercentUsage attribute exposed on the broker MBean > which showed how much memory was being used by the broker destinations, as a > percentage of the overall memory. > Although the memory model in Artemis is different, I think it would still be > useful to see how much memory the addresses are using in total and also have > it expressed as a percentage of the global-max-size. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ARTEMIS-1433) expose total Address memory usage in JMX
Pat Fox created ARTEMIS-1433: Summary: expose total Address memory usage in JMX Key: ARTEMIS-1433 URL: https://issues.apache.org/jira/browse/ARTEMIS-1433 Project: ActiveMQ Artemis Issue Type: Improvement Components: Broker Affects Versions: 2.3.0 Reporter: Pat Fox Priority: Minor activemq 5.x had a MemoryPercentUsage attribute exposed on the broker MBean which showed how much memory was being used by the broker destinations, as a percentage of the overall memory. Although the memory model in Artemis is different, I think it would still be useful to see how much memory the addresses are using in total and also have it expressed as a percentage of the global-max-size. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1423) [ActiveMQServerControl.listQueues(), filtering ] add numeric filtering for ActiveMQServerControl.listQueues()
[ https://issues.apache.org/jira/browse/ARTEMIS-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168956#comment-16168956 ] Pat Fox commented on ARTEMIS-1423: -- adding a PR request with a suggested implementation > [ActiveMQServerControl.listQueues(), filtering ] add numeric filtering for > ActiveMQServerControl.listQueues() > -- > > Key: ARTEMIS-1423 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1423 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.3.0 >Reporter: Pat Fox >Priority: Minor > > At the moment ActiveMQServerControl.listQueues() filters results using > operation EQUALS and CONTAINS that carry out a string comparison on the > specified column. > It would by nice to allow the filter to work with a numeric comparison on the > columns that contain numeric value. Also to add GREATER_THAN and LESS_THAN > operations, this would allow queues such as "list queues with MessageCount > GREATER_THAN 1000" or "list queues with ConsumerCount LESS_THAN 2" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ARTEMIS-1423) [ActiveMQServerControl.listQueues(), filtering ] add numeric filtering for ActiveMQServerControl.listQueues()
Pat Fox created ARTEMIS-1423: Summary: [ActiveMQServerControl.listQueues(), filtering ] add numeric filtering for ActiveMQServerControl.listQueues() Key: ARTEMIS-1423 URL: https://issues.apache.org/jira/browse/ARTEMIS-1423 Project: ActiveMQ Artemis Issue Type: Improvement Components: Broker Affects Versions: 2.3.0 Reporter: Pat Fox Priority: Minor At the moment ActiveMQServerControl.listQueues() filters results using operation EQUALS and CONTAINS that carry out a string comparison on the specified column. It would by nice to allow the filter to work with a numeric comparison on the columns that contain numeric value. Also to add GREATER_THAN and LESS_THAN operations, this would allow queues such as "list queues with MessageCount GREATER_THAN 1000" or "list queues with ConsumerCount LESS_THAN 2" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1384) add a CLI command to display basic queue stats
[ https://issues.apache.org/jira/browse/ARTEMIS-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151609#comment-16151609 ] Pat Fox commented on ARTEMIS-1384: -- adding a PR for a suggested implementation. > add a CLI command to display basic queue stats > --- > > Key: ARTEMIS-1384 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1384 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.3.0 >Reporter: Pat Fox >Priority: Minor > > In activemq 5.x there is a command line tool (called dstat) that listed some > basic stats for queues/topics on the broker (current message count, current > number of consumers, number of enqueued messages, number of dequeued > messages). > This is very useful for troubleshooting as a quick way to check basic > destination stats or capture information if other management tools are not > available. > It would be good to have a similar command in the Artemis CLI that listed > minimal set of stats for each queue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ARTEMIS-1384) add a CLI command to display basic queue stats
Pat Fox created ARTEMIS-1384: Summary: add a CLI command to display basic queue stats Key: ARTEMIS-1384 URL: https://issues.apache.org/jira/browse/ARTEMIS-1384 Project: ActiveMQ Artemis Issue Type: Improvement Components: Broker Affects Versions: 2.3.0 Reporter: Pat Fox Priority: Minor In activemq 5.x there is a command line tool (called dstat) that listed some basic stats for queues/topics on the broker (current message count, current number of consumers, number of enqueued messages, number of dequeued messages). This is very useful for troubleshooting as a quick way to check basic destination stats or capture information if other management tools are not available. It would be good to have a similar command in the Artemis CLI that listed minimal set of stats for each queue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1381) add a JMX operation removeAllMessages() to the queue
[ https://issues.apache.org/jira/browse/ARTEMIS-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150654#comment-16150654 ] Pat Fox commented on ARTEMIS-1381: -- Thanks [~jbertram] > add a JMX operation removeAllMessages() to the queue > - > > Key: ARTEMIS-1381 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1381 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.3.0 >Reporter: Pat Fox >Priority: Minor > Fix For: 2.4.0 > > > it would be good to add a removeAllMessages() JMX operation to clear all > messages from the queue, to make it a little more intuitive in various JMX > browsers (such as jconsole) > removing all the messages can be achieved by passing "null" to the > removeMessages(String filter) operation but when using a JMX browser it is > not immediately obvious what filter to use. Also the default value for the > filter param using jconsole is "String", so you have to define the null > filter value explicitly -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ARTEMIS-1381) add a JMX operation removeAllMessages() to the queue
Pat Fox created ARTEMIS-1381: Summary: add a JMX operation removeAllMessages() to the queue Key: ARTEMIS-1381 URL: https://issues.apache.org/jira/browse/ARTEMIS-1381 Project: ActiveMQ Artemis Issue Type: Improvement Components: Broker Affects Versions: 2.3.0 Reporter: Pat Fox Priority: Minor it would be good to add a removeAllMessages() JMX operation to clear all messages from the queue, to make it a little more intuitive in various JMX browsers (such as jconsole) removing all the messages can be achieved by passing "null" to the removeMessages(String filter) operation but when using a JMX browser it is not immediately obvious what filter to use. Also the default value for the filter param using jconsole is "String", so you have to define the null filter value explicitly -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1381) add a JMX operation removeAllMessages() to the queue
[ https://issues.apache.org/jira/browse/ARTEMIS-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149637#comment-16149637 ] Pat Fox commented on ARTEMIS-1381: -- adding a pull request with suggested change now > add a JMX operation removeAllMessages() to the queue > - > > Key: ARTEMIS-1381 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1381 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.3.0 >Reporter: Pat Fox >Priority: Minor > > it would be good to add a removeAllMessages() JMX operation to clear all > messages from the queue, to make it a little more intuitive in various JMX > browsers (such as jconsole) > removing all the messages can be achieved by passing "null" to the > removeMessages(String filter) operation but when using a JMX browser it is > not immediately obvious what filter to use. Also the default value for the > filter param using jconsole is "String", so you have to define the null > filter value explicitly -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ARTEMIS-1370) consumer command, does not offer a ClientID command line arg
[
https://issues.apache.org/jira/browse/ARTEMIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pat Fox updated ARTEMIS-1370:
-
Summary: consumer command, does not offer a ClientID command line arg
(was: Artemis consumer command, does not offer a ClientID command line arg )
> consumer command, does not offer a ClientID command line arg
> -
>
> Key: ARTEMIS-1370
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1370
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.3.0
>Reporter: Pat Fox
>Priority: Minor
>
> using
> {code}
> ./artemis consumer --destination topic://myexample --durable
> {code}
> it gives me
> {code}
> javax.jms.IllegalStateException: Cannot create durable subscription - client
> ID has not been set
> at
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:746)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createDurableSubscriber(ActiveMQSession.java:484)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createDurableSubscriber(ActiveMQSession.java:458)
> at
> org.apache.activemq.artemis.cli.commands.messages.ConsumerThread.consume(ConsumerThread.java:140)
> at
> org.apache.activemq.artemis.cli.commands.messages.ConsumerThread.run(ConsumerThread.java:64)
> {code}
> There currently seems no command line option available to set a client id
> when running artemis consumer.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ARTEMIS-1370) Artemis consumer command, does not offer a ClientID command line arg
[
https://issues.apache.org/jira/browse/ARTEMIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pat Fox updated ARTEMIS-1370:
-
Summary: Artemis consumer command, does not offer a ClientID command line
arg (was: Artemis consumer command, does not accept a ClientID arg )
> Artemis consumer command, does not offer a ClientID command line arg
> -
>
> Key: ARTEMIS-1370
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1370
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.3.0
>Reporter: Pat Fox
>Priority: Minor
>
> using
> {code}
> ./artemis consumer --destination topic://myexample --durable
> {code}
> it gives me
> {code}
> javax.jms.IllegalStateException: Cannot create durable subscription - client
> ID has not been set
> at
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:746)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createDurableSubscriber(ActiveMQSession.java:484)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createDurableSubscriber(ActiveMQSession.java:458)
> at
> org.apache.activemq.artemis.cli.commands.messages.ConsumerThread.consume(ConsumerThread.java:140)
> at
> org.apache.activemq.artemis.cli.commands.messages.ConsumerThread.run(ConsumerThread.java:64)
> {code}
> There currently seems no command line option available to set a client id
> when running artemis consumer.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ARTEMIS-1370) Artemis consumer command, does not accept a ClientID arg
[
https://issues.apache.org/jira/browse/ARTEMIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138172#comment-16138172
]
Pat Fox commented on ARTEMIS-1370:
--
creating a PR now
> Artemis consumer command, does not accept a ClientID arg
> -
>
> Key: ARTEMIS-1370
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1370
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.3.0
>Reporter: Pat Fox
>Priority: Minor
>
> using
> {code}
> ./artemis consumer --destination topic://myexample --durable
> {code}
> it gives me
> {code}
> javax.jms.IllegalStateException: Cannot create durable subscription - client
> ID has not been set
> at
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:746)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createDurableSubscriber(ActiveMQSession.java:484)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createDurableSubscriber(ActiveMQSession.java:458)
> at
> org.apache.activemq.artemis.cli.commands.messages.ConsumerThread.consume(ConsumerThread.java:140)
> at
> org.apache.activemq.artemis.cli.commands.messages.ConsumerThread.run(ConsumerThread.java:64)
> {code}
> There currently seems no command line option available to set a client id
> when running artemis consumer.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ARTEMIS-1370) Artemis consumer command, does not accept a ClientID arg
Pat Fox created ARTEMIS-1370:
Summary: Artemis consumer command, does not accept a ClientID arg
Key: ARTEMIS-1370
URL: https://issues.apache.org/jira/browse/ARTEMIS-1370
Project: ActiveMQ Artemis
Issue Type: Improvement
Components: Broker
Affects Versions: 2.3.0
Reporter: Pat Fox
Priority: Minor
using
{code}
./artemis consumer --destination topic://myexample --durable
{code}
it gives me
{code}
javax.jms.IllegalStateException: Cannot create durable subscription - client ID
has not been set
at
org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:746)
at
org.apache.activemq.artemis.jms.client.ActiveMQSession.createDurableSubscriber(ActiveMQSession.java:484)
at
org.apache.activemq.artemis.jms.client.ActiveMQSession.createDurableSubscriber(ActiveMQSession.java:458)
at
org.apache.activemq.artemis.cli.commands.messages.ConsumerThread.consume(ConsumerThread.java:140)
at
org.apache.activemq.artemis.cli.commands.messages.ConsumerThread.run(ConsumerThread.java:64)
{code}
There currently seems no command line option available to set a client id when
running artemis consumer.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
