[
https://issues.apache.org/jira/browse/AMQ-9483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957005#comment-17957005
]
Matt Pavlovich edited comment on AMQ-9483 at 6/9/25 2:26 PM:
-------------------------------------------------------------
||#||Consumer Type||Failover||OptAckInt||Thread Type||Current||Expected||Fix||
|uc-0|recv|n|n|daemon| ? | ? | ? |
|uc-1|recv|n|n|user| ? | ? | ? |
|uc-2|recv|n|y|daemon| ? | ? | ? |
|uc-3|recv|n|y|user| ? | ? | ? |
|uc-4|recv|y|n|daemon| ? | ? | ? |
|uc-5|recv|y|n|user| ? | ? | ? |
|uc-6|recv|y|y|daemon| ? | ? | ? |
|uc-6|recv|y|y|user| ? | ? | ? |
Note: May need a table with message listener as well
was (Author: mattrpav):
||Consumer type||Failover||OptAckInt||App Thread||Current||Expected||Fix||
|recv|n|n|daemon| ? | ? | ? |
|recv|n|n|non-daemon| ? | ? | ? |
|recv|n|y|daemon| ? | ? | ? |
|recv|n|y|non-daemon| ? | ? | ? |
|recv|y|n|daemon| ? | ? | ? |
|recv|y|n|non-daemon| ? | ? | ? |
|recv|y|y|daemon| ? | ? | ? |
|recv|y|y|non-daemon| ? | ? | ? |
Note: May need a table with message listener as well
> 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, 6.1.7, 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: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
