[jira] [Commented] (ARTEMIS-4796) Simplify SimpleString API
[
https://issues.apache.org/jira/browse/ARTEMIS-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853814#comment-17853814
]
ASF subversion and git services commented on ARTEMIS-4796:
--
Commit 220a5ae2aa176d19185b6f3ec41b24b6f04e0c6f in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=220a5ae2aa ]
ARTEMIS-4796 add tests & remove refs
> Simplify SimpleString API
> -
>
> Key: ARTEMIS-4796
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4796
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Instead of using the verbosely named {{toSimpleString}} static factory method
> (and its overloaded counterparts), {{SimpleString}} should provide {{of}}
> implementations. This change would make the code more concise and readable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Work logged] (ARTEMIS-4796) Simplify SimpleString API
[
https://issues.apache.org/jira/browse/ARTEMIS-4796?focusedWorklogId=922873=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-922873
]
ASF GitHub Bot logged work on ARTEMIS-4796:
---
Author: ASF GitHub Bot
Created on: 10/Jun/24 21:03
Start Date: 10/Jun/24 21:03
Worklog Time Spent: 10m
Work Description: tabish121 merged PR #4967:
URL: https://github.com/apache/activemq-artemis/pull/4967
Issue Time Tracking
---
Worklog Id: (was: 922873)
Time Spent: 3.5h (was: 3h 20m)
> Simplify SimpleString API
> -
>
> Key: ARTEMIS-4796
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4796
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Instead of using the verbosely named {{toSimpleString}} static factory method
> (and its overloaded counterparts), {{SimpleString}} should provide {{of}}
> implementations. This change would make the code more concise and readable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Work logged] (ARTEMIS-4809) Make intermediateMessageReferences initial capacity configurable
[
https://issues.apache.org/jira/browse/ARTEMIS-4809?focusedWorklogId=922855=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-922855
]
ASF GitHub Bot logged work on ARTEMIS-4809:
---
Author: ASF GitHub Bot
Created on: 10/Jun/24 18:12
Start Date: 10/Jun/24 18:12
Worklog Time Spent: 10m
Work Description: joshb1050 commented on PR #4966:
URL:
https://github.com/apache/activemq-artemis/pull/4966#issuecomment-2159000754
Thanks @jbertram! I have updated my PR to make this configurable on a
per-address basis and via XML as well. I have also added tests for the
functionality. Please let me know if there is a different approach I should be
taking here.
Issue Time Tracking
---
Worklog Id: (was: 922855)
Time Spent: 0.5h (was: 20m)
> Make intermediateMessageReferences initial capacity configurable
>
>
> Key: ARTEMIS-4809
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4809
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
>Reporter: Josh Byster
>Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In some setups, there could be a few hundred thousand queues that are created
> due to many consumers that are connecting. However, most of these are empty
> and stay empty for the entire day since there aren't necessarily messages to
> be sent.
> The 8K {{intermediateMessageReferences}} instantiates an 64KB buffer
> ({{Object[]}}). This means we have large allocation and live heap that
> ultimately remains empty for almost the entire day.
> It would be quite nice if we could configure this initial size.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Work logged] (ARTEMIS-4811) Upgrade Netty to 4.1.110.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-4811?focusedWorklogId=922846=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-922846 ] ASF GitHub Bot logged work on ARTEMIS-4811: --- Author: ASF GitHub Bot Created on: 10/Jun/24 16:21 Start Date: 10/Jun/24 16:21 Worklog Time Spent: 10m Work Description: ehsavoie opened a new pull request, #4969: URL: https://github.com/apache/activemq-artemis/pull/4969 (no comment) Issue Time Tracking --- Worklog Id: (was: 922846) Remaining Estimate: 0h Time Spent: 10m > Upgrade Netty to 4.1.110.Final > -- > > Key: ARTEMIS-4811 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4811 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Emmanuel Hugonnet >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org For additional commands, e-mail: issues-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
[jira] [Created] (ARTEMIS-4811) Upgrade Netty to 4.1.110.Final
Emmanuel Hugonnet created ARTEMIS-4811: -- Summary: Upgrade Netty to 4.1.110.Final Key: ARTEMIS-4811 URL: https://issues.apache.org/jira/browse/ARTEMIS-4811 Project: ActiveMQ Artemis Issue Type: Dependency upgrade Reporter: Emmanuel Hugonnet -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org For additional commands, e-mail: issues-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
[jira] [Commented] (ARTEMIS-4800) Simplify QueueConfiguration API
[ https://issues.apache.org/jira/browse/ARTEMIS-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853701#comment-17853701 ] ASF subversion and git services commented on ARTEMIS-4800: -- Commit 14c564a48144b0e052c6e064ba0f94744335 in activemq-artemis's branch refs/heads/main from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=14c564a481 ] ARTEMIS-4800 simplify QueueConfiguration API This commit does the following: - deprecate all QueueConfiguration ctors - add `of` static factory methods for all the deprecated ctors - replace any uses of the normal ctors with the `of` counterparts This makes the code more concise and readable. > Simplify QueueConfiguration API > --- > > Key: ARTEMIS-4800 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4800 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org For additional commands, e-mail: issues-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
[jira] [Work logged] (ARTEMIS-4800) Simplify QueueConfiguration API
[ https://issues.apache.org/jira/browse/ARTEMIS-4800?focusedWorklogId=922832=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-922832 ] ASF GitHub Bot logged work on ARTEMIS-4800: --- Author: ASF GitHub Bot Created on: 10/Jun/24 14:58 Start Date: 10/Jun/24 14:58 Worklog Time Spent: 10m Work Description: tabish121 merged PR #4964: URL: https://github.com/apache/activemq-artemis/pull/4964 Issue Time Tracking --- Worklog Id: (was: 922832) Time Spent: 0.5h (was: 20m) > Simplify QueueConfiguration API > --- > > Key: ARTEMIS-4800 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4800 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org For additional commands, e-mail: issues-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
[jira] [Work logged] (ARTEMIS-4780) Artemis web console does not ever set 'artemisJmxDomain' in localStorage
[
https://issues.apache.org/jira/browse/ARTEMIS-4780?focusedWorklogId=922816=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-922816
]
ASF GitHub Bot logged work on ARTEMIS-4780:
---
Author: ASF GitHub Bot
Created on: 10/Jun/24 12:58
Start Date: 10/Jun/24 12:58
Worklog Time Spent: 10m
Work Description: andytaylor commented on PR #18:
URL:
https://github.com/apache/activemq-artemis-console/pull/18#issuecomment-2158283290
I have made it configurable and this time actually use it, I can reopen this
or raise a new PR, wdyt?
Issue Time Tracking
---
Worklog Id: (was: 922816)
Time Spent: 1h 10m (was: 1h)
> Artemis web console does not ever set 'artemisJmxDomain' in localStorage
>
>
> Key: ARTEMIS-4780
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4780
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Josh Byster
>Assignee: Andy Taylor
>Priority: Minor
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> We relocate our artemis packages as part of our shading process.
> I did set up:
>
> {code:java}
> aActiveMQServer.getConfiguration().setJMXDomain("com.abc.shaded.org.apache.activemq.artemis");
> {code}
> However the web console does not show up. I noticed in the code it's because
> we try to read in localStorage['artemisJmxDomain'] but never actually set it
> as far as I can tell. Thus we always default to org.apache.activemq.artemis.
> Everything works properly when setting localStorage['artemisJmxDomain'] =
> "com.abc.shaded.org.apache.activemq.artemis"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Work logged] (ARTEMIS-4545) Allow node ID to be configured
[ https://issues.apache.org/jira/browse/ARTEMIS-4545?focusedWorklogId=922811=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-922811 ] ASF GitHub Bot logged work on ARTEMIS-4545: --- Author: ASF GitHub Bot Created on: 10/Jun/24 12:50 Start Date: 10/Jun/24 12:50 Worklog Time Spent: 10m Work Description: gtully commented on PR #4951: URL: https://github.com/apache/activemq-artemis/pull/4951#issuecomment-2158260584 > @gtully Do you know of any current test that demonstrates (or at least includes) having to wait for a lease expiry for the JDBC case? https://github.com/apache/activemq-artemis/blob/362dbd11ac132e66f7bce99eb0fb4aa020346210/artemis-server/src/test/java/org/apache/activemq/artemis/core/server/impl/jdbc/JdbcLeaseLockTest.java#L218 that looks like it should have to wait. Issue Time Tracking --- Worklog Id: (was: 922811) Time Spent: 1h (was: 50m) > Allow node ID to be configured > -- > > Key: ARTEMIS-4545 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4545 > Project: ActiveMQ Artemis > Issue Type: New Feature >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > In certain situations it would be beneficial to configure the node ID rather > than having it automatically generated. > For example, when using replication + failback if the primary server fails > the backup will take over. Then when the primary is restarted it will > initiate failback. However, if the primary broker's journal is damaged or > lost during the initial failure then it won't be able to initiate failback > because it won't have the same node ID as the backup. This kind of situation > is not uncommon in cloud environments where there is no persistent, attached > storage. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org For additional commands, e-mail: issues-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
[jira] [Work logged] (ARTEMIS-4545) Allow node ID to be configured
[ https://issues.apache.org/jira/browse/ARTEMIS-4545?focusedWorklogId=922794=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-922794 ] ASF GitHub Bot logged work on ARTEMIS-4545: --- Author: ASF GitHub Bot Created on: 10/Jun/24 11:51 Start Date: 10/Jun/24 11:51 Worklog Time Spent: 10m Work Description: AntonRoskvist commented on PR #4951: URL: https://github.com/apache/activemq-artemis/pull/4951#issuecomment-2158137960 @gtully Do you know of any current test that demonstrates (or at least includes) having to wait for a lease expiry for the JDBC case? Issue Time Tracking --- Worklog Id: (was: 922794) Time Spent: 50m (was: 40m) > Allow node ID to be configured > -- > > Key: ARTEMIS-4545 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4545 > Project: ActiveMQ Artemis > Issue Type: New Feature >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > In certain situations it would be beneficial to configure the node ID rather > than having it automatically generated. > For example, when using replication + failback if the primary server fails > the backup will take over. Then when the primary is restarted it will > initiate failback. However, if the primary broker's journal is damaged or > lost during the initial failure then it won't be able to initiate failback > because it won't have the same node ID as the backup. This kind of situation > is not uncommon in cloud environments where there is no persistent, attached > storage. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org For additional commands, e-mail: issues-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
[jira] [Assigned] (AMQ-9513) AMQP 1.0 message with multiple Data sections can be sent to broker but corrupted
[ https://issues.apache.org/jira/browse/AMQ-9513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-9513: - Assignee: Jean-Baptiste Onofré > AMQP 1.0 message with multiple Data sections can be sent to broker but > corrupted > > > Key: AMQ-9513 > URL: https://issues.apache.org/jira/browse/AMQ-9513 > Project: ActiveMQ Classic > Issue Type: Bug > Components: AMQP >Affects Versions: 5.18.4, 6.1.2 >Reporter: Yuriy Lepikhov >Assignee: Jean-Baptiste Onofré >Priority: Major > > ActiveMQ Classic uses Qpid Proton-J to support AMQP 1.0, but Qpid Proton-J > does not support messages with multiple Data sections (see, PROTON-2299). > One can send such message to broker, broker will accept such message, but it > will use last odd Data section as message body (no exception thrown or > warning logged). > It is even possible to receive such message from broker, but it will contain > fewer bytes than original (and may be not from beginning). > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org For additional commands, e-mail: issues-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
