You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (Jira)" <ji...@apache.org> on 2025/03/24 15:42:00 UTC
[jira] [Updated] (AMQ-9483) Non Daemon Connection Keeping JVM alive when combined with optimizedAckScheduledAckInterval
[ https://issues.apache.org/jira/browse/AMQ-9483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Pavlovich updated AMQ-9483:
--------------------------------
Fix Version/s: 5.18.8
> Non Daemon Connection Keeping JVM alive when combined with optimizedAckScheduledAckInterval
> -------------------------------------------------------------------------------------------
>
> Key: AMQ-9483
> URL: https://issues.apache.org/jira/browse/AMQ-9483
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.18.4
> Reporter: Matthew Washburn
> Assignee: Matt Pavlovich
> Priority: Major
> Fix For: 6.2.0, 5.19.1, 5.18.8
>
> Attachments: 0001-make-sure-the-executor-service-for-deliveryingAcknow.patch, 796.patch
>
>
> The thread used to send ack unacked messages when using the optimizedAckScheduledAckInterval is not daemon even if the connection is set to daemon. This is probably advantageous as you would not want a queue or durable topic consumer to shutdown before it has finished acking a message causing it to be redelivered on restart. On the other hand, it means that if the optimized ack scheduler ever kicks in on a daemon connection the JVM will never exit. Also the thread isn't uniquely named so it's hard to track down.
>
> I'm not sure how to get in the situation where there are unacked messages that are acked by the timer so I'm not sure how to create a simple repo script but the attached patch fixes my application.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact