[jira] [Commented] (AMQ-9018) Active Consumers not being shown post Activmq 5.16.5 Upgrade
[ https://issues.apache.org/jira/browse/AMQ-9018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575973#comment-17575973 ] Gary D Motts commented on AMQ-9018: --- This looks similar to https://issues.apache.org/jira/browse/AMQ-8597 > Active Consumers not being shown post Activmq 5.16.5 Upgrade > > > Key: AMQ-9018 > URL: https://issues.apache.org/jira/browse/AMQ-9018 > Project: ActiveMQ > Issue Type: Bug > Components: Web Console >Affects Versions: 5.16.5 >Reporter: Gary D Motts >Priority: Major > Attachments: AMQ_Console_Missing_Active_Consumers1.png, > AMQ_Console_Missing_Active_Consumers2.png, > AMQ_Console_Missing_Active_Consumers3.png > > > ActiveMQ Console is not displaying the active consumers, see images -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (AMQ-9018) Active Consumers not being shown post Activmq 5.16.5 Upgrade
Gary Motts created AMQ-9018: --- Summary: Active Consumers not being shown post Activmq 5.16.5 Upgrade Key: AMQ-9018 URL: https://issues.apache.org/jira/browse/AMQ-9018 Project: ActiveMQ Issue Type: Bug Components: Web Console Affects Versions: 5.16.5 Reporter: Gary Motts Attachments: AMQ_Console_Missing_Active_Consumers1.png, AMQ_Console_Missing_Active_Consumers2.png, AMQ_Console_Missing_Active_Consumers3.png ActiveMQ Console is not displaying the active consumers, see images -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575676#comment-17575676 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/5/22 1:50 PM: --- i use the MqttAsyncClient to connect the sever and it can not receive the code and i found another problem, i has set the lastWill, and after it conn success . i Unplug the network cable for test; and zhe server do not call ActiveMQServerMessagePlugin afterSend method; it just call beforeMessageRoute、afterMessageRoute method；and zhe route method cannot get session info [client_id、connId、clientIp；how can i get zhe session info after lastWill sended; was (Author: JIRAUSER293605): i use the MqttAsyncClient to connect the sever and it can not receive the code and i found another problem, i has set the lastWill, after it conn success Unplug the network cable for test; and zhe server can not send zhe lastWill message, and also the ActiveMQServerMessagePlugin method can not invoke > MQTTReasonCodes byte loss of precision，must int type > > > Key: ARTEMIS-3913 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3913 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: gongping.zhu >Priority: Major > Attachments: image-2022-08-02-08-23-52-965.png, > image-2022-08-02-08-24-39-288.png, image-2022-08-02-08-31-01-074.png, > image-2022-08-02-08-42-24-117.png, image-2022-08-02-08-43-39-442.png, > image-2022-08-02-08-45-11-459.png, image-2022-08-02-08-54-34-267.png, > image-2022-08-05-08-32-12-492.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-3923) AddressControlImpl.getRoles doesn't return all the security role permissions
[ https://issues.apache.org/jira/browse/ARTEMIS-3923?focusedWorklogId=798390=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-798390 ] ASF GitHub Bot logged work on ARTEMIS-3923: --- Author: ASF GitHub Bot Created on: 05/Aug/22 10:44 Start Date: 05/Aug/22 10:44 Worklog Time Spent: 10m Work Description: brusdev commented on PR #4169: URL: https://github.com/apache/activemq-artemis/pull/4169#issuecomment-1206307579 @ehsavoie could you remove '[]:' from your commit message, i.e. `ARTEMIS-3923 AddressControlImpl.getRoles doesn't return all the security role permissions.` Issue Time Tracking --- Worklog Id: (was: 798390) Time Spent: 20m (was: 10m) > AddressControlImpl.getRoles doesn't return all the security role permissions > > > Key: ARTEMIS-3923 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3923 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Emmanuel Hugonnet >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > The permissions BROWSE, CREATE_ADDRESS and DELETE_ADDRESS aren't provided in > the returned array. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575676#comment-17575676 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/5/22 9:56 AM: --- i use the MqttAsyncClient to connect the sever and it can not receive the code and i found another problem, i has set the lastWill, after it conn success Unplug the network cable for test; and zhe server can not send zhe lastWill message, and also the ActiveMQServerMessagePlugin method can not invoke was (Author: JIRAUSER293605): i use the MqttAsyncClient to connect the sever and it can not receive the code and i found another problem, i has set the lastWill, after it conn success Unplug the network cable for test; and zhe server can not send zhe lastWill message > MQTTReasonCodes byte loss of precision，must int type > > > Key: ARTEMIS-3913 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3913 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: gongping.zhu >Priority: Major > Attachments: image-2022-08-02-08-23-52-965.png, > image-2022-08-02-08-24-39-288.png, image-2022-08-02-08-31-01-074.png, > image-2022-08-02-08-42-24-117.png, image-2022-08-02-08-43-39-442.png, > image-2022-08-02-08-45-11-459.png, image-2022-08-02-08-54-34-267.png, > image-2022-08-05-08-32-12-492.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575676#comment-17575676 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/5/22 9:47 AM: --- i use the MqttAsyncClient to connect the sever and it can not receive the code and i found another problem, i has set the lastWill, after it conn success Unplug the network cable for test; and zhe server can not send zhe lastWill message was (Author: JIRAUSER293605): i use the MqttAsyncClient to connect the sever and it can not receive the code > MQTTReasonCodes byte loss of precision，must int type > > > Key: ARTEMIS-3913 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3913 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: gongping.zhu >Priority: Major > Attachments: image-2022-08-02-08-23-52-965.png, > image-2022-08-02-08-24-39-288.png, image-2022-08-02-08-31-01-074.png, > image-2022-08-02-08-42-24-117.png, image-2022-08-02-08-43-39-442.png, > image-2022-08-02-08-45-11-459.png, image-2022-08-02-08-54-34-267.png, > image-2022-08-05-08-32-12-492.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575676#comment-17575676 ] gongping.zhu commented on ARTEMIS-3913: --- i use the MqttAsyncClient to connect the sever and it can not receive the code > MQTTReasonCodes byte loss of precision，must int type > > > Key: ARTEMIS-3913 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3913 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: gongping.zhu >Priority: Major > Attachments: image-2022-08-02-08-23-52-965.png, > image-2022-08-02-08-24-39-288.png, image-2022-08-02-08-31-01-074.png, > image-2022-08-02-08-42-24-117.png, image-2022-08-02-08-43-39-442.png, > image-2022-08-02-08-45-11-459.png, image-2022-08-02-08-54-34-267.png, > image-2022-08-05-08-32-12-492.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-3923) AddressControlImpl.getRoles doesn't return all the security role permissions
[ https://issues.apache.org/jira/browse/ARTEMIS-3923?focusedWorklogId=798324=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-798324 ] ASF GitHub Bot logged work on ARTEMIS-3923: --- Author: ASF GitHub Bot Created on: 05/Aug/22 08:40 Start Date: 05/Aug/22 08:40 Worklog Time Spent: 10m Work Description: ehsavoie opened a new pull request, #4169: URL: https://github.com/apache/activemq-artemis/pull/4169 …curity role permissions. * Adding the missing permissions to the array. Signed-off-by: Emmanuel Hugonnet Issue Time Tracking --- Worklog Id: (was: 798324) Remaining Estimate: 0h Time Spent: 10m > AddressControlImpl.getRoles doesn't return all the security role permissions > > > Key: ARTEMIS-3923 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3923 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Emmanuel Hugonnet >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > The permissions BROWSE, CREATE_ADDRESS and DELETE_ADDRESS aren't provided in > the returned array. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3923) AddressControlImpl.getRoles doesn't return all the security role permissions
Emmanuel Hugonnet created ARTEMIS-3923: -- Summary: AddressControlImpl.getRoles doesn't return all the security role permissions Key: ARTEMIS-3923 URL: https://issues.apache.org/jira/browse/ARTEMIS-3923 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Emmanuel Hugonnet The permissions BROWSE, CREATE_ADDRESS and DELETE_ADDRESS aren't provided in the returned array. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=798303=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-798303 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 05/Aug/22 07:34 Start Date: 05/Aug/22 07:34 Worklog Time Spent: 10m Work Description: jbonofre commented on PR #871: URL: https://github.com/apache/activemq/pull/871#issuecomment-1206140169 Yes. It's pretty easy: create a new commit with git commit --allow-empty and then rebase and squash. Then you can force push, it will trigger a new Jenkins execution. Issue Time Tracking --- Worklog Id: (was: 798303) Time Spent: 1h 50m (was: 1h 40m) > remove xalan dependency due to it being end of life > --- > > Key: AMQ-9005 > URL: https://issues.apache.org/jira/browse/AMQ-9005 > Project: ActiveMQ > Issue Type: Improvement >Reporter: PJ Fanning >Priority: Major > Fix For: 5.18.0, 5.17.2 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Xalan is no longer supported. > https://lists.apache.org/thread/s8kjny5270ssfcp46v0fl39lk98987w7 > It is better to use JAXP TransformerFactory than using xalan directly. If you > add xalan dependency just to ensure that you have a JAXP compliant > transformer on the classpath, this is unnecessary - the Java runtime has a > built-in implementation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3922) Reducing contention on java.lang.Throwable#getOurStackTrace
[
https://issues.apache.org/jira/browse/ARTEMIS-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575618#comment-17575618
]
Rico Neubauer commented on ARTEMIS-3922:
PR
https://github.com/apache/activemq-artemis/pull/4168
> Reducing contention on java.lang.Throwable#getOurStackTrace
> ---
>
> Key: ARTEMIS-3922
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3922
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Affects Versions: 2.24.0
>Reporter: Rico Neubauer
>Priority: Major
> Attachments: threads.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This is a request for improvement rg. performance in a very specific case,
> but easy to accomplish.
> h2. Scenario
> On certain contaier'ed Windows machines we have identified that
> {{java.lang.Throwable#getOurStackTrace}} along with
> {{java.lang.StackTraceElement#initStackTraceElements}} show up as a very
> expensive operations. The reason behind this is still unclear, but since the
> {{#getOurStackTrace}} is synchronized, it suffers even more when the native
> method {{#initStackTraceElements}} takes an unexpected long time.
> This shows in thread-dumps in 2 locations for Artemis, where
> connection-creation is the more crucial one from my pov.
> See attached threads.txt
> h2. Remedy
> Fortunately the location where this gets used via
> {{Thread.currentThread().getStackTrace()}} is simple to replace, since the
> information needed could just get passed by caller.
> Please see attached patch for my proposal.
> Also available [here as
> commit|https://github.com/seeburger-ag/activemq-artemis/commit/7396b9356256706a886f35da3a27274084e5a973].
> Can create a pull request as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-3922) Reducing contention on java.lang.Throwable#getOurStackTrace
[
https://issues.apache.org/jira/browse/ARTEMIS-3922?focusedWorklogId=798302=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-798302
]
ASF GitHub Bot logged work on ARTEMIS-3922:
---
Author: ASF GitHub Bot
Created on: 05/Aug/22 07:32
Start Date: 05/Aug/22 07:32
Worklog Time Spent: 10m
Work Description: MrEasy opened a new pull request, #4168:
URL: https://github.com/apache/activemq-artemis/pull/4168
By allowing to pass caller's classname directly to
org.apache.activemq.artemis.utils.ActiveMQThreadFactory#defaultThreadFactory
instead of calculating it from stack.
Issue Time Tracking
---
Worklog Id: (was: 798302)
Remaining Estimate: 0h
Time Spent: 10m
> Reducing contention on java.lang.Throwable#getOurStackTrace
> ---
>
> Key: ARTEMIS-3922
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3922
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Affects Versions: 2.24.0
>Reporter: Rico Neubauer
>Priority: Major
> Attachments: threads.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This is a request for improvement rg. performance in a very specific case,
> but easy to accomplish.
> h2. Scenario
> On certain contaier'ed Windows machines we have identified that
> {{java.lang.Throwable#getOurStackTrace}} along with
> {{java.lang.StackTraceElement#initStackTraceElements}} show up as a very
> expensive operations. The reason behind this is still unclear, but since the
> {{#getOurStackTrace}} is synchronized, it suffers even more when the native
> method {{#initStackTraceElements}} takes an unexpected long time.
> This shows in thread-dumps in 2 locations for Artemis, where
> connection-creation is the more crucial one from my pov.
> See attached threads.txt
> h2. Remedy
> Fortunately the location where this gets used via
> {{Thread.currentThread().getStackTrace()}} is simple to replace, since the
> information needed could just get passed by caller.
> Please see attached patch for my proposal.
> Also available [here as
> commit|https://github.com/seeburger-ag/activemq-artemis/commit/7396b9356256706a886f35da3a27274084e5a973].
> Can create a pull request as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=798300=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-798300 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 05/Aug/22 07:30 Start Date: 05/Aug/22 07:30 Worklog Time Spent: 10m Work Description: lucastetreault commented on PR #871: URL: https://github.com/apache/activemq/pull/871#issuecomment-1206137075 @jbonofre is there a way I can re-initiate the tests? Everything passed for me: ``` [INFO] [INFO] Reactor Summary for ActiveMQ 5.18.0-SNAPSHOT: [INFO] [INFO] ActiveMQ ... SUCCESS [ 0.481 s] [INFO] ActiveMQ :: Openwire Generator . SUCCESS [ 0.334 s] [INFO] ActiveMQ :: Client . SUCCESS [01:04 min] [INFO] ActiveMQ :: Openwire Legacy Support SUCCESS [ 0.103 s] [INFO] ActiveMQ :: JAAS ... SUCCESS [ 13.006 s] [INFO] ActiveMQ :: Broker . SUCCESS [ 49.482 s] [INFO] ActiveMQ :: KahaDB Store ... SUCCESS [02:45 min] [INFO] ActiveMQ :: STOMP Protocol . SUCCESS [10:06 min] [INFO] ActiveMQ :: MQTT Protocol .. SUCCESS [17:06 min] [INFO] ActiveMQ :: JDBC Store . SUCCESS [ 4.500 s] [INFO] ActiveMQ :: Generic JMS Pool ... SUCCESS [ 36.790 s] [INFO] ActiveMQ :: Pool ... SUCCESS [ 3.421 s] [INFO] ActiveMQ :: RA . SUCCESS [01:31 min] [INFO] ActiveMQ :: Spring . SUCCESS [ 54.835 s] [INFO] ActiveMQ :: Console SUCCESS [ 4.809 s] [INFO] ActiveMQ :: Partition Management ... SUCCESS [ 16.057 s] [INFO] ActiveMQ :: Runtime Configuration .. SUCCESS [07:57 min] [INFO] ActiveMQ :: Tooling SUCCESS [ 0.009 s] [INFO] ActiveMQ :: JUnit Rule . SUCCESS [ 1.965 s] [INFO] ActiveMQ :: Unit Tests . SUCCESS [ 02:06 h] [INFO] ActiveMQ :: HTTP Protocol Support .. SUCCESS [09:07 min] [INFO] ActiveMQ :: AMQP ... SUCCESS [05:05 min] [INFO] ActiveMQ :: All JAR bundle . SUCCESS [ 0.213 s] [INFO] ActiveMQ :: Log4j Appender . SUCCESS [ 0.138 s] [INFO] ActiveMQ :: Apache Karaf ... SUCCESS [ 0.901 s] [INFO] ActiveMQ :: ConnectionFactory .. SUCCESS [ 0.058 s] [INFO] ActiveMQ :: RAR SUCCESS [ 1.941 s] [INFO] ActiveMQ :: Run Jar SUCCESS [ 0.093 s] [INFO] ActiveMQ :: Shiro .. SUCCESS [ 2.049 s] [INFO] ActiveMQ :: Memory Usage Test Plugin ... SUCCESS [ 1.381 s] [INFO] ActiveMQ :: Performance Test Plugin SUCCESS [ 5.114 s] [INFO] ActiveMQ :: StartUp/Stop Plugin SUCCESS [ 3.505 s] [INFO] ActiveMQ :: Web SUCCESS [ 13.664 s] [INFO] ActiveMQ :: OSGi bundle SUCCESS [ 0.812 s] [INFO] ActiveMQ :: Blueprint .. SUCCESS [ 0.042 s] [INFO] ActiveMQ :: Web Demo ... SUCCESS [ 24.623 s] [INFO] ActiveMQ :: Web Console SUCCESS [ 4.367 s] [INFO] ActiveMQ :: Karaf Integration Tests SUCCESS [ 1.081 s] [INFO] ActiveMQ :: Assembly ... SUCCESS [ 24.476 s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 03:05 h [INFO] Finished at: 2022-08-03T09:44:54Z [INFO] ``` Issue Time Tracking --- Worklog Id: (was: 798300) Time Spent: 1h 40m (was: 1.5h) > remove xalan dependency due to it being end of life > --- > > Key: AMQ-9005 > URL: https://issues.apache.org/jira/browse/AMQ-9005 > Project: ActiveMQ > Issue Type: Improvement >Reporter: PJ Fanning >Priority: Major > Fix For: 5.18.0, 5.17.2 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Xalan is no longer
