-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception when configuring AsyncApiDocket with Producer and Consumers with the same topic name #136
Comments
I think the Problem is the TreeSet that is used to merge the messages of multiple operations. TreeSet requires all elements to implement Comparable if no Comparator is given:
From https://docs.oracle.com/javase/7/docs/api/java/util/TreeSet.html#TreeSet() Unfortunately TreeSet does not enforce implementing the interface and Message does not implement comparable. |
I just came across the same issue and resolved it in #137 Checks are still running at this point... However, I am not sure how to continue with the (message) sorting. @sam0r040 suggested to only do the sorting when items are returned to the ui. Maybe let the objectMapper do the sorting for us? |
Fix is released with springwolf-kafka:0.10.3 (including springwolf-core fix) |
When I try and use
|
Good question, havent seen this error before. |
@timonback I'm a maven newbie, but I think I've managed to somewhat circle what the issue is, I'll need your knowledge to connect the dots. Upon checking the debug output when I do I went to go check and found that Again, a newbie here, but perhaps the solution will is to fix the release by adding a simple .jar file without the classifier? for your reference, this is the highlight of my pom.xml:
|
Thank you for the detective work here! When looking at the maven artifact, there was an (unexpected) change of artifact naming, namely the I assume it is related to the spring update in springwolf. Possible fix in springwolf is mentioned in https://stackoverflow.com/questions/67663728/spring-boot-2-5-0-generates-plain-jar-file-can-i-remove-it#67752182 but I'll have to come back to it. |
Regression of the spring boot update released in springwolf 0.10.3 Current artifact name: springwolf-kafka-0.10.3-plain.jar Should be (previous behaviour): springwolf-kafka-0.10.3.jar Relates to: springwolf#136
Regression of the spring boot update released in springwolf 0.10.3 Current artifact name: springwolf-kafka-0.10.3-plain.jar Should be (previous behaviour): springwolf-kafka-0.10.3.jar Relates to: #136
With the fix in #152, this is resolved. At least, the latest SNAPSHOT build does not contain the Are you able to verify it with maven using version Maven Snapshot Repo: https://s01.oss.sonatype.org/content/repositories/snapshots/io/github/springwolf/springwolf-kafka/0.10.3-SNAPSHOT/ |
@timonback I'm getting the following error when trying to use KafkaConsumerData
|
Hi @AhmedNSidd,
I assume that you are running an older java version. Since you get this message, the previous issue is resolved, right? |
@timonback Yup, issue is resolved. I'm not getting the error anymore, and the UI looks majestic. Feel free to close the issue now. Thanks for your help. |
Describe the bug
An exception occurs if you try to document both a Kafka Consumer and Producer with the same topic name in the AsyncApiDocket configuration bean
Dependencies and versions used
Code example
Configuring using AsyncApiDocket with simple configurations and a producer and a consumer with the same topic name should replicate the error.
Stack trace and error logs
The text was updated successfully, but these errors were encountered: