Skip to content

Document thread leak risk #3

@l-robinson

Description

@l-robinson

Currently the documentation suggests that it would be safe to create a new PasswordCheckVerifier() whenever it is required however this results in new thread pools being created each time.

It would be good if this was pointed out in the documentation / best practices illustrated to avoid production thread leaks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions