Hi,
I can't reproduce this issue against Artemis 2.11.0 because this issue was
already fixed by Clebert with ARTEMIS-2592.
Before the fix, the QueueImpl.removeConsumer locks the queue until the
deleting of auto-create queue.
The deleting of a queue calls ManagementServiceImpl.unregisterQueue that
If it helps, I can raise a PR for this over the weekend
On Sat, 21 Mar 2020 at 00:53, Clebert Suconic
wrote:
> The fix should be straightforward. ManagementServiceIMpl is also
> holding a lock PostOffice. Which I'm not sure we still need to do it..
> it's ancient code.
>
>
> We could perhaps rem
The fix should be straightforward. ManagementServiceIMpl is also
holding a lock PostOffice. Which I'm not sure we still need to do it..
it's ancient code.
We could perhaps remove it.. but at this point it's a riskier choice.
We probably need to move listener.onNotification calls to a single
execu
Hi Clebert,
I guess you mean `auto-delete-queues-delay`[1]. It can be used to set a
timeout before removing auto-created queues.
[1]
https://activemq.apache.org/components/artemis/documentation/latest/address-model.html
Regards,
Domenico
--
Sent from: http://activemq.2283324.n4.nabble.com/Act
or at least.. there's a back-off period.. I forgot the name now...
where you can set a timeout to remove the queue.. lets say if no
clients reconnecting in 5 minutes.
@Domenico: remember what I'm talking about?
On Fri, Mar 20, 2020 at 11:48 AM Clebert Suconic
wrote:
>
> I would highly recommend
I would highly recommend to disable auto-create in any production system.
We actually have that for testing, and going forward we though about
setting to false by default.
On Thu, Mar 19, 2020 at 9:53 AM brusdev wrote:
>
> Hi ldebello,
>
> the deadlock is due to a collision from 2 threads on the
Hi Domenico
Thanks for the reply, we are going to test the suggested change and we have
created the jira.
https://issues.apache.org/jira/browse/ARTEMIS-2670
Thanks for your help.
Regards,
Luis
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi ldebello,
the deadlock is due to a collision from 2 threads on the same queue with the
auto delete queue policy enabled:
- the first thread is trying to add a redistributor to the queue for a new
consumer.
- the second thread is trying to delete the queue because it is empty and
the last consum
For some reason we got the deadlock in another instance (it seems to me
related to the number of connection, doing this bug more visible) attaching
the thread dump just in case someone see something similar.
jstack -l 27571
2020-03-16 10:00:15
Full thread dump OpenJDK 64-Bit Server VM (25.222-b10
