[jira] [Work logged] (ARTEMIS-2655) Support auto-creation w/FQQN for STOMP
[ https://issues.apache.org/jira/browse/ARTEMIS-2655?focusedWorklogId=411576=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-411576 ] ASF GitHub Bot logged work on ARTEMIS-2655: --- Author: ASF GitHub Bot Created on: 28/Mar/20 00:46 Start Date: 28/Mar/20 00:46 Worklog Time Spent: 10m Work Description: michaelpearce-gain commented on issue #3018: ARTEMIS-2655 support auto-creation w/FQQN & STOMP URL: https://github.com/apache/activemq-artemis/pull/3018#issuecomment-605369813 i think you can merge @jbertram its been 2 weeks an no other comments This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 411576) Time Spent: 0.5h (was: 20m) > Support auto-creation w/FQQN for STOMP > -- > > Key: ARTEMIS-2655 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2655 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: STOMP >Affects Versions: 2.11.0 >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Addresses and queues are not properly auto-created when using STOMP & FQQN. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2666) Add management for duplicate ID cache
[ https://issues.apache.org/jira/browse/ARTEMIS-2666?focusedWorklogId=411573=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-411573 ] ASF GitHub Bot logged work on ARTEMIS-2666: --- Author: ASF GitHub Bot Created on: 28/Mar/20 00:45 Start Date: 28/Mar/20 00:45 Worklog Time Spent: 10m Work Description: michaelpearce-gain commented on issue #3033: ARTEMIS-2666 mngmnt for duplicate ID cache URL: https://github.com/apache/activemq-artemis/pull/3033#issuecomment-605369594 +1, nice nice...simply but really useful. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 411573) Time Spent: 20m (was: 10m) > Add management for duplicate ID cache > -- > > Key: ARTEMIS-2666 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2666 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2682) OpenWireMessageConverter refactoring
[
https://issues.apache.org/jira/browse/ARTEMIS-2682?focusedWorklogId=411572=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-411572
]
ASF GitHub Bot logged work on ARTEMIS-2682:
---
Author: ASF GitHub Bot
Created on: 28/Mar/20 00:44
Start Date: 28/Mar/20 00:44
Worklog Time Spent: 10m
Work Description: michaelpearce-gain commented on issue #3043:
ARTEMIS-2682: OpenWireMessageConverter refactoring
URL: https://github.com/apache/activemq-artemis/pull/3043#issuecomment-605369255
its still not compiling.even after your latest commit, i really am
thinking is this PR worth it, if its only a refactor, but no benefit, just risk
of what else is broken, if it doesnt even compile atm...?!?!
The biggest thing for me in this space if someone was to refactor is to
actually introduce Native OpenWireMessage support, so for openwire to openwire
we dont convert. Then it be worth the risk/effort.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 411572)
Time Spent: 40m (was: 0.5h)
> OpenWireMessageConverter refactoring
>
>
> Key: ARTEMIS-2682
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2682
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: OpenWire
>Affects Versions: 2.12.0
>Reporter: Federico Valeri
>Priority: Minor
> Labels: openwire, refactoring
> Time Spent: 40m
> Remaining Estimate: 0h
>
> I'm proposing the {{OpenWireMessageConverter}} refactoring to have a similar
> layout as the {{AMQPConverter}}. The latter has two dedicated classes for
> inbound and outbound messages with a singleton entry point for the converter.
> This change is basically doing the same without semantics change and also
> adding a unit test for the converter. I'm also eliminating some duplicated
> code, but the bulk of the code remains untouched.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2682) OpenWireMessageConverter refactoring
[
https://issues.apache.org/jira/browse/ARTEMIS-2682?focusedWorklogId=411571=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-411571
]
ASF GitHub Bot logged work on ARTEMIS-2682:
---
Author: ASF GitHub Bot
Created on: 28/Mar/20 00:43
Start Date: 28/Mar/20 00:43
Worklog Time Spent: 10m
Work Description: michaelpearce-gain commented on issue #3043:
ARTEMIS-2682: OpenWireMessageConverter refactoring
URL: https://github.com/apache/activemq-artemis/pull/3043#issuecomment-605369255
its still not compiling.even after your latest commit, i really am
thinking is this PR worth it, if its only a refactor, but not benefit, just
risk oi what else is broken, if it doesnt even compile?!?!
The biggest thing for me in this space if someone was to refactor is to
actually introduce Native OpenWireMessage support, so for openwire to openwire
we dont convert. Then it be worth the risk/effort.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 411571)
Time Spent: 0.5h (was: 20m)
> OpenWireMessageConverter refactoring
>
>
> Key: ARTEMIS-2682
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2682
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: OpenWire
>Affects Versions: 2.12.0
>Reporter: Federico Valeri
>Priority: Minor
> Labels: openwire, refactoring
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I'm proposing the {{OpenWireMessageConverter}} refactoring to have a similar
> layout as the {{AMQPConverter}}. The latter has two dedicated classes for
> inbound and outbound messages with a singleton entry point for the converter.
> This change is basically doing the same without semantics change and also
> adding a unit test for the converter. I'm also eliminating some duplicated
> code, but the bulk of the code remains untouched.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2680) Use queue name for address if none specified via configuration
[
https://issues.apache.org/jira/browse/ARTEMIS-2680?focusedWorklogId=411567=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-411567
]
ASF GitHub Bot logged work on ARTEMIS-2680:
---
Author: ASF GitHub Bot
Created on: 28/Mar/20 00:37
Start Date: 28/Mar/20 00:37
Worklog Time Spent: 10m
Work Description: michaelpearce-gain commented on issue #3047:
ARTEMIS-2680 use q name for addr if none specified via config
URL: https://github.com/apache/activemq-artemis/pull/3047#issuecomment-605368361
fair enough, im not heavily against so go ahead and merge if others also
happy, just really doesnt make much sense to have a queue but not to define an
address.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 411567)
Time Spent: 1.5h (was: 1h 20m)
> Use queue name for address if none specified via configuration
> --
>
> Key: ARTEMIS-2680
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2680
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> If
> {{org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl#createQueue()}}
> is invoked with an effectively {{null}} address name then the queue name
> will be used for the address. This is not true of queues created via
> {{org.apache.activemq.artemis.core.config.CoreQueueConfiguration}}, but it
> should be.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2681) Timestamp not set on notification messages
[ https://issues.apache.org/jira/browse/ARTEMIS-2681?focusedWorklogId=411327=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-411327 ] ASF GitHub Bot logged work on ARTEMIS-2681: --- Author: ASF GitHub Bot Created on: 27/Mar/20 19:42 Start Date: 27/Mar/20 19:42 Worklog Time Spent: 10m Work Description: asfgit commented on pull request #3049: ARTEMIS-2681 timestamp not set on notif msgs URL: https://github.com/apache/activemq-artemis/pull/3049 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 411327) Time Spent: 1.5h (was: 1h 20m) > Timestamp not set on notification messages > -- > > Key: ARTEMIS-2681 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2681 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2681) Timestamp not set on notification messages
[ https://issues.apache.org/jira/browse/ARTEMIS-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17069013#comment-17069013 ] ASF subversion and git services commented on ARTEMIS-2681: -- Commit 59e07c97800363a07d0e3a5ff32f4cdc75e50852 in activemq-artemis's branch refs/heads/master from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=59e07c9 ] ARTEMIS-2681 timestamp not set on notif msgs > Timestamp not set on notification messages > -- > > Key: ARTEMIS-2681 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2681 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Minor > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2608) ClassCastException when consuming a message using OpenWire
[
https://issues.apache.org/jira/browse/ARTEMIS-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068913#comment-17068913
]
ASF subversion and git services commented on ARTEMIS-2608:
--
Commit 8cf35385a474d1d1ef5d70b501d5144ccb9249ba in activemq-artemis's branch
refs/heads/master from Federico Valeri
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=8cf3538 ]
ARTEMIS-2608 Fix ClassCastException on binary properties conversion
> ClassCastException when consuming a message using OpenWire
> --
>
> Key: ARTEMIS-2608
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2608
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, OpenWire
>Affects Versions: 2.11.0
>Reporter: Federico Valeri
>Priority: Major
> Time Spent: 6h 10m
> Remaining Estimate: 0h
>
> This issue seems to be related to the conversion of binary properties.
> Quick workaround: clear message properties in the AMQP producer.
> Reproducer (attached):
> 1. Send a message to the broker using OpenWire client
> 2. Consume that message using AMQP client
> 3. Send that message back to the broker using AMQP client
> Result: message could not be consumed by the OpenWire consumer.
> {code:java}
> 2020-01-23 12:52:44,095 WARN [org.apache.activemq.artemis.core.server] Error
> during message dispatch: java.lang.ClassCastException:
> org.apache.activemq.artemis.api.core.SimpleString cannot be cast to [B
> at
> org.apache.activemq.artemis.core.protocol.openwire.OpenWireMessageConverter.toAMQMessage(OpenWireMessageConverter.java:629)
> [artemis-openwire-protocol-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.protocol.openwire.OpenWireMessageConverter.createMessageDispatch(OpenWireMessageConverter.java:501)
> [artemis-openwire-protocol-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.protocol.openwire.amq.AMQConsumer.handleDeliver(AMQConsumer.java:258)
> [artemis-openwire-protocol-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.protocol.openwire.amq.AMQSession.sendMessage(AMQSession.java:312)
> [artemis-openwire-protocol-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.deliverStandardMessage(ServerConsumerImpl.java:1161)
> [artemis-server-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.proceedDeliver(ServerConsumerImpl.java:504)
> [artemis-server-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.proceedDeliver(QueueImpl.java:3510)
> [artemis-server-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.deliver(QueueImpl.java:2856)
> [artemis-server-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.access$2300(QueueImpl.java:122)
> [artemis-server-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl$DeliverRunner.run(QueueImpl.java:3848)
> [artemis-server-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
> [artemis-commons-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
> [artemis-commons-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
> [artemis-commons-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_232]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_232]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> [artemis-commons-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2608) ClassCastException when consuming a message using OpenWire
[
https://issues.apache.org/jira/browse/ARTEMIS-2608?focusedWorklogId=411199=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-411199
]
ASF GitHub Bot logged work on ARTEMIS-2608:
---
Author: ASF GitHub Bot
Created on: 27/Mar/20 17:13
Start Date: 27/Mar/20 17:13
Worklog Time Spent: 10m
Work Description: asfgit commented on pull request #2954: ARTEMIS-2608
Fix ClassCastException on binary properties conversion
URL: https://github.com/apache/activemq-artemis/pull/2954
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 411199)
Time Spent: 6h 20m (was: 6h 10m)
> ClassCastException when consuming a message using OpenWire
> --
>
> Key: ARTEMIS-2608
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2608
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, OpenWire
>Affects Versions: 2.11.0
>Reporter: Federico Valeri
>Priority: Major
> Time Spent: 6h 20m
> Remaining Estimate: 0h
>
> This issue seems to be related to the conversion of binary properties.
> Quick workaround: clear message properties in the AMQP producer.
> Reproducer (attached):
> 1. Send a message to the broker using OpenWire client
> 2. Consume that message using AMQP client
> 3. Send that message back to the broker using AMQP client
> Result: message could not be consumed by the OpenWire consumer.
> {code:java}
> 2020-01-23 12:52:44,095 WARN [org.apache.activemq.artemis.core.server] Error
> during message dispatch: java.lang.ClassCastException:
> org.apache.activemq.artemis.api.core.SimpleString cannot be cast to [B
> at
> org.apache.activemq.artemis.core.protocol.openwire.OpenWireMessageConverter.toAMQMessage(OpenWireMessageConverter.java:629)
> [artemis-openwire-protocol-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.protocol.openwire.OpenWireMessageConverter.createMessageDispatch(OpenWireMessageConverter.java:501)
> [artemis-openwire-protocol-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.protocol.openwire.amq.AMQConsumer.handleDeliver(AMQConsumer.java:258)
> [artemis-openwire-protocol-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.protocol.openwire.amq.AMQSession.sendMessage(AMQSession.java:312)
> [artemis-openwire-protocol-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.deliverStandardMessage(ServerConsumerImpl.java:1161)
> [artemis-server-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.proceedDeliver(ServerConsumerImpl.java:504)
> [artemis-server-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.proceedDeliver(QueueImpl.java:3510)
> [artemis-server-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.deliver(QueueImpl.java:2856)
> [artemis-server-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.access$2300(QueueImpl.java:122)
> [artemis-server-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl$DeliverRunner.run(QueueImpl.java:3848)
> [artemis-server-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
> [artemis-commons-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
> [artemis-commons-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
> [artemis-commons-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_232]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_232]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> [artemis-commons-2.11.0-SNAPSHOT.jar:2.11.0-SNAPSHOT]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (ARTEMIS-2677) Artemis 2.11.0 RejectedExecutionException after successful failover
[
https://issues.apache.org/jira/browse/ARTEMIS-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065455#comment-17065455
]
Justin Bertram edited comment on ARTEMIS-2677 at 3/27/20, 2:14 PM:
---
Attached broker.xml and broker-slave.xml.
I am running a master on 3GB RAM and a slave on 2GB RAM. In general failover
works.
Load on Artemis we process is around average 5-7M messages (text and binary) a
day (approx single message size text message size 7kb). Max messages around
1GB.
I tried to reproduce again with same configuration in AWS with other pair of
master and slave by shutting down master. Failover worked fine and all
consumers were successfully moved to the slave, producers got updated topology
and Artemis was receiving messages, and didn't get
{{RejectedExecutionException}}.
I will try reproducing it in isolation on one machine. Can you please guide in
which situations Artemis throws {{RejectedExecutionException}} (e.g, is it
related to resources (memory, CPU, or slow NFS) on the machine at given
point-in-time when this happened)?
Please let me know if you have any suggestion related to configuration tunings
or resource changes needs to be applied help reduce the possibility of such
exception?
was (Author: jigaronline):
Attached broker.xml and broker-slave.xml.
I am running a master on 3GB RAM and a slave on 2GB RAM. In-general failover
works.
Load on Artemis we process is around average 5-7M messages (text and binary) a
day (approx single message size text message size7 kb). Max messages around
1GB.
I tried to reproduce again with same configuration in AWS with other pair of
master and slave by shutting down master. Failover worked fine and all
consumers were successfully moved to the slave, producers got updated topology
and Artemis was receiving messages, and didn't get "RejectedExecutionException".
I will try reproducing it, in isolation on one machine. Can you please guide in
which situations Artemis throws "RejectedExecutionException"?
E.g, I mean is it related to resources (memory, cpu or slow NFS) on the machine
at given point-in-time when this happened.
Please let me know if you have any suggestion related to configuration tunings
or resource changes needs to be applied help reduce the possiblity of such
exception?
> Artemis 2.11.0 RejectedExecutionException after successful failover
> ---
>
> Key: ARTEMIS-2677
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2677
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Environment: Environment: Artemis 2.11.0 (Master-Slave)
> SharedStore, FilePing. AWS EFS/NFS.
>Reporter: Jigar Shah
>Priority: Major
> Attachments: broker - slave.xml, broker.xml
>
>
> Observed an issue on master shutdown, the slave became active. Right after
> slave being active it started printing "RejectedExecutionException". Also,
> consumers from master to slave was not transferred. And client application
> stopped processing messages.
> Note RejectedExecutionException had [Terminated, pool size = 0, active
> threads = 0, queued tasks = 0, completed tasks = 59059]
> Following are the logs during failover from master to slave:
> Master1:
> {noformat}
> 2020-03-18 12:34:39,911 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 26fb51af-690c-11ea-959a-12f8371a8293
> 2020-03-18 12:34:39,912 INFO [org.apache.activemq.artemis.core.server]
> AMQ221029: stopped bridge
> $.artemis.internal.sf.my-cluster.2c85cd9e-5f75-11ea-9be1-0af9119190b9
> 2020-03-18 12:34:39,950 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
> 2655265e-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 2655265e-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
> 2662e209-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 2662e209-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
> 2669bfdd-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 2669bfdd-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,993 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
>
[jira] [Commented] (ARTEMIS-2677) Artemis 2.11.0 RejectedExecutionException after successful failover
[
https://issues.apache.org/jira/browse/ARTEMIS-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068748#comment-17068748
]
Justin Bertram commented on ARTEMIS-2677:
-
The attached broker configurations look fine granted both are run on the same
machine since they're both using {{localhost}} for their lone {{acceptor}}.
> Artemis 2.11.0 RejectedExecutionException after successful failover
> ---
>
> Key: ARTEMIS-2677
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2677
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Environment: Environment: Artemis 2.11.0 (Master-Slave)
> SharedStore, FilePing. AWS EFS/NFS.
>Reporter: Jigar Shah
>Priority: Major
> Attachments: broker - slave.xml, broker.xml
>
>
> Observed an issue on master shutdown, the slave became active. Right after
> slave being active it started printing "RejectedExecutionException". Also,
> consumers from master to slave was not transferred. And client application
> stopped processing messages.
> Note RejectedExecutionException had [Terminated, pool size = 0, active
> threads = 0, queued tasks = 0, completed tasks = 59059]
> Following are the logs during failover from master to slave:
> Master1:
> {noformat}
> 2020-03-18 12:34:39,911 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 26fb51af-690c-11ea-959a-12f8371a8293
> 2020-03-18 12:34:39,912 INFO [org.apache.activemq.artemis.core.server]
> AMQ221029: stopped bridge
> $.artemis.internal.sf.my-cluster.2c85cd9e-5f75-11ea-9be1-0af9119190b9
> 2020-03-18 12:34:39,950 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
> 2655265e-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 2655265e-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
> 2662e209-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 2662e209-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
> 2669bfdd-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 2669bfdd-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,993 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
> 26615b64-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,994 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 26615b64-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,994 WARN [org.apache.activemq.artemis.core.client]
> AMQ212037: Connection failure to artemis1.sl.idsk.com/10.110.0.17:61616 has
> been detected: AMQ219015: The connection was disconnected because of server
> shutdown [code=DISCONNECTED]
> 2020-03-18 12:34:40,123 FINE [org.jgroups.protocols.FILE_PING] remove
> persistence-fs
> 2020-03-18 12:34:40,137 FINE [org.jgroups.protocols.FD_SOCK]
> ip-10-110-0-17-18496: socket to ip-10-110-0-88-23224 was closed gracefully
> 2020-03-18 12:34:40,138 FINE [org.jgroups.protocols.TCP] closing sockets and
> stopping threads
> 2020-03-18 12:34:40,169 WARN [org.apache.activemq.artemis.core.client]
> AMQ212004: Failed to connect to server.
> 2020-03-18 12:34:41,336 INFO [io.hawt.web.AuthenticationFilter] Destroying
> hawtio authentication filter
> 2020-03-18 12:34:41,341 INFO [io.hawt.HawtioContextListener] Destroying
> hawtio services
> 2020-03-18 12:34:41,464 INFO
> [org.apache.activemq.hawtio.plugin.PluginContextListener] Destroyed
> artemis-plugin plugin
> 2020-03-18 12:34:41,472 INFO
> [org.apache.activemq.hawtio.branding.PluginContextListener] Destroyed
> activemq-branding plugin
> 2020-03-18 12:34:41,509 INFO [org.apache.activemq.artemis.core.server]
> AMQ221002: Apache ActiveMQ Artemis Message Broker version 2.11.0
> [19ade3bb-5f75-11ea-b327-1216d251b187] stopped, uptime 5 hours 2 minutes
> {noformat}
> Slave1:
> {noformat}
> 2020-03-18 12:35:01,613 INFO [org.apache.activemq.artemis.core.server]
> AMQ221010: Backup Server is now live
> 2020-03-18 12:35:01,626 INFO [org.apache.activemq.artemis.core.server]
> AMQ221027: Bridge ClusterConnectionBridge@5ced3917
> [name=$.artemis.internal.sf.my-cluster.2c85cd9e-5f75-11ea-9be1-0af9119190b9,
> queue=QueueImpl[name=$.artemis.internal.sf.my-cluster.2c85cd9e-5f75-11ea-9be1-0af9119190b9,
>
[jira] [Work logged] (AMQ-7458) Implement bounds checking on the message scheduling properties
[ https://issues.apache.org/jira/browse/AMQ-7458?focusedWorklogId=411025=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-411025 ] ASF GitHub Bot logged work on AMQ-7458: --- Author: ASF GitHub Bot Created on: 27/Mar/20 12:15 Start Date: 27/Mar/20 12:15 Worklog Time Spent: 10m Work Description: coheigea commented on pull request #521: AMQ-7458 - Implement bounds checking on the message scheduling proper… URL: https://github.com/apache/activemq/pull/521 …ties This task is to implement bounds checking on the message scheduling properties. The values for delay, period + repeat should be rejected if they are < 0. Also, a maximum value should be set (and configurable) for the max repeat value, as it has the potential to cause a denial of service issue if many messages are sent with a repeat value of Integer.MAX_VALUE. In the accompanying PR, I've set the default max value to 1000. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 411025) Remaining Estimate: 0h Time Spent: 10m > Implement bounds checking on the message scheduling properties > -- > > Key: AMQ-7458 > URL: https://issues.apache.org/jira/browse/AMQ-7458 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0 > > Time Spent: 10m > Remaining Estimate: 0h > > This task is to implement bounds checking on the message scheduling > properties. The values for delay, period + repeat should be rejected if they > are < 0. Also, a maximum value should be set (and configurable) for the max > repeat value, as it has the potential to cause a denial of service issue if > many messages are sent with a repeat value of Integer.MAX_VALUE. In the > accompanying PR, I've set the default max value to 1000. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMQ-7458) Implement bounds checking on the message scheduling properties
Colm O hEigeartaigh created AMQ-7458: Summary: Implement bounds checking on the message scheduling properties Key: AMQ-7458 URL: https://issues.apache.org/jira/browse/AMQ-7458 Project: ActiveMQ Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 5.16.0 This task is to implement bounds checking on the message scheduling properties. The values for delay, period + repeat should be rejected if they are < 0. Also, a maximum value should be set (and configurable) for the max repeat value, as it has the potential to cause a denial of service issue if many messages are sent with a repeat value of Integer.MAX_VALUE. In the accompanying PR, I've set the default max value to 1000. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7442) Add JDK 11 build support
[ https://issues.apache.org/jira/browse/AMQ-7442?focusedWorklogId=410948=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-410948 ] ASF GitHub Bot logged work on AMQ-7442: --- Author: ASF GitHub Bot Created on: 27/Mar/20 09:34 Start Date: 27/Mar/20 09:34 Worklog Time Spent: 10m Work Description: jbonofre commented on issue #511: AMQ-7442 - Adding build support for JDK 11 URL: https://github.com/apache/activemq/pull/511#issuecomment-604904311 I also have a branch with full build on JDK 11+, I will open and will let you know. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 410948) Time Spent: 0.5h (was: 20m) > Add JDK 11 build support > > > Key: AMQ-7442 > URL: https://issues.apache.org/jira/browse/AMQ-7442 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 5.15.11 >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.17.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > 5.16.0 has been updated to be runtime compatible with Java 8+ including Java > 11 and this is the Jira to allow build compatibility with JDK 11 as well. > I'm targeting 5.17.0 for this as it will make it easier if we remove Scala > and LevelDB support. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7447) Update copyright years
[ https://issues.apache.org/jira/browse/AMQ-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068477#comment-17068477 ] ASF subversion and git services commented on AMQ-7447: -- Commit 0075bb695a750a75d1f350751a50248a45517e7a in activemq's branch refs/heads/activemq-5.15.x from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=0075bb6 ] AMQ-7447 - Update copyright years (cherry picked from commit c3cdffb373b74782bfa01692406449ab0ea18667) > Update copyright years > -- > > Key: AMQ-7447 > URL: https://issues.apache.org/jira/browse/AMQ-7447 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > There are numerous instances in the codebase where the copyright years are > out of date, they should be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMQ-7447) Update copyright years
[ https://issues.apache.org/jira/browse/AMQ-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7447. --- Resolution: Fixed > Update copyright years > -- > > Key: AMQ-7447 > URL: https://issues.apache.org/jira/browse/AMQ-7447 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > There are numerous instances in the codebase where the copyright years are > out of date, they should be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7447) Update copyright years
[ https://issues.apache.org/jira/browse/AMQ-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068475#comment-17068475 ] ASF subversion and git services commented on AMQ-7447: -- Commit da9e4028c939f5fc194e63fadc586bfb42c1a7e1 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=da9e402 ] Merge pull request #513 from coheigea/AMQ-7447 AMQ-7447 - Update copyright years > Update copyright years > -- > > Key: AMQ-7447 > URL: https://issues.apache.org/jira/browse/AMQ-7447 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > There are numerous instances in the codebase where the copyright years are > out of date, they should be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7447) Update copyright years
[ https://issues.apache.org/jira/browse/AMQ-7447?focusedWorklogId=410947=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-410947 ] ASF GitHub Bot logged work on AMQ-7447: --- Author: ASF GitHub Bot Created on: 27/Mar/20 09:29 Start Date: 27/Mar/20 09:29 Worklog Time Spent: 10m Work Description: jbonofre commented on pull request #513: AMQ-7447 - Update copyright years URL: https://github.com/apache/activemq/pull/513 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 410947) Time Spent: 20m (was: 10m) > Update copyright years > -- > > Key: AMQ-7447 > URL: https://issues.apache.org/jira/browse/AMQ-7447 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > There are numerous instances in the codebase where the copyright years are > out of date, they should be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7447) Update copyright years
[ https://issues.apache.org/jira/browse/AMQ-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068474#comment-17068474 ] ASF subversion and git services commented on AMQ-7447: -- Commit c3cdffb373b74782bfa01692406449ab0ea18667 in activemq's branch refs/heads/master from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=c3cdffb ] AMQ-7447 - Update copyright years > Update copyright years > -- > > Key: AMQ-7447 > URL: https://issues.apache.org/jira/browse/AMQ-7447 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > There are numerous instances in the codebase where the copyright years are > out of date, they should be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7447) Update copyright years
[ https://issues.apache.org/jira/browse/AMQ-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068476#comment-17068476 ] ASF subversion and git services commented on AMQ-7447: -- Commit da9e4028c939f5fc194e63fadc586bfb42c1a7e1 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=da9e402 ] Merge pull request #513 from coheigea/AMQ-7447 AMQ-7447 - Update copyright years > Update copyright years > -- > > Key: AMQ-7447 > URL: https://issues.apache.org/jira/browse/AMQ-7447 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > There are numerous instances in the codebase where the copyright years are > out of date, they should be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7449) Update Shiro to 1.5.2
[ https://issues.apache.org/jira/browse/AMQ-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068468#comment-17068468 ] ASF subversion and git services commented on AMQ-7449: -- Commit e718257dd2f12743f66dae8df13771443a0e0f2b in activemq's branch refs/heads/activemq-5.15.x from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=e718257 ] AMQ-7449 - Update Apache Shiro to 1.5.2 (cherry picked from commit ba42d5527ab76d030af78889b8700dcbe877fc78) > Update Shiro to 1.5.2 > - > > Key: AMQ-7449 > URL: https://issues.apache.org/jira/browse/AMQ-7449 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to update Shiro to 1.5.2 due to CVE-2020-1957 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMQ-7449) Update Shiro to 1.5.2
[ https://issues.apache.org/jira/browse/AMQ-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7449: -- Component/s: Security/JAAS Broker > Update Shiro to 1.5.2 > - > > Key: AMQ-7449 > URL: https://issues.apache.org/jira/browse/AMQ-7449 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker, Security/JAAS >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to update Shiro to 1.5.2 due to CVE-2020-1957 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMQ-7449) Update Shiro to 1.5.2
[ https://issues.apache.org/jira/browse/AMQ-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7449. --- Resolution: Fixed > Update Shiro to 1.5.2 > - > > Key: AMQ-7449 > URL: https://issues.apache.org/jira/browse/AMQ-7449 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker, Security/JAAS >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to update Shiro to 1.5.2 due to CVE-2020-1957 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7449) Update Shiro to 1.5.2
[ https://issues.apache.org/jira/browse/AMQ-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068464#comment-17068464 ] ASF subversion and git services commented on AMQ-7449: -- Commit ba42d5527ab76d030af78889b8700dcbe877fc78 in activemq's branch refs/heads/master from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=ba42d55 ] AMQ-7449 - Update Apache Shiro to 1.5.2 > Update Shiro to 1.5.2 > - > > Key: AMQ-7449 > URL: https://issues.apache.org/jira/browse/AMQ-7449 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to update Shiro to 1.5.2 due to CVE-2020-1957 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7449) Update Shiro to 1.5.2
[ https://issues.apache.org/jira/browse/AMQ-7449?focusedWorklogId=410941=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-410941 ] ASF GitHub Bot logged work on AMQ-7449: --- Author: ASF GitHub Bot Created on: 27/Mar/20 09:24 Start Date: 27/Mar/20 09:24 Worklog Time Spent: 10m Work Description: jbonofre commented on pull request #516: AMQ-7449 - Update Apache Shiro to 1.5.2 URL: https://github.com/apache/activemq/pull/516 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 410941) Time Spent: 20m (was: 10m) > Update Shiro to 1.5.2 > - > > Key: AMQ-7449 > URL: https://issues.apache.org/jira/browse/AMQ-7449 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to update Shiro to 1.5.2 due to CVE-2020-1957 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7449) Update Shiro to 1.5.2
[ https://issues.apache.org/jira/browse/AMQ-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068465#comment-17068465 ] ASF subversion and git services commented on AMQ-7449: -- Commit 5f02e220a0d5f668e27344c2a03b8c3d6c3c923b in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=5f02e22 ] Merge pull request #516 from coheigea/AMQ-7449 AMQ-7449 - Update Apache Shiro to 1.5.2 > Update Shiro to 1.5.2 > - > > Key: AMQ-7449 > URL: https://issues.apache.org/jira/browse/AMQ-7449 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to update Shiro to 1.5.2 due to CVE-2020-1957 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7449) Update Shiro to 1.5.2
[ https://issues.apache.org/jira/browse/AMQ-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068466#comment-17068466 ] ASF subversion and git services commented on AMQ-7449: -- Commit 5f02e220a0d5f668e27344c2a03b8c3d6c3c923b in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=5f02e22 ] Merge pull request #516 from coheigea/AMQ-7449 AMQ-7449 - Update Apache Shiro to 1.5.2 > Update Shiro to 1.5.2 > - > > Key: AMQ-7449 > URL: https://issues.apache.org/jira/browse/AMQ-7449 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to update Shiro to 1.5.2 due to CVE-2020-1957 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7454) Remove xmpp artifacts
[ https://issues.apache.org/jira/browse/AMQ-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068460#comment-17068460 ] ASF subversion and git services commented on AMQ-7454: -- Commit 1c504160d823068286bc74e963017ffa265cd6aa in activemq's branch refs/heads/master from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=1c50416 ] AMQ-7454 - Remove xmpp artifacts > Remove xmpp artifacts > - > > Key: AMQ-7454 > URL: https://issues.apache.org/jira/browse/AMQ-7454 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > There are a few artifacts left over from activemq-xmpp, which should be > removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMQ-7454) Remove xmpp artifacts
[ https://issues.apache.org/jira/browse/AMQ-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7454. --- Resolution: Fixed > Remove xmpp artifacts > - > > Key: AMQ-7454 > URL: https://issues.apache.org/jira/browse/AMQ-7454 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > There are a few artifacts left over from activemq-xmpp, which should be > removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7454) Remove xmpp artifacts
[ https://issues.apache.org/jira/browse/AMQ-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068461#comment-17068461 ] ASF subversion and git services commented on AMQ-7454: -- Commit 4d968391a73f97f57e3c727ee7c60b232b2a6f63 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=4d96839 ] Merge pull request #518 from coheigea/AMQ-7454 AMQ-7454 - Remove xmpp artifacts > Remove xmpp artifacts > - > > Key: AMQ-7454 > URL: https://issues.apache.org/jira/browse/AMQ-7454 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > There are a few artifacts left over from activemq-xmpp, which should be > removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7454) Remove xmpp artifacts
[ https://issues.apache.org/jira/browse/AMQ-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068462#comment-17068462 ] ASF subversion and git services commented on AMQ-7454: -- Commit 4d968391a73f97f57e3c727ee7c60b232b2a6f63 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=4d96839 ] Merge pull request #518 from coheigea/AMQ-7454 AMQ-7454 - Remove xmpp artifacts > Remove xmpp artifacts > - > > Key: AMQ-7454 > URL: https://issues.apache.org/jira/browse/AMQ-7454 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > There are a few artifacts left over from activemq-xmpp, which should be > removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7454) Remove xmpp artifacts
[ https://issues.apache.org/jira/browse/AMQ-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068463#comment-17068463 ] ASF subversion and git services commented on AMQ-7454: -- Commit de922498e28ffe986fbd1910fd9a3276ca9c20b3 in activemq's branch refs/heads/activemq-5.15.x from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=de92249 ] AMQ-7454 - Remove xmpp artifacts (cherry picked from commit 1c504160d823068286bc74e963017ffa265cd6aa) > Remove xmpp artifacts > - > > Key: AMQ-7454 > URL: https://issues.apache.org/jira/browse/AMQ-7454 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > There are a few artifacts left over from activemq-xmpp, which should be > removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7454) Remove xmpp artifacts
[ https://issues.apache.org/jira/browse/AMQ-7454?focusedWorklogId=410939=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-410939 ] ASF GitHub Bot logged work on AMQ-7454: --- Author: ASF GitHub Bot Created on: 27/Mar/20 09:22 Start Date: 27/Mar/20 09:22 Worklog Time Spent: 10m Work Description: jbonofre commented on pull request #518: AMQ-7454 - Remove xmpp artifacts URL: https://github.com/apache/activemq/pull/518 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 410939) Time Spent: 20m (was: 10m) > Remove xmpp artifacts > - > > Key: AMQ-7454 > URL: https://issues.apache.org/jira/browse/AMQ-7454 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 20m > Remaining Estimate: 0h > > There are a few artifacts left over from activemq-xmpp, which should be > removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7457) Support wider password encryption schemes
[ https://issues.apache.org/jira/browse/AMQ-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068458#comment-17068458 ] ASF subversion and git services commented on AMQ-7457: -- Commit 6d4437ab355b37272d444116c914f59d0ecb6f95 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=6d4437a ] Merge pull request #520 from coheigea/AMQ-7457 AMQ-7457 - Support wider password encryption schemes > Support wider password encryption schemes > - > > Key: AMQ-7457 > URL: https://issues.apache.org/jira/browse/AMQ-7457 > Project: ActiveMQ > Issue Type: Improvement > Components: Security/JAAS >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0 > > Time Spent: 20m > Remaining Estimate: 0h > > For password encryption we only support the (default) algorithm > PBEWithMD5AndDES. This task is to support more modern PBE algorithms for: > * The activemq encrypt/decrypt script > * JAAS properties > In addition, we could use the more modern jasypt-spring4 dependency instead > of jasypt-spring13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7457) Support wider password encryption schemes
[ https://issues.apache.org/jira/browse/AMQ-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068459#comment-17068459 ] ASF subversion and git services commented on AMQ-7457: -- Commit 6d4437ab355b37272d444116c914f59d0ecb6f95 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=6d4437a ] Merge pull request #520 from coheigea/AMQ-7457 AMQ-7457 - Support wider password encryption schemes > Support wider password encryption schemes > - > > Key: AMQ-7457 > URL: https://issues.apache.org/jira/browse/AMQ-7457 > Project: ActiveMQ > Issue Type: Improvement > Components: Security/JAAS >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0 > > Time Spent: 20m > Remaining Estimate: 0h > > For password encryption we only support the (default) algorithm > PBEWithMD5AndDES. This task is to support more modern PBE algorithms for: > * The activemq encrypt/decrypt script > * JAAS properties > In addition, we could use the more modern jasypt-spring4 dependency instead > of jasypt-spring13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMQ-7454) Remove xmpp artifacts
[ https://issues.apache.org/jira/browse/AMQ-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7454: -- Component/s: Broker > Remove xmpp artifacts > - > > Key: AMQ-7454 > URL: https://issues.apache.org/jira/browse/AMQ-7454 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 5.16.0, 5.15.13 > > Time Spent: 10m > Remaining Estimate: 0h > > There are a few artifacts left over from activemq-xmpp, which should be > removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7457) Support wider password encryption schemes
[ https://issues.apache.org/jira/browse/AMQ-7457?focusedWorklogId=410937=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-410937 ] ASF GitHub Bot logged work on AMQ-7457: --- Author: ASF GitHub Bot Created on: 27/Mar/20 09:20 Start Date: 27/Mar/20 09:20 Worklog Time Spent: 10m Work Description: jbonofre commented on pull request #520: AMQ-7457 - Support wider password encryption schemes URL: https://github.com/apache/activemq/pull/520 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 410937) Time Spent: 20m (was: 10m) > Support wider password encryption schemes > - > > Key: AMQ-7457 > URL: https://issues.apache.org/jira/browse/AMQ-7457 > Project: ActiveMQ > Issue Type: Improvement > Components: Security/JAAS >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0 > > Time Spent: 20m > Remaining Estimate: 0h > > For password encryption we only support the (default) algorithm > PBEWithMD5AndDES. This task is to support more modern PBE algorithms for: > * The activemq encrypt/decrypt script > * JAAS properties > In addition, we could use the more modern jasypt-spring4 dependency instead > of jasypt-spring13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7457) Support wider password encryption schemes
[ https://issues.apache.org/jira/browse/AMQ-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068457#comment-17068457 ] ASF subversion and git services commented on AMQ-7457: -- Commit 9599ad8d95958ca8e2506f6efb46ebdb29a53d4d in activemq's branch refs/heads/master from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=9599ad8 ] AMQ-7457 - Support wider password encryption schemes > Support wider password encryption schemes > - > > Key: AMQ-7457 > URL: https://issues.apache.org/jira/browse/AMQ-7457 > Project: ActiveMQ > Issue Type: Improvement > Components: Security/JAAS >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0 > > Time Spent: 20m > Remaining Estimate: 0h > > For password encryption we only support the (default) algorithm > PBEWithMD5AndDES. This task is to support more modern PBE algorithms for: > * The activemq encrypt/decrypt script > * JAAS properties > In addition, we could use the more modern jasypt-spring4 dependency instead > of jasypt-spring13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMQ-7457) Support wider password encryption schemes
[ https://issues.apache.org/jira/browse/AMQ-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7457: -- Component/s: Security/JAAS > Support wider password encryption schemes > - > > Key: AMQ-7457 > URL: https://issues.apache.org/jira/browse/AMQ-7457 > Project: ActiveMQ > Issue Type: Improvement > Components: Security/JAAS >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0 > > Time Spent: 10m > Remaining Estimate: 0h > > For password encryption we only support the (default) algorithm > PBEWithMD5AndDES. This task is to support more modern PBE algorithms for: > * The activemq encrypt/decrypt script > * JAAS properties > In addition, we could use the more modern jasypt-spring4 dependency instead > of jasypt-spring13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMQ-7457) Support wider password encryption schemes
[ https://issues.apache.org/jira/browse/AMQ-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7457. --- Resolution: Fixed > Support wider password encryption schemes > - > > Key: AMQ-7457 > URL: https://issues.apache.org/jira/browse/AMQ-7457 > Project: ActiveMQ > Issue Type: Improvement > Components: Security/JAAS >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0 > > Time Spent: 20m > Remaining Estimate: 0h > > For password encryption we only support the (default) algorithm > PBEWithMD5AndDES. This task is to support more modern PBE algorithms for: > * The activemq encrypt/decrypt script > * JAAS properties > In addition, we could use the more modern jasypt-spring4 dependency instead > of jasypt-spring13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2677) Artemis 2.11.0 RejectedExecutionException after successful failover
[
https://issues.apache.org/jira/browse/ARTEMIS-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068429#comment-17068429
]
Jigar Shah commented on ARTEMIS-2677:
-
We are trying to reproduce it. But not able to re-produce situation. Any issues
in configuration was identified on uploaded broker.xml(s)
> Artemis 2.11.0 RejectedExecutionException after successful failover
> ---
>
> Key: ARTEMIS-2677
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2677
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Environment: Environment: Artemis 2.11.0 (Master-Slave)
> SharedStore, FilePing. AWS EFS/NFS.
>Reporter: Jigar Shah
>Priority: Major
> Attachments: broker - slave.xml, broker.xml
>
>
> Observed an issue on master shutdown, the slave became active. Right after
> slave being active it started printing "RejectedExecutionException". Also,
> consumers from master to slave was not transferred. And client application
> stopped processing messages.
> Note RejectedExecutionException had [Terminated, pool size = 0, active
> threads = 0, queued tasks = 0, completed tasks = 59059]
> Following are the logs during failover from master to slave:
> Master1:
> {noformat}
> 2020-03-18 12:34:39,911 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 26fb51af-690c-11ea-959a-12f8371a8293
> 2020-03-18 12:34:39,912 INFO [org.apache.activemq.artemis.core.server]
> AMQ221029: stopped bridge
> $.artemis.internal.sf.my-cluster.2c85cd9e-5f75-11ea-9be1-0af9119190b9
> 2020-03-18 12:34:39,950 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
> 2655265e-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 2655265e-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
> 2662e209-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 2662e209-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
> 2669bfdd-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,951 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 2669bfdd-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,993 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
> 26615b64-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,994 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 26615b64-690c-11ea-9d7c-12f7d16c4f81
> 2020-03-18 12:34:39,994 WARN [org.apache.activemq.artemis.core.client]
> AMQ212037: Connection failure to artemis1.sl.idsk.com/10.110.0.17:61616 has
> been detected: AMQ219015: The connection was disconnected because of server
> shutdown [code=DISCONNECTED]
> 2020-03-18 12:34:40,123 FINE [org.jgroups.protocols.FILE_PING] remove
> persistence-fs
> 2020-03-18 12:34:40,137 FINE [org.jgroups.protocols.FD_SOCK]
> ip-10-110-0-17-18496: socket to ip-10-110-0-88-23224 was closed gracefully
> 2020-03-18 12:34:40,138 FINE [org.jgroups.protocols.TCP] closing sockets and
> stopping threads
> 2020-03-18 12:34:40,169 WARN [org.apache.activemq.artemis.core.client]
> AMQ212004: Failed to connect to server.
> 2020-03-18 12:34:41,336 INFO [io.hawt.web.AuthenticationFilter] Destroying
> hawtio authentication filter
> 2020-03-18 12:34:41,341 INFO [io.hawt.HawtioContextListener] Destroying
> hawtio services
> 2020-03-18 12:34:41,464 INFO
> [org.apache.activemq.hawtio.plugin.PluginContextListener] Destroyed
> artemis-plugin plugin
> 2020-03-18 12:34:41,472 INFO
> [org.apache.activemq.hawtio.branding.PluginContextListener] Destroyed
> activemq-branding plugin
> 2020-03-18 12:34:41,509 INFO [org.apache.activemq.artemis.core.server]
> AMQ221002: Apache ActiveMQ Artemis Message Broker version 2.11.0
> [19ade3bb-5f75-11ea-b327-1216d251b187] stopped, uptime 5 hours 2 minutes
> {noformat}
> Slave1:
> {noformat}
> 2020-03-18 12:35:01,613 INFO [org.apache.activemq.artemis.core.server]
> AMQ221010: Backup Server is now live
> 2020-03-18 12:35:01,626 INFO [org.apache.activemq.artemis.core.server]
> AMQ221027: Bridge ClusterConnectionBridge@5ced3917
> [name=$.artemis.internal.sf.my-cluster.2c85cd9e-5f75-11ea-9be1-0af9119190b9,
> queue=QueueImpl[name=$.artemis.internal.sf.my-cluster.2c85cd9e-5f75-11ea-9be1-0af9119190b9,
> postOffice=PostOfficeImpl
[jira] [Work logged] (AMQ-7457) Support wider password encryption schemes
[ https://issues.apache.org/jira/browse/AMQ-7457?focusedWorklogId=410897=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-410897 ] ASF GitHub Bot logged work on AMQ-7457: --- Author: ASF GitHub Bot Created on: 27/Mar/20 08:34 Start Date: 27/Mar/20 08:34 Worklog Time Spent: 10m Work Description: coheigea commented on pull request #520: AMQ-7457 - Support wider password encryption schemes URL: https://github.com/apache/activemq/pull/520 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 410897) Remaining Estimate: 0h Time Spent: 10m > Support wider password encryption schemes > - > > Key: AMQ-7457 > URL: https://issues.apache.org/jira/browse/AMQ-7457 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0 > > Time Spent: 10m > Remaining Estimate: 0h > > For password encryption we only support the (default) algorithm > PBEWithMD5AndDES. This task is to support more modern PBE algorithms for: > * The activemq encrypt/decrypt script > * JAAS properties > In addition, we could use the more modern jasypt-spring4 dependency instead > of jasypt-spring13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMQ-7457) Support wider password encryption schemes
Colm O hEigeartaigh created AMQ-7457: Summary: Support wider password encryption schemes Key: AMQ-7457 URL: https://issues.apache.org/jira/browse/AMQ-7457 Project: ActiveMQ Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 5.16.0 For password encryption we only support the (default) algorithm PBEWithMD5AndDES. This task is to support more modern PBE algorithms for: * The activemq encrypt/decrypt script * JAAS properties In addition, we could use the more modern jasypt-spring4 dependency instead of jasypt-spring13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
