Skip to content

Exception in message processor causes consumer to exit #240

Closed

Description

@bwegrzyn

According to the documentation, it says that usually you do not need to catch exceptions in the message processor.

Currently, if an exception occurs, the consumer process exits completely instead of logging an error.

I can wrap my processors in a try/catch, but it would be a nice improvement to have the consumer automatically catch exceptions and log them.

Activity

  1. makasim commented on Oct 20, 2017

    @makasim
    Member

    That's expected behavior, a consumer has to fail fast for various reasons.

    We discussed that several times some time ago and came to a conclusion that this is the right behavior.

  2. bwegrzyn commented on Oct 20, 2017

    @bwegrzyn
    Author

    Ok, that makes sense. Maybe the documentation could be a little clearer on that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions