Received message are still being processed after disconnect about cometd HOT 9 CLOSED

@dyutiman what you describe is custom application logic that you have to implement yourself.

From the CometD point of view, the messages have been received and they will be processed.
Whether some of them contain an application-specific "event id", CometD cannot know and won't know what it means, so you have to implement your own logic.

from cometd.

It seems like working!!

Thank you so much @sbordet

from cometd.

If the messages have been fully received, they will be processed by CometD.

If you want to stop the processing of already received messages, you can just ignore them, and you do this in your application.

You want to do this on the client or on the server?

from cometd.

I want to do this on the client side.

We keep track of the event id we process and in the next subscription we used the last processed event id to begin. Here as the events are still in process even after we disconnect the client, the next immediate subscription is picking an intermiddiate event id (among those which are being processed).
This is causing duplicate event processing.

from cometd.

Thanks for the reply @sbordet

Yes I agree that it is application specific. I just wanted to check if there is any way available that when I disconnect the client the background Jetty thread which received all the events can be interrupted.

from cometd.

You can do this with a client extension, something like this:

bayeuxClient.addExtension(new Extension() {
  boolean rcv(ClientSession session, Message.Mutable message) {
    if (bayeuxClient.isDisconnected()) {
      // Drop the message.
      return false;
    }
    return true;
  }
});

from cometd.

This is great. Thanks a lot! Let me try this out and confirm.

from cometd.

Does it work for you?

from cometd.

I will update here once we try this.

from cometd.