# ByteBuffer and the Dreaded NoSuchMethodError

DevFeed: [ByteBuffer and the Dreaded NoSuchMethodError](<https://devfeed.tech/articles/bytebuffer-and-the-dreaded-nosuchmethoderror-18804.md>)

Original publisher: [Read original article](<https://www.morling.dev/blog/bytebuffer-and-the-dreaded-nosuchmethoderror/>)

Published: 2020-12-21T16:45:00Z

Content type: article

Language: en

Sources: [Gunnar Morling](<https://devfeed.tech/sources/gunnar-morling.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [Apache Pulsar](<https://devfeed.tech/topics/pulsar.md>), [Eclipse Vert.x](<https://devfeed.tech/topics/vertx.md>)

Tags: [apache](<https://devfeed.tech/tags/apache.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [debezium](<https://devfeed.tech/tags/debezium.md>), [issue](<https://devfeed.tech/tags/issue.md>), [java](<https://devfeed.tech/tags/java.md>), [java-9](<https://devfeed.tech/tags/java-9.md>)

## AI overview

This article explains why Java code compiled with JDK 9 or newer can trigger NoSuchMethodError when run on Java 8. Covariant return types cause the compiler to record a method signature that is unavailable in Java 8, creating a compatibility problem for projects that target older Java runtimes.

## Source excerpt

Table of Contents How to Prevent This Situation? The other day, a user in the Debezium community reported an interesting issue; They were using Debezium with Java 1.8 and got an odd NoSuchMethodError: