[jira] [Commented] (AMQ-8451) Message URL Host is incorrect

[ https://issues.apache.org/jira/browse/AMQ-8451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484561#comment-17484561 ] Varun Ramachandran commented on AMQ-8451: - Thanks for your suggestion [~jbonofre] 

[jira] [Created] (AMQ-8467) Upgrade to xstream 1.4.19

Jean-Baptiste Onofré created AMQ-8467: - Summary: Upgrade to xstream 1.4.19 Key: AMQ-8467 URL: https://issues.apache.org/jira/browse/AMQ-8467 Project: ActiveMQ Issue Type: Dependency upgra

[jira] [Commented] (ARTEMIS-3085) Support registering IOCriticalErrorListener on the broker

[ https://issues.apache.org/jira/browse/ARTEMIS-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484644#comment-17484644 ] Emmanuel Hugonnet commented on ARTEMIS-3085: Sorry guys I missed the notifi

[jira] [Commented] (ARTEMIS-3308) Federated queue will not move large messages

[ https://issues.apache.org/jira/browse/ARTEMIS-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484649#comment-17484649 ] Alexander Andreevich Revkov commented on ARTEMIS-3308: -- Bug did no

[jira] [Commented] (ARTEMIS-3308) Federated queue will not move large messages

[ https://issues.apache.org/jira/browse/ARTEMIS-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484666#comment-17484666 ] Gary Tully commented on ARTEMIS-3308: - I wonder if you are experiencing the default

[jira] [Commented] (ARTEMIS-3308) Federated queue will not move large messages

[ https://issues.apache.org/jira/browse/ARTEMIS-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484676#comment-17484676 ] Alexander Andreevich Revkov commented on ARTEMIS-3308: -- of course

[jira] [Updated] (ARTEMIS-3662) Remove deprecated config from default broker.xml

[ https://issues.apache.org/jira/browse/ARTEMIS-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-3662: Priority: Minor (was: Major) > Remove deprecated config from default broker.xml > --

[jira] [Work logged] (ARTEMIS-2413) Upgrade JGroups

[ https://issues.apache.org/jira/browse/ARTEMIS-2413?focusedWorklogId=717986&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-717986 ] ASF GitHub Bot logged work on ARTEMIS-2413: --- Author: ASF GitHub B

[jira] [Commented] (ARTEMIS-2816) paging=true not cleared with load balanced configuration

[ https://issues.apache.org/jira/browse/ARTEMIS-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484750#comment-17484750 ] Thomas Wood commented on ARTEMIS-2816: -- Ill do some testing today. > paging=true

[jira] [Commented] (AMQ-8467) Upgrade to xstream 1.4.19

[ https://issues.apache.org/jira/browse/AMQ-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484760#comment-17484760 ] ASF subversion and git services commented on AMQ-8467: -- Commit 2206eb3

[jira] [Work logged] (AMQ-8467) Upgrade to xstream 1.4.19

[ https://issues.apache.org/jira/browse/AMQ-8467?focusedWorklogId=718051&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-718051 ] ASF GitHub Bot logged work on AMQ-8467: --- Author: ASF GitHub Bot

[jira] [Commented] (AMQ-8467) Upgrade to xstream 1.4.19

[ https://issues.apache.org/jira/browse/AMQ-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484761#comment-17484761 ] ASF subversion and git services commented on AMQ-8467: -- Commit daeb23a

[jira] [Resolved] (AMQ-8467) Upgrade to xstream 1.4.19

[ https://issues.apache.org/jira/browse/AMQ-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-8467. --- Resolution: Fixed > Upgrade to xstream 1.4.19 > - > >

[jira] [Commented] (AMQ-8467) Upgrade to xstream 1.4.19

[ https://issues.apache.org/jira/browse/AMQ-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484764#comment-17484764 ] ASF subversion and git services commented on AMQ-8467: -- Commit fbdf3c5

[jira] [Commented] (AMQ-8451) Message URL Host is incorrect

[ https://issues.apache.org/jira/browse/AMQ-8451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484765#comment-17484765 ] Jean-Baptiste Onofré commented on AMQ-8451: --- OK, so I consider the issue as "fixe

[jira] [Resolved] (AMQ-8451) Message URL Host is incorrect

[ https://issues.apache.org/jira/browse/AMQ-8451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-8451. --- Fix Version/s: (was: 5.17.0) (was: 5.16.4) Resolution:

[jira] [Created] (ARTEMIS-3663) Client connection with "useEpoll=false" fails with "incompatible event loop type"

Apache Dev created ARTEMIS-3663: --- Summary: Client connection with "useEpoll=false" fails with "incompatible event loop type" Key: ARTEMIS-3663 URL: https://issues.apache.org/jira/browse/ARTEMIS-3663 Pro

[jira] [Created] (AMQ-8468) CVE-2022-23437: Infinite loop within Apache XercesJ xml parser

Colm O hEigeartaigh created AMQ-8468: Summary: CVE-2022-23437: Infinite loop within Apache XercesJ xml parser Key: AMQ-8468 URL: https://issues.apache.org/jira/browse/AMQ-8468 Project: ActiveMQ

[jira] [Commented] (ARTEMIS-3663) Client connection with "useEpoll=false" fails with "incompatible event loop type"

[ https://issues.apache.org/jira/browse/ARTEMIS-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484784#comment-17484784 ] Justin Bertram commented on ARTEMIS-3663: - I recreated this on 2.19.0, but I ca

[jira] [Resolved] (ARTEMIS-3663) Client connection with "useEpoll=false" fails with "incompatible event loop type"

[ https://issues.apache.org/jira/browse/ARTEMIS-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-3663. - Resolution: Cannot Reproduce > Client connection with "useEpoll=false" fails with "inco

[jira] [Comment Edited] (ARTEMIS-3663) Client connection with "useEpoll=false" fails with "incompatible event loop type"

[ https://issues.apache.org/jira/browse/ARTEMIS-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484784#comment-17484784 ] Justin Bertram edited comment on ARTEMIS-3663 at 1/31/22, 4:49 PM: --

[jira] [Updated] (ARTEMIS-3663) Client connection with "useEpoll=false" fails with "incompatible event loop type"

[ https://issues.apache.org/jira/browse/ARTEMIS-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-3663: Component/s: (was: API) > Client connection with "useEpoll=false" fails with "incompa

[jira] [Created] (ARTEMIS-3664) Critical Analyzer should not kick in during Starting phase of the broker

Clebert Suconic created ARTEMIS-3664: Summary: Critical Analyzer should not kick in during Starting phase of the broker Key: ARTEMIS-3664 URL: https://issues.apache.org/jira/browse/ARTEMIS-3664 Pr

[jira] [Assigned] (AMQ-8468) CVE-2022-23437: Infinite loop within Apache XercesJ xml parser

[ https://issues.apache.org/jira/browse/AMQ-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-8468: - Assignee: Jean-Baptiste Onofré > CVE-2022-23437: Infinite loop within Apache Xerce

[jira] [Updated] (AMQ-8468) CVE-2022-23437: Infinite loop within Apache XercesJ xml parser

[ https://issues.apache.org/jira/browse/AMQ-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-8468: -- Fix Version/s: 5.17.0 > CVE-2022-23437: Infinite loop within Apache XercesJ xml parser >

[jira] [Commented] (ARTEMIS-2816) paging=true not cleared with load balanced configuration

[ https://issues.apache.org/jira/browse/ARTEMIS-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484834#comment-17484834 ] Thomas Wood commented on ARTEMIS-2816: -- Just ran some tests and the paging flag is

[jira] [Commented] (ARTEMIS-3509) STOMP Websocket client disconnected after ConcurrentModificationException in Broker

[ https://issues.apache.org/jira/browse/ARTEMIS-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484837#comment-17484837 ] Justin Bertram commented on ARTEMIS-3509: - Any update here? Can you provide any

[jira] [Resolved] (ARTEMIS-2816) paging=true not cleared with load balanced configuration

[ https://issues.apache.org/jira/browse/ARTEMIS-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-2816. - Resolution: Cannot Reproduce > paging=true not cleared with load balanced configuration

[jira] [Commented] (ARTEMIS-2816) paging=true not cleared with load balanced configuration

[ https://issues.apache.org/jira/browse/ARTEMIS-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484839#comment-17484839 ] Justin Bertram commented on ARTEMIS-2816: - Thanks for the update. I'm going to

[jira] [Commented] (ARTEMIS-3664) Critical Analyzer should not kick in during Starting phase of the broker

[ https://issues.apache.org/jira/browse/ARTEMIS-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484852#comment-17484852 ] ASF subversion and git services commented on ARTEMIS-3664: -- Co

[jira] [Work logged] (ARTEMIS-3664) Critical Analyzer should not kick in during Starting phase of the broker

[ https://issues.apache.org/jira/browse/ARTEMIS-3664?focusedWorklogId=718144&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-718144 ] ASF GitHub Bot logged work on ARTEMIS-3664: --- Author: ASF GitHub B

[jira] [Reopened] (AMQ-8449) apache-activemq-5.16.3 - How to upgrade Log4j-1.2.17.1 to Log4J 2.x to fix log4j related security issue

[ https://issues.apache.org/jira/browse/AMQ-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinivasa Yadlapalli reopened AMQ-8449: --- > apache-activemq-5.16.3 - How to upgrade Log4j-1.2.17.1 to Log4J 2.x to fix > log4j relat

[jira] [Commented] (AMQ-8449) apache-activemq-5.16.3 - How to upgrade Log4j-1.2.17.1 to Log4J 2.x to fix log4j related security issue

[ https://issues.apache.org/jira/browse/AMQ-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484853#comment-17484853 ] Srinivasa Yadlapalli commented on AMQ-8449: --- Please resolve this > apache-active

[jira] [Created] (AMQ-8469) Automoto blog

Anton Morko created AMQ-8469: Summary: Automoto blog Key: AMQ-8469 URL: https://issues.apache.org/jira/browse/AMQ-8469 Project: ActiveMQ Issue Type: Bug Reporter: Anton Morko Blog p

[jira] [Updated] (AMQ-8469) Automoto blog

[ https://issues.apache.org/jira/browse/AMQ-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Morko updated AMQ-8469: - Description: [Blog|https://www.naj-katalog.eu/] pre nadšencov [automobilov|https://autmoto.sk/] a motoriek

[jira] [Created] (ARTEMIS-3665) NullPointerException in ServerLocator.createSessionFactory

Stephen Baker created ARTEMIS-3665: -- Summary: NullPointerException in ServerLocator.createSessionFactory Key: ARTEMIS-3665 URL: https://issues.apache.org/jira/browse/ARTEMIS-3665 Project: ActiveMQ Art

[jira] [Work logged] (ARTEMIS-3613) Deprecate stompMaxFramePayloadLength which is use for any protocol no just stomp

[ https://issues.apache.org/jira/browse/ARTEMIS-3613?focusedWorklogId=718221&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-718221 ] ASF GitHub Bot logged work on ARTEMIS-3613: --- Author: ASF GitHub B

[jira] [Updated] (ARTEMIS-3665) NullPointerException in ServerLocator.createSessionFactory

[ https://issues.apache.org/jira/browse/ARTEMIS-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Baker updated ARTEMIS-3665: --- Description: In one environment I am frequently seeing a NullPointerException in ServerLoc

[jira] [Commented] (ARTEMIS-3665) NullPointerException in ServerLocator.createSessionFactory

[ https://issues.apache.org/jira/browse/ARTEMIS-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484965#comment-17484965 ] Clebert Suconic commented on ARTEMIS-3665: -- can you try with 2.19.1? > NullPo

[jira] [Commented] (AMQ-7426) Upgrade to log4j2

[ https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485053#comment-17485053 ] Srikrishna Erra commented on AMQ-7426: -- Hi [~jbonofre],    Is there a plan on includi