Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-29597

Remove Kafka AdminClient warn when using SSL

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 11.2
    • Fix Version/s: 11.x
    • Component/s: Streams

      Description

      When using ssl like:

          <kafkaConfig name="default" topicPrefix="nuxeo-">
            <producer>
              <property name="bootstrap.servers">...</property>
              <property name="default.replication.factor">1</property>
              <property name="delivery.timeout.ms">120000</property>
              <property name="acks">1</property>
              <property name="security.protocol">SSL</property>
              <property name="ssl.truststore.type">JKS</property>
              <property name="ssl.truststore.location">/etc/.../kafka.client.truststore.jks</property>
              <property name="ssl.truststore.password">...</property>
            </producer>
      

      Everything works but we have the following warns in the server.log:

      2020-08-28T10:19:03,299 WARN  [main] [org.apache.kafka.clients.admin.AdminClientConfig] The configuration 'ssl.truststore.location' was supplied but isn't a known config.
      2020-08-28T10:19:03,301 WARN  [main] [org.apache.kafka.clients.admin.AdminClientConfig] The configuration 'ssl.truststore.password' was supplied but isn't a known config.
      2020-08-28T10:19:03,301 WARN  [main] [org.apache.kafka.clients.admin.AdminClientConfig] The configuration 'ssl.truststore.type' was supplied but isn't a known config.
      

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.