[jira] [Updated] (ARTEMIS-4445) Upgrade 2.30.0 - 2.31.0 -- documentation insufficient
[
https://issues.apache.org/jira/browse/ARTEMIS-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
arne anka updated ARTEMIS-4445:
---
Description:
To update an existing 2.30.0 to 2.31.0
[https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
only mentions
"You should be able to use {{artemis upgrade}} to switch the Artemis home of
your installation and migrate configuration files."
I cannot simply run a script on an installation, w/o any information what
exactly that script does.
Please, provide infomation similar to all the previous upgrades what exactly
will be changed and why.
was:
To update an existing 2.30.0 to
https://activemq.apache.org/components/artemis/documentation/latest/versions.html
"You should be able to use {{artemis upgrade}} to switch the Artemis home of
your installation and migrate configuration files."
> Upgrade 2.30.0 - 2.31.0 -- documentation insufficient
> -
>
> Key: ARTEMIS-4445
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4445
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: arne anka
>Priority: Major
>
> To update an existing 2.30.0 to 2.31.0
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> only mentions
> "You should be able to use {{artemis upgrade}} to switch the Artemis home of
> your installation and migrate configuration files."
> I cannot simply run a script on an installation, w/o any information what
> exactly that script does.
> Please, provide infomation similar to all the previous upgrades what exactly
> will be changed and why.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4445) Upgrade 2.30.0 - 2.31.0 -- documentation insufficient
[
https://issues.apache.org/jira/browse/ARTEMIS-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
arne anka updated ARTEMIS-4445:
---
Summary: Upgrade 2.30.0 - 2.31.0 -- documentation insufficient (was:
Upgrade 2.30.0 - 2.30.1 -- documentation insufficient)
> Upgrade 2.30.0 - 2.31.0 -- documentation insufficient
> -
>
> Key: ARTEMIS-4445
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4445
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: arne anka
>Priority: Major
>
> To update an existing 2.30.0 to
> https://activemq.apache.org/components/artemis/documentation/latest/versions.html
> "You should be able to use {{artemis upgrade}} to switch the Artemis home of
> your installation and migrate configuration files."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4445) Upgrade 2.30.0 - 2.30.1 -- documentation insufficient
[ https://issues.apache.org/jira/browse/ARTEMIS-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] arne anka updated ARTEMIS-4445: --- Summary: Upgrade 2.30.0 - 2.30.1 -- documentation insufficient (was: Upgrade 2.30.0 - 2.30.1_ doumentation insufficient) > Upgrade 2.30.0 - 2.30.1 -- documentation insufficient > - > > Key: ARTEMIS-4445 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4445 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: arne anka >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4445) Upgrade 2.30.0 - 2.30.1 -- documentation insufficient
[
https://issues.apache.org/jira/browse/ARTEMIS-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
arne anka updated ARTEMIS-4445:
---
Description:
To update an existing 2.30.0 to
https://activemq.apache.org/components/artemis/documentation/latest/versions.html
"You should be able to use {{artemis upgrade}} to switch the Artemis home of
your installation and migrate configuration files."
> Upgrade 2.30.0 - 2.30.1 -- documentation insufficient
> -
>
> Key: ARTEMIS-4445
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4445
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: arne anka
>Priority: Major
>
> To update an existing 2.30.0 to
> https://activemq.apache.org/components/artemis/documentation/latest/versions.html
> "You should be able to use {{artemis upgrade}} to switch the Artemis home of
> your installation and migrate configuration files."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4445) Upgrade 2.30.0 - 2.30.1_ doumentation insufficient
arne anka created ARTEMIS-4445: -- Summary: Upgrade 2.30.0 - 2.30.1_ doumentation insufficient Key: ARTEMIS-4445 URL: https://issues.apache.org/jira/browse/ARTEMIS-4445 Project: ActiveMQ Artemis Issue Type: Bug Reporter: arne anka -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4414) "AMQ214019: Invalid configuration" should provide clear information about file and maybe line number
[
https://issues.apache.org/jira/browse/ARTEMIS-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
arne anka updated ARTEMIS-4414:
---
Description:
Figured out the basic issue. Remains the ... limited information in the log.
The error does NOWHERE mention what config file actually causes the error.
That renders the error message mostly pointless and makes fixing unnecessarily
difficult:
{code:java}
2023-09-01 14:15:35,485 ERROR [org.apache.activemq.artemis.core.client]
AMQ214019: Invalid configuration
org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was
found starting with element '{"urn:activemq:core":connectors}'. One of
'{"urn:activemq:core":system-property-prefix,
"urn:activemq:core":internal-naming-prefix,
"urn:activemq:core":amqp-use-core-subscription-naming,
"urn:activemq:core":resolve-protocols,
"urn:activemq:core":graceful-shutdown-enabled,
"urn:activemq:core":graceful-shutdown-timeout,"urn:activemq:core":security-enabled,
"urn:activemq:core":security-invalidation-interval,
"urn:activemq:core":authentication-cache-size,
"urn:activemq:core":authorization-cache-size,
"urn:activemq:core":journal-lock-acquisition-timeout,
"urn:activemq:core":wild-card-routing-enabled,
"urn:activemq:core":management-address,
"urn:activemq:core":management-notification-address,
"urn:activemq:core":cluster-user, "urn:activemq:core":cluster-password,
"urn:activemq:core":password-codec, "urn:activemq:core":mask-password,
"urn:activemq:core":log-delegate-factory-class-name,
"urn:activemq:core":jmx-management-enabled, "urn:activemq:core":jmx-domain,
"urn:activemq:core":jmx-use-broker-name,
"urn:activemq:core":message-counter-enabled,
"urn:activemq:core":message-counter-sample-period,
"urn:activemq:core":message-counter-max-day-history,
"urn:activemq:core":connection-ttl-override,
"urn:activemq:core":connection-ttl-check-interval,
"urn:activemq:core":configuration-file-refresh-period,
"urn:activemq:core":temporary-queue-namespace,
"urn:activemq:core":async-connection-execution-enabled,
"urn:activemq:core":transaction-timeout,
"urn:activemq:core":transaction-timeout-scan-period,
"urn:activemq:core":message-expiry-scan-period,
"urn:activemq:core":message-expiry-thread-priority,
"urn:activemq:core":address-queue-scan-period,
"urn:activemq:core":id-cache-size, "urn:activemq:core":persist-id-cache,
"urn:activemq:core":remoting-incoming-interceptors,
"urn:activemq:core":remoting-outgoing-interceptors,
"urn:activemq:core":persist-delivery-count-before-delivery,
"urn:activemq:core":max-redelivery-records,
"urn:activemq:core":populate-validated-user,
"urn:activemq:core":reject-empty-validated-user,
"urn:activemq:core":mqtt-session-scan-interval,
"urn:activemq:core":broadcast-groups,
"urn:activemq:core":discovery-groups,"urn:activemq:core":diverts,
"urn:activemq:core":queues, "urn:activemq:core":bridges,
"urn:activemq:core":federations, "urn:activemq:core":ha-policy,
"urn:activemq:core":cluster-connections,
"urn:activemq:core":broker-connections, "urn:activemq:core":connection-routers,
"urn:activemq:core":grouping-handler, "urn:activemq:core":create-bindings-dir,
"urn:activemq:core":page-max-concurrent-io,
"urn:activemq:core":read-whole-page,
"urn:activemq:core":journal-retention-directory,
"urn:activemq:core":node-manager-lock-directory,
"urn:activemq:core":create-journal-dir,
"urn:activemq:core":journal-buffer-size,
"urn:activemq:core":journal-sync-transactional,
"urn:activemq:core":journal-sync-non-transactional,
"urn:activemq:core":log-journal-write-rate,
"urn:activemq:core":journal-compact-percentage,
"urn:activemq:core":journal-compact-min-files,
"urn:activemq:core":journal-file-open-timeout,
"urn:activemq:core":server-dump-interval, "urn:activemq:core":global-max-size,
"urn:activemq:core":memory-warning-threshold,
"urn:activemq:core":memory-measure-interval, "urn:activemq:core":store,
"urn:activemq:core":suppress-session-notifications,
"urn:activemq:core":broker-plugins, "urn:activemq:core":metrics-plugin,
"urn:activemq:core":metrics, "urn:activemq:core":resource-limit-settings,
"urn:activemq:core":connector-services, "urn:activemq:core":network-check-list,
"urn:activemq:core":network-check-URL-list,
"urn:activemq:core":network-check-period,
"urn:activemq:core":network-check-timeout,
"urn:activemq:core":network-check-NIC,
"urn:activemq:core":network-check-ping-command,
"urn:activemq:core":network-check-ping6-command}' is expected.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:204)
~[?:?]
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:135)
~[?:?]
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
~[?:?]
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
[jira] [Created] (ARTEMIS-4414) After update 2.29.0 to 2.30.0: "AMQ214019: Invalid configuration" but no info in what file
arne anka created ARTEMIS-4414:
--
Summary: After update 2.29.0 to 2.30.0: "AMQ214019: Invalid
configuration" but no info in what file
Key: ARTEMIS-4414
URL: https://issues.apache.org/jira/browse/ARTEMIS-4414
Project: ActiveMQ Artemis
Issue Type: Bug
Affects Versions: 2.30.0
Reporter: arne anka
I've split the runtime and configuration in two separate folders and thus only
need to unpack the relaesed TAR, replace the previous one and restart Artemis.
That works very well and is just to make clear that there's no chance, a
configuration was modified during upgrade!
Since neither the release notes nor the documentation mention any configuration
changes from 2.29.0 to 2.30.0 I did the same as usual, but after restart the
log is full of the error message below.
What's even worse – the error does NOWHERE mention what config file actually
causes the error.
That renders the error message mostly pointless nad makes fixing unnecessarily
difficult:
{code:java}
2023-09-01 14:15:35,485 ERROR [org.apache.activemq.artemis.core.client]
AMQ214019: Invalid configuration
org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was
found starting with element '{"urn:activemq:core":connectors}'. One of
'{"urn:activemq:core":system-property-prefix,
"urn:activemq:core":internal-naming-prefix,
"urn:activemq:core":amqp-use-core-subscription-naming,
"urn:activemq:core":resolve-protocols,
"urn:activemq:core":graceful-shutdown-enabled,
"urn:activemq:core":graceful-shutdown-timeout,"urn:activemq:core":security-enabled,
"urn:activemq:core":security-invalidation-interval,
"urn:activemq:core":authentication-cache-size,
"urn:activemq:core":authorization-cache-size,
"urn:activemq:core":journal-lock-acquisition-timeout,
"urn:activemq:core":wild-card-routing-enabled,
"urn:activemq:core":management-address,
"urn:activemq:core":management-notification-address,
"urn:activemq:core":cluster-user, "urn:activemq:core":cluster-password,
"urn:activemq:core":password-codec, "urn:activemq:core":mask-password,
"urn:activemq:core":log-delegate-factory-class-name,
"urn:activemq:core":jmx-management-enabled, "urn:activemq:core":jmx-domain,
"urn:activemq:core":jmx-use-broker-name,
"urn:activemq:core":message-counter-enabled,
"urn:activemq:core":message-counter-sample-period,
"urn:activemq:core":message-counter-max-day-history,
"urn:activemq:core":connection-ttl-override,
"urn:activemq:core":connection-ttl-check-interval,
"urn:activemq:core":configuration-file-refresh-period,
"urn:activemq:core":temporary-queue-namespace,
"urn:activemq:core":async-connection-execution-enabled,
"urn:activemq:core":transaction-timeout,
"urn:activemq:core":transaction-timeout-scan-period,
"urn:activemq:core":message-expiry-scan-period,
"urn:activemq:core":message-expiry-thread-priority,
"urn:activemq:core":address-queue-scan-period,
"urn:activemq:core":id-cache-size, "urn:activemq:core":persist-id-cache,
"urn:activemq:core":remoting-incoming-interceptors,
"urn:activemq:core":remoting-outgoing-interceptors,
"urn:activemq:core":persist-delivery-count-before-delivery,
"urn:activemq:core":max-redelivery-records,
"urn:activemq:core":populate-validated-user,
"urn:activemq:core":reject-empty-validated-user,
"urn:activemq:core":mqtt-session-scan-interval,
"urn:activemq:core":broadcast-groups,
"urn:activemq:core":discovery-groups,"urn:activemq:core":diverts,
"urn:activemq:core":queues, "urn:activemq:core":bridges,
"urn:activemq:core":federations, "urn:activemq:core":ha-policy,
"urn:activemq:core":cluster-connections,
"urn:activemq:core":broker-connections, "urn:activemq:core":connection-routers,
"urn:activemq:core":grouping-handler, "urn:activemq:core":create-bindings-dir,
"urn:activemq:core":page-max-concurrent-io,
"urn:activemq:core":read-whole-page,
"urn:activemq:core":journal-retention-directory,
"urn:activemq:core":node-manager-lock-directory,
"urn:activemq:core":create-journal-dir,
"urn:activemq:core":journal-buffer-size,
"urn:activemq:core":journal-sync-transactional,
"urn:activemq:core":journal-sync-non-transactional,
"urn:activemq:core":log-journal-write-rate,
"urn:activemq:core":journal-compact-percentage,
"urn:activemq:core":journal-compact-min-files,
"urn:activemq:core":journal-file-open-timeout,
"urn:activemq:core":server-dump-interval, "urn:activemq:core":global-max-size,
"urn:activemq:core":memory-warning-threshold,
"urn:activemq:core":memory-measure-interval, "urn:activemq:core":store,
"urn:activemq:core":suppress-session-notifications,
"urn:activemq:core":broker-plugins, "urn:activemq:core":metrics-plugin,
"urn:activemq:core":metrics, "urn:activemq:core":resource-limit-settings,
"urn:activemq:core":connector-services, "urn:activemq:core":network-check-list,
"urn:activemq:core":network-check-URL-list,
"urn:activemq:core":network-check-period,
[jira] [Comment Edited] (ARTEMIS-4260) address-setting with wildcard not inherited by actual address
[
https://issues.apache.org/jira/browse/ARTEMIS-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716778#comment-17716778
]
arne anka edited comment on ARTEMIS-4260 at 4/26/23 3:54 PM:
-
I see. Maybe it would be worthwhile to add a note to the doc, that this is
_not_ similar to startsWith() or such?
I've read that page several times, but it never occured to me (seeing the name
rather as one string and not as a hierarchy of tokens).
was (Author: 2020-11-12):
I see. Maybe it would be worthwhile to add a note to the doc, that this is
_not_ similar to startsWith() or such?
I've read that page several times, but it never occured to me (seeing the name
rather as one string and not as a hierarchy of tokens).
Another thing: I am stuck with the underscore – just to be sure: I would need
to define
{code:java}
_{code}
instead, right? Or is there a way to have several delimiters?
> address-setting with wildcard not inherited by actual address
> -
>
> Key: ARTEMIS-4260
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4260
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.28.0
>Reporter: arne anka
>Priority: Minor
>
> In my broker.xml I got
> {code:java}
>
> IMP.DLQ
> IMP.ExpiryQueue
> {code}
> {code:java}
>
>
>
>
>
>
>
> {code}
> According to what I read in docs and examples, all adresses starting with
> {noformat}
> IMP{noformat}
> should inherit the DLQ and Expiry adresses from the address-setting.
> Yet, when starting Artemis it logs
> {code:java}
> 2023-04-26 16:05:59,810 WARN [org.apache.activemq.artemis.core.server]
> AMQ222165: No Dead Letter Address configured for queue IMP_MISC in
> AddressSettings
> 2023-04-26 16:05:59,811 WARN [org.apache.activemq.artemis.core.server]
> AMQ222166: No Expiry Address configured for queue IMP_MISC in AddressSettings
> {code}
> I am currently fighting my way through the code, looking for the place where
> the actual merging happens, but no luck so far.
> Maybe in a first step, someone can give me a pointer where to look (and maybe
> how to log)?
> And is there a way to see the actual configuration of an address once Artemis
> is up and running? Didn't find anything in the Web-Console.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4260) address-setting with wildcard not inherited by actual address
[
https://issues.apache.org/jira/browse/ARTEMIS-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716778#comment-17716778
]
arne anka commented on ARTEMIS-4260:
I see. Maybe it would be worthwhile to add a note to the doc, that this is
_not_ similar to startsWith() or such?
I've read that page several times, but it never occured to me (seeing the name
rather as one string and not as a hierarchy of tokens).
Another thing: I am stuck with the underscore – just to be sure: I would need
to define
{code:java}
_{code}
instead, right? Or is there a way to have several delimiters?
> address-setting with wildcard not inherited by actual address
> -
>
> Key: ARTEMIS-4260
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4260
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.28.0
>Reporter: arne anka
>Priority: Minor
>
> In my broker.xml I got
> {code:java}
>
> IMP.DLQ
> IMP.ExpiryQueue
> {code}
> {code:java}
>
>
>
>
>
>
>
> {code}
> According to what I read in docs and examples, all adresses starting with
> {noformat}
> IMP{noformat}
> should inherit the DLQ and Expiry adresses from the address-setting.
> Yet, when starting Artemis it logs
> {code:java}
> 2023-04-26 16:05:59,810 WARN [org.apache.activemq.artemis.core.server]
> AMQ222165: No Dead Letter Address configured for queue IMP_MISC in
> AddressSettings
> 2023-04-26 16:05:59,811 WARN [org.apache.activemq.artemis.core.server]
> AMQ222166: No Expiry Address configured for queue IMP_MISC in AddressSettings
> {code}
> I am currently fighting my way through the code, looking for the place where
> the actual merging happens, but no luck so far.
> Maybe in a first step, someone can give me a pointer where to look (and maybe
> how to log)?
> And is there a way to see the actual configuration of an address once Artemis
> is up and running? Didn't find anything in the Web-Console.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9251) address-setting w/ wildcard not in herited by actual address
[ https://issues.apache.org/jira/browse/AMQ-9251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716777#comment-17716777 ] arne anka commented on AMQ-9251: I created a new ticket which took a bit longer than expected. While submitting JIRA threw an error about an outdated XSRF token. Then a popup appeared proposing to try again, but then it didn't recognize "ActiveMQ Artemis" as a valid project. The projects list did indeed not contain "ActiveMQ Artemis" anymore, so I switched to "ActiveMQ", expecting a su-project dropdown or such – but all it did was clearing the content entirely, except the subject. I then cancelled the ticket and tried again from scratch. Apparently this resulted in JIRA a) submitting my original ticket (ARTEMIS-4260) despite the error b) submitting this one c) properly and as expected submitting ARTEMIS-4261 (which Justin then closed as duplicate) I don't know whether it is worth looking into, and whether JIRA logged some errors. > address-setting w/ wildcard not in herited by actual address > > > Key: AMQ-9251 > URL: https://issues.apache.org/jira/browse/AMQ-9251 > Project: ActiveMQ > Issue Type: Bug >Reporter: arne anka >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4261) address-setting w/ wildcard not in herited by actual address
[
https://issues.apache.org/jira/browse/ARTEMIS-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716760#comment-17716760
]
arne anka commented on ARTEMIS-4261:
Oh, Jira did post the first one despite a spurios error message ...
> address-setting w/ wildcard not in herited by actual address
>
>
> Key: ARTEMIS-4261
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4261
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: arne anka
>Priority: Minor
>
> In my broker.xml I got
> {code:java}
>
> IMP.DLQ
> IMP.ExpiryQueue
>
>
>
>
>
>
>
> {code}
> My understanding from the docs is, that each actual address starting with
> {code:java}
> IMP{code}
> should inherit the DQL and ExpiryQueue setting.
> And yet, when starting Artemis, it logs
> {code:java}
> 2023-04-26 16:05:59,810 WARN [org.apache.activemq.artemis.core.server]
> AMQ222165: No Dead Letter Address configured for queue IMP_MISC in
> AddressSettings
> 2023-04-26 16:05:59,811 WARN [org.apache.activemq.artemis.core.server]
> AMQ222166: No Expiry Address configured for queue IMP_MISC in AddressSettings
> {code}
> Currently, I am fighting my way through the code, to find the place where the
> inheritance occurs, but no luck so far.
> Can someone point me there, and may tell me hhow to see the actual address
> configuration onced Artemis is up and running? Didn't find anything in the
> web-console.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4261) address-setting w/ wildcard not in herited by actual address
arne anka created ARTEMIS-4261:
--
Summary: address-setting w/ wildcard not in herited by actual
address
Key: ARTEMIS-4261
URL: https://issues.apache.org/jira/browse/ARTEMIS-4261
Project: ActiveMQ Artemis
Issue Type: Bug
Reporter: arne anka
In my broker.xml I got
{code:java}
IMP.DLQ
IMP.ExpiryQueue
{code}
My understanding from the docs is, that each actual address starting with
{code:java}
IMP{code}
should inherit the DQL and ExpiryQueue setting.
And yet, when starting Artemis, it logs
{code:java}
2023-04-26 16:05:59,810 WARN [org.apache.activemq.artemis.core.server]
AMQ222165: No Dead Letter Address configured for queue IMP_MISC in
AddressSettings
2023-04-26 16:05:59,811 WARN [org.apache.activemq.artemis.core.server]
AMQ222166: No Expiry Address configured for queue IMP_MISC in AddressSettings
{code}
Currently, I am fighting my way through the code, to find the place where the
inheritance occurs, but no luck so far.
Can someone point me there, and may tell me hhow to see the actual address
configuration onced Artemis is up and running? Didn't find anything in the
web-console.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (AMQ-9251) address-setting w/ wildcard not in herited by actual address
arne anka created AMQ-9251: -- Summary: address-setting w/ wildcard not in herited by actual address Key: AMQ-9251 URL: https://issues.apache.org/jira/browse/AMQ-9251 Project: ActiveMQ Issue Type: Bug Reporter: arne anka -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4260) address-setting w/ wildcard not in herited by actual address
arne anka created ARTEMIS-4260:
--
Summary: address-setting w/ wildcard not in herited by actual
address
Key: ARTEMIS-4260
URL: https://issues.apache.org/jira/browse/ARTEMIS-4260
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Broker
Affects Versions: 2.28.0
Reporter: arne anka
In my broker.xml I got
{code:java}
IMP.DLQ
IMP.ExpiryQueue
{code}
{code:java}
{code}
According to what I read in docs and examples, all adresses starting with
{noformat}
IMP{noformat}
should inherit the DLQ and Expiry adresses from the address-setting.
Yet, when starting Artemis it logs
{code:java}
2023-04-26 16:05:59,810 WARN [org.apache.activemq.artemis.core.server]
AMQ222165: No Dead Letter Address configured for queue IMP_MISC in
AddressSettings
2023-04-26 16:05:59,811 WARN [org.apache.activemq.artemis.core.server]
AMQ222166: No Expiry Address configured for queue IMP_MISC in AddressSettings
{code}
I am currently fighting my way through the code, looking for the place where
the actual merging happens, but no luck so far.
Maybe in a first step, someone can give me a pointer where to look (and maybe
how to log)?
And is there a way to see the actual configuration of an address once Artemis
is up and running? Didn't find anything in the Web-Console.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4147) artemis.profile: use variables consistently
[ https://issues.apache.org/jira/browse/ARTEMIS-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682051#comment-17682051 ] arne anka commented on ARTEMIS-4147: Oh, and everywhere else as well. Just stumbled over `bin/artemis` where variables are used `ARTEMIS_INSTANCE` but also re-defined for no plausible reason: `ARTEMIS_INSTANCE_ETC` Not sure if it is feasible with XML like `bootstrap.xml` where the same path is set again. > artemis.profile: use variables consistently > --- > > Key: ARTEMIS-4147 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4147 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Configuration >Reporter: arne anka >Priority: Minor > > Generated > `artemis.profile` > starts with a section of variables > ``` > ARTEMIS_HOME='/tmp/apache-artemis-2.27.1' > ARTEMIS_INSTANCE='/tmp/apache-artemis-2.27.1/artemis' > ARTEMIS_DATA_DIR='/tmp/apache-artemis-2.27.1/artemis/data' > ARTEMIS_ETC_DIR='/tmp/apache-artemis-2.27.1/artemis/etc' > ARTEMIS_OOME_DUMP='/tmp/apache-artemis-2.27.1/artemis/log/oom_dump.hprof > ARTEMIS_INSTANCE_URI='file:/tmp/apache-artemis-2.27.1/artemis/' > ARTEMIS_INSTANCE_ETC_URI='file:/tmp/apache-artemis-2.27.1/artemis/etc/' > ``` > basically none of these variables is being reused. > So, whenever I need to change either > `ARTEMIS_HOME` > or > `ARTEMIS_INSTANCE` > I need to change each and every variable. > Instead, I propose to re-use > `ARTEMIS_HOME` > `ARTEMIS_INSTANCE` > so one needs to change only in one place: > ``` > ARTEMIS_HOME='/tmp/apache-artemis-2.27.1' > ARTEMIS_INSTANCE='$ARTEMIS_HOME/artemis' > ARTEMIS_DATA_DIR='$ARTEMIS_INSTANCE/data' > ARTEMIS_ETC_DIR='$ARTEMIS_INSTANCE/etc' > ARTEMIS_OOME_DUMP='$ARTEMIS_INSTANCE/log/oom_dump.hprof > ARTEMIS_INSTANCE_URI='file:$ARTEMIS_INSTANCE/' > ARTEMIS_INSTANCE_ETC_URI='file:$ARTEMIS_INSTANCE/etc/' > ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4147) artemis.profile: use variables consistently
arne anka created ARTEMIS-4147: -- Summary: artemis.profile: use variables consistently Key: ARTEMIS-4147 URL: https://issues.apache.org/jira/browse/ARTEMIS-4147 Project: ActiveMQ Artemis Issue Type: Bug Components: Configuration Reporter: arne anka Generated `artemis.profile` starts with a section of variables ``` ARTEMIS_HOME='/tmp/apache-artemis-2.27.1' ARTEMIS_INSTANCE='/tmp/apache-artemis-2.27.1/artemis' ARTEMIS_DATA_DIR='/tmp/apache-artemis-2.27.1/artemis/data' ARTEMIS_ETC_DIR='/tmp/apache-artemis-2.27.1/artemis/etc' ARTEMIS_OOME_DUMP='/tmp/apache-artemis-2.27.1/artemis/log/oom_dump.hprof ARTEMIS_INSTANCE_URI='file:/tmp/apache-artemis-2.27.1/artemis/' ARTEMIS_INSTANCE_ETC_URI='file:/tmp/apache-artemis-2.27.1/artemis/etc/' ``` basically none of these variables is being reused. So, whenever I need to change either `ARTEMIS_HOME` or `ARTEMIS_INSTANCE` I need to change each and every variable. Instead, I propose to re-use `ARTEMIS_HOME` `ARTEMIS_INSTANCE` so one needs to change only in one place: ``` ARTEMIS_HOME='/tmp/apache-artemis-2.27.1' ARTEMIS_INSTANCE='$ARTEMIS_HOME/artemis' ARTEMIS_DATA_DIR='$ARTEMIS_INSTANCE/data' ARTEMIS_ETC_DIR='$ARTEMIS_INSTANCE/etc' ARTEMIS_OOME_DUMP='$ARTEMIS_INSTANCE/log/oom_dump.hprof ARTEMIS_INSTANCE_URI='file:$ARTEMIS_INSTANCE/' ARTEMIS_INSTANCE_ETC_URI='file:$ARTEMIS_INSTANCE/etc/' ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3865) Web Console: "Artemis" node does not exist after login, needs reload
[ https://issues.apache.org/jira/browse/ARTEMIS-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557370#comment-17557370 ] arne anka commented on ARTEMIS-3865: I see this constantly. The broker runs on a dedicated VM in our internal network, access is routed through some firewall appliances. No SSL. No proxy. While playing around with a second instance I created, the issue seems to be tied to a high volume of messages. Currently we're close to peak load of the day and I need to reload twice (once even thrice) to get logo and node to show up. The test instance has no messages to process and responds at once, as expected. Looks like there's a too small timeout somewhere when attempting to connect, but I'd expect to see some errors in either the browser's developer tools or the log file. > Web Console: "Artemis" node does not exist after login, needs reload > > > Key: ARTEMIS-3865 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3865 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Web Console >Affects Versions: 2.22.0 > Environment: Browser: Vivaldi 5.3 >Reporter: arne anka >Priority: Major > Attachments: after_login.png, after_reload.png, dev_tools.png > > > Right after login the Artemis node is missing from the tree/list left. > Also, the ActiveMQ logo is not displayed, only the broken image icon. > After one, sometimes more reloads, the Artemis node and the log eventually > appear. > I did not experience the issue before 2.21.0, but since then continuously. > Happens even after each logout, where at least the logo should be cached > already. > Browser's Dev Tools' Network tab does not show anything useful. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (ARTEMIS-3865) Web Console: "Artemis" node does not exist after login, needs reload
arne anka created ARTEMIS-3865: -- Summary: Web Console: "Artemis" node does not exist after login, needs reload Key: ARTEMIS-3865 URL: https://issues.apache.org/jira/browse/ARTEMIS-3865 Project: ActiveMQ Artemis Issue Type: Bug Components: Web Console Affects Versions: 2.22.0 Environment: Browser: Vivaldi 5.3 Reporter: arne anka Attachments: after_login.png, after_reload.png, dev_tools.png Right after login the Artemis node is missing from the tree/list left. Also, the ActiveMQ logo is not displayed, only the broken image icon. After one, sometimes more reloads, the Artemis node and the log eventually appear. I did not experience the issue before 2.21.0, but since then continuously. Happens even after each logout, where at least the logo should be cached already. Browser's Dev Tools' Network tab does not show anything useful. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (ARTEMIS-3847) Documentation does not mention 2.22
arne anka created ARTEMIS-3847: -- Summary: Documentation does not mention 2.22 Key: ARTEMIS-3847 URL: https://issues.apache.org/jira/browse/ARTEMIS-3847 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.22.0 Reporter: arne anka [https://activemq.apache.org/components/artemis/documentation/latest/versions.html] pretends to be about 2.22 but that version is nowhere mentioned. Most recent version is 2.21, no info about changes/caveats upon upgrade. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (ARTEMIS-3642) Management Console -> Browse Queue -> [] Select All broken after first use
arne anka created ARTEMIS-3642: -- Summary: Management Console -> Browse Queue -> [] Select All broken after first use Key: ARTEMIS-3642 URL: https://issues.apache.org/jira/browse/ARTEMIS-3642 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.20.0 Environment: Linux amd64 Vivaldi: 5.0.2497.38 JavaScript: V8 9.6.180.22 Reporter: arne anka Browse Queue view has a left-most column with checkboxes to select messages to be deleted/moved/... The Table header as a checkbox as well to select all messages shown in the current page. Checking the box in the header checks for each message, unchecking unchecks for each message. I'll call that checkbox "Select All". Now, I need to delete alreg number of messages which means more than one page. I check "Select All" and all messages are checked. I hit "Delete", confirm, and the messages disappear, next page is shown – and "Select All" is still checked. Unchecking and re-checking does not check any message anymore. Only after reloading the whole webpage (F5) the checkbox again works as expected. Seems to me as if somewhere a status is not reset correctly after a deletion (and probably move and resend as well). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ARTEMIS-3611) update to most recent log4j
arne anka created ARTEMIS-3611: -- Summary: update to most recent log4j Key: ARTEMIS-3611 URL: https://issues.apache.org/jira/browse/ARTEMIS-3611 Project: ActiveMQ Artemis Issue Type: Bug Components: Web Console Reporter: arne anka While not vulnerable to the recently published issue, the web console still uses log4j 1.2.x – which is long out of support and sports a longish list of unfixed issues, and thus vulnerabilities. Given that log4j 1.2.x is also an apache project, it is disturbing that its EOL more than 6 years ago seems not to have been noticed nor acted upon. It should as soon as possible be updated to a secure version. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17435923#comment-17435923
]
arne anka commented on ARTEMIS-3535:
Thanks, I am aware of the workaround, but so far the update was on my staging
server only.
Is there an estimate as to when 2.20.0 (presuming the fix included) will be
released?
BTW:
maybe the producer should be amended to also produce a {{byte}} test message?
{code:java}
./artemis producer --destination queue://unlimitedQueue --message-count 1
--byte-size 5000
{code}
I suspected {{byte}} vs {{text}} early on (since it was the most obvious
difference) and tried to check that way, but had to jump through all the hoops
with REST instead.
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
>Affects Versions: 2.19.0
>Reporter: arne anka
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.20.0
>
> Attachments: artemis-rest-2.19.0.war, broken_message.png, broker.xml,
> limited.jpg, rest.messaging.config.file.xml, test.xml, unlimited.jpg, web.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17435489#comment-17435489
]
arne anka edited comment on ARTEMIS-3535 at 10/28/21, 3:20 PM:
---
Are you familiar with the artemis-rest portion of the Artemis project? They may
be able to tell you whether these steps can be shortened.
Anyway, that's what I am using.
Create a WAR of it (change POM's {{packaging}} from {{jar}} to {{war}}), make
sure to include the provided {{web.xml}} (in {{src/main/webapp/WEB-INF/}}) and
{{rest.message...xml}} ({{src/main/resources/}}) before building.
Edit: seems Jira accepted my WAR, so you can just use that.
Add the WAR to {{$ARTEMIS_HOME/web/}} and to {{bootstrap.xml}} and (re)start
the broker.
As far as I can tell, the {{test.xml}} topic registration is required by
artemis-rest to create the REST endpoint and mapping to a queue
({{FOO.topic/test}}) – at least, if omitted, the file will not appear.
Send a file via curl
{code:java}
curl -vvv -4 http://localhost:8161/rest/topics/FOO.topic/create -d
@/tmp/test.txt
{code}
Due to the non-existant link target {{[http://localhost:50001/]}} messages
will end up in {{DLQ}}.
Alternatively, pause queue {{FOO.topic/test}} to see messages there.
# open console
# expand 0.0.0.0 -> addresses -> FOO.topic -> queues -> multicast -> test
# switch to *Browse Queue*
# *Show* message
# as you can see, the message is not shown, neither bytes nor text, despite
being ~20k of size:
!broken_message.png!
was (Author: 2020-11-12):
Are you familiar with the artemis-rest portion of the Artemis project? They may
be able to tell you whether these steps can be shortened.
Anyway, that's what I am using.
Create a WAR of it (change POM's {{packaging}} from {{jar}} to {{war}}), make
sure to include the provided {{web.xml}} (in {{src/main/webapp/WEB-INF/}}) and
{{rest.message...xml}} ({{src/main/resources/}}) before building.
Add the WAR to {{$ARTEMIS_HOME/web/}} and to {{bootstrap.xml}} and (re)start
the broker.
As far as I can tell, the {{test.xml}} topic registration is required by
artemis-rest to create the REST endpoint and mapping to a queue
({{FOO.topic/test}}) – at least, if omitted, the file will not appear.
Send a file via curl
{code:java}
curl -vvv -4 http://localhost:8161/rest/topics/FOO.topic/create -d
@/tmp/test.txt
{code}
Due to the non-existant link target {{[http://localhost:50001/]}} messages
will end up in {{DLQ}}.
Alternatively, pause queue {{FOO.topic/test}} to see messages there.
# open console
# expand 0.0.0.0 -> addresses -> FOO.topic -> queues -> multicast -> test
# switch to *Browse Queue*
# *Show* message
# as you can see, the message is not shown, neither bytes nor text, despite
being ~20k of size:
!broken_message.png!
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: artemis-rest-2.19.0.war, broken_message.png, broker.xml,
> limited.jpg, rest.messaging.config.file.xml, test.xml, unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17435492#comment-17435492
]
arne anka commented on ARTEMIS-3535:
Let's see ...
[^artemis-rest-2.19.0.war]
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: artemis-rest-2.19.0.war, broken_message.png, broker.xml,
> limited.jpg, rest.messaging.config.file.xml, test.xml, unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
arne anka updated ARTEMIS-3535:
---
Attachment: artemis-rest-2.19.0.war
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: artemis-rest-2.19.0.war, broken_message.png, broker.xml,
> limited.jpg, rest.messaging.config.file.xml, test.xml, unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17435489#comment-17435489
]
arne anka commented on ARTEMIS-3535:
Are you familiar with the artemis-rest portion of the Artemis project? They may
be able to tell you whether these steps can be shortened.
Anyway, that's what I am using.
Create a WAR of it (change POM's {{packaging}} from {{jar}} to {{war}}), make
sure to include the provided {{web.xml}} (in {{src/main/webapp/WEB-INF/}}) and
{{rest.message...xml}} ({{src/main/resources/}}) before building.
Add the WAR to {{$ARTEMIS_HOME/web/}} and to {{bootstrap.xml}} and (re)start
the broker.
As far as I can tell, the {{test.xml}} topic registration is required by
artemis-rest to create the REST endpoint and mapping to a queue
({{FOO.topic/test}}) – at least, if omitted, the file will not appear.
Send a file via curl
{code:java}
curl -vvv -4 http://localhost:8161/rest/topics/FOO.topic/create -d
@/tmp/test.txt
{code}
Due to the non-existant link target {{[http://localhost:50001/]}} messages
will end up in {{DLQ}}.
Alternatively, pause queue {{FOO.topic/test}} to see messages there.
# open console
# expand 0.0.0.0 -> addresses -> FOO.topic -> queues -> multicast -> test
# switch to *Browse Queue*
# *Show* message
# as you can see, the message is not shown, neither bytes nor text, despite
being ~20k of size:
!broken_message.png!
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: broken_message.png, broker.xml, limited.jpg,
> rest.messaging.config.file.xml, test.xml, unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
arne anka updated ARTEMIS-3535:
---
Attachment: broken_message.png
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: broken_message.png, broker.xml, limited.jpg,
> rest.messaging.config.file.xml, test.xml, unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17435392#comment-17435392
]
arne anka edited comment on ARTEMIS-3535 at 10/28/21, 1:34 PM:
---
Edit: to be clear, I followed your steps above to create a broker. Everything
belwo refers to that created broker.
In case it matters: the `producer` command sends `text`, not `bytes` as Artemis
supposes my messages to be; sending one of my XML or a plain text messages with
`–data` fails with an error.
Next, I send my messages via REST, once I add the artemis-rest.war the issue
appears – no matter whether I send XML or plain text.
So, obviously the communication between the REST webapp and the server is
somehow causing trouble.
Since the created WAR is about 29M I won't attach it, but here's the additional
files:
[^web.xml]
[^rest.messaging.config.file.xml]
and the `push-topic-registration` (lives in
$ARTEMIS_HOME/push-registrations/topics/)
[^test.xml]
In `broker.xml` add
{code:xml}
...
{code}
was (Author: 2020-11-12):
In case it matters: the `producer` command sends `text`, not `bytes` as Artemis
supposes my messages to be; sending one of my XML or a plain text messages with
`–data` fails with an error.
Next, I send my messages via REST, once I add the artemis-rest.war the issue
appears – no matter whether I send XML or plain text.
So, obviously the communication between the REST webapp and the server is
somehow causing trouble.
Since the created WAR is about 29M I won't attach it, but here's the additional
files:
[^web.xml]
[^rest.messaging.config.file.xml]
and the `push-topic-registration` (lives in
$ARTEMIS_HOME/push-registrations/topics/)
[^test.xml]
In `broker.xml` add
{code:xml}
...
{code}
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: broker.xml, limited.jpg, rest.messaging.config.file.xml,
> test.xml, unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17435392#comment-17435392
]
arne anka edited comment on ARTEMIS-3535 at 10/28/21, 1:11 PM:
---
In case it matters: the `producer` command sends `text`, not `bytes` as Artemis
supposes my messages to be; sending one of my XML or a plain text messages with
`–data` fails with an error.
Next, I send my messages via REST, once I add the artemis-rest.war the issue
appears – no matter whether I send XML or plain text.
So, obviously the communication between the REST webapp and the server is
somehow causing trouble.
Since the created WAR is about 29M I won't attach it, but here's the additional
files:
[^web.xml]
[^rest.messaging.config.file.xml]
and the `push-topic-registration` (lives in
$ARTEMIS_HOME/push-registrations/topics/)
[^test.xml]
In `broker.xml` add
{code:xml}
...
{code}
was (Author: 2020-11-12):
In case it matters: the `producer` command sends `text`, not `bytes` as Artemis
supposes my messages to be; sending one of my XML or a plain text messages with
`–data` fails with an error.
Next, I send my messages via REST, once I add the artemis-rest.war the issue
appears – no matter whether I send XML or plain text.
So, obviously the communication between the REST webapp and the server is
somehow causing trouble.
Since the created WAR is about 29M I won't attach it, but here's the additional
files:
[^web.xml]
[^rest.messaging.config.file.xml]
and the `push-topic-registration` (lives in
$ARTEMIS_HOME/push-registrations/topics/)
[^test.xml]
In `broker.xml` add
```
...
```
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: broker.xml, limited.jpg, rest.messaging.config.file.xml,
> test.xml, unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17435392#comment-17435392
]
arne anka commented on ARTEMIS-3535:
In case it matters: the `producer` command sends `text`, not `bytes` as Artemis
supposes my messages to be; sending one of my XML or a plain text messages with
`–data` fails with an error.
Next, I send my messages via REST, once I add the artemis-rest.war the issue
appears – no matter whether I send XML or plain text.
So, obviously the communication between the REST webapp and the server is
somehow causing trouble.
Since the created WAR is about 29M I won't attach it, but here's the additional
files:
[^web.xml]
[^rest.messaging.config.file.xml]
and the `push-topic-registration` (lives in
$ARTEMIS_HOME/push-registrations/topics/)
[^test.xml]
In `broker.xml` add
```
...
```
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: broker.xml, limited.jpg, rest.messaging.config.file.xml,
> test.xml, unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
arne anka updated ARTEMIS-3535:
---
Attachment: test.xml
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: broker.xml, limited.jpg, rest.messaging.config.file.xml,
> test.xml, unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
arne anka updated ARTEMIS-3535:
---
Attachment: rest.messaging.config.file.xml
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: broker.xml, limited.jpg, rest.messaging.config.file.xml,
> unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
arne anka updated ARTEMIS-3535:
---
Attachment: web.xml
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: broker.xml, limited.jpg, unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433015#comment-17433015
]
arne anka commented on ARTEMIS-3535:
[~jbertram]
Care to elaborate? I am just a user – how exactly am I supposed to provide that
information?
I got an installation that I upgraded from 2.17.0 to 2.19.0. The only
difference was adding above line to broker.xml.
Short of giving you access to my installation, I don't quite see what can be
done. I got the impression it is an interaction between different settings,
though, tried to understand how exactly the setting works, but didn't get far.
Attached the broker.xml which seems to be the relevant configuration file:
[^broker.xml]
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: broker.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
arne anka updated ARTEMIS-3535:
---
Attachment: broker.xml
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
> Attachments: broker.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages
[ https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17431093#comment-17431093 ] arne anka commented on ARTEMIS-3141: Maybe I misunderstand the rationale of this feature, but what but understand is, that the _attributes_ may grow to large and cause issues. Since the message body is treated as an attribute, it's affected. So, my idea was not to add the body as attribute at all, but to "get a single full message by ID" whenever so requested. Did I get that completely wrong? > limit the amount of data returned from jmx/queue control listMessages > - > > Key: ARTEMIS-3141 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3141 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: JMX >Affects Versions: 2.17.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.18.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The list methods of queue control that are exposed via jmx seem to be > unbounded. > 1) they list all messages > 2) they display the full body > To protect both the broker and the browser/UI/client it would make sense to > limit both the number of messages and the size of the data that is returned. > Imaging 500k messages pending messages with a body of 10k... and 400k are > paged to disk. It would be crazy to try and list those. > I need to do some more tests to verify the extent a broker will do to support > the current api. I note that the browse functionality can be paged and with > out a page defaults to 200 messages. That is sensible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17431074#comment-17431074
]
arne anka commented on ARTEMIS-3535:
I have an already existing installation where it happens.
Seems, there's an untested dependency to another setting?
Given that the feature was introduced w/o any doumentation, it's near to
impossible to figure out what that might be.
> management-message-attribute-size-limit = -1 does not unlimit
> -
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
>Reporter: arne anka
>Priority: Major
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
>
> ...
>
> -1
>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ARTEMIS-3536) version 2.19.0 released but not "Affects Version/s"
arne anka created ARTEMIS-3536: -- Summary: version 2.19.0 released but not "Affects Version/s" Key: ARTEMIS-3536 URL: https://issues.apache.org/jira/browse/ARTEMIS-3536 Project: ActiveMQ Artemis Issue Type: Bug Reporter: arne anka As per [https://activemq.apache.org/components/artemis/documentation/latest/versions.html] and the download page, 2.19.0 has been released officially. Yet, it is not vaialbale as version in the Affects Version/s dropdown above. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3535) management-message-attribute-size-limit = -1 does not unlimit
arne anka created ARTEMIS-3535:
--
Summary: management-message-attribute-size-limit = -1 does not
unlimit
Key: ARTEMIS-3535
URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Web Console
Environment: A' Artems 2.19.0
Reporter: arne anka
With the new option messages are truncated.
[https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
states for 2.18.0 that this may be overriden by using
-1
as value. But that doesn't work.
{{broker.xml}}
{code:xml}
...
-1
{code}
Text shown is empty.
Changing -1 to eg 1024 text appears partially.
Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages
[ https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17431035#comment-17431035 ] arne anka commented on ARTEMIS-3141: [~jbertram] [~gtully] Shouldn't the message body in Managment Console -> Browse Queue -> Show the not be provided by different means instead of a truncated attribute? I rather often need to check messages in a DLQ, but with the new truncation, the messages are always too short (and -1 does not work, see above). If populating with too large a property is an issue in several places, the message body as attribute seems to be a misfit, doesn't it? > limit the amount of data returned from jmx/queue control listMessages > - > > Key: ARTEMIS-3141 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3141 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: JMX >Affects Versions: 2.17.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.18.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The list methods of queue control that are exposed via jmx seem to be > unbounded. > 1) they list all messages > 2) they display the full body > To protect both the broker and the browser/UI/client it would make sense to > limit both the number of messages and the size of the data that is returned. > Imaging 500k messages pending messages with a body of 10k... and 400k are > paged to disk. It would be crazy to try and list those. > I need to do some more tests to verify the extent a broker will do to support > the current api. I note that the browse functionality can be paged and with > out a page defaults to 200 messages. That is sensible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3531) adding documentation for management-message-attribute-size-limit
[ https://issues.apache.org/jira/browse/ARTEMIS-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17431033#comment-17431033 ] arne anka commented on ARTEMIS-3531: [~erwindon] So? My comment explicitly addressed that – and added emphasis to it's priority mismatch. Documentation _must not_ be a separate issue and at low priority at that. > adding documentation for management-message-attribute-size-limit > > > Key: ARTEMIS-3531 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3531 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.18.0, 2.19.0 >Reporter: Erwin Dondorp >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > The documentation pages do not mention configuration parameter > `management-message-attribute-size-limit`. This parameter is used to control > which part (size) of the messages can be browsed. it was introduced in 2.18.0 > to solve out-of-memory problems. > PR will be supplied... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages
[ https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430487#comment-17430487 ] arne anka commented on ARTEMIS-3141: My comment above relates to ARTEMIS-3532 > limit the amount of data returned from jmx/queue control listMessages > - > > Key: ARTEMIS-3141 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3141 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: JMX >Affects Versions: 2.17.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.18.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The list methods of queue control that are exposed via jmx seem to be > unbounded. > 1) they list all messages > 2) they display the full body > To protect both the broker and the browser/UI/client it would make sense to > limit both the number of messages and the size of the data that is returned. > Imaging 500k messages pending messages with a body of 10k... and 400k are > paged to disk. It would be crazy to try and list those. > I need to do some more tests to verify the extent a broker will do to support > the current api. I note that the browse functionality can be paged and with > out a page defaults to 200 messages. That is sensible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages
[
https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430485#comment-17430485
]
arne anka commented on ARTEMIS-3141:
{{broker.xml}}
{code:xml}
...
-1
{code}
Text shown is empty.
Changing -1 to eg 1024 text appears partially.
Seems -1 does not work as expected.
A' Artems 2.19.0
> limit the amount of data returned from jmx/queue control listMessages
> -
>
> Key: ARTEMIS-3141
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3141
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: JMX
>Affects Versions: 2.17.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>Priority: Major
> Fix For: 2.18.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The list methods of queue control that are exposed via jmx seem to be
> unbounded.
> 1) they list all messages
> 2) they display the full body
> To protect both the broker and the browser/UI/client it would make sense to
> limit both the number of messages and the size of the data that is returned.
> Imaging 500k messages pending messages with a body of 10k... and 400k are
> paged to disk. It would be crazy to try and list those.
> I need to do some more tests to verify the extent a broker will do to support
> the current api. I note that the browse functionality can be paged and with
> out a page defaults to 200 messages. That is sensible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3531) adding documentation for management-message-attribute-size-limit
[ https://issues.apache.org/jira/browse/ARTEMIS-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430477#comment-17430477 ] arne anka commented on ARTEMIS-3531: I don't see how documentation for change qualifying for a mention in the short release information can be classified as "minor". Would someone at least add the information here as to where and how to configure that setting? Currently it is breaking parts of my workflow and I need to fix that. > adding documentation for management-message-attribute-size-limit > > > Key: ARTEMIS-3531 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3531 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.18.0, 2.19.0 >Reporter: Erwin Dondorp >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > The documentation pages do not mention configuration parameter > `management-message-attribute-size-limit`. This parameter is used to control > which part (size) of the messages can be browsed. it was introduced in 2.18.0 > to solve out-of-memory problems. > PR will be supplied... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3532) Management Console -> Browse Queue -> Show/Resend: message truncated
arne anka created ARTEMIS-3532: -- Summary: Management Console -> Browse Queue -> Show/Resend: message truncated Key: ARTEMIS-3532 URL: https://issues.apache.org/jira/browse/ARTEMIS-3532 Project: ActiveMQ Artemis Issue Type: Bug Components: Web Console Affects Versions: 2.19.0 Environment: A' Artemis 2.19.0 Linux Centos 7.9 Reporter: arne anka Attachments: Screenshot_20211019_115738.png Browse a queue, hit Show on a message. Message is XML, and has a size of ~14B, but the shown text of the message is only about 8 lines long and the hex part seems not to be much longer. Trying Resend causes a issue on the receiving end since the message is not only truncated but garbled as well (not even an XML snippet anymore but random bytes apparently) See attached screenshot for message properties. Similar message in 2.17.0 (same environment) works as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-3143) UI wastes space
arne anka created ARTEMIS-3143:
--
Summary: UI wastes space
Key: ARTEMIS-3143
URL: https://issues.apache.org/jira/browse/ARTEMIS-3143
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Web Console
Affects Versions: 2.17.0
Reporter: arne anka
Since at least 2.16 there's a huge side bar, which in my browser window takes
up almost a fifth of the available space.
The font size used to the tab headers ("Current Status", "Brwose Connections",
...) takes up much more space than justified for such a redundant information
(after all, the active tab is there and highlighted already).
The header with that misleading sandwich icon (nowhere else that icon is used
to toggle, everywhere it is used to indicate a menu) takes up too much valuable
space as well – for just a toggle, logo and the menu this is wasting space.
With custom CSS I managed to get an acceptable layout that does not waste space
at the expense of information and functionality – after all, isn't the console
first and foremost a tool to be used effectively?
body {
zoom: 85%;
}
page-header {
zoom: 50%;
}
.pf-c-page__sidebar {
max-width: 8em;
zoom: 75%;
}
.tree-nav-main {
zoom: 90%;
}
.tree-nav-main .nav-tabs {
zoom: 80%
}
artemis-browse-queue>h1 {
zoom: 50%;
}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ARTEMIS-3142) configure tabs shown directly/default tab
arne anka created ARTEMIS-3142: -- Summary: configure tabs shown directly/default tab Key: ARTEMIS-3142 URL: https://issues.apache.org/jira/browse/ARTEMIS-3142 Project: ActiveMQ Artemis Issue Type: Improvement Components: Web Console Reporter: arne anka I almost exclusively use the tabs "Browse" and "Operations". While in at least 2.10 "Browse" was the default tab, with 2.16 this too has been moved to a drop down. I'd really prefer to be able to configure * what tabs are shown directly (moving the rest to the drop down) * what tab should be shown as default The current default of status seems to be a waste of space – that little bit of information easily fits into the oversized side bar or the header, both of which take up valuable space. I don't know what JS library is used to build the Web Consle UI, but I imagine it should be rather trivial to add such a configuration section (list with checkboxes for the tabs to be shown, second checkbox or separate drop down to select the default tab) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2987) Management Console -> Queue -> Message: view with text only
[ https://issues.apache.org/jira/browse/ARTEMIS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234824#comment-17234824 ] arne anka commented on ARTEMIS-2987: Attached a small patch to achieve the original request > Management Console -> Queue -> Message: view with text only > --- > > Key: ARTEMIS-2987 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2987 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: arne anka >Priority: Minor > Attachments: 1.jpg, 2.jpg, ARTEMIS-2987.patch, > Screenshot_20201118_140052.png, Screenshot_20201118_153254.png, > Screenshot_20201118_153435.png > > > In tab [Artemis]expand addresses to a queue with messages in it > In the right area where the messages are listed click on a messaeg id > A view opens that is full of the byte calue of the content. > To get to a human readable representation one has to scroll down to the > "text" section. > When doin that the navigation bar disappears as well, so every timeI navigate > to a new message I have to scroll down a lengthy view and scroll up gaian to > get to the next message. > > Since my messages are esxclusively XML I have no use at all for the "byte" > section, but it is impossible to get rid of it and I have to go through those > tedious steps over and over again. > Preferences do not offer a text-only representation. > > So, please include a representation that only shows the text, and while at it > make the navigation bar stay in place when scrolling the message. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2987) Management Console -> Queue -> Message: view with text only
[ https://issues.apache.org/jira/browse/ARTEMIS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] arne anka updated ARTEMIS-2987: --- Attachment: ARTEMIS-2987.patch > Management Console -> Queue -> Message: view with text only > --- > > Key: ARTEMIS-2987 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2987 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: arne anka >Priority: Minor > Attachments: 1.jpg, 2.jpg, ARTEMIS-2987.patch, > Screenshot_20201118_140052.png, Screenshot_20201118_153254.png, > Screenshot_20201118_153435.png > > > In tab [Artemis]expand addresses to a queue with messages in it > In the right area where the messages are listed click on a messaeg id > A view opens that is full of the byte calue of the content. > To get to a human readable representation one has to scroll down to the > "text" section. > When doin that the navigation bar disappears as well, so every timeI navigate > to a new message I have to scroll down a lengthy view and scroll up gaian to > get to the next message. > > Since my messages are esxclusively XML I have no use at all for the "byte" > section, but it is impossible to get rid of it and I have to go through those > tedious steps over and over again. > Preferences do not offer a text-only representation. > > So, please include a representation that only shows the text, and while at it > make the navigation bar stay in place when scrolling the message. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2987) Management Console -> Queue -> Message: view with text only
[ https://issues.apache.org/jira/browse/ARTEMIS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234683#comment-17234683 ] arne anka commented on ARTEMIS-2987: Managed to send a short XML file to create a screenshot with everything. If you compare the bytes section to the plain text, you probaly can imagine how large it is when the XML is more substantial. Screenshot_20201118_153435.png shows the Prefrences drop down – here a simple option "text only" would be helpful. And, of course, if those fat tables Properties and Headers could be collapsible again and with a far smaller font for the names. > Management Console -> Queue -> Message: view with text only > --- > > Key: ARTEMIS-2987 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2987 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: arne anka >Priority: Minor > Attachments: 1.jpg, 2.jpg, Screenshot_20201118_140052.png, > Screenshot_20201118_153254.png, Screenshot_20201118_153435.png > > > In tab [Artemis]expand addresses to a queue with messages in it > In the right area where the messages are listed click on a messaeg id > A view opens that is full of the byte calue of the content. > To get to a human readable representation one has to scroll down to the > "text" section. > When doin that the navigation bar disappears as well, so every timeI navigate > to a new message I have to scroll down a lengthy view and scroll up gaian to > get to the next message. > > Since my messages are esxclusively XML I have no use at all for the "byte" > section, but it is impossible to get rid of it and I have to go through those > tedious steps over and over again. > Preferences do not offer a text-only representation. > > So, please include a representation that only shows the text, and while at it > make the navigation bar stay in place when scrolling the message. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2987) Management Console -> Queue -> Message: view with text only
[ https://issues.apache.org/jira/browse/ARTEMIS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] arne anka updated ARTEMIS-2987: --- Attachment: Screenshot_20201118_153435.png > Management Console -> Queue -> Message: view with text only > --- > > Key: ARTEMIS-2987 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2987 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: arne anka >Priority: Minor > Attachments: 1.jpg, 2.jpg, Screenshot_20201118_140052.png, > Screenshot_20201118_153254.png, Screenshot_20201118_153435.png > > > In tab [Artemis]expand addresses to a queue with messages in it > In the right area where the messages are listed click on a messaeg id > A view opens that is full of the byte calue of the content. > To get to a human readable representation one has to scroll down to the > "text" section. > When doin that the navigation bar disappears as well, so every timeI navigate > to a new message I have to scroll down a lengthy view and scroll up gaian to > get to the next message. > > Since my messages are esxclusively XML I have no use at all for the "byte" > section, but it is impossible to get rid of it and I have to go through those > tedious steps over and over again. > Preferences do not offer a text-only representation. > > So, please include a representation that only shows the text, and while at it > make the navigation bar stay in place when scrolling the message. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2987) Management Console -> Queue -> Message: view with text only
[ https://issues.apache.org/jira/browse/ARTEMIS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] arne anka updated ARTEMIS-2987: --- Attachment: Screenshot_20201118_153254.png > Management Console -> Queue -> Message: view with text only > --- > > Key: ARTEMIS-2987 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2987 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: arne anka >Priority: Minor > Attachments: 1.jpg, 2.jpg, Screenshot_20201118_140052.png, > Screenshot_20201118_153254.png > > > In tab [Artemis]expand addresses to a queue with messages in it > In the right area where the messages are listed click on a messaeg id > A view opens that is full of the byte calue of the content. > To get to a human readable representation one has to scroll down to the > "text" section. > When doin that the navigation bar disappears as well, so every timeI navigate > to a new message I have to scroll down a lengthy view and scroll up gaian to > get to the next message. > > Since my messages are esxclusively XML I have no use at all for the "byte" > section, but it is impossible to get rid of it and I have to go through those > tedious steps over and over again. > Preferences do not offer a text-only representation. > > So, please include a representation that only shows the text, and while at it > make the navigation bar stay in place when scrolling the message. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2987) Management Console -> Queue -> Message: view with text only
[ https://issues.apache.org/jira/browse/ARTEMIS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] arne anka updated ARTEMIS-2987: --- Attachment: Screenshot_20201118_140052.png > Management Console -> Queue -> Message: view with text only > --- > > Key: ARTEMIS-2987 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2987 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: arne anka >Priority: Minor > Attachments: 1.jpg, 2.jpg, Screenshot_20201118_140052.png > > > In tab [Artemis]expand addresses to a queue with messages in it > In the right area where the messages are listed click on a messaeg id > A view opens that is full of the byte calue of the content. > To get to a human readable representation one has to scroll down to the > "text" section. > When doin that the navigation bar disappears as well, so every timeI navigate > to a new message I have to scroll down a lengthy view and scroll up gaian to > get to the next message. > > Since my messages are esxclusively XML I have no use at all for the "byte" > section, but it is impossible to get rid of it and I have to go through those > tedious steps over and over again. > Preferences do not offer a text-only representation. > > So, please include a representation that only shows the text, and while at it > make the navigation bar stay in place when scrolling the message. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2987) Management Console -> Queue -> Message: view with text only
[ https://issues.apache.org/jira/browse/ARTEMIS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234590#comment-17234590 ] arne anka commented on ARTEMIS-2987: Finally managed to update to 2.16.0, and far from being an improvement it's much worse now. As your second screenshot already shows there are no two big fat tables Headers Properties which cannot be collapsed anymore (as was the case in 2.10.1), but take now up even more space than necessary. Secondly, I don't know what kind of message you posted for your screenshot, but with my XML mesages I still get the bytes: ... text: display. So, now instead of just needing to scroll over that large "bytes:" area I also have to scroll over thos large tables that used to be collpased. BTW: I'd really appreciate if you could wait for my response before closing – it is obviously premature and unjustified. > Management Console -> Queue -> Message: view with text only > --- > > Key: ARTEMIS-2987 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2987 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: arne anka >Priority: Minor > Attachments: 1.jpg, 2.jpg, Screenshot_20201118_140052.png > > > In tab [Artemis]expand addresses to a queue with messages in it > In the right area where the messages are listed click on a messaeg id > A view opens that is full of the byte calue of the content. > To get to a human readable representation one has to scroll down to the > "text" section. > When doin that the navigation bar disappears as well, so every timeI navigate > to a new message I have to scroll down a lengthy view and scroll up gaian to > get to the next message. > > Since my messages are esxclusively XML I have no use at all for the "byte" > section, but it is impossible to get rid of it and I have to go through those > tedious steps over and over again. > Preferences do not offer a text-only representation. > > So, please include a representation that only shows the text, and while at it > make the navigation bar stay in place when scrolling the message. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2999) Documentation insufficient for updates of existing Artemis installation
arne anka created ARTEMIS-2999:
--
Summary: Documentation insufficient for updates of existing
Artemis installation
Key: ARTEMIS-2999
URL: https://issues.apache.org/jira/browse/ARTEMIS-2999
Project: ActiveMQ Artemis
Issue Type: Bug
Affects Versions: 2.16.0
Reporter: arne anka
Apparently the only bit of information regarding updates of an existing Artemis
installation is the "Versions" section of the user manual.
But even with 2.16.0 it ends with 2.14 and the instructions for 2.14 are less
than helpful:
"Make sure the existing queues have their parameters set according to the
{{broker.xml}} values before upgrading."
* What parameters exactly?
* How exactly _DO_ I update? Unpack the new archive and copy $INSTANCE over?
* $INSTANCE/bin/ scripts are generated during instance creation – are they
still valid? Do I need to change anything?
Since the documentation in general is little user friendly for users that do
not work full time with Artemis, I had a hard time setting up Artemis initially
with the existing documentation (and judging from my research back then I am
far from being alone), and I certainly don't want to jeopardize it now due to a
lack of useful directions.
Would it be possible to revisit this and documentation in general keeping in
mind that also users outside of the Artemis community may want to use this?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ARTEMIS-2998) example broker.xml does not validate artemis-configuration.xsd
arne anka created ARTEMIS-2998:
--
Summary: example broker.xml does not validate
artemis-configuration.xsd
Key: ARTEMIS-2998
URL: https://issues.apache.org/jira/browse/ARTEMIS-2998
Project: ActiveMQ Artemis
Issue Type: Bug
Affects Versions: 2.16.0
Reporter: arne anka
{code:java}
$ xmllint --schema apache-artemis-2.16.0/schema/artemis-configuration.xsd
apache-artemis-2.16.0/examples/features/federation/federated-queue/src/main/resources/activemq/server0/broker.xml
--noout
apache-artemis-2.16.0/examples/features/federation/federated-queue/src/main/resources/activemq/server0/broker.xml:22:
elementconfiguration: Schemas validity error : Element
'{urn:activemq}configuration': No matching global declaration available for the
validation root.
apache-artemis-2.16.0/examples/features/federation/federated-queue/src/main/resources/activemq/server0/broker.xml
fails to validate{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ARTEMIS-2988) Management Console -> Queue -> Messages: allow download of messages
arne anka created ARTEMIS-2988: -- Summary: Management Console -> Queue -> Messages: allow download of messages Key: ARTEMIS-2988 URL: https://issues.apache.org/jira/browse/ARTEMIS-2988 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: arne anka It would be helpful if one could download messages in for instance a DLQ. Currently one has to jump through several hoops to get at the text and then copy it to an external editor. Since the text is already there it shouldn't be too hard to just allow to save one or more messages to files. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2987) Management Console -> Queue -> Message: view with text only
arne anka created ARTEMIS-2987: -- Summary: Management Console -> Queue -> Message: view with text only Key: ARTEMIS-2987 URL: https://issues.apache.org/jira/browse/ARTEMIS-2987 Project: ActiveMQ Artemis Issue Type: Improvement Components: Web Console Reporter: arne anka In tab [Artemis]expand addresses to a queue with messages in it In the right area where the messages are listed click on a messaeg id A view opens that is full of the byte calue of the content. To get to a human readable representation one has to scroll down to the "text" section. When doin that the navigation bar disappears as well, so every timeI navigate to a new message I have to scroll down a lengthy view and scroll up gaian to get to the next message. Since my messages are esxclusively XML I have no use at all for the "byte" section, but it is impossible to get rid of it and I have to go through those tedious steps over and over again. Preferences do not offer a text-only representation. So, please include a representation that only shows the text, and while at it make the navigation bar stay in place when scrolling the message. -- This message was sent by Atlassian Jira (v8.3.4#803005)
