[jira] [Commented] (ARTEMIS-2841) Global TTL and/or exact xxpiry time for a broker/address
[
https://issues.apache.org/jira/browse/ARTEMIS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155015#comment-17155015
]
Justin Bertram commented on ARTEMIS-2841:
-
This may have been closed by mistake as part of the 2.14.0 release process.
In any event, I think some of what you want is already possible using the
{{expiry-delay}} address setting. Using this setting the broker can apply a
TTL/expiry delay on any incoming message that doesn't already have a TTL/expiry
value set. There's also the {{min-expiry-delay}} and {{max-expiry-delay}} which
you can use to change the value of the TTL/expiry delay on messages which
already have one set. Read more about this in [the
documentation|http://activemq.apache.org/components/artemis/documentation/latest/message-expiry.html].
That said, there is no option to set an absolute expiration time (e.g. all
messages expire at midnight).
> Global TTL and/or exact xxpiry time for a broker/address
>
>
> Key: ARTEMIS-2841
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2841
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
>Affects Versions: 2.14.0
>Reporter: obby
>Priority: Major
> Labels: features
> Fix For: 2.15.0
>
>
> In certain application logic and business requirements I have come across,
> there has been a need to have a global TTL or set time for expiry of all
> messages in a broker or address. one use case was that at midnight, all
> messages should expire and not be sent. Another use case was that every
> message would have a set ttl (8 hours). This is all achievable currently from
> application by setting the expiry time or expiration delay for a message in
> the the producer. But it would really be helpful if there was an option to
> set the same at address/broker level.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2841) Global TTL and/or exact xxpiry time for a broker/address
[ https://issues.apache.org/jira/browse/ARTEMIS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155014#comment-17155014 ] Clebert Suconic commented on ARTEMIS-2841: -- I closed it by accident during the release report.. sorry about that. We have address settings already. I think we already have such thing. > Global TTL and/or exact xxpiry time for a broker/address > > > Key: ARTEMIS-2841 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2841 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 2.14.0 >Reporter: obby >Priority: Major > Labels: features > Fix For: 2.14.0 > > > In certain application logic and business requirements I have come across, > there has been a need to have a global TTL or set time for expiry of all > messages in a broker or address. one use case was that at midnight, all > messages should expire and not be sent. Another use case was that every > message would have a set ttl (8 hours). This is all achievable currently from > application by setting the expiry time or expiration delay for a message in > the the producer. But it would really be helpful if there was an option to > set the same at address/broker level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (ARTEMIS-2841) Global TTL and/or exact xxpiry time for a broker/address
[ https://issues.apache.org/jira/browse/ARTEMIS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic reopened ARTEMIS-2841: -- > Global TTL and/or exact xxpiry time for a broker/address > > > Key: ARTEMIS-2841 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2841 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 2.14.0 >Reporter: obby >Priority: Major > Labels: features > Fix For: 2.14.0 > > > In certain application logic and business requirements I have come across, > there has been a need to have a global TTL or set time for expiry of all > messages in a broker or address. one use case was that at midnight, all > messages should expire and not be sent. Another use case was that every > message would have a set ttl (8 hours). This is all achievable currently from > application by setting the expiry time or expiration delay for a message in > the the producer. But it would really be helpful if there was an option to > set the same at address/broker level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2841) Global TTL and/or exact xxpiry time for a broker/address
[ https://issues.apache.org/jira/browse/ARTEMIS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic updated ARTEMIS-2841: - Fix Version/s: (was: 2.14.0) 2.15.0 > Global TTL and/or exact xxpiry time for a broker/address > > > Key: ARTEMIS-2841 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2841 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 2.14.0 >Reporter: obby >Priority: Major > Labels: features > Fix For: 2.15.0 > > > In certain application logic and business requirements I have come across, > there has been a need to have a global TTL or set time for expiry of all > messages in a broker or address. one use case was that at midnight, all > messages should expire and not be sent. Another use case was that every > message would have a set ttl (8 hours). This is all achievable currently from > application by setting the expiry time or expiration delay for a message in > the the producer. But it would really be helpful if there was an option to > set the same at address/broker level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2841) Global TTL and/or exact xxpiry time for a broker/address
[ https://issues.apache.org/jira/browse/ARTEMIS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154993#comment-17154993 ] obby commented on ARTEMIS-2841: --- no comment by closer? > Global TTL and/or exact xxpiry time for a broker/address > > > Key: ARTEMIS-2841 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2841 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 2.14.0 >Reporter: obby >Priority: Major > Labels: features > Fix For: 2.14.0 > > > In certain application logic and business requirements I have come across, > there has been a need to have a global TTL or set time for expiry of all > messages in a broker or address. one use case was that at midnight, all > messages should expire and not be sent. Another use case was that every > message would have a set ttl (8 hours). This is all achievable currently from > application by setting the expiry time or expiration delay for a message in > the the producer. But it would really be helpful if there was an option to > set the same at address/broker level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2815) Null pointer exception on queue update
[
https://issues.apache.org/jira/browse/ARTEMIS-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-2815.
> Null pointer exception on queue update
> --
>
> Key: ARTEMIS-2815
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2815
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.13.0
>Reporter: Krzysztof Porębski
>Assignee: Krzysztof Porębski
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Null pointer exception is thrown on the attempt to update a queue created
> without a filter.
> The problem is with getQueueConfiguration method in QueueImpl class. There is
> no check if filter is null before getFilterString is invoked.
> {code:java}
> @Override
> public QueueConfiguration getQueueConfiguration() {
>return new QueueConfiguration(name)
> .setAddress(address)
> .setId(id)
> .setRoutingType(routingType)
> .setFilterString(filter.getFilterString())
> .setDurable(isDurable())
> .setUser(user)
> .setMaxConsumers(maxConsumers)
> .setExclusive(exclusive)
> .setGroupRebalance(groupRebalance)
> .setGroupBuckets(groupBuckets)
> .setGroupFirstKey(groupFirstKey)
> .setLastValue(false)
> .setLastValue(null)
> .setNonDestructive(nonDestructive)
> .setPurgeOnNoConsumers(purgeOnNoConsumers)
> .setConsumersBeforeDispatch(consumersBeforeDispatch)
> .setDelayBeforeDispatch(delayBeforeDispatch)
> .setAutoDelete(autoDelete)
> .setAutoDeleteDelay(autoDeleteDelay)
> .setAutoDeleteMessageCount(autoDeleteMessageCount)
> .setRingSize(ringSize)
> .setConfigurationManaged(configurationManaged)
> .setTemporary(temporary)
> .setInternal(internalQueue)
> .setTransient(refCountForConsumers instanceof TransientQueueManagerImpl)
> .setAutoCreated(autoCreated);
> }{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2771) Support JVM GC & thread metrics
[ https://issues.apache.org/jira/browse/ARTEMIS-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2771. > Support JVM GC & thread metrics > --- > > Key: ARTEMIS-2771 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2771 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.14.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2783) User not set on shared queue
[ https://issues.apache.org/jira/browse/ARTEMIS-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2783. > User not set on shared queue > > > Key: ARTEMIS-2783 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2783 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.13.0 >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2798) Expiration for AMQP messages not properly reloaded
[
https://issues.apache.org/jira/browse/ARTEMIS-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-2798.
> Expiration for AMQP messages not properly reloaded
> --
>
> Key: ARTEMIS-2798
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2798
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.13.0
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{expiration}} data for AMQP messages is not properly reloaded after a
> broker restart which means that messages which should expire won't actually
> expire.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2778) AcceptorControl returns only transport parameters
[ https://issues.apache.org/jira/browse/ARTEMIS-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2778. > AcceptorControl returns only transport parameters > - > > Key: ARTEMIS-2778 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2778 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.14.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The AcceptorControl returns only transport parameters and it doesn't return > the protocol parameters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2806) deployQueue missing address argument
[ https://issues.apache.org/jira/browse/ARTEMIS-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2806. > deployQueue missing address argument > > > Key: ARTEMIS-2806 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2806 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.12.0 >Reporter: Qihong Xu >Priority: Minor > Fix For: 2.14.0 > > Time Spent: 50m > Remaining Estimate: 0h > > In ActiveMQServerControlImpl, deployQueue method is missing address argument > which results in creating non-matched addresses and queues. (For example, > using deployQueue to create a subscriber A_0 under existing address A, it > finally returns a new topic A_0 with a subscriber A_0 ) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2769) NumberFormatException
[
https://issues.apache.org/jira/browse/ARTEMIS-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-2769.
> NumberFormatException
> ---
>
> Key: ARTEMIS-2769
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2769
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.12.0, 2.13.0
>Reporter: Todor Neykov
>Assignee: Clebert Suconic
>Priority: Minor
> Labels: easyfix
> Fix For: 2.14.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Hi,
> I found an issue in ConfigurationHelper.getIntProperty()
> If there is a String propery but not a numeric value it lead to
> NumberFormatException.
> My expectation in this case is to be returned a default value instead of
> exception.
> The code is
> {code:java}
> if (prop instanceof String) {
> return Integer.valueOf((String) prop);
> } else ...
>
> {code}
> Fix proposal :
> {code:java}
> if (prop instanceof String)
> {
> try
> {
> return Integer.valueOf((String)prop);
> }
> catch (NumberFormatException e)
> {
> ActiveMQClientLogger.LOGGER.propertyNotInteger(propName,
> prop.getClass().getName());
> return def;
> }
> }
> else ...
> {code}
> Same case is in getLongProperty()
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2799) sniHost property not allowed
[
https://issues.apache.org/jira/browse/ARTEMIS-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-2799.
> sniHost property not allowed
>
>
> Key: ARTEMIS-2799
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2799
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.14.0
>
>
> In the documentation {{sniHost}} is described as an option for a
> {{connector}} or {{acceptor}}. In the {{CoreClientOverOneWaySSLTest}} this is
> also tested. However, the {{sniHost}} is not in the allowable acceptor and
> connector keys. Setting it via the {{broker.xml}} is therefore not possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2781) Return only local queue names for AddressControl.getQueueNames()
[
https://issues.apache.org/jira/browse/ARTEMIS-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-2781.
> Return only local queue names for AddressControl.getQueueNames()
>
>
> Key: ARTEMIS-2781
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2781
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> There is a discrepancy between what {{AddressControl.getQueueNames()}}
> returns and what {{ActiveMQServerControl.getQueueNames()}} returns. The
> former returns the names of both local and remote queue bindings whereas the
> latter only returns the names of local queue bindings. This is confusing for
> users. They return values should be consistent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2776) Dockerfile improvements to startup arguments
[ https://issues.apache.org/jira/browse/ARTEMIS-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2776. > Dockerfile improvements to startup arguments > > > Key: ARTEMIS-2776 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2776 > Project: ActiveMQ Artemis > Issue Type: Improvement > Environment: Windows 10 running scripts in WSL >Reporter: Zeke Rogers >Priority: Minor > Fix For: 2.14.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The current Dockerfiles for Ubuntu and CentOS contain an environment variable > ANONYMOUS_LOGIN that is not actually being used, resulting in anonymous > logins always being allowed. > In addition, the options "--http-host 0.0.0.0 --relax-jolokia" are included > by default, and overriding them would also require putting the username and > password in the entire CREATE_ARGUMENTS environment variable, making the > previous ARTEMIS_USER and ARTEMIS_PASSWORD variables moot. > This could be made easier to add extra options without having to re-specify > the username and the password. This is especially true in environments where > a secrets file may be used for usernames/passwords (such as Kubernetes) but > the rest of the args can be in plain text. In this scenario, having the > username and password as separate envrionment variables from the other > arguments is very beneficial. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2809) Retain public access to api's used by activemq-cli-tools around xml import/export
[ https://issues.apache.org/jira/browse/ARTEMIS-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2809. > Retain public access to api's used by activemq-cli-tools around xml > import/export > - > > Key: ARTEMIS-2809 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2809 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: API >Affects Versions: 2.13.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Labels: activemq-cli-tools > Fix For: 2.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > > [activemq-cli-tools|https://github.com/apache/activemq-cli-tools] produces > xml from kahadb that can be imported by artemis. > the current code 0.1.0 base builds against 2.2 but some of the dependencies > have been refactored away (made package private) in subsequent versions. > To have it build with the latest version we have to revert the package > private or have duplicate code. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2109) enable building Artemis with JDK 11+
[ https://issues.apache.org/jira/browse/ARTEMIS-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2109. > enable building Artemis with JDK 11+ > > > Key: ARTEMIS-2109 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2109 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.13.0 >Reporter: Miroslav Novak >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.14.0 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > Artemis requires using JDK8 to build (not run), and cannot be built on JDK > 11+. To ease mixing and matching in particular development environments it > would be good to enable building with 11+ also. > This Jira will enable building with JDK8, or 11+. In the JDK8 case the build > will target Java 8 as always, and JDK8 will still be required for building > releases. In the JDK 11+ case the build will currently target Java 11. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2795) update to proton-j 0.33.5 and qpid-jms 0.52.0
[ https://issues.apache.org/jira/browse/ARTEMIS-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2795. > update to proton-j 0.33.5 and qpid-jms 0.52.0 > - > > Key: ARTEMIS-2795 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2795 > Project: ActiveMQ Artemis > Issue Type: Task > Components: AMQP >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > > update to proton-j 0.33.5 and qpid-jms 0.52.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2821) AWS load balancer health check causes log entries 224088 with every check
[ https://issues.apache.org/jira/browse/ARTEMIS-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2821. > AWS load balancer health check causes log entries 224088 with every check > - > > Key: ARTEMIS-2821 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2821 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.13.0 >Reporter: Bas >Priority: Minor > Fix For: 2.14.0 > > > Hi, > > When using health checks from an AWS load balancer which opens a connection > to the opened artemis port, we get log entries mentioning code 224088 with > every health check. > The connection are being closed by the load balancer but there is no > implementation of channelInactive so this case is not handled properly. In > the end the connection is closed but it also logs 224088. > Fix is to handle channelinactive and cancel the future which closes the netty > channel. It is not necessary to close this channel because netty is already > telling you the channel is closed. > > See pull request: [https://github.com/apache/activemq-artemis/pull/3196] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2830) NPE in XML exporter
[
https://issues.apache.org/jira/browse/ARTEMIS-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-2830.
> NPE in XML exporter
> ---
>
> Key: ARTEMIS-2830
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2830
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It's sometimes possible for there to be acks in the journal for messages
> which aren't actually in the journal any more. In this situation you would
> likely see messages like this in the log when starting the broker:
> {noformat}
> 2020-06-24 10:28:08,630 ERROR [org.apache.activemq.artemis.core.server]
> AMQ224009: Cannot find message 20,491,425
> 2020-06-24 10:28:08,630 ERROR [org.apache.activemq.artemis.core.server]
> AMQ224010: Cannot find queue messages for queueID=996 on ack for
> messageID=20,491,432
> {noformat}
> If you run the {{data exp}} command to export the journal in this condition
> you'll hit a {{NullPointerException}}:
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.activemq.artemis.cli.commands.tools.xml.XmlDataExporter.removeAcked(XmlDataExporter.java:279)
> at
> org.apache.activemq.artemis.cli.commands.tools.xml.XmlDataExporter.processMessageJournal(XmlDataExporter.java:267)
> at
> org.apache.activemq.artemis.cli.commands.tools.xml.XmlDataExporter.writeXMLData(XmlDataExporter.java:149)
> at
> org.apache.activemq.artemis.cli.commands.tools.xml.XmlDataExporter.writeOutput(XmlDataExporter.java:143)
> at
> org.apache.activemq.artemis.cli.commands.tools.xml.XmlDataExporter.process(XmlDataExporter.java:132)
> at
> org.apache.activemq.artemis.cli.commands.tools.xml.XmlDataExporter.execute(XmlDataExporter.java:99)
> at org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:150)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2797) Reset queue properties by unsetting them in broker.xml
[ https://issues.apache.org/jira/browse/ARTEMIS-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2797. > Reset queue properties by unsetting them in broker.xml > -- > > Key: ARTEMIS-2797 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2797 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.13.0 >Reporter: Jan Šmucr >Priority: Major > Labels: pull-request-available > Fix For: 2.14.0 > > Time Spent: 8h 10m > Remaining Estimate: 0h > > Currently the queue properties cannot be removed because of property new > value null checks leading to quitting the PostOfficeImpl#updateQueue() > instead of resetting the properties to their default values. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2790) No examples documentation in the bin archive
[ https://issues.apache.org/jira/browse/ARTEMIS-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2790. > No examples documentation in the bin archive > > > Key: ARTEMIS-2790 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2790 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Domenico Francesco Bruscino >Priority: Minor > Fix For: 2.14.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The documentation of the examples is generated during release but it isn't > copied in the bin archive during release because of the build order. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2805) Wrong day-of-month in web console
[ https://issues.apache.org/jira/browse/ARTEMIS-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2805. > Wrong day-of-month in web console > - > > Key: ARTEMIS-2805 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2805 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.14.0 > > > The web console displays the day of the _week_ instead of the day of the > month in the timestamp column while browsing a queue from the web console. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2789) Fix memory estimage for AMQP Large Message
[ https://issues.apache.org/jira/browse/ARTEMIS-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2789. > Fix memory estimage for AMQP Large Message > -- > > Key: ARTEMIS-2789 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2789 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > > There's a memory estimate into AMQP Large Message that's currently returning > 0. > > Unfortunately there's no way to test this. This is just an estimate. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (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 ] Clebert Suconic closed ARTEMIS-2793. > 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 > Fix For: 2.14.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > we should probably log something different so users know no voting occured -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2810) Support all address-settings via management
[
https://issues.apache.org/jira/browse/ARTEMIS-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-2810.
> Support all address-settings via management
> ---
>
> Key: ARTEMIS-2810
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2810
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently not all address-settings (e.g. {{min-expiry-delay}},
> {{max-expiry-delay}}, {{enable-metrics}}) can be set and/or retrieved via
> management.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2836) Console diagram view contains broken destination links and raw tool tips
[ https://issues.apache.org/jira/browse/ARTEMIS-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2836. > Console diagram view contains broken destination links and raw tool tips > > > Key: ARTEMIS-2836 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2836 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Web Console >Affects Versions: 2.13.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.14.0 > > > The destination links in the node view don't work and there is verbose > logging of the json returned from the broker. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2774) Remove the divert transformer on divert destroying
[ https://issues.apache.org/jira/browse/ARTEMIS-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2774. > Remove the divert transformer on divert destroying > -- > > Key: ARTEMIS-2774 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2774 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The divert's transformer is added automatically when the divert is created > but it is not removed when the divert is destroyed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2791) ArrayIndexOutOfBoundsException in SSLContextFactoryProvider
[
https://issues.apache.org/jira/browse/ARTEMIS-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-2791.
> ArrayIndexOutOfBoundsException in SSLContextFactoryProvider
> ---
>
> Key: ARTEMIS-2791
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2791
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.13.0
> Environment: Artemis 2.13.0 running in Karaf 4.2.8
>Reporter: Rico Neubauer
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Hi,
> updated from 2.12.0 to 2.13.0 and new class
> {{org.apache.activemq.artemis.spi.core.remoting.ssl.SSLContextFactoryProvider}}
> introduced with ARTEMIS-2704 produces an {{ArrayIndexOutOfBoundsException}}
> on shutdown:
> {code}
> ERROR org.apache.activemq.artemis.core.server FelixStartLevel
> [org.apache.activemq.artemis-server-osgi:2.13.0.SEE1]
>AMQ224068: Unable to stop component:
> org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl
> java.lang.ExceptionInInitializerError: null
> at
> org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl.stop(RemotingServiceImpl.java:384)
> ~[?:?]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:1153)
> ~[?:?]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:1031)
> ~[?:?]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:876)
> ~[?:?]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:870)
> ~[?:?]
> at
> org.apache.activemq.artemis.osgi.OsgiBroker$ServerTrackerCallBackImpl.stop(OsgiBroker.java:242)
> ~[?:?]
> at
> org.apache.activemq.artemis.osgi.ProtocolTracker.protocolRemoved(ProtocolTracker.java:122)
> ~[?:?]
> at
> org.apache.activemq.artemis.osgi.ProtocolTracker.removedService(ProtocolTracker.java:94)
> ~[?:?]
> at
> org.apache.activemq.artemis.osgi.ProtocolTracker.removedService(ProtocolTracker.java:38)
> ~[?:?]
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:967)
> ~[osgi.core-6.0.0.jar:?]
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:870)
> ~[osgi.core-6.0.0.jar:?]
> at
> org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
> ~[osgi.core-6.0.0.jar:?]
> at org.osgi.util.tracker.ServiceTracker.close(ServiceTracker.java:377)
> ~[osgi.core-6.0.0.jar:?]
> at
> org.apache.activemq.artemis.osgi.OsgiBroker.stop(OsgiBroker.java:147) ~[?:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_242]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_242]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_242]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_242]
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invokeMethod(BaseMethod.java:228)
> ~[?:?]
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.access$500(BaseMethod.java:41)
> ~[?:?]
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod$Resolved.invoke(BaseMethod.java:664)
> ~[?:?]
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invoke(BaseMethod.java:510)
> ~[?:?]
> at
> org.apache.felix.scr.impl.inject.methods.ActivateMethod.invoke(ActivateMethod.java:317)
> ~[?:?]
> at
> org.apache.felix.scr.impl.inject.methods.ActivateMethod.invoke(ActivateMethod.java:307)
> ~[?:?]
> at
> org.apache.felix.scr.impl.manager.SingleComponentManager.disposeImplementationObject(SingleComponentManager.java:407)
> ~[?:?]
> at
> org.apache.felix.scr.impl.manager.SingleComponentManager.deleteComponent(SingleComponentManager.java:163)
> ~[?:?]
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.doDeactivate(AbstractComponentManager.java:831)
> ~[?:?]
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.deactivateInternal(AbstractComponentManager.java:805)
> ~[?:?]
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.dispose(AbstractComponentManager.java:584)
> ~[?:?]
> at
> org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.disposeComponents(ConfigurableComponentHolder.java:716)
> ~[?:?]
> at
> org.apache.felix.scr.impl.BundleComponentActivator.dispose(BundleComponentActivator.java:510)
> ~[?:?]
> at
> org.apache.felix.scr.impl
[jira] [Closed] (ARTEMIS-2787) Allow a queue to be disabled, so that messages are not routed to it.
[ https://issues.apache.org/jira/browse/ARTEMIS-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2787. > Allow a queue to be disabled, so that messages are not routed to it. > > > Key: ARTEMIS-2787 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2787 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Reporter: Michael Andre Pearce >Priority: Major > Fix For: 2.14.0 > > Time Spent: 7h 40m > Remaining Estimate: 0h > > There are a number of scenarios where it can be useful to disable a queue, so > messages are not routed to it. > 1) An issue that requires investigation but you wish to keep the consumers > active, but do not wish to have message build up on the broker > > 2) you want to connect consumers to a address, but you do not wish the flow > to start and wish to manage the enablement and disablement centrally. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2788) OpenWire producerId leak in session state
[ https://issues.apache.org/jira/browse/ARTEMIS-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2788. > OpenWire producerId leak in session state > - > > Key: ARTEMIS-2788 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2788 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: OpenWire >Affects Versions: 2.13.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.14.0 > > Time Spent: 50m > Remaining Estimate: 0h > > A session that loops creating and closing producers will demonstrate a leak > in the sessionState of the openwire connection, unchecked it can lead to OOM -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2786) Timestamp in console is incorrect
[ https://issues.apache.org/jira/browse/ARTEMIS-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2786. > 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 > Fix For: 2.14.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > 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] [Closed] (ARTEMIS-2807) Avoid notifications on critical IO error
[
https://issues.apache.org/jira/browse/ARTEMIS-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-2807.
> Avoid notifications on critical IO error
>
>
> Key: ARTEMIS-2807
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2807
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When the broker hits a "critical" IO error it will shut itself down. However,
> during the shutdown process multiple notifications are sent. These
> notifications trigger disk IO which can delay (and potentially hang)
> shutdown. Here's an example from a thread-dump from a broker hung in shutdown:
>
> {noformat}
> "Thread-11" #73 prio=5 os_prio=0 tid=0x7fa3fc002800 nid=0x1907 waiting on
> condition [0x7fa48d60d000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x9b1055f0> (a
> java.util.concurrent.CountDownLatch$Sync)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
> at
> org.apache.activemq.artemis.core.journal.impl.SimpleWaitIOCallback.waitCompletion(SimpleWaitIOCallback.java:61)
> at
> org.apache.activemq.artemis.core.journal.impl.JournalBase.appendAddRecord(JournalBase.java:52)
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendAddRecord(JournalImpl.java:93)
> at
> org.apache.activemq.artemis.core.journal.Journal.appendAddRecord(Journal.java:65)
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.storeID(AbstractJournalStorageManager.java:805)
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.BatchingIDGenerator.storeID(BatchingIDGenerator.java:147)
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.BatchingIDGenerator.saveCheckPoint(BatchingIDGenerator.java:132)
> - locked <0x90f23850> (a
> org.apache.activemq.artemis.core.persistence.impl.journal.BatchingIDGenerator)
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.BatchingIDGenerator.generateID(BatchingIDGenerator.java:111)
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.generateID(AbstractJournalStorageManager.java:334)
> at
> org.apache.activemq.artemis.core.server.management.impl.ManagementServiceImpl.sendNotification(ManagementServiceImpl.java:678)
> - locked <0x90b0ab20> (a java.lang.Object)
> - locked <0x90f21550> (a
> org.apache.activemq.artemis.core.server.management.impl.ManagementServiceImpl)
> at
> org.apache.activemq.artemis.core.server.cluster.impl.BroadcastGroupImpl.stop(BroadcastGroupImpl.java:142)
> - locked <0x90b0b650> (a
> org.apache.activemq.artemis.core.server.cluster.impl.BroadcastGroupImpl)
> at
> org.apache.activemq.artemis.core.server.cluster.ClusterManager.stop(ClusterManager.java:310)
> - locked <0x90b0b508> (a
> org.apache.activemq.artemis.core.server.cluster.ClusterManager)
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stopComponent(ActiveMQServerImpl.java:1355)
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:1090)
> - locked <0x90f1d128> (a
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl)
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:1054)
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5.run(ActiveMQServerImpl.java:860)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2841) Global TTL and/or exact xxpiry time for a broker/address
[ https://issues.apache.org/jira/browse/ARTEMIS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2841. Resolution: Fixed > Global TTL and/or exact xxpiry time for a broker/address > > > Key: ARTEMIS-2841 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2841 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 2.14.0 >Reporter: obby >Priority: Major > Labels: features > Fix For: 2.14.0 > > > In certain application logic and business requirements I have come across, > there has been a need to have a global TTL or set time for expiry of all > messages in a broker or address. one use case was that at midnight, all > messages should expire and not be sent. Another use case was that every > message would have a set ttl (8 hours). This is all achievable currently from > application by setting the expiry time or expiration delay for a message in > the the producer. But it would really be helpful if there was an option to > set the same at address/broker level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2841) Global TTL and/or exact xxpiry time for a broker/address
obby created ARTEMIS-2841: - Summary: Global TTL and/or exact xxpiry time for a broker/address Key: ARTEMIS-2841 URL: https://issues.apache.org/jira/browse/ARTEMIS-2841 Project: ActiveMQ Artemis Issue Type: New Feature Components: Broker Affects Versions: 2.14.0 Reporter: obby Fix For: 2.14.0 In certain application logic and business requirements I have come across, there has been a need to have a global TTL or set time for expiry of all messages in a broker or address. one use case was that at midnight, all messages should expire and not be sent. Another use case was that every message would have a set ttl (8 hours). This is all achievable currently from application by setting the expiry time or expiration delay for a message in the the producer. But it would really be helpful if there was an option to set the same at address/broker level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2620) Avoid Exception on client when large message file corrupted
[ https://issues.apache.org/jira/browse/ARTEMIS-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic updated ARTEMIS-2620: - Fix Version/s: (was: 2.14.0) 2.15.0 > Avoid Exception on client when large message file corrupted > --- > > Key: ARTEMIS-2620 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2620 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.11.0 >Reporter: Howard Gao >Assignee: Howard Gao >Priority: Major > Fix For: 2.15.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The broker should be more resilient so that it can avoid throwing an > exception on the client side when it encounters an invalid or empty large > message file(corrupted for any reason). It would be better to deal with it > within the broker and not allow the issue to manifest itself on the consuming > client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ARTEMIS-2804) Human readable timestamp is incorrectly parsed in web console
[ https://issues.apache.org/jira/browse/ARTEMIS-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-2804. Resolution: Fixed > Human readable timestamp is incorrectly parsed in web console > - > > Key: ARTEMIS-2804 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2804 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Web Console >Affects Versions: 2.13.0 >Reporter: Avinash Dongre >Priority: Minor > Labels: pull-request-available > Fix For: 2.14.0 > > Attachments: incorrect_timestamp.PNG > > Time Spent: 1h > Remaining Estimate: 0h > > When a queue is browsed using the web console, the DAY is incorrect in the > human-readable timestamp. Please see the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2840) Missing AddressControl audit logging
[
https://issues.apache.org/jira/browse/ARTEMIS-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-2840:
Description: The {{pause}} and {{resume}} operations do not log the
success/failure of the operation to the audit log.
> Missing AddressControl audit logging
>
>
> Key: ARTEMIS-2840
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2840
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
>
> The {{pause}} and {{resume}} operations do not log the success/failure of the
> operation to the audit log.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ARTEMIS-2840) Missing AddressControl audit logging
Justin Bertram created ARTEMIS-2840: --- Summary: Missing AddressControl audit logging Key: ARTEMIS-2840 URL: https://issues.apache.org/jira/browse/ARTEMIS-2840 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Justin Bertram Assignee: Justin Bertram -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2839) Audit logging typo for resuming queue
Justin Bertram created ARTEMIS-2839: --- Summary: Audit logging typo for resuming queue Key: ARTEMIS-2839 URL: https://issues.apache.org/jira/browse/ARTEMIS-2839 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Justin Bertram Assignee: Justin Bertram -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2837) Bursts of open files under high load
[ https://issues.apache.org/jira/browse/ARTEMIS-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154500#comment-17154500 ] ASF subversion and git services commented on ARTEMIS-2837: -- Commit 1761f76308010ee2f0862392575185026215223f in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=1761f76 ] ARTEMIS-2837 Avoiding bursts on writes and pending callbacks > Bursts of open files under high load > > > Key: ARTEMIS-2837 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2837 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.13.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.14.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2837) Bursts of open files under high load
[ https://issues.apache.org/jira/browse/ARTEMIS-2837?focusedWorklogId=456577&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-456577 ] ASF GitHub Bot logged work on ARTEMIS-2837: --- Author: ASF GitHub Bot Created on: 09/Jul/20 12:31 Start Date: 09/Jul/20 12:31 Worklog Time Spent: 10m Work Description: asfgit merged pull request #3214: URL: https://github.com/apache/activemq-artemis/pull/3214 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 456577) Time Spent: 0.5h (was: 20m) > Bursts of open files under high load > > > Key: ARTEMIS-2837 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2837 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.13.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.14.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2837) Bursts of open files under high load
[ https://issues.apache.org/jira/browse/ARTEMIS-2837?focusedWorklogId=456576&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-456576 ] ASF GitHub Bot logged work on ARTEMIS-2837: --- Author: ASF GitHub Bot Created on: 09/Jul/20 12:31 Start Date: 09/Jul/20 12:31 Worklog Time Spent: 10m Work Description: asfgit closed pull request #3214: URL: https://github.com/apache/activemq-artemis/pull/3214 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 456576) Time Spent: 20m (was: 10m) > Bursts of open files under high load > > > Key: ARTEMIS-2837 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2837 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.13.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2823) Improve JDBC connection management
[ https://issues.apache.org/jira/browse/ARTEMIS-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154430#comment-17154430 ] Mikko commented on ARTEMIS-2823: Submitted a pull request last week: [https://github.com/apache/activemq-artemis/pull/3204] > Improve JDBC connection management > -- > > Key: ARTEMIS-2823 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2823 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Reporter: Mikko >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > I have a case where the whole clustering reliability and HA must rely on HA > capabilities of clustered database, and running on top of application server > is not an option. > The current JDBC store implementation is rather bare bones on the connection > management side. JDBC driver is used directly with no management layer. At > startup, the broker just opens couple of direct connections to database and > expects them to be available forever. This is something that cannot be > expected in HA production environment. So, similarly to the discussion linked > below, in our case we lose the db connection after one hour, and all the > brokers need to be restared to get new connections: > [http://activemq.2283324.n4.nabble.com/Artemis-does-not-reconnect-to-MySQL-after-connection-timeout-td4751956.html] > > This is something that could be resolved by simply using JDBC4 isValid > checks, but proper connection handling and pooling through datasource would > be preferrable. > I have implemented a solution for this by using DBCP2 datasource. Our test > cluster has been successfully running this forked version since the release > of Artemis 2.13.0. I will prepare of pull request if this is seen to be > something that can be useful. -- 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)
