[jira] [Work logged] (ARTEMIS-4553) Support partial word matches for address settings
[ https://issues.apache.org/jira/browse/ARTEMIS-4553?focusedWorklogId=910458=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910458 ] ASF GitHub Bot logged work on ARTEMIS-4553: --- Author: ASF GitHub Bot Created on: 19/Mar/24 05:18 Start Date: 19/Mar/24 05:18 Worklog Time Spent: 10m Work Description: brusdev closed pull request #4730: ARTEMIS-4553 Support partial word matches for address settings URL: https://github.com/apache/activemq-artemis/pull/4730 Issue Time Tracking --- Worklog Id: (was: 910458) Time Spent: 1h 20m (was: 1h 10m) > Support partial word matches for address settings > - > > Key: ARTEMIS-4553 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4553 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently, though the documentation specifies that the "*" wildcard matcher > is only intended to match a complete word (delimited string using the > configured delimiter), it appears that it also works for partial word > matches, like " > Could this behavior be supported and documented going forward, as reverting > this behavior would break existing configurations? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4689) Import command should accept URL
[ https://issues.apache.org/jira/browse/ARTEMIS-4689?focusedWorklogId=910445=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910445 ] ASF GitHub Bot logged work on ARTEMIS-4689: --- Author: ASF GitHub Bot Created on: 19/Mar/24 01:16 Start Date: 19/Mar/24 01:16 Worklog Time Spent: 10m Work Description: clebertsuconic commented on PR #4859: URL: https://github.com/apache/activemq-artemis/pull/4859#issuecomment-2005554570 @jbertram I missed that you didn't set the right super class on XMLDataImporter. if you could merge this before the release please? Issue Time Tracking --- Worklog Id: (was: 910445) Time Spent: 1h 50m (was: 1h 40m) > Import command should accept URL > > > Key: ARTEMIS-4689 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4689 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > Currently the import command only takes host & port with regard to its > connection to the broker. It should take a URL instead so that the connection > can be configured appropriately for more use-cases (e.g. using TLS). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4689) Import command should accept URL
[ https://issues.apache.org/jira/browse/ARTEMIS-4689?focusedWorklogId=910446=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910446 ] ASF GitHub Bot logged work on ARTEMIS-4689: --- Author: ASF GitHub Bot Created on: 19/Mar/24 01:16 Start Date: 19/Mar/24 01:16 Worklog Time Spent: 10m Work Description: clebertsuconic commented on PR #4859: URL: https://github.com/apache/activemq-artemis/pull/4859#issuecomment-200078 I will merge it when all the tests are good (just running the CI to double check it) Issue Time Tracking --- Worklog Id: (was: 910446) Time Spent: 2h (was: 1h 50m) > Import command should accept URL > > > Key: ARTEMIS-4689 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4689 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 2h > Remaining Estimate: 0h > > Currently the import command only takes host & port with regard to its > connection to the broker. It should take a URL instead so that the connection > can be configured appropriately for more use-cases (e.g. using TLS). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4689) Import command should accept URL
[ https://issues.apache.org/jira/browse/ARTEMIS-4689?focusedWorklogId=910444=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910444 ] ASF GitHub Bot logged work on ARTEMIS-4689: --- Author: ASF GitHub Bot Created on: 19/Mar/24 01:15 Start Date: 19/Mar/24 01:15 Worklog Time Spent: 10m Work Description: clebertsuconic opened a new pull request, #4859: URL: https://github.com/apache/activemq-artemis/pull/4859 (no comment) Issue Time Tracking --- Worklog Id: (was: 910444) Time Spent: 1h 40m (was: 1.5h) > Import command should accept URL > > > Key: ARTEMIS-4689 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4689 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > Currently the import command only takes host & port with regard to its > connection to the broker. It should take a URL instead so that the connection > can be configured appropriately for more use-cases (e.g. using TLS). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4689) Import command should accept URL
[ https://issues.apache.org/jira/browse/ARTEMIS-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828141#comment-17828141 ] ASF subversion and git services commented on ARTEMIS-4689: -- Commit 71d33932244bea52d16f8cdf1482f17c088cbb2b in activemq-artemis's branch refs/heads/main from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=71d3393224 ] ARTEMIS-4689 import command should accept URL > Import command should accept URL > > > Key: ARTEMIS-4689 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4689 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > Currently the import command only takes host & port with regard to its > connection to the broker. It should take a URL instead so that the connection > can be configured appropriately for more use-cases (e.g. using TLS). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4689) Import command should accept URL
[ https://issues.apache.org/jira/browse/ARTEMIS-4689?focusedWorklogId=910443=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910443 ] ASF GitHub Bot logged work on ARTEMIS-4689: --- Author: ASF GitHub Bot Created on: 19/Mar/24 01:06 Start Date: 19/Mar/24 01:06 Worklog Time Spent: 10m Work Description: clebertsuconic merged PR #4855: URL: https://github.com/apache/activemq-artemis/pull/4855 Issue Time Tracking --- Worklog Id: (was: 910443) Time Spent: 1.5h (was: 1h 20m) > Import command should accept URL > > > Key: ARTEMIS-4689 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4689 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > Currently the import command only takes host & port with regard to its > connection to the broker. It should take a URL instead so that the connection > can be configured appropriately for more use-cases (e.g. using TLS). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828110#comment-17828110
]
ASF subversion and git services commented on ARTEMIS-4691:
--
Commit 308aed306076cb789f0a2672744e0c4c1dbb6c7f in activemq-artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=308aed3060 ]
ARTEMIS-4691 Fixing LockManagerBackupSyncJournalTest
Fixing a few intermittent failures
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?focusedWorklogId=910408=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910408
]
ASF GitHub Bot logged work on ARTEMIS-4691:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 21:36
Start Date: 18/Mar/24 21:36
Worklog Time Spent: 10m
Work Description: clebertsuconic merged PR #4858:
URL: https://github.com/apache/activemq-artemis/pull/4858
Issue Time Tracking
---
Worklog Id: (was: 910408)
Time Spent: 2h (was: 1h 50m)
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?focusedWorklogId=910397=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910397
]
ASF GitHub Bot logged work on ARTEMIS-4691:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 20:44
Start Date: 18/Mar/24 20:44
Worklog Time Spent: 10m
Work Description: clebertsuconic opened a new pull request, #4858:
URL: https://github.com/apache/activemq-artemis/pull/4858
Fixing a few intermittent failures
Issue Time Tracking
---
Worklog Id: (was: 910397)
Time Spent: 1h 50m (was: 1h 40m)
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?focusedWorklogId=910386=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910386
]
ASF GitHub Bot logged work on ARTEMIS-4691:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 18:31
Start Date: 18/Mar/24 18:31
Worklog Time Spent: 10m
Work Description: jbertram merged PR #4857:
URL: https://github.com/apache/activemq-artemis/pull/4857
Issue Time Tracking
---
Worklog Id: (was: 910386)
Time Spent: 1h 40m (was: 1.5h)
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828077#comment-17828077
]
ASF subversion and git services commented on ARTEMIS-4691:
--
Commit 499a4eab6bf3134f2f8660f428f089eeb4001484 in activemq-artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=499a4eab6b ]
ARTEMIS-4691 log.warn on inVM closing
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?focusedWorklogId=910361=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910361
]
ASF GitHub Bot logged work on ARTEMIS-4691:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 15:10
Start Date: 18/Mar/24 15:10
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on code in PR #4857:
URL: https://github.com/apache/activemq-artemis/pull/4857#discussion_r1528750765
##
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SimpleTest.java:
##
Review Comment:
Ok.. I had already moved it anyway. thanks
Issue Time Tracking
---
Worklog Id: (was: 910361)
Time Spent: 1.5h (was: 1h 20m)
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (AMQ-9452) StatisticsPlugin - field firstMessageTimestamp is not produced for AuthorizationDestinationFilter
[
https://issues.apache.org/jira/browse/AMQ-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned AMQ-9452:
-
Assignee: Jean-Baptiste Onofré
> StatisticsPlugin - field firstMessageTimestamp is not produced for
> AuthorizationDestinationFilter
> -
>
> Key: AMQ-9452
> URL: https://issues.apache.org/jira/browse/AMQ-9452
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.18.3
>Reporter: Grzegorz Kochański
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{StatisticsBroker}} does not send field {{firstMessageTimestamp}} as dest
> may be instance of {{DestinationFilter}} (in my case:
> {{{}AuthorizationDestinationFilter{}}})
> {code:java}
> if (includeFirstMessageTimestamp) {
> if (dest instanceof Queue) {
> ((Queue) dest).doBrowse(tempFirstMessage, 1);
> }
> else if (dest instanceof Topic) {
> ((Topic) dest).doBrowse(tempFirstMessage, 1);
> }
> if (!tempFirstMessage.isEmpty()) {
> Message message = tempFirstMessage.get(0);
> // NOTICE: Client-side, you may get the broker "now" Timestamp by
> msg.getJMSTimestamp()
> // This allows for calculating age.
> statsMessage.setLong("firstMessageTimestamp",
> message.getBrokerInTime());
> tempFirstMessage.clear();
> } {code}
>
> It appears that {{BaseDestination}} may be unwinded:
> {code:java}
> //unwind BaseDestination
> while (dest instanceof DestinationFilter) {
> dest = ((DestinationFilter) dest).getNext();
> }
> {code}
>
>
> related to feature:
> https://github.com/apache/activemq/commit/9167a79b79e4c121cfe0a5b82456f52bf3ecc3c7
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (AMQ-9452) StatisticsPlugin - field firstMessageTimestamp is not produced for AuthorizationDestinationFilter
[
https://issues.apache.org/jira/browse/AMQ-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated AMQ-9452:
--
Fix Version/s: 5.18.4
6.2.0
6.1.1
> StatisticsPlugin - field firstMessageTimestamp is not produced for
> AuthorizationDestinationFilter
> -
>
> Key: AMQ-9452
> URL: https://issues.apache.org/jira/browse/AMQ-9452
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.18.3
>Reporter: Grzegorz Kochański
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.18.4, 6.2.0, 6.1.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{StatisticsBroker}} does not send field {{firstMessageTimestamp}} as dest
> may be instance of {{DestinationFilter}} (in my case:
> {{{}AuthorizationDestinationFilter{}}})
> {code:java}
> if (includeFirstMessageTimestamp) {
> if (dest instanceof Queue) {
> ((Queue) dest).doBrowse(tempFirstMessage, 1);
> }
> else if (dest instanceof Topic) {
> ((Topic) dest).doBrowse(tempFirstMessage, 1);
> }
> if (!tempFirstMessage.isEmpty()) {
> Message message = tempFirstMessage.get(0);
> // NOTICE: Client-side, you may get the broker "now" Timestamp by
> msg.getJMSTimestamp()
> // This allows for calculating age.
> statsMessage.setLong("firstMessageTimestamp",
> message.getBrokerInTime());
> tempFirstMessage.clear();
> } {code}
>
> It appears that {{BaseDestination}} may be unwinded:
> {code:java}
> //unwind BaseDestination
> while (dest instanceof DestinationFilter) {
> dest = ((DestinationFilter) dest).getNext();
> }
> {code}
>
>
> related to feature:
> https://github.com/apache/activemq/commit/9167a79b79e4c121cfe0a5b82456f52bf3ecc3c7
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?focusedWorklogId=910357=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910357
]
ASF GitHub Bot logged work on ARTEMIS-4691:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 14:58
Start Date: 18/Mar/24 14:58
Worklog Time Spent: 10m
Work Description: jbertram commented on code in PR #4857:
URL: https://github.com/apache/activemq-artemis/pull/4857#discussion_r1528729315
##
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SimpleTest.java:
##
Review Comment:
As the JavaDoc states this test is, "A simple test-case used for
documentation purposes." This test is referenced in the [Hacking
Guide](https://activemq.apache.org/components/artemis/documentation/hacking-guide/#writing-tests)
as a guide to help folks get started writing tests. Adding anything
superfluous to basic testing is going to diminish the effectiveness of the test
as a generic example.
Issue Time Tracking
---
Worklog Id: (was: 910357)
Time Spent: 1h 20m (was: 1h 10m)
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?focusedWorklogId=910356=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910356
]
ASF GitHub Bot logged work on ARTEMIS-4691:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 14:58
Start Date: 18/Mar/24 14:58
Worklog Time Spent: 10m
Work Description: jbertram commented on code in PR #4857:
URL: https://github.com/apache/activemq-artemis/pull/4857#discussion_r1528729315
##
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SimpleTest.java:
##
Review Comment:
As the JavaDoc states this test is, "A simple test-case used for
documentation purposes." This test is referenced in the Hacking Guide as a
guide to help folks get started writing tests. Adding anything superfluous to
basic testing is going to diminish the effectiveness of the test as a generic
example.
Issue Time Tracking
---
Worklog Id: (was: 910356)
Time Spent: 1h 10m (was: 1h)
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?focusedWorklogId=910355=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910355
]
ASF GitHub Bot logged work on ARTEMIS-4691:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 14:57
Start Date: 18/Mar/24 14:57
Worklog Time Spent: 10m
Work Description: jbertram commented on code in PR #4857:
URL: https://github.com/apache/activemq-artemis/pull/4857#discussion_r1528729315
##
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SimpleTest.java:
##
Review Comment:
As the JavaDoc states, "A simple test-case used for documentation purposes."
This test is referenced in the Hacking Guide as a guide to help folks get
started writing tests. Adding anything superfluous to basic testing is going to
diminish the effectiveness of the test as a generic example.
Issue Time Tracking
---
Worklog Id: (was: 910355)
Time Spent: 1h (was: 50m)
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?focusedWorklogId=910354=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910354
]
ASF GitHub Bot logged work on ARTEMIS-4691:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 14:55
Start Date: 18/Mar/24 14:55
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on code in PR #4857:
URL: https://github.com/apache/activemq-artemis/pull/4857#discussion_r1528725300
##
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SimpleTest.java:
##
Review Comment:
I don't see any reference from the doc as the javadoc in the test states.
Issue Time Tracking
---
Worklog Id: (was: 910354)
Time Spent: 50m (was: 40m)
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?focusedWorklogId=910350=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910350
]
ASF GitHub Bot logged work on ARTEMIS-4691:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 14:54
Start Date: 18/Mar/24 14:54
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on code in PR #4857:
URL: https://github.com/apache/activemq-artemis/pull/4857#discussion_r1528722765
##
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SimpleTest.java:
##
Review Comment:
why?
Issue Time Tracking
---
Worklog Id: (was: 910350)
Time Spent: 0.5h (was: 20m)
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?focusedWorklogId=910351=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910351
]
ASF GitHub Bot logged work on ARTEMIS-4691:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 14:54
Start Date: 18/Mar/24 14:54
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on code in PR #4857:
URL: https://github.com/apache/activemq-artemis/pull/4857#discussion_r1528723764
##
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SimpleTest.java:
##
Review Comment:
the test still simple ;)
Issue Time Tracking
---
Worklog Id: (was: 910351)
Time Spent: 40m (was: 0.5h)
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=910348=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910348 ] ASF GitHub Bot logged work on ARTEMIS-4498: --- Author: ASF GitHub Bot Created on: 18/Mar/24 14:53 Start Date: 18/Mar/24 14:53 Worklog Time Spent: 10m Work Description: clebertsuconic commented on PR #4856: URL: https://github.com/apache/activemq-artemis/pull/4856#issuecomment-2004134298 @AntonRoskvist I would rather delay this fix and do a proper fix in the next release. I'm looking to fix this before the next release, which may be a shorter release (timewise on when we are releasing it). Issue Time Tracking --- Worklog Id: (was: 910348) Time Spent: 6h 40m (was: 6.5h) > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 6h 40m > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?focusedWorklogId=910349=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910349
]
ASF GitHub Bot logged work on ARTEMIS-4691:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 14:53
Start Date: 18/Mar/24 14:53
Worklog Time Spent: 10m
Work Description: jbertram commented on code in PR #4857:
URL: https://github.com/apache/activemq-artemis/pull/4857#discussion_r1528721751
##
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SimpleTest.java:
##
Review Comment:
This should be in a new test rather than modifying `SimpleTest`.
Issue Time Tracking
---
Worklog Id: (was: 910349)
Time Spent: 20m (was: 10m)
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9455) MessagePolicies added to DestinationPolicy
[ https://issues.apache.org/jira/browse/AMQ-9455?focusedWorklogId=910345=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910345 ] ASF GitHub Bot logged work on AMQ-9455: --- Author: ASF GitHub Bot Created on: 18/Mar/24 14:35 Start Date: 18/Mar/24 14:35 Worklog Time Spent: 10m Work Description: mattrpav opened a new pull request, #1182: URL: https://github.com/apache/activemq/pull/1182 (no comment) Issue Time Tracking --- Worklog Id: (was: 910345) Remaining Estimate: 0h Time Spent: 10m > MessagePolicies added to DestinationPolicy > -- > > Key: AMQ-9455 > URL: https://issues.apache.org/jira/browse/AMQ-9455 > Project: ActiveMQ Classic > Issue Type: New Feature >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > A configurable list of message policy entries that will all for message > enrichment and enforcement of message content policies. > This feature would serve to replace broker-wide plugins: > ForcePersistencyModeBrokerPlugin > TimeStampingBrokerPLugin > UserIDBroker -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=910346=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910346 ] ASF GitHub Bot logged work on ARTEMIS-4498: --- Author: ASF GitHub Bot Created on: 18/Mar/24 14:35 Start Date: 18/Mar/24 14:35 Worklog Time Spent: 10m Work Description: AntonRoskvist commented on PR #4856: URL: https://github.com/apache/activemq-artemis/pull/4856#issuecomment-2004087999 @clebertsuconic I agree that everything should be manageable, except perhaps for some protocol specific queues as you stated. Since the property "internal" is used to filter weather or not an address or queue should get exposed for management or not ( as of now ) and said protocol managers rely on this to filter Advisories for instance, a new property might be needed to decide if the destination should be manageable or not, instead of the current "internal" that has other uses, besides deciding manageability. Since that change would take some more work to implement it is out of scope for this release, which I 100% agree with. My interim solution/idea/example is to leave all this logic as is, with the only change being to manually register management for addresses and queues under "Notifications, SnF and AMQPMirror(which already ran this for the queues)". i.e. get management/metrics for the most critical parts for the upcoming release. This would later be replaced by the aforementioned "proper" change. (I don't like doing things that way but I'm weighing it against the usefulness of these destinations metrics I thought I'd ask at least) Issue Time Tracking --- Worklog Id: (was: 910346) Time Spent: 6.5h (was: 6h 20m) > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 6.5h > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4691) AMQ212037 warning when closing any in-vm connection
[
https://issues.apache.org/jira/browse/ARTEMIS-4691?focusedWorklogId=910343=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910343
]
ASF GitHub Bot logged work on ARTEMIS-4691:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 14:33
Start Date: 18/Mar/24 14:33
Worklog Time Spent: 10m
Work Description: clebertsuconic opened a new pull request, #4857:
URL: https://github.com/apache/activemq-artemis/pull/4857
(no comment)
Issue Time Tracking
---
Worklog Id: (was: 910343)
Remaining Estimate: 0h
Time Spent: 10m
> AMQ212037 warning when closing any in-vm connection
> ---
>
> Key: ARTEMIS-4691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.32.0
>Reporter: Todor Neykov
>Priority: Minor
> Attachments: image-2024-03-15-13-25-35-025.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We noticed this warning message after calling {{close()}} of an
> InVMConnection, e.g.:
> {noformat}
> AMQ212037: Connection failure to invm:0 has been detected: null
> [code=GENERIC_EXCEPTION]{noformat}
> !image-2024-03-15-13-25-35-025.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=910332=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910332 ] ASF GitHub Bot logged work on ARTEMIS-4498: --- Author: ASF GitHub Bot Created on: 18/Mar/24 13:40 Start Date: 18/Mar/24 13:40 Worklog Time Spent: 10m Work Description: clebertsuconic commented on PR #4856: URL: https://github.com/apache/activemq-artemis/pull/4856#issuecomment-2003937354 I don't understand your interim solution? you're forcing the registration if address =management address? I think everything should be manageable. (I have been bitten by that before) you may want to hidden certain address from the console, that could reappear after a toggle is selected. (maybe we hide internal addresses?) functionally I think we should have a flag to hide certain control queues only... (that I don't have a name for them yet). MQTT and OpenWire protocol managers have a few... even those should be able to reappear after a select toggle on the console. Issue Time Tracking --- Worklog Id: (was: 910332) Time Spent: 6h 20m (was: 6h 10m) > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 6h 20m > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4657) Support better correlation ID compatibility between JMS clients
[
https://issues.apache.org/jira/browse/ARTEMIS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated ARTEMIS-4657:
Summary: Support better correlation ID compatibility between JMS clients
(was: Support correlation ID compatibility between JMS clients)
> Support better correlation ID compatibility between JMS clients
> ---
>
> Key: ARTEMIS-4657
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4657
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.33.0
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> Currently there are some use-cases with both {{String}} and {{byte[]}} values
> of JMS correlation ID that don't work between Core, OpenWire, and AMQP. We
> should support as many as possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4657) Support correlation ID compatibility between JMS clients
[
https://issues.apache.org/jira/browse/ARTEMIS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved ARTEMIS-4657.
-
Fix Version/s: 2.33.0
Resolution: Fixed
> Support correlation ID compatibility between JMS clients
>
>
> Key: ARTEMIS-4657
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4657
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.33.0
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> Currently there are some use-cases with both {{String}} and {{byte[]}} values
> of JMS correlation ID that don't work between Core, OpenWire, and AMQP. We
> should support as many as possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4657) Support correlation ID compatibility between JMS clients
[
https://issues.apache.org/jira/browse/ARTEMIS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827961#comment-17827961
]
ASF subversion and git services commented on ARTEMIS-4657:
--
Commit 50fae08b09a76e200ef107d06cc867231f644ccd in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=50fae08b09 ]
ARTEMIS-4657 support better correlation ID compat b/w JMS clients
> Support correlation ID compatibility between JMS clients
>
>
> Key: ARTEMIS-4657
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4657
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> Currently there are some use-cases with both {{String}} and {{byte[]}} values
> of JMS correlation ID that don't work between Core, OpenWire, and AMQP. We
> should support as many as possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4657) Support correlation ID compatibility between JMS clients
[
https://issues.apache.org/jira/browse/ARTEMIS-4657?focusedWorklogId=910324=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910324
]
ASF GitHub Bot logged work on ARTEMIS-4657:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 13:19
Start Date: 18/Mar/24 13:19
Worklog Time Spent: 10m
Work Description: gemmellr merged PR #4833:
URL: https://github.com/apache/activemq-artemis/pull/4833
Issue Time Tracking
---
Worklog Id: (was: 910324)
Time Spent: 5h 20m (was: 5h 10m)
> Support correlation ID compatibility between JMS clients
>
>
> Key: ARTEMIS-4657
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4657
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> Currently there are some use-cases with both {{String}} and {{byte[]}} values
> of JMS correlation ID that don't work between Core, OpenWire, and AMQP. We
> should support as many as possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=910320=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910320 ] ASF GitHub Bot logged work on ARTEMIS-4498: --- Author: ASF GitHub Bot Created on: 18/Mar/24 12:41 Start Date: 18/Mar/24 12:41 Worklog Time Spent: 10m Work Description: AntonRoskvist commented on PR #4856: URL: https://github.com/apache/activemq-artemis/pull/4856#issuecomment-2003807846 @clebertsuconic Perhaps a simpler interim solution could be used in the mean-time, doing something like what I've added here: https://github.com/AntonRoskvist/activemq-artemis/tree/interim_ARTEMIS-4498 If you'd rather wait for the proper fix then that's fine too of course. Issue Time Tracking --- Worklog Id: (was: 910320) Time Spent: 6h 10m (was: 6h) > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 6h 10m > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9452) StatisticsPlugin - field firstMessageTimestamp is not produced for AuthorizationDestinationFilter
[
https://issues.apache.org/jira/browse/AMQ-9452?focusedWorklogId=910317=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910317
]
ASF GitHub Bot logged work on AMQ-9452:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 12:09
Start Date: 18/Mar/24 12:09
Worklog Time Spent: 10m
Work Description: ggkochanski commented on PR #1174:
URL: https://github.com/apache/activemq/pull/1174#issuecomment-2003745435
really nice metric (tried patched version in action), I encourage to merge
https://github.com/apache/activemq/assets/8193600/b1ecb6b4-2bae-46bc-9fe3-04f859b5eab8;>
Issue Time Tracking
---
Worklog Id: (was: 910317)
Time Spent: 40m (was: 0.5h)
> StatisticsPlugin - field firstMessageTimestamp is not produced for
> AuthorizationDestinationFilter
> -
>
> Key: AMQ-9452
> URL: https://issues.apache.org/jira/browse/AMQ-9452
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.18.3
>Reporter: Grzegorz Kochański
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{StatisticsBroker}} does not send field {{firstMessageTimestamp}} as dest
> may be instance of {{DestinationFilter}} (in my case:
> {{{}AuthorizationDestinationFilter{}}})
> {code:java}
> if (includeFirstMessageTimestamp) {
> if (dest instanceof Queue) {
> ((Queue) dest).doBrowse(tempFirstMessage, 1);
> }
> else if (dest instanceof Topic) {
> ((Topic) dest).doBrowse(tempFirstMessage, 1);
> }
> if (!tempFirstMessage.isEmpty()) {
> Message message = tempFirstMessage.get(0);
> // NOTICE: Client-side, you may get the broker "now" Timestamp by
> msg.getJMSTimestamp()
> // This allows for calculating age.
> statsMessage.setLong("firstMessageTimestamp",
> message.getBrokerInTime());
> tempFirstMessage.clear();
> } {code}
>
> It appears that {{BaseDestination}} may be unwinded:
> {code:java}
> //unwind BaseDestination
> while (dest instanceof DestinationFilter) {
> dest = ((DestinationFilter) dest).getNext();
> }
> {code}
>
>
> related to feature:
> https://github.com/apache/activemq/commit/9167a79b79e4c121cfe0a5b82456f52bf3ecc3c7
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4510) Add auto-create-destination logic to diverts
[ https://issues.apache.org/jira/browse/ARTEMIS-4510?focusedWorklogId=910298=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910298 ] ASF GitHub Bot logged work on ARTEMIS-4510: --- Author: ASF GitHub Bot Created on: 18/Mar/24 09:33 Start Date: 18/Mar/24 09:33 Worklog Time Spent: 10m Work Description: AntonRoskvist commented on PR #4681: URL: https://github.com/apache/activemq-artemis/pull/4681#issuecomment-2003331818 @clebertsuconic Started a thread on the dev mailing list to see if we can reach some consensus there, flagging this as draft until then. Issue Time Tracking --- Worklog Id: (was: 910298) Time Spent: 3h 40m (was: 3.5h) > Add auto-create-destination logic to diverts > > > Key: ARTEMIS-4510 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4510 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 3h 40m > Remaining Estimate: 0h > > This enables the use of dynamic routing decisions within the transformer by > setting the message address. It also covers for a rare problem where if any > of the forwarding addresses are removed during runtime, such as from > auto-delete, the message would get silently dropped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9459) Add appropriate JVM Args to allow access to sun.nio.* classes
[
https://issues.apache.org/jira/browse/AMQ-9459?focusedWorklogId=910296=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910296
]
ASF GitHub Bot logged work on AMQ-9459:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 08:14
Start Date: 18/Mar/24 08:14
Worklog Time Spent: 10m
Work Description: AM-19 commented on PR #1181:
URL: https://github.com/apache/activemq/pull/1181#issuecomment-2003165380
> It works for me. Which JDK are you using (provider) ?
>
> I will do some tests but it looks like an environment issue to me. Let me
double check.
Hello, I tested using Java Runtime: Eclipse Adoptium 17.0.10.
Just to double check, can you share your Runtime, Ill test using the exact
version, Will see how it goes,
Issue Time Tracking
---
Worklog Id: (was: 910296)
Time Spent: 1h 50m (was: 1h 40m)
> Add appropriate JVM Args to allow access to sun.nio.* classes
> -
>
> Key: AMQ-9459
> URL: https://issues.apache.org/jira/browse/AMQ-9459
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.17.6
>Reporter: Anubhav Mishra
>Priority: Minor
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters
> following exception:
> {code:java}
> ERROR | Could not set property soTimeout on
> ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=x] |
> org.apache.activemq.util.IntrospectionSupport | main
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.nio.ch.ServerSocketAdaptor.setSoTimeout(int) throws
> java.net.SocketException accessible: module java.base does not "opens
> sun.nio.ch" to unnamed module @4739cd70
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.configureServerSocket(TcpTransportServer.java:202)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:144)
> at
> org.apache.activemq.transport.auto.nio.AutoNioSslTransportFactory.doBind(AutoNioSslTransportFactory.java:122)
> at
> org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
> at
> org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:340)
> at
> org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:148)
> at
> org.apache.activemq.broker.TransportConnector.asManagedConnector(TransportConnector.java:113)
> at
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2241)
> at
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2728)
> at
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2624)
> at
> org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:762)
> at
> org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:724)
> at
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:622) {code}
> According to Oracle, with [JEP 403 (link1)|https://openjdk.java.net/jeps/403]
> and [JEP 403 (link2)|https://bugs.openjdk.java.net/browse/JDK-8263547] which
> has been decided to be *delivered from JDK 17 and onwards* , the
> setAccessible approach which was introduced as part of
> https://issues.apache.org/jira/browse/AMQ-7121 wont work.
>
> Fix: Adding the following in activemq file should do the job:
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9459) Add appropriate JVM Args to allow access to sun.nio.* classes
[
https://issues.apache.org/jira/browse/AMQ-9459?focusedWorklogId=910283=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910283
]
ASF GitHub Bot logged work on AMQ-9459:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 07:11
Start Date: 18/Mar/24 07:11
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #1181:
URL: https://github.com/apache/activemq/pull/1181#issuecomment-2003071743
It works for me. Which JDK are you using (provider) ?
I will do some tests but it looks like an environment issue to me. Let me
double check.
Issue Time Tracking
---
Worklog Id: (was: 910283)
Time Spent: 1h 40m (was: 1.5h)
> Add appropriate JVM Args to allow access to sun.nio.* classes
> -
>
> Key: AMQ-9459
> URL: https://issues.apache.org/jira/browse/AMQ-9459
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.17.6
>Reporter: Anubhav Mishra
>Priority: Minor
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters
> following exception:
> {code:java}
> ERROR | Could not set property soTimeout on
> ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=x] |
> org.apache.activemq.util.IntrospectionSupport | main
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.nio.ch.ServerSocketAdaptor.setSoTimeout(int) throws
> java.net.SocketException accessible: module java.base does not "opens
> sun.nio.ch" to unnamed module @4739cd70
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.configureServerSocket(TcpTransportServer.java:202)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:144)
> at
> org.apache.activemq.transport.auto.nio.AutoNioSslTransportFactory.doBind(AutoNioSslTransportFactory.java:122)
> at
> org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
> at
> org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:340)
> at
> org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:148)
> at
> org.apache.activemq.broker.TransportConnector.asManagedConnector(TransportConnector.java:113)
> at
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2241)
> at
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2728)
> at
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2624)
> at
> org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:762)
> at
> org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:724)
> at
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:622) {code}
> According to Oracle, with [JEP 403 (link1)|https://openjdk.java.net/jeps/403]
> and [JEP 403 (link2)|https://bugs.openjdk.java.net/browse/JDK-8263547] which
> has been decided to be *delivered from JDK 17 and onwards* , the
> setAccessible approach which was introduced as part of
> https://issues.apache.org/jira/browse/AMQ-7121 wont work.
>
> Fix: Adding the following in activemq file should do the job:
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9459) Add appropriate JVM Args to allow access to sun.nio.* classes
[
https://issues.apache.org/jira/browse/AMQ-9459?focusedWorklogId=910282=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910282
]
ASF GitHub Bot logged work on AMQ-9459:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 07:06
Start Date: 18/Mar/24 07:06
Worklog Time Spent: 10m
Work Description: AM-19 commented on PR #1181:
URL: https://github.com/apache/activemq/pull/1181#issuecomment-2003066163
> Ok, so I don't think we need it :)
Actually It does occur in 6.x
My bad I mis-spelled property while testing.
`
ERROR | Could not set property soTimeout on
ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=61616]
java.lang.reflect.InaccessibleObjectException: Unable to make public void
sun.nio.ch.ServerSocketAdaptor.setSoTimeout(int) throws
java.net.SocketException accessible: module java.base does not "opens
sun.nio.ch" to unnamed module @6f0603b8
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
~[?:?]
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
~[?:?]
at
java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199) ~[?:?]
at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
~[?:?]
at
org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
~[activemq-client-6.1.0.jar:6.1.0]
at
org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
~[activemq-client-6.1.0.jar:6.1.0]
at
org.apache.activemq.transport.tcp.TcpTransportServer.configureServerSocket(TcpTransportServer.java:204)
~[activemq-client-6.1.0.jar:6.1.0]
at
org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:146)
~[activemq-client-6.1.0.jar:6.1.0]
at
org.apache.activemq.transport.auto.nio.AutoNioSslTransportFactory.doBind(AutoNioSslTransportFactory.java:122)
~[activemq-broker-6.1.0.jar:6.1.0]
at
org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
~[activemq-broker-6.1.0.jar:6.1.0]
at
org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:349)
~[activemq-broker-6.1.0.jar:6.1.0]
at
org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:148)
~[activemq-broker-6.1.0.jar:6.1.0]
at
org.apache.activemq.broker.TransportConnector.asManagedConnector(TransportConnector.java:113)
~[activemq-broker-6.1.0.jar:6.1.0]
at
org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2248)
~[activemq-broker-6.1.0.jar:6.1.0]
at
org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2735)
~[activemq-broker-6.1.0.jar:6.1.0]
at
org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2631)
~[activemq-broker-6.1.0.jar:6.1.0]
at
org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:768)
~[activemq-broker-6.1.0.jar:6.1.0]
at
org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:730)
~[activemq-broker-6.1.0.jar:6.1.0]
at
org.apache.activemq.broker.BrokerService.start(BrokerService.java:628)
~[activemq-broker-6.1.0.jar:6.1.0]
at
org.apache.activemq.xbean.XBeanBrokerService.afterPropertiesSet(XBeanBrokerService.java:73)
~[activemq-spring-6.1.0.jar:6.1.0]
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[?:?]
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
~[?:?]
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:?]
at java.base/java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
`
Issue Time Tracking
---
Worklog Id: (was: 910282)
Time Spent: 1.5h (was: 1h 20m)
> Add appropriate JVM Args to allow access to sun.nio.* classes
> -
>
> Key: AMQ-9459
> URL: https://issues.apache.org/jira/browse/AMQ-9459
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.17.6
>Reporter: Anubhav Mishra
>Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters
> following exception:
> {code:java}
> ERROR | Could not set property soTimeout on
> ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=x] |
[jira] [Work logged] (AMQ-9459) Add appropriate JVM Args to allow access to sun.nio.* classes
[
https://issues.apache.org/jira/browse/AMQ-9459?focusedWorklogId=910281=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910281
]
ASF GitHub Bot logged work on AMQ-9459:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 07:04
Start Date: 18/Mar/24 07:04
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #1181:
URL: https://github.com/apache/activemq/pull/1181#issuecomment-2003063759
Ok, so I don't think we need it :)
Issue Time Tracking
---
Worklog Id: (was: 910281)
Time Spent: 1h 20m (was: 1h 10m)
> Add appropriate JVM Args to allow access to sun.nio.* classes
> -
>
> Key: AMQ-9459
> URL: https://issues.apache.org/jira/browse/AMQ-9459
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.17.6
>Reporter: Anubhav Mishra
>Priority: Minor
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters
> following exception:
> {code:java}
> ERROR | Could not set property soTimeout on
> ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=x] |
> org.apache.activemq.util.IntrospectionSupport | main
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.nio.ch.ServerSocketAdaptor.setSoTimeout(int) throws
> java.net.SocketException accessible: module java.base does not "opens
> sun.nio.ch" to unnamed module @4739cd70
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.configureServerSocket(TcpTransportServer.java:202)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:144)
> at
> org.apache.activemq.transport.auto.nio.AutoNioSslTransportFactory.doBind(AutoNioSslTransportFactory.java:122)
> at
> org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
> at
> org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:340)
> at
> org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:148)
> at
> org.apache.activemq.broker.TransportConnector.asManagedConnector(TransportConnector.java:113)
> at
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2241)
> at
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2728)
> at
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2624)
> at
> org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:762)
> at
> org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:724)
> at
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:622) {code}
> According to Oracle, with [JEP 403 (link1)|https://openjdk.java.net/jeps/403]
> and [JEP 403 (link2)|https://bugs.openjdk.java.net/browse/JDK-8263547] which
> has been decided to be *delivered from JDK 17 and onwards* , the
> setAccessible approach which was introduced as part of
> https://issues.apache.org/jira/browse/AMQ-7121 wont work.
>
> Fix: Adding the following in activemq file should do the job:
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9459) Add appropriate JVM Args to allow access to sun.nio.* classes
[
https://issues.apache.org/jira/browse/AMQ-9459?focusedWorklogId=910280=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910280
]
ASF GitHub Bot logged work on AMQ-9459:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 07:02
Start Date: 18/Mar/24 07:02
Worklog Time Spent: 10m
Work Description: AM-19 commented on PR #1181:
URL: https://github.com/apache/activemq/pull/1181#issuecomment-2003060436
Correction: Issue does not occur in 6.x
Issue Time Tracking
---
Worklog Id: (was: 910280)
Time Spent: 1h 10m (was: 1h)
> Add appropriate JVM Args to allow access to sun.nio.* classes
> -
>
> Key: AMQ-9459
> URL: https://issues.apache.org/jira/browse/AMQ-9459
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.17.6
>Reporter: Anubhav Mishra
>Priority: Minor
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters
> following exception:
> {code:java}
> ERROR | Could not set property soTimeout on
> ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=x] |
> org.apache.activemq.util.IntrospectionSupport | main
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.nio.ch.ServerSocketAdaptor.setSoTimeout(int) throws
> java.net.SocketException accessible: module java.base does not "opens
> sun.nio.ch" to unnamed module @4739cd70
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.configureServerSocket(TcpTransportServer.java:202)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:144)
> at
> org.apache.activemq.transport.auto.nio.AutoNioSslTransportFactory.doBind(AutoNioSslTransportFactory.java:122)
> at
> org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
> at
> org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:340)
> at
> org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:148)
> at
> org.apache.activemq.broker.TransportConnector.asManagedConnector(TransportConnector.java:113)
> at
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2241)
> at
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2728)
> at
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2624)
> at
> org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:762)
> at
> org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:724)
> at
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:622) {code}
> According to Oracle, with [JEP 403 (link1)|https://openjdk.java.net/jeps/403]
> and [JEP 403 (link2)|https://bugs.openjdk.java.net/browse/JDK-8263547] which
> has been decided to be *delivered from JDK 17 and onwards* , the
> setAccessible approach which was introduced as part of
> https://issues.apache.org/jira/browse/AMQ-7121 wont work.
>
> Fix: Adding the following in activemq file should do the job:
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9459) Add appropriate JVM Args to allow access to sun.nio.* classes
[
https://issues.apache.org/jira/browse/AMQ-9459?focusedWorklogId=910278=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910278
]
ASF GitHub Bot logged work on AMQ-9459:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 06:53
Start Date: 18/Mar/24 06:53
Worklog Time Spent: 10m
Work Description: AM-19 commented on PR #1181:
URL: https://github.com/apache/activemq/pull/1181#issuecomment-2003050122
> @AM-19 ok it's what I thought: let me check but I don't think it happens
on 6.x.
Let me validate on 6.x, Will reply in this Thread.
Issue Time Tracking
---
Worklog Id: (was: 910278)
Time Spent: 1h (was: 50m)
> Add appropriate JVM Args to allow access to sun.nio.* classes
> -
>
> Key: AMQ-9459
> URL: https://issues.apache.org/jira/browse/AMQ-9459
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.17.6
>Reporter: Anubhav Mishra
>Priority: Minor
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters
> following exception:
> {code:java}
> ERROR | Could not set property soTimeout on
> ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=x] |
> org.apache.activemq.util.IntrospectionSupport | main
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.nio.ch.ServerSocketAdaptor.setSoTimeout(int) throws
> java.net.SocketException accessible: module java.base does not "opens
> sun.nio.ch" to unnamed module @4739cd70
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.configureServerSocket(TcpTransportServer.java:202)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:144)
> at
> org.apache.activemq.transport.auto.nio.AutoNioSslTransportFactory.doBind(AutoNioSslTransportFactory.java:122)
> at
> org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
> at
> org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:340)
> at
> org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:148)
> at
> org.apache.activemq.broker.TransportConnector.asManagedConnector(TransportConnector.java:113)
> at
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2241)
> at
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2728)
> at
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2624)
> at
> org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:762)
> at
> org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:724)
> at
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:622) {code}
> According to Oracle, with [JEP 403 (link1)|https://openjdk.java.net/jeps/403]
> and [JEP 403 (link2)|https://bugs.openjdk.java.net/browse/JDK-8263547] which
> has been decided to be *delivered from JDK 17 and onwards* , the
> setAccessible approach which was introduced as part of
> https://issues.apache.org/jira/browse/AMQ-7121 wont work.
>
> Fix: Adding the following in activemq file should do the job:
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9459) Add appropriate JVM Args to allow access to sun.nio.* classes
[
https://issues.apache.org/jira/browse/AMQ-9459?focusedWorklogId=910277=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910277
]
ASF GitHub Bot logged work on AMQ-9459:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 06:52
Start Date: 18/Mar/24 06:52
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #1181:
URL: https://github.com/apache/activemq/pull/1181#issuecomment-2003048198
@AM-19 ok it's what I thought: let me check but I don't think it happens on
6.x.
Issue Time Tracking
---
Worklog Id: (was: 910277)
Time Spent: 50m (was: 40m)
> Add appropriate JVM Args to allow access to sun.nio.* classes
> -
>
> Key: AMQ-9459
> URL: https://issues.apache.org/jira/browse/AMQ-9459
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.17.6
>Reporter: Anubhav Mishra
>Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters
> following exception:
> {code:java}
> ERROR | Could not set property soTimeout on
> ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=x] |
> org.apache.activemq.util.IntrospectionSupport | main
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.nio.ch.ServerSocketAdaptor.setSoTimeout(int) throws
> java.net.SocketException accessible: module java.base does not "opens
> sun.nio.ch" to unnamed module @4739cd70
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.configureServerSocket(TcpTransportServer.java:202)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:144)
> at
> org.apache.activemq.transport.auto.nio.AutoNioSslTransportFactory.doBind(AutoNioSslTransportFactory.java:122)
> at
> org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
> at
> org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:340)
> at
> org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:148)
> at
> org.apache.activemq.broker.TransportConnector.asManagedConnector(TransportConnector.java:113)
> at
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2241)
> at
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2728)
> at
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2624)
> at
> org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:762)
> at
> org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:724)
> at
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:622) {code}
> According to Oracle, with [JEP 403 (link1)|https://openjdk.java.net/jeps/403]
> and [JEP 403 (link2)|https://bugs.openjdk.java.net/browse/JDK-8263547] which
> has been decided to be *delivered from JDK 17 and onwards* , the
> setAccessible approach which was introduced as part of
> https://issues.apache.org/jira/browse/AMQ-7121 wont work.
>
> Fix: Adding the following in activemq file should do the job:
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9459) Add appropriate JVM Args to allow access to sun.nio.* classes
[
https://issues.apache.org/jira/browse/AMQ-9459?focusedWorklogId=910276=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910276
]
ASF GitHub Bot logged work on AMQ-9459:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 06:49
Start Date: 18/Mar/24 06:49
Worklog Time Spent: 10m
Work Description: AM-19 commented on PR #1181:
URL: https://github.com/apache/activemq/pull/1181#issuecomment-2003045074
> Which versions of AMQ are you refering ?
Issue is Observed in 5.17.6, but will Ideally occur in 5.18.x and 6.0.x
Issue Time Tracking
---
Worklog Id: (was: 910276)
Time Spent: 40m (was: 0.5h)
> Add appropriate JVM Args to allow access to sun.nio.* classes
> -
>
> Key: AMQ-9459
> URL: https://issues.apache.org/jira/browse/AMQ-9459
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.17.6
>Reporter: Anubhav Mishra
>Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters
> following exception:
> {code:java}
> ERROR | Could not set property soTimeout on
> ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=x] |
> org.apache.activemq.util.IntrospectionSupport | main
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.nio.ch.ServerSocketAdaptor.setSoTimeout(int) throws
> java.net.SocketException accessible: module java.base does not "opens
> sun.nio.ch" to unnamed module @4739cd70
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.configureServerSocket(TcpTransportServer.java:202)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:144)
> at
> org.apache.activemq.transport.auto.nio.AutoNioSslTransportFactory.doBind(AutoNioSslTransportFactory.java:122)
> at
> org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
> at
> org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:340)
> at
> org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:148)
> at
> org.apache.activemq.broker.TransportConnector.asManagedConnector(TransportConnector.java:113)
> at
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2241)
> at
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2728)
> at
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2624)
> at
> org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:762)
> at
> org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:724)
> at
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:622) {code}
> According to Oracle, with [JEP 403 (link1)|https://openjdk.java.net/jeps/403]
> and [JEP 403 (link2)|https://bugs.openjdk.java.net/browse/JDK-8263547] which
> has been decided to be *delivered from JDK 17 and onwards* , the
> setAccessible approach which was introduced as part of
> https://issues.apache.org/jira/browse/AMQ-7121 wont work.
>
> Fix: Adding the following in activemq file should do the job:
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9459) Add appropriate JVM Args to allow access to sun.nio.* classes
[
https://issues.apache.org/jira/browse/AMQ-9459?focusedWorklogId=910275=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910275
]
ASF GitHub Bot logged work on AMQ-9459:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 06:48
Start Date: 18/Mar/24 06:48
Worklog Time Spent: 10m
Work Description: jbonofre commented on code in PR #1181:
URL: https://github.com/apache/activemq/pull/1181#discussion_r1527932695
##
assembly/src/release/bin/activemq:
##
@@ -346,6 +346,7 @@ invokeJar(){
--add-opens java.rmi/sun.rmi.transport.tcp=ALL-UNNAMED \
--add-opens java.base/java.util.concurrent=ALL-UNNAMED \
--add-opens java.base/java.util.concurrent.atomic=ALL-UNNAMED \
+ --add-opens java.base/sun.nio.ch=ALL-UNNAMED \
Review Comment:
AFAIR, this package is not available on all JDK (not sure adoptium has it
for instance).
Issue Time Tracking
---
Worklog Id: (was: 910275)
Time Spent: 0.5h (was: 20m)
> Add appropriate JVM Args to allow access to sun.nio.* classes
> -
>
> Key: AMQ-9459
> URL: https://issues.apache.org/jira/browse/AMQ-9459
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.17.6
>Reporter: Anubhav Mishra
>Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters
> following exception:
> {code:java}
> ERROR | Could not set property soTimeout on
> ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=x] |
> org.apache.activemq.util.IntrospectionSupport | main
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.nio.ch.ServerSocketAdaptor.setSoTimeout(int) throws
> java.net.SocketException accessible: module java.base does not "opens
> sun.nio.ch" to unnamed module @4739cd70
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.configureServerSocket(TcpTransportServer.java:202)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:144)
> at
> org.apache.activemq.transport.auto.nio.AutoNioSslTransportFactory.doBind(AutoNioSslTransportFactory.java:122)
> at
> org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
> at
> org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:340)
> at
> org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:148)
> at
> org.apache.activemq.broker.TransportConnector.asManagedConnector(TransportConnector.java:113)
> at
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2241)
> at
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2728)
> at
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2624)
> at
> org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:762)
> at
> org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:724)
> at
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:622) {code}
> According to Oracle, with [JEP 403 (link1)|https://openjdk.java.net/jeps/403]
> and [JEP 403 (link2)|https://bugs.openjdk.java.net/browse/JDK-8263547] which
> has been decided to be *delivered from JDK 17 and onwards* , the
> setAccessible approach which was introduced as part of
> https://issues.apache.org/jira/browse/AMQ-7121 wont work.
>
> Fix: Adding the following in activemq file should do the job:
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9459) Add appropriate JVM Args to allow access to sun.nio.* classes
[
https://issues.apache.org/jira/browse/AMQ-9459?focusedWorklogId=910273=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910273
]
ASF GitHub Bot logged work on AMQ-9459:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 06:25
Start Date: 18/Mar/24 06:25
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #1181:
URL: https://github.com/apache/activemq/pull/1181#issuecomment-2003017023
Which versions of AMQ are you refering ?
Issue Time Tracking
---
Worklog Id: (was: 910273)
Time Spent: 20m (was: 10m)
> Add appropriate JVM Args to allow access to sun.nio.* classes
> -
>
> Key: AMQ-9459
> URL: https://issues.apache.org/jira/browse/AMQ-9459
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.17.6
>Reporter: Anubhav Mishra
>Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters
> following exception:
> {code:java}
> ERROR | Could not set property soTimeout on
> ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=x] |
> org.apache.activemq.util.IntrospectionSupport | main
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.nio.ch.ServerSocketAdaptor.setSoTimeout(int) throws
> java.net.SocketException accessible: module java.base does not "opens
> sun.nio.ch" to unnamed module @4739cd70
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.configureServerSocket(TcpTransportServer.java:202)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:144)
> at
> org.apache.activemq.transport.auto.nio.AutoNioSslTransportFactory.doBind(AutoNioSslTransportFactory.java:122)
> at
> org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
> at
> org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:340)
> at
> org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:148)
> at
> org.apache.activemq.broker.TransportConnector.asManagedConnector(TransportConnector.java:113)
> at
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2241)
> at
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2728)
> at
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2624)
> at
> org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:762)
> at
> org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:724)
> at
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:622) {code}
> According to Oracle, with [JEP 403 (link1)|https://openjdk.java.net/jeps/403]
> and [JEP 403 (link2)|https://bugs.openjdk.java.net/browse/JDK-8263547] which
> has been decided to be *delivered from JDK 17 and onwards* , the
> setAccessible approach which was introduced as part of
> https://issues.apache.org/jira/browse/AMQ-7121 wont work.
>
> Fix: Adding the following in activemq file should do the job:
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9459) Add appropriate JVM Args to allow access to sun.nio.* classes
[
https://issues.apache.org/jira/browse/AMQ-9459?focusedWorklogId=910271=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910271
]
ASF GitHub Bot logged work on AMQ-9459:
---
Author: ASF GitHub Bot
Created on: 18/Mar/24 06:16
Start Date: 18/Mar/24 06:16
Worklog Time Spent: 10m
Work Description: AM-19 opened a new pull request, #1181:
URL: https://github.com/apache/activemq/pull/1181
When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters
following exception:
```
ERROR | Could not set property soTimeout on
ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=x] |
org.apache.activemq.util.IntrospectionSupport | main
java.lang.reflect.InaccessibleObjectException: Unable to make public void
sun.nio.ch.ServerSocketAdaptor.setSoTimeout(int) throws
java.net.SocketException accessible: module java.base does not "opens
sun.nio.ch" to unnamed module @4739cd70
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
at
java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
at
org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
at
org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
at
org.apache.activemq.transport.tcp.TcpTransportServer.configureServerSocket(TcpTransportServer.java:202)
at
org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:144)
at
org.apache.activemq.transport.auto.nio.AutoNioSslTransportFactory.doBind(AutoNioSslTransportFactory.java:122)
at
org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
at
org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:340)
at
org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:148)
at
org.apache.activemq.broker.TransportConnector.asManagedConnector(TransportConnector.java:113)
at
org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2241)
at
org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2728)
at
org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2624)
at
org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:762)
at
org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:724)
at
org.apache.activemq.broker.BrokerService.start(BrokerService.java:622)
```
According to Oracle, with [JEP 403
(link1)](https://openjdk.java.net/jeps/403) and [JEP 403
(link2)](https://bugs.openjdk.java.net/browse/JDK-8263547) which has been
decided to be delivered from JDK 17 and onwards , the setAccessible approach
which was introduced as part of https://issues.apache.org/jira/browse/AMQ-7121
wont work.
Issue Time Tracking
---
Worklog Id: (was: 910271)
Remaining Estimate: 0h
Time Spent: 10m
> Add appropriate JVM Args to allow access to sun.nio.* classes
> -
>
> Key: AMQ-9459
> URL: https://issues.apache.org/jira/browse/AMQ-9459
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.17.6
>Reporter: Anubhav Mishra
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When ActiveMQ running ActiveMQ on Java 17 or later JRE, it encounters
> following exception:
> {code:java}
> ERROR | Could not set property soTimeout on
> ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=x] |
> org.apache.activemq.util.IntrospectionSupport | main
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.nio.ch.ServerSocketAdaptor.setSoTimeout(int) throws
> java.net.SocketException accessible: module java.base does not "opens
> sun.nio.ch" to unnamed module @4739cd70
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> at
>
