liaodn opened a new issue, #231:
URL: https://github.com/apache/bifromq/issues/231

   ## Background
   `InboxFetchPipeline` maintains an inbox-to-session mapping used by 
`signalFetch`. `signalFetch` may run concurrently with session updates 
triggered by fetch hints.
   
   ## Problem
   Under concurrent signaling and session removal or re-registration, iterating 
session IDs can throw `ConcurrentModificationException`.
   In addition, stale session IDs may remain in the mapping after their fetch 
state is gone, which can lead to:
   - `signalFetch` reporting a positive signal path when no live session is 
actually present
   - orphaned mapping entries that should have been cleaned


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to