Skip to main content
usman35
Silver ⭐️
usman35
Silver ⭐️
Jun 28, 2023 8:01 AM UTC

Publish_Kafka_1_0 processor not stops working after upgrading to CFM 2.1.5 SP1

  • Oct 5, 2026 8:43 AM UTC
  • 0 replies
  • 1138 views
  • Translate All

After upgrading to CFM 2.1.5 SP1from an older version, PublishKafkaRecord_1_0 stops working with the below error:

 

PublishKafka_1_0[id=36f1cffe-503d-3181-a562-ae216b5616b5] Processing halted: yielding
[1 sec] java.lang.IllegalArgumentException: SaslMechanism value [null] not found at
org.apache.nifi.kafka.shared.property.SaslMechanism.lambda$getSaslMechanism$1
(SaslMechanism.java:57) at java.base/java.util.Optional.orElseThrow(Optional.java:408)
at org.apache.nifi.kafka.shared.property.SaslMechanism.getSaslMechanism(SaslMechanism.
java:57) at org.apache.nifi.kafka.shared.login.DelegatingLoginConfigProvider.
getConfiguration(DelegatingLoginConfigProvider.java:51) at org.apache.nifi.kafka.
shared.property.provider.StandardKafkaPropertyProvider.setSecurityProperties
(StandardKafkaPropertyProvider.java:86) at org.apache.nifi.kafka.shared.property.
provider.StandardKafkaPropertyProvider.getProperties(StandardKafkaPropertyProvider.
java:75)

This happens due an improvement performed in NIFI-10866.

 

Resolution

You can switch to newer PublishKafkaRecord processor like PublishKafkaRecord_2_0 or PublishKafkaRecord_2_6, both of which successfully eliminate the issue and also provide newer features as compared to the older 1_0 processor.

 

    Terms & ConditionsAccessibility statement