[ARTEMIS-4905] PeriodicConnectionExpiry plugin comparison error treating seconds as milli seconds

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.35.0
• Fix Version/s: 2.36.0
• Component/s: Configuration
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 03/Jul/24 11:52
• Updated: 24/Jul/24 17:02
• Resolved: 03/Jul/24 15:10

Description

The comparison with current time millis is treating the expirySeconds as seconds rather than millis in error, leading to immediate expiry.
the workaround is to configure expirySeconds as milliseconds...

Issue Links

• links to: GitHub Pull Request #5067