[ https://issues.apache.org/jira/browse/NIFI-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257014#comment-16257014 ]
Aldrin Piri commented on NIFI-4616: ----------------------------------- This is a clone of NIFI-2739. I am noticing similar behavior when connecting to an SSL enabled Kafka broker. If I configure a Consume Kafka processor with Security Provider and an SSL Context Service and then start it, it will not error and have a task attempting to connect even when my broker is not started. If I then start my broker, the processor will remain in its prior state. Stopping the processor, I see another concurrent task pop up, providing a total of 2 and then a warning level bulletin is posted with the following. {quote} 2017-11-17 09:09:29,640 WARN [Timer-Driven Process Thread-9] o.a.n.p.kafka.pubsub.ConsumeKafka_0_10 ConsumeKafka_0_10[id=015f1005-38d4-13aa-8ba4-def62a3de935] Was interrupted while trying to communicate with Kafka with lease org.apache.nifi.processors.kafka.pubsub.ConsumerPool$SimpleConsumerLease@230ccbef. Will roll back session and discard any partially received data. {quote} > ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to > communicate with Kafka broker that is SSL enabled > ------------------------------------------------------------------------------------------------------------------------ > > Key: NIFI-4616 > URL: https://issues.apache.org/jira/browse/NIFI-4616 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Affects Versions: 1.4.0 > Reporter: Aldrin Piri > Fix For: 1.1.0 > > > If I use ConsumeKafka and point to a broker that is in a bad state, I see > ConsumeKafka block indefinitely. -- This message was sent by Atlassian JIRA (v6.4.14#64029)