[
https://issues.apache.org/jira/browse/CAMEL-23670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18097709#comment-18097709
]
Omar Atie commented on CAMEL-23670:
-----------------------------------
```
h4. Analysis: root cause is the HotSpot JVM on ppc64le, not the Camel components
I investigated the three reported failures. They are all the same JVM-level
error —
{\{java.lang.IncompatibleClassChangeError: Class X does not implement the
requested interface Y}}
— raised at runtime during interface method dispatch (invokeinterface), even
though the
class does implement the interface (via inheritance / Scala traits). This is a
symptom of
incorrect interface/itable resolution inside the JVM, not an application defect.
The three failures are in completely unrelated technology stacks:
* camel-dfdl: \{{LocalSequence does not implement ElementDeclMixin}} — both are
Daffodil-internal Scala classes (\{{org.apache.daffodil.core.dsom.*}}). Camel
does not
reference these classes at all; the error occurs entirely within Daffodil's
own class
hierarchy while parsing a DFDL schema.
* camel-endpointdsl: \{{EndpointRoutesConfigurationTest$2 does not implement
OnCamelContextStopping}}
— the anonymous class genuinely does not implement that SPI interface, yet
the JVM dispatches
as if it must.
* camel-jooq: \{{SelectImpl does not implement StreamCache}} — a jOOQ query
class vs a Camel SPI.
The same error type appearing across three unrelated libraries (Daffodil/Scala,
Camel core,
jOOQ) points to the JVM as the common factor rather than any single component.
The decisive evidence is already in this ticket:
* Fails on Temurin *HotSpot* 26.0.1, 27-beta and 28-beta — all on *ppc64le*.
* Passes on IBM Semeru *OpenJ9* 26.0.1 — same Java version, same ppc64le
architecture,
different JVM implementation.
Same architecture + same Java version, differing only by JVM → the variable is
HotSpot on
ppc64le (in these EA/beta builds). This indicates a HotSpot defect on ppc64le,
not a Camel
regression. Camel behaves correctly and even passes on OpenJ9 on the same
platform.
Recommendation: there is no Camel code change to make here. Suggested path is
to treat this
as an upstream OpenJDK/ppc64le issue and keep this ticket open pending a fixed
HotSpot build,
optionally adding a narrow ppc64le test-skip for these modules if CI needs to
be green in the
interim (there is precedent via the ppc64le profile added under CAMEL-23538).
_This comment was generated by an AI agent (Cursor Agent, Opus 4.8) on behalf
of Omar Atie (@atiaomar1978-hub) and may contain inaccuracies; please verify
before acting._
```
> [JDK26] Several IncompatibleClassChangeError on ppc64le
> -------------------------------------------------------
>
> Key: CAMEL-23670
> URL: https://issues.apache.org/jira/browse/CAMEL-23670
> Project: Camel
> Issue Type: Sub-task
> Components: camel-dfdl, camel-endpointdsl, camel-jooq, camel-smooks
> Affects Versions: 4.20.0
> Reporter: Aurélien Pupier
> Priority: Major
>
> Class org.apache.daffodil.core.dsom.LocalSequence does not implement the
> requested interface org.apache.daffodil.core.dsom.ElementDeclMixin
> Class org.apache.camel.builder.endpoint.EndpointRoutesConfigurationTest$2
> does not implement the requested interface
> org.apache.camel.spi.OnCamelContextStopping
> java.lang.IncompatibleClassChangeError: Class org.jooq.impl.SelectImpl does
> not implement the requested interface org.apache.camel.StreamCache
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
