Skip to content
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.

Sign up for GitHub

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

Jump to bottom

5.5.10 unable to run on Java 8 #3767

Closed
thomasbigger584 opened this issue Apr 5, 2022 · 1 comment
Closed

5.5.10 unable to run on Java 8 #3767

thomasbigger584 opened this issue Apr 5, 2022 · 1 comment
Labels
status: duplicate There is already an issue similar to this. The link to it should be present

Comments

@thomasbigger584
Copy link

In what version(s) of Spring Integration are you seeing this issue?

5.5.10

Describe the bug

We upgraded a minor version from 5.5.9 to 5.5.10 and now getting an error running on Java 8 due to List.of in class org.springframework.integration.support.json.JacksonJsonUtils introduced in Java 9. This should be at least a major upgrade as it affects those only able to run on Java 8.

IntegrationTest > testKafkaConsumer() FAILED
    java.lang.IllegalStateException at DefaultCacheAwareContextLoaderDelegate.java:132
        Caused by: org.springframework.beans.factory.BeanCreationException at ConstructorResolver.java:658
            Caused by: org.springframework.beans.BeanInstantiationException at SimpleInstantiationStrategy.java:185
                Caused by: java.lang.NoSuchMethodError at JacksonJsonUtils.java:58

To Reproduce

Create an integration flow with kafka and run it with java 8.

Expected behavior

I expect this to run on Java 8.
@thomasbigger584 thomasbigger584 added status: waiting-for-triage The issue need to be evaluated and its future decided type: bug labels Apr 5, 2022
@artembilan
Copy link
Member

A duplication of #3761

@artembilan artembilan added status: duplicate There is already an issue similar to this. The link to it should be present and removed type: bug status: waiting-for-triage The issue need to be evaluated and its future decided labels Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: duplicate There is already an issue similar to this. The link to it should be present
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@artembilan @thomasbigger584