Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Java 21 breaks access to netty-buffer class

未关闭
#1,106 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
java
领域
backend, data-engineering

调研方向

首先，在 Java 21 上启动 Arrow Flight 服务器时重现该故障，然后检查堆栈跟踪中识别出的 PooledByteBufAllocatorL 和 NettyAllocationManager。将相关的访问行为与 Java 17 进行比较；当不再发生 IllegalAccessError 且服务器成功启动时，即表示完成。

由索引模型根据 Issue 内容生成。

描述

Type: bug
Describe the bug, including details regarding any error messages, version, and platform.

When trying to start an Arrow Flight server use is made of class io.netty.buffer.PoolArena in netty-buffer that is no longer accessible in java 21 from class io.netty.buffer.PooledByteBufAllocatorL in arrow-memory-netty-buffer-patch-19.0.0.jar.
I think this might be caused by Java 21 being more restrictive than 17.

Stack trace ```java Exception in thread "main" java.lang.IllegalAccessError: failed to access class io.netty.buffer.PoolArena from class io.netty.buffer.PooledByteBufAllocatorL$InnerAllocator (io.netty.buffer.PoolArena is in unnamed module of loader 'app'; io.netty.buffer.PooledByteBufAllocatorL$InnerAllocator is in unnamed module of loader org.apache.hop.core.plugins.HopURLClassLoader @26612078) at io.netty.buffer.PooledByteBufAllocatorL$InnerAllocator.(PooledByteBufAllocatorL.java:141) at io.netty.buffer.PooledByteBufAllocatorL.(PooledByteBufAllocatorL.java:46) at org.apache.arrow.memory.netty.NettyAllocationManager.(NettyAllocationManager.java:54) at org.apache.arrow.memory.netty.DefaultAllocationManagerFactory.(DefaultAllocationManagerFactory.java:26) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:423) at java.base/java.lang.Class.forName(Class.java:414) at org.apache.arrow.memory.DefaultAllocationManagerOption.getFactory(DefaultAllocationManagerOption.java:105) at org.apache.arrow.memory.DefaultAllocationManagerOption.getDefaultAllocationManagerFactory(DefaultAllocationManagerOption.java:92) at org.apache.arrow.memory.BaseAllocator$Config.getAllocationManagerFactory(BaseAllocator.java:826) at org.apache.arrow.memory.ImmutableConfig.access$001(ImmutableConfig.java:20) at org.apache.arrow.memory.ImmutableConfig$InitShim.getAllocationManagerFactory(ImmutableConfig.java:80) at org.apache.arrow.memory.ImmutableConfig.(ImmutableConfig.java:43) at org.apache.arrow.memory.ImmutableConfig$Builder.build(ImmutableConfig.java:492) at org.apache.arrow.memory.BaseAllocator.(BaseAllocator.java:72) at org.apache.hop.arrow.flight.ArrowFlightServer.(ArrowFlightServer.java:59) at org.apache.hop.arrow.command.ArrowCommand.run(ArrowCommand.java:108) at picocli.CommandLine.executeUserObject(CommandLine.java:2045) at picocli.CommandLine.access$1500(CommandLine.java:148) at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2469) at picocli.CommandLine$RunLast.handle(CommandLine.java:2461) at picocli.CommandLine$RunLast.handle(CommandLine.java:2423) at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277) at picocli.CommandLine$RunLast.execute(CommandLine.java:2425) at picocli.CommandLine.execute(CommandLine.java:2174) at org.apache.hop.hop.Hop.main(Hop.java:131) 
</details>
主要语言
Java
星标
95
派生
154
平均合并
2 天 10 小时
30 天内合并 PR
11

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

apache/arrow-java 的其他 Issue

查看 apache/arrow-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。