[
https://issues.apache.org/jira/browse/LOGGING-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Soloschenko updated LOGGING-200:
---------------------------------------
Description:
Currently there is an issue during GraalVM native image builds that causes the
following error:
{code:java}
[2/8] Performing analysis... [*****]
(155,9s @ 12,14GB)
83.337 types, 149.022 fields, and 537.059 methods found reachable
48.153 types, 51.963 fields, and 224.453 methods registered for reflection
182 types, 280 fields, and 149 methods registered for JNI access
0 downcalls and 0 upcalls registered for foreign access
4 native libraries: dl, pthread, rt, z
[3/8] Building universe...
(36,1s @ 12,13GB)
[4/8] Parsing methods... [****]
(14,8s @ 6,40GB)
[5/8] Inlining methods... [***]
(5,5s @ 7,09GB)
[6/8] Compiling methods... [*********]
(89,5s @ 10,64GB)
[7/8] Laying out methods... [*****]
(29,1s @ 11,45GB)
Error: Type not found during analysis:
HotSpotType<Lorg/apache/commons/logging/impl/Log4JLogger;, resolved>{code}
I was able to fix this by adding reflection and serialization hints for
org.apache.commons.logging.impl.Log4JLogger no matter if I was using
log4j-to-slf4j, so I assume the reflection hint has to be applied to
log4j-to-slf4j
Versions I use:
* Commons Logging 1.3.6
* Liberica NIK 25.0.2+1 with JDK 25.0.2+13
* Native Image Plugin 1.1.0 with Reachable Metadata Version 1.0.1
* Spring Boot 4.0.6
It only occurs if no commons-logging:commons-logging:1.3.6 is present in the
classpath.
was:
Currently there is an issue during GraalVM native image builds that causes the
following error:
{code:java}
[2/8] Performing analysis... [*****]
(155,9s @ 12,14GB)
83.337 types, 149.022 fields, and 537.059 methods found reachable
48.153 types, 51.963 fields, and 224.453 methods registered for reflection
182 types, 280 fields, and 149 methods registered for JNI access
0 downcalls and 0 upcalls registered for foreign access
4 native libraries: dl, pthread, rt, z
[3/8] Building universe...
(36,1s @ 12,13GB)
[4/8] Parsing methods... [****]
(14,8s @ 6,40GB)
[5/8] Inlining methods... [***]
(5,5s @ 7,09GB)
[6/8] Compiling methods... [*********]
(89,5s @ 10,64GB)
[7/8] Laying out methods... [*****]
(29,1s @ 11,45GB)Error: Type not found during analysis:
HotSpotType<Lorg/apache/commons/logging/impl/Log4JLogger;, resolved>{code}
I was able to fix this by adding reflection and serialization hints for
org.apache.commons.logging.impl.Log4JLogger no matter if I was using
log4j-to-slf4j, so I assume the reflection hint has to be applied to
log4j-to-slf4j
Versions I use:
* Commons Logging 1.3.6
* Liberica NIK 25.0.2+1 with JDK 25.0.2+13
* Native Image Plugin 1.1.0 with Reachable Metadata Version 1.0.1
* Spring Boot 4.0.6
It only occurs if no commons-logging:commons-logging:1.3.6 is present in the
classpath.
> Type not found during analysis: HotSpotType during GraalVM native image build
> -----------------------------------------------------------------------------
>
> Key: LOGGING-200
> URL: https://issues.apache.org/jira/browse/LOGGING-200
> Project: Commons Logging
> Issue Type: Bug
> Affects Versions: 1.3.6
> Reporter: Tobias Soloschenko
> Priority: Minor
>
> Currently there is an issue during GraalVM native image builds that causes
> the following error:
> {code:java}
> [2/8] Performing analysis... [*****]
> (155,9s @ 12,14GB)
> 83.337 types, 149.022 fields, and 537.059 methods found reachable
> 48.153 types, 51.963 fields, and 224.453 methods registered for reflection
> 182 types, 280 fields, and 149 methods registered for JNI access
> 0 downcalls and 0 upcalls registered for foreign access
> 4 native libraries: dl, pthread, rt, z
> [3/8] Building universe...
> (36,1s @ 12,13GB)
> [4/8] Parsing methods... [****]
> (14,8s @ 6,40GB)
> [5/8] Inlining methods... [***]
> (5,5s @ 7,09GB)
> [6/8] Compiling methods... [*********]
> (89,5s @ 10,64GB)
> [7/8] Laying out methods... [*****]
> (29,1s @ 11,45GB)
> Error: Type not found during analysis:
> HotSpotType<Lorg/apache/commons/logging/impl/Log4JLogger;, resolved>{code}
>
> I was able to fix this by adding reflection and serialization hints for
> org.apache.commons.logging.impl.Log4JLogger no matter if I was using
> log4j-to-slf4j, so I assume the reflection hint has to be applied to
> log4j-to-slf4j
>
> Versions I use:
> * Commons Logging 1.3.6
> * Liberica NIK 25.0.2+1 with JDK 25.0.2+13
> * Native Image Plugin 1.1.0 with Reachable Metadata Version 1.0.1
> * Spring Boot 4.0.6
> It only occurs if no commons-logging:commons-logging:1.3.6 is present in the
> classpath.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
