I found out by logger that for those Applications whose Processors *are
initialized* it is logged that:
INFO AbstractCoordinator:677 - [Consumer
clientId=sk5-client-StreamThread-1-consumer, groupId=sk5-appid]
Discovered group coordinator myserver:6667 (id: 2147482646 rack: null)
>
> INFO Consu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It's hard to say. However, calling `KafkaStreams#close()` in the
uncaught exception handler is considered bad practice (using a timeout
avoids the deadlock, but it would be better to just set a boolean flag
and call `close()` from outside the handler
I tried to create a kafka streams application, but there was a bug in my
code. I believe there was a deadlock for my application and whenever I
tried to run an application instance with the same
StreamsConfig.APPLICATION_ID_CONFIG id it could not start. I had to create
another instance with differe
