hibernate/hibernate-orm · error · ArchiveException
Error accessing nested jar
Error message
Error accessing nested jar
What it means
Thrown by JarInputStreamBasedArchiveDescriptor when reading entries from a nested jar InputStream fails with a ZipException or IOException.
Source
Thrown at hibernate-core/src/main/java/org/hibernate/boot/archive/internal/JarInputStreamBasedArchiveDescriptor.java:115
catch (URISyntaxException e) {
throw new ArchiveException(
String.format( Locale.ROOT,
"Unable to create archive entry URI: %s - %s",
archiveUrl,
jarEntry.getName()
),
e
);
}
finally {
subJarInputStream.close();
}
}
catch (ArchiveException e) {
throw e;
}
catch (Exception e) {
throw new ArchiveException( "Error accessing nested jar", e );
}
}
else {
try {
final String entryName = extractName( jarEntry );
final InputStreamAccess inputStreamAccess = buildByteBasedInputStreamAccess( entryName, jarInputStream );
final String relativeName = extractRelativeName( jarEntry );
entryConsumer.accept( new ArchiveEntryImpl(
relativeName,
relativeName,
new URI( archiveUrl + "!/" + relativeName ),
inputStreamAccess
) );
}
catch (URISyntaxException e) {
throw new ArchiveException(
String.format( Locale.ROOT,View on GitHub (pinned to fad1729dce)
Solutions
- Rebuild the outer archive so the nested jar is written completely.
- Test nested jars with 'unzip -t' after extracting them.
- Avoid shading/repackaging steps that corrupt nested jars.
Example fix
A nested jar (jar inside jar) could not be read. Nested archives are not supported for scanning; unpack the nested jar or move the classes to the top-level archive.
When it happens
Trigger: A jar embedded inside another jar is corrupt or truncated, so iterating its entries fails during scanning.
Common situations: Corrupt nested jar from a failed or partial assembly; repackaging tools that damaged inner jars.
AI-assisted analysis of hibernate/hibernate-orm@fad1729dce (2026-08-22).
Data as JSON: /api/errors/eea24d7f06999d5b.
Report an issue: GitHub.