[jira] [Commented] (ARTEMIS-2446) AMQP message transmission with UUID properties fails
[
https://issues.apache.org/jira/browse/ARTEMIS-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17571596#comment-17571596
]
Erwin Dondorp commented on ARTEMIS-2446:
[~kohtala]
I'm interested in anything related to AMQP.
The 2 related "caused-by" issues are closed.
Do you know whether that also solved the problem that you reported in this
issue?
(I know it has been a while...)
This may save me some time as I otherwise may try to reproduce this.
> AMQP message transmission with UUID properties fails
>
>
> Key: ARTEMIS-2446
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2446
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.9.0
> Environment: I run the broker in a Docker container created based on
> [https://github.com/vromero/activemq-artemis-docker.] It is based on
> openjdk:8u222-jdk-stretch image. I've removed the etc and etc-override
> volumes, removed the excess protocol jars, added guest login.
>Reporter: Marko Kohtala
>Priority: Major
>
> I have an application using AMQP messaging and it works with ActiveMQ Artemis
> for small messages, but is failing for larger messages with error:
>
> {noformat}
> 2019-08-06T06:47:01.793175725Z Calculating performance journal ...
> 2019-08-06T06:47:22.324883428Z 144000
> 2019-08-06T06:47:33.378573751Z _ _ _
> 2019-08-06T06:47:33.378610153Z / \ | |_ ___ __ __(_) _
> 2019-08-06T06:47:33.378622654Z / _ \| _ \ __|/ _ \ \/ | |/ __/
> 2019-08-06T06:47:33.378634254Z / ___ \ | \/ |_/ __/ |\/| | |\___ \
> 2019-08-06T06:47:33.378645955Z /_/ \_\| \__\|_| |_|_|/___ /
> 2019-08-06T06:47:33.378657155Z Apache ActiveMQ Artemis 2.9.0
> 2019-08-06T06:47:33.378668156Z
> 2019-08-06T06:47:33.378679156Z
> 2019-08-06T06:47:37.544726699Z 2019-08-06 06:47:37,477 INFO
> [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting
> ActiveMQ Artemis Server
> 2019-08-06T06:47:38.565550895Z 2019-08-06 06:47:38,564 INFO
> [org.apache.activemq.artemis.core.server] AMQ221000: live Message Broker is
> starting with configuration Broker Configuration
> (clustered=false,journalDirectory=data/journal,bindingsDirectory=data/bindings,largeMessagesDirectory=data/large-messages,pagingDirectory=data/paging)
> 2019-08-06T06:47:38.742539672Z 2019-08-06 06:47:38,738 INFO
> [org.apache.activemq.artemis.core.server] AMQ221012: Using AIO Journal
> 2019-08-06T06:47:39.048523728Z 2019-08-06 06:47:39,043 INFO
> [org.apache.activemq.artemis.core.server] AMQ221057: Global Max Size is being
> adjusted to 1/2 of the JVM max size (-Xmx). being defined as 3,099,590,656
> 2019-08-06T06:47:39.281507988Z 2019-08-06 06:47:39,278 INFO
> [org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
> [artemis-server]. Adding protocol support for: CORE
> 2019-08-06T06:47:39.281536789Z 2019-08-06 06:47:39,279 INFO
> [org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
> [artemis-amqp-protocol]. Adding protocol support for: AMQP
> 2019-08-06T06:47:40.433221253Z 2019-08-06 06:47:40,426 INFO
> [org.apache.activemq.artemis.core.server] AMQ221034: Waiting indefinitely to
> obtain live lock
> 2019-08-06T06:47:40.433255155Z 2019-08-06 06:47:40,427 INFO
> [org.apache.activemq.artemis.core.server] AMQ221035: Live Server Obtained
> live lock
> 2019-08-06T06:47:40.927969551Z 2019-08-06 06:47:40,925 INFO
> [org.apache.activemq.artemis.core.server] AMQ221080: Deploying address DLQ
> supporting [ANYCAST]
> 2019-08-06T06:47:41.038512746Z 2019-08-06 06:47:41,035 INFO
> [org.apache.activemq.artemis.core.server] AMQ221003: Deploying ANYCAST queue
> DLQ on address DLQ
> 2019-08-06T06:47:41.822560701Z 2019-08-06 06:47:41,814 INFO
> [org.apache.activemq.artemis.core.server] AMQ221080: Deploying address
> ExpiryQueue supporting [ANYCAST]
> 2019-08-06T06:47:41.831706739Z 2019-08-06 06:47:41,830 INFO
> [org.apache.activemq.artemis.core.server] AMQ221003: Deploying ANYCAST queue
> ExpiryQueue on address ExpiryQueue
> 2019-08-06T06:47:41.857242562Z 2019-08-06 06:47:41,850 INFO
> [org.apache.activemq.artemis.core.server] AMQ221080: Deploying address
> /exchange/amq.fanout/analysis supporting [MULTICAST]
> 2019-08-06T06:47:41.876622291Z 2019-08-06 06:47:41,875 INFO
> [org.apache.activemq.artemis.core.server] AMQ221080: Deploying address
> /topic/heartbeat supporting [MULTICAST]
> 2019-08-06T06:47:43.249534752Z 2019-08-06 06:47:43,242 INFO
> [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor
> at 0.0.0.0:5672 for protocols [AMQP]
> 2019-08-06T06:47:43.274616353Z 2019-08-06 06:47:43,267 INFO
> [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
> 2019-08-06T06:47:43.274655755Z
[jira] [Updated] (ARTEMIS-3707) ResourceAdapter improvements
[ https://issues.apache.org/jira/browse/ARTEMIS-3707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic updated ARTEMIS-3707: - Fix Version/s: 2.25.0 (was: 2.24.0) > ResourceAdapter improvements > > > Key: ARTEMIS-3707 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3707 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Waldi >Priority: Major > Fix For: 2.25.0 > > Time Spent: 8h 50m > Remaining Estimate: 0h > > Hi Everybody, > I've tried to install the resourceAdapter in openliberty/WLP by myself. I've > got in some troubles and fixed it by myself. Now, I would like to provide the > modifications and a small piece of documentation of the resourceAdapter, if > interested. > * Sample config / project for openliberty/WLP > * remove usage of the transactionManager in the resource adapter > * fix the jakarta ra.xml namespaces and classnames > * create a maven build for a rar archive with fewer dependencies and > therefore a smaller footprint. > I took notice of ARTEMIS-1487 and ARTEMIS-1614. In my opinion, with my > contributions, we can close these issues. Can you tell me your thoughts and > give me feedback? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3905) Can't find "Connect" tab on Artemis Console Navigation Menu
[ https://issues.apache.org/jira/browse/ARTEMIS-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3905. > Can't find "Connect" tab on Artemis Console Navigation Menu > --- > > Key: ARTEMIS-3905 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3905 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Web Console >Affects Versions: 2.16.0, 2.19.0, 2.23.0 >Reporter: João Santos >Assignee: Justin Bertram >Priority: Minor > Fix For: 2.24.0 > > > I've just installed and configured an ActiveMQ Artemis 2.23.0 Cluster and was > looking to host the web console on a single cluster separated machine which > would connect to each of the nodes. > According to the > [documentation|https://activemq.apache.org/components/artemis/documentation/latest/management-console.html], > there is a "Connect" tab which can be used to connect to other brokers, but > I can't seem to find it in any of the brokers I've configured so far. > I have two other Artemis deployments in versions 2.19.0 and 2.16.0 and I'm > also unable to find the "Connect" tab in any of them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-2618) Improve Handling of Shutdown on critical I/O Error
[
https://issues.apache.org/jira/browse/ARTEMIS-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic updated ARTEMIS-2618:
-
Fix Version/s: 2.25.0
(was: 2.24.0)
> Improve Handling of Shutdown on critical I/O Error
> --
>
> Key: ARTEMIS-2618
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2618
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Affects Versions: 2.11.0
>Reporter: Rico Neubauer
>Priority: Major
> Fix For: 2.25.0
>
> Attachments: Improve-Handling-of-Shutdown-on-critic.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Would like to request an improvement in the handling of critical I/O errors
> on opening journal files.
> If {{org.apache.activemq.artemis.core.io.nio.NIOSequentialFile}} fails to
> open a journal file, the whole server shuts down with {{@Message(id = 222010,
> value = "Critical IO Error, shutting down the server. file=1, message=0"}}.
> We have seen this in the wild, where a backup-software locked the file for a
> short time while journal was about getting opened, resulting in the shutdown.
> Proposed improvement would be to have a short-running retry for opening the
> journal files and only fail fatally if error persists.
> Will attach a proposal patch. Can also create a PR if you accept.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3902) Adding reason for Security failure on Audit Security Message
[ https://issues.apache.org/jira/browse/ARTEMIS-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic updated ARTEMIS-3902: - Fix Version/s: 2.25.0 (was: 2.24.0) > Adding reason for Security failure on Audit Security Message > - > > Key: ARTEMIS-3902 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3902 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.25.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3881) Upgrade jetty to v10
[ https://issues.apache.org/jira/browse/ARTEMIS-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3881. > Upgrade jetty to v10 > > > Key: ARTEMIS-3881 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3881 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade > Components: Web Console >Affects Versions: 2.24.0 >Reporter: Gasperc >Priority: Minor > Labels: pull-request-available > Fix For: 2.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Changes in jetty v10: > Minimum java requirement has been bumped to Java 11, some code refactoring > and support for websocket over http/2. > [https://www.eclipse.org/lists/jetty-announce/msg00149.html] > > Built and tested locally, everything seems to work. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3558) [DOC] Add broker-connections to broker.xml reference
[ https://issues.apache.org/jira/browse/ARTEMIS-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3558. > [DOC] Add broker-connections to broker.xml reference > > > Key: ARTEMIS-3558 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3558 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Paul Wright >Priority: Major > Fix For: 2.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > > [https://activemq.apache.org/components/artemis/documentation/latest/configuration-index.html] > > doesn't contain a reference and link to: > > https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3877) move javadoc creation to release profile as with other site content
[ https://issues.apache.org/jira/browse/ARTEMIS-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3877. > move javadoc creation to release profile as with other site content > --- > > Key: ARTEMIS-3877 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3877 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.23.1 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.24.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The build contains some javadoc generation as part of the artemis-website > module, for addition of API docs to the website etc. None of the other > content in artemis-website is built during a regular build, instead being > deferred only to builds using the release profile, but the javadoc is always > generated. > This adds ~1minute to the overall build, or now about ~1/3rd of the total > time remaining after prior tweaks reduced it to the current ~3minutes. This a > fairly huge overhead given its likely very few developers ever look at that > output for most builds, instead probably either having an IDE already > providing Javadoc access if needed, or for more standalone APIs like JMS > perhaps just looking at the specs own published API docs. > The Javadoc creation should be moved into the release profile like the other > artemis-website bits and thus reduce the time for a dev builds both locally > and in many CI jobs (i.e. all those not specifically verifying the release > profile). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3874) reduce use of test-jar and related module/test interdependencies
[ https://issues.apache.org/jira/browse/ARTEMIS-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3874. > reduce use of test-jar and related module/test interdependencies > > > Key: ARTEMIS-3874 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3874 > Project: ActiveMQ Artemis > Issue Type: Test > Components: Tests >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.24.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The build currently makes a lot of use of 'test-jar' dependencies between > various modules, which can complicate the build and can lead to unexpected > behaviours at times. It makes lots of the modules inter-dependent on each > other (particularly their tests) when they really otherwise arent. It means > that unexpected test resources/classes (from other modules) you wouldnt > normally expect to be on a modules test claspath can be, and can mean the > same for some of their dependencies (scope dependent), sometimes making the > test env quite different than would be expected. It requires creating all > these test-jars that normally dont even exist, and publishing many, and also > requires doing so during the 'test' phase which normally shouldnt need to > package anything to ensure they exist before other modules run that might > require them (otherwise the build will fail). > I had hoped to eradicate their use towards leveraging the update in the > logging changes (and related config..) being worked on, but their use and the > related build intertwining was far more extensive than I had appreciated, so > this is a partial step toward a larger change that would need to happen later > perhaps over time. From the 'main' (non-test) modules it leaves only > artemis-server producing a test-jar and confines all use of them to the > non-deployed 'tests' subtree, where there is still a notable reduction in > use. It introduces a new module to share some rules and utilities amongst all > the modules tests, and leverages the existing artemis-test-support module as > a place to host utilities etc that depend on the clients/broker (which thus > cant live in a module those modules require, due to creating a cycle) and > supply other items to tests that use them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3864) Stomp Transactions are leaking sessions on ActiveMQServer
[ https://issues.apache.org/jira/browse/ARTEMIS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3864. > Stomp Transactions are leaking sessions on ActiveMQServer > - > > Key: ARTEMIS-3864 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3864 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.23.1 >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.24.0 > > > Create a transaction in stomp with being > commit the transaction. > The session will never be closed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-1964) Address control has 2 methods to get same metric
[
https://issues.apache.org/jira/browse/ARTEMIS-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-1964.
> Address control has 2 methods to get same metric
>
>
> Key: ARTEMIS-1964
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1964
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.23.1
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.24.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{getNumberOfMessages()}} and {{getMessageCount()}} both return the same
> metric albeit in different ways. This is confusing and should be refactored.
> Also, {{getNumberOfMessages()}} inspects both "local" and "remote" queue
> bindings which is wrong. This can result in differences between the values
> reported by each.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3858) navigating from session to related consumers/producers gives NPE
[ https://issues.apache.org/jira/browse/ARTEMIS-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3858. > navigating from session to related consumers/producers gives NPE > > > Key: ARTEMIS-3858 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3858 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Web Console >Affects Versions: 2.22.0 >Reporter: Erwin Dondorp >Assignee: Domenico Francesco Bruscino >Priority: Minor > Fix For: 2.24.0 > > Time Spent: 1h > Remaining Estimate: 0h > > on an Artemis cluster, go to page Sessions. > then click on the value in either columns "Consumer Count" or "Producer > Count". > see the resulting error message "could not invoke list > sessionsjava.lang.NullPointerException : no mapping for value". the resulting > consumer/producer table is always empty. > the browser console shows the error message "Uncaught TypeError: > $scope.workspace is undefined" > a PR is added -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3895) properties config - treat url with / as directory of alphabetically ordered <..>.properties files
[ https://issues.apache.org/jira/browse/ARTEMIS-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3895. > properties config - treat url with / as directory of alphabetically ordered > <..>.properties files > - > > Key: ARTEMIS-3895 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3895 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Configuration >Affects Versions: 2.23.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > > the current url identifies a comma separated list of property files, with > this change a directory url can be configured by using a trailing '/' and any > .properties files in that directory will be applied in order of their sorted > names. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3859) Offer "Original Queue" column only for dead-letter or expiry queues
[ https://issues.apache.org/jira/browse/ARTEMIS-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3859. > Offer "Original Queue" column only for dead-letter or expiry queues > --- > > Key: ARTEMIS-3859 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3859 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > > If you're browsing a non dead-letter or non expiry queue then de-selecting > the column labelled "Original Queue (Expiry/DLQ's only)" removes the "Show" > button. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3851) MQTT subscription queues exist after restart despite CleanSession=1
[
https://issues.apache.org/jira/browse/ARTEMIS-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-3851.
> MQTT subscription queues exist after restart despite CleanSession=1
> ---
>
> Key: ARTEMIS-3851
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3851
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.24.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> MQTT subscription queues are not cleaned up if the broker goes down while the
> consumer is connected.
> To reproduce the issue:
> # Run AMQ broker with standard configuration (addresses and queues are
> auto-created)
> # Run a MQTT consumer connecting to the target topic with
> {{CleanSession=true}}. At this point a subscription queue will be created on
> the address for the MQTT topic.
> # Run a MQTT producer sending messages into the target topic.
> # Since the producer is running, the consumer is receiving the messages.
> # Shutdown AMQ (it can be done gracefully or by killing -9 it).
> # Stop the MQTT producer.
> # Stop the MQTT consumer
> # Start the broker. After it is restarted, the old queue associated to the
> MQTT consumer is still there and it's not deleted.
> # Run again the MQTT producer. The broker continues enqueuing messages into
> the old subscription queue.
> # Stop the MQTT producer. The queue stops growing but it's still there with
> messages inside.
> The MQTT 3.1.1 specification states in [section
> 3.1.2.4|http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_Toc398718030]:
> bq. If CleanSession is set to 1, the Client and Server MUST discard any
> previous Session and start a new one. This Session lasts as long as the
> Network Connection. State data associated with this Session MUST NOT be
> reused in any subsequent Session [MQTT-3.1.2-6].
> When the broker is stopped the network connection is terminated so the
> session's state data (including any messages for any subscriptions) should be
> removed.
> To be clear, this works differently in MQTT 5 where {{CleanSession}} became
> {{CleanStart}} and session expiry interval was added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3890) LVQ - missing and duplicate messages for existing consumer
[ https://issues.apache.org/jira/browse/ARTEMIS-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3890. > LVQ - missing and duplicate messages for existing consumer > -- > > Key: ARTEMIS-3890 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3890 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.23.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Labels: lvq > Fix For: 2.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > > With parallel producers and multiple last value properties, an existing > consumer competes with the deliver loop to get messages that are replaced. > In addition, some duplicates can occur when non destructive as iterators get > a replay in error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3885) refresh documentation build deps
[ https://issues.apache.org/jira/browse/ARTEMIS-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3885. > refresh documentation build deps > > > Key: ARTEMIS-3885 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3885 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.24.0 > > > refresh documentation build deps -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3888) Make web console detection more robust
[
https://issues.apache.org/jira/browse/ARTEMIS-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-3888.
> Make web console detection more robust
> --
>
> Key: ARTEMIS-3888
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3888
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.24.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently the broker detects the presence of the web console by looking for
> the *name* of a file (i.e. {{console.war}}). This is fragile because if the
> file is renamed for any reason then the broker won't print the status of the
> web console when it starts.
> The broker needs to use a more robust way of detecting the presence of the
> web console.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3863) properties config - allow role configuration
[ https://issues.apache.org/jira/browse/ARTEMIS-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3863. > properties config - allow role configuration > > > Key: ARTEMIS-3863 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3863 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Configuration >Affects Versions: 2.23.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.24.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > the Role class need constructor and setter methods > the Set needs some type information to allow creation > This sort of thing should be possible: > securityRoles.TEST.users.send=true > securityRoles.TEST.users.consume=true > securityRoles.TEST.admins.createAddress=true -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3870) Mark the -all client deps as optional in the distribution pom to avoid clashing/duplicate deps
[ https://issues.apache.org/jira/browse/ARTEMIS-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3870. > Mark the -all client deps as optional in the distribution pom to avoid > clashing/duplicate deps > -- > > Key: ARTEMIS-3870 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3870 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.23.1 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The two '-all' client artifacts produced by the build from the 'original' > client module components, are both listed dependencies in the apache-artemis > distribution pom in the artemis-distribution dir. These two -all clients are > mutually exclusive and dont coexist, containing the same classes but with > javax.jms and jakarta.jms spec impls, and the artifacts also contain > effective duplicates of all the original jms client [transitive] dependencies > already being passed on separately (giving 3 copies in various cases). > For these reasons they should be marked 'optional' in the pom so that they > arent automatically passed on to anyone happening to use the pom (albeit that > itself should be rare). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3873) AMQP Broker Connection Encrypted Attributes
[
https://issues.apache.org/jira/browse/ARTEMIS-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-3873.
> AMQP Broker Connection Encrypted Attributes
> ---
>
> Key: ARTEMIS-3873
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3873
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Configuration
>Reporter: Ryan Highley
>Assignee: Domenico Francesco Bruscino
>Priority: Minor
> Fix For: 2.24.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The {{amqp-connection}} configuration handler does not allow "ENC(...)"
> values for the {{user}} and {{password}} attributes. These values should be
> handled using the same approach as other security credentials when processing
> the {{broker.xml}} configuration.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3878) Upgrade Derby test dep to 10.14.2.0
[ https://issues.apache.org/jira/browse/ARTEMIS-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3878. > Upgrade Derby test dep to 10.14.2.0 > --- > > Key: ARTEMIS-3878 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3878 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade > Components: Tests >Affects Versions: 2.23.1 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.24.0 > > > Upgrade Derby test dep to 10.14.2.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3899) Improve salt calculation
[ https://issues.apache.org/jira/browse/ARTEMIS-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3899. > Improve salt calculation > > > Key: ARTEMIS-3899 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3899 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Justin Bertram >Priority: Major > Fix For: 2.24.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3820) expired AMQP messages do not show value for "original queue"
[ https://issues.apache.org/jira/browse/ARTEMIS-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3820. > expired AMQP messages do not show value for "original queue" > > > Key: ARTEMIS-3820 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3820 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Web Console >Affects Versions: 2.22.0 >Reporter: Erwin Dondorp >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.24.0 > > Attachments: image.png, screenshot-1.png > > Time Spent: 10m > Remaining Estimate: 0h > > When an AMQP message expired it ends up on a queue under the expiry address. > When viewing a queue under the expiry address, a column "Original Queue" > becomes visible. > However, for (at least) AMQP messages, this column remains empty. > !screenshot-1.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3883) align various dependency versions used in build/test/examples
[ https://issues.apache.org/jira/browse/ARTEMIS-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3883. > align various dependency versions used in build/test/examples > - > > Key: ARTEMIS-3883 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3883 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.23.1 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.24.0 > > Attachments: ARTEMIS-3883-WIP-DS-version.diff > > Time Spent: 20m > Remaining Estimate: 0h > > There are cases where the build uses a particular dependency version, e.g as > part of a component itself or during its tests, and then the examples also > use that dependency but with a different version. This is due to not sharing > a common definition of the version used, and/or not having > dependencyManagement to govern it. > > This leads to the build unecessarily grabbing distinct versions of artifacts > in cases, slowing the overall build and using more resources than needed. > Where possible the versions should be aligned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3892) User limits not working with certificate authentication
[ https://issues.apache.org/jira/browse/ARTEMIS-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3892. > User limits not working with certificate authentication > --- > > Key: ARTEMIS-3892 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3892 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.24.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3891) properties config - allow divert/transformer configuration
[ https://issues.apache.org/jira/browse/ARTEMIS-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3891. > properties config - allow divert/transformer configuration > -- > > Key: ARTEMIS-3891 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3891 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Configuration >Affects Versions: 2.23.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.24.0 > > Time Spent: 10m > Remaining Estimate: 0h > > TransformerConfig needs a converter from string > this will allow: > divertConfigurations.divert1.address=address > divertConfigurations.divert1.forwardingAddress=forwardAddress > divertConfigurations.divert1.transformerConfiguration=className > divertConfigurations.divert1.transformerConfiguration.properties.b=val_b -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3876) avoid unecessary artemis-native dependency unpack for each module
[ https://issues.apache.org/jira/browse/ARTEMIS-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3876. > avoid unecessary artemis-native dependency unpack for each module > - > > Key: ARTEMIS-3876 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3876 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.23.1 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.24.0 > > > The build currently runs the dependency:unpack operation for every module, > extracting the artemis-native .so files into /target/bin for each > module. > However, the the surefire argLine is configuring java.library.path to look > only in /target/bin for the bits extracted, not the individual > /target/bin dirs. As such, the per-module output isnt actually > being used except the one in the root, meaning all the other executions are > superfluous and can be disabled. This will be done by setting the dependency > plugin definition not to be inherited by the child modules as it currently is > being. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3893) update to commons-configuration 2.8.0
[ https://issues.apache.org/jira/browse/ARTEMIS-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3893. > update to commons-configuration 2.8.0 > - > > Key: ARTEMIS-3893 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3893 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Affects Versions: 2.23.1 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.24.0 > > > update to commons-configuration 2.8.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-2965) Allow mirror to stop capture events and delete inner queue
[ https://issues.apache.org/jira/browse/ARTEMIS-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic updated ARTEMIS-2965: - Fix Version/s: 2.25.0 (was: 2.24.0) > Allow mirror to stop capture events and delete inner queue > -- > > Key: ARTEMIS-2965 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2965 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.16.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Critical > Fix For: 2.25.0 > > > When a mirror starts, the current events will not be cleared when > brokerConnection.stop() is called. > > We should support removing the Mirror manager, and deleting the queue upon > brokerConnection.stop(). > (or another method TBD that would determine the semantic to remove the SnF > queue and future generation on mirror). > Related comments: > [https://github.com/apache/activemq-artemis/pull/3316#discussion_r513491335] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3850) Eliminate Soft Cache in paging, and add reading options
[ https://issues.apache.org/jira/browse/ARTEMIS-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic updated ARTEMIS-3850: - Summary: Eliminate Soft Cache in paging, and add reading options (was: Add Option to read messages into paging based on sizing and eliminate caching) > Eliminate Soft Cache in paging, and add reading options > --- > > Key: ARTEMIS-3850 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3850 > Project: ActiveMQ Artemis > Issue Type: New Feature >Affects Versions: 2.22.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.24.0 > > Time Spent: 11h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3850) Eliminate Soft Cache in paging, and add reading options
[ https://issues.apache.org/jira/browse/ARTEMIS-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-3850. Resolution: Fixed > Eliminate Soft Cache in paging, and add reading options > --- > > Key: ARTEMIS-3850 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3850 > Project: ActiveMQ Artemis > Issue Type: New Feature >Affects Versions: 2.22.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.24.0 > > Time Spent: 11h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ARTEMIS-3850) Add Option to read messages into paging based on sizing and eliminate caching
[ https://issues.apache.org/jira/browse/ARTEMIS-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic reopened ARTEMIS-3850: -- > Add Option to read messages into paging based on sizing and eliminate caching > - > > Key: ARTEMIS-3850 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3850 > Project: ActiveMQ Artemis > Issue Type: New Feature >Affects Versions: 2.22.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.24.0 > > Time Spent: 11h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Deleted] (ARTEMIS-3907) đất nền vĩnh thanh nhơn trạch
[ https://issues.apache.org/jira/browse/ARTEMIS-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Domenico Francesco Bruscino deleted ARTEMIS-3907: - > đất nền vĩnh thanh nhơn trạch > - > > Key: ARTEMIS-3907 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3907 > Project: ActiveMQ Artemis > Issue Type: Bug > Environment: đất nền Vĩnh Thanh Nhơn Trạch được đánh giá là khu vực > có tiềm năng phát triển tốt, cơ hội sinh lợi cao. tốc độ tăng trưởng của BĐS > Nhơn Trạch đã có nhiều bước phát triển vượt bậc, trong đó mặt bằng chung của > đất nền Vĩnh Thanh, Nhơn Trạch đã tăng hơn 30% so với cùng kỳ năm ngoái. >Reporter: Maxreal22 >Priority: Major > > https://maxreal.vn/dat-nen-vinh-thanh-nhon-trach/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
