[AMQ-9483] Non Daemon Connection Keeping JVM alive when combined with optimizedAckScheduledAckInterval

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.18.4
• Component/s: JMS client
• Patch Info: Patch Available
• Flags: Patch

Language

java

• Assignee: Unassigned
• Reporter: Matthew Washburn
• Created: 19/Apr/24 13:56
• Updated: 26/Apr/24 16:03

Description

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. 

Issue Links

• fixes: AMQ-796 Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive.