registry-cli | easy manipulation of docker-registry from command line | Continuous Deployment library

Acording to this answer: https://stackoverflow.com/a/51236918/16651073 tomcat falls back to default logging if it can resolve the location

Can you try to save the properties without the spaces.

Like this: logging.file.name=application.logs

Your code works for me(even with wrong values-at least doesn't terminate). Please use logback in your code and keep logger level to DEBUG. This way you will be able to observe carefully what is happening when your kafka streams is launching. Probably kafka thread is terminating due to some reason which we can't just guess like that.

PS: Sorry I don't have reputation to add a comment.

You're publishing to your local Maven cache, but sbt uses Ivy.

Try removing the publishTo setting, it shouldn't be needed. Just use the publishLocal task to publish to your local Ivy cache.

The firewall in the cloud was blocking the requests. For some reason they were classified not as http, but as confluent requests, which the firewall did not knew about and therefore were blocking. The aimed at a "confluent" app within the k8s. I don't know where this app comes from, but ... Enabling those requests solved the issue.

I faced a similar issue. You may or may not have two installations of Node.js.

• First try cleaning the cache by running npm cache clean
• If the previous suggestion doesn't solve your issue then you probably have two versions installed. I'd suggest you to delete the npm in AppData, uninstall both versions of Node.js, and install the latest versions.

By excluding spring-boot-starter-web you did exclude all its dependencies, which are necessary to run a Spring Boot project in a servlet environment. Most notably you did exclude spring-web, which contains most of the classes you find in the error messages.

As its name suggests spring-boot-starter-web isn't centered around Tomcat, only its dependency spring-boot-starter-tomcat is. So you should exclude the latter artifact and include spring-boot-starter-undertow to pull the necessary Undertow dependencies into the project:

Ok so, for me what worked was a rebuild of the project in Intellij.

Boot 2.3 uses spring-kafka 2.5 by default (and kafka-clients 2.5.0); since you have overridden its prescribed spring-kafka version to 2.6.5, you must override all of the kafka dependencies to match

kafka-clients 2.6.1, kafka-streams 2.6.1 (if you are using them).

If you are using the embedded Kafka broker in tests, there are a bunch of other jars you need. See https://docs.spring.io/spring-kafka/docs/current/reference/html/#update-deps

2.6.x is used by Boot 2.4 and will bring in all the right versions.

Confluent 5.4 uses Kafka 2.4.

You should use the version of confluent that matches Spring Boot's prescribed versions of spring-kafka, kafka-clients.

If you use Boot 2.4.x, use confluent 6.0.

https://docs.confluent.io/platform/current/installation/versions-interoperability.html

I see this in your config: spring.cloud.stream.kafka.streams.binder.configuration.default.key.serde. That is the default key Serde. Did you mean to use it as value.serde. Then, that needs to be changed.

With that said, you can set the Serde on the individual binding as well (which has higher precedence).

You can also define a bean of type RetrySpecificAvroSerde in your applications, if your Kafka Streams function is strongly typed (i.e. KStream generic arguments are using the correct type). This method has the highest precedence in the binder.

After correcting it, if it still fails, please share with us a small sample, then we can take a look.