Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kpl-callback-pool-* in KinesisProducer is not shutdown on destroy() #98

Open
ghost opened this issue Apr 4, 2017 · 1 comment
Open

Comments

@ghost
Copy link

ghost commented Apr 4, 2017

There are times when we need to restart the kinesis producer to get messages to send again, and we do this by calling KinesisProducer.destroy(), followed by new KinesisProducer(config). However, we notice that when doing this, the old kpl-callback-pool is still lingering around, so the more restarts we do, the more of these we have hanging around.

The threadpool should be shutdown when calling KinesisProducer.destroy()

@skidder
Copy link
Contributor

skidder commented Apr 5, 2017

This might be a duplicate of #93

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant