That said, it may not sound right to even do that. I cannot inquire the brand new builders as to why it had been done so means, they’re not here any longer. This project’s story are only able to learn the help of its Git records.
I suspect our company is having fun with Spring Research Others completely wrong, improperly blend WebMVC basics. Whenever we hadn’t done this right away, some thing might have work at much convenient. We are now through with brand new Spring season Research Rest migration. It is time to disperse to our very own next Springtime component, Spring season Kafka. Springtime Kafka, or in other words Spring getting Apache Kafka , is a superb cure for play with Kafka on your own Springtime ideas. It provides easy-to-play with layouts for giving texts and you can normal Spring annotations to have sipping messages.Spring season Kafka
Configuring the new consumers
step step 1 [ERROR] coffees.lang.IllegalStateException: Didn't weight ApplicationContext 2 step three As a result of: org.springframework.kidney beans.warehouse.BeanCreationException: Error creating bean having name 'consumerFactory' discussed in classification road financial support [ de / software / config / KafkaConsumerConfig . class ]: cuatro 5 Caused by: java . lang . NullPointerException 6 at java . ft / java . util . concurrent . ConcurrentHashMap . putVal ( ConcurrentHashMap . java: 1011 ) seven at java . base / java . kissbrides.com me gusta util . concurrent . ConcurrentHashMap . init >( ConcurrentHashMap . java: 852 ) 8 at org . springframework . kafka . center . DefaultKafkaConsumerFactory . init >( DefaultKafkaConsumerFactory . java: 125 ) 9 at org . springframework . kafka . core . DefaultKafkaConsumerFactory . init >( DefaultKafkaConsumerFactory . java: 98 ) 10 at de . app . config . KafkaConsumerConfig . consumerFactory ( AbstractKafkaConsumerConfig . java: 120 )
It turns out, we had been configuring the consumerConfigs bean and setting null values in its properties. The following change from HashMap to ConcurrentHashMap means we can no longer configure null values. We refactored our code and now tests are green. Easy-peasy.
Kafka texts with JsonFilter
1 [ERROR] org .apache .kafka mon .mistakes .SerializationException : Can also be 't serialize analysis [Skills [payload=MyClass(Id=201000000041600097, . ] getting point [my-topic] 2 3 Because of: com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Never take care of PropertyFilter with id ‘myclassFilter' ; zero FilterProvider configured (compliment of site chain: de- .take to .Feel [ "payload" ] ) 4 during the com .fasterxml .jackson .databind .exc .InvalidDefinitionException .regarding (InvalidDefinitionException .java : 77 )
Some of our Java Beans use ato manipulate the serialization and deserialization. This requires a propertyFilter to be configured on the ObjectMapper.
Spring for Apache Kafka made a change to the JsonSerializer , introducing an ObjectWriter . When the ObjectWriter instance is created, the ObjectMapper configuration is copied, not referenced. Our test case was re-configuring the ObjectMapper with the appropriate propertyFilter after the ObjectWriter instance was created. Hence, the ObjectWriter didn't know anything about the propertyFilter (since the configuration was already copied). After some refactoring, changing how we create and configure the JsonSerializer , our test cases were green.
Running our build $ mvn clean verify finally resulted in a green build. Everything is working as it should. We pushed our changes to Bitbucket and everything built like a charm.
Training learned updating Spring Kafka
Courses learned through the Spring season Boot enhance
Spring and Spring Boot do a great job documenting their releases, their release notes are well maintained. That being said, upgrading was challenging, it took quite a while before everything was working again. A big part of that is on us, for not following best practices, guidelines, etc. A lot of this code was written when the team was just starting out with Spring and Spring Boot. Code evolves over time, without refactoring and applying those latest practices. Eventually that catches up with you, but we use this as a learning experience and improved things. Our test cases are now significantly better, and we'll keep a closer eye on them moving forward.