hibernate/hibernate-orm · error · HibernateException

Not all named supertypes (extends) were found : <toBeLinkedQ

Error message

Not all named supertypes (extends) were found : <toBeLinkedQueue.keySet()>

What it means

Error "Not all named supertypes (extends) were found : <toBeLinkedQueue.keySet()>" thrown in hibernate/hibernate-orm.

Source

Thrown at hibernate-core/src/main/java/org/hibernate/boot/model/source/internal/hbm/EntityHierarchyBuilder.java:70

	 *
	 * @return The built hierarchies
	 *
	 * @throws HibernateException Indicates subclass mappings still waiting to be linked to their super types
	 */
	public List<EntityHierarchySourceImpl> buildHierarchies() throws HibernateException {
		if ( toBeLinkedQueue != null && !toBeLinkedQueue.isEmpty() ) {
			if ( BOOT_LOGGER.isDebugEnabled() ) {
				for ( var waitingListEntry : toBeLinkedQueue.entrySet() ) {
					for ( var waitingEntry : waitingListEntry.getValue() ) {
						BOOT_LOGGER.entitySupertypeExtendsNotFound(
								waitingListEntry.getKey(),
								waitingEntry.sourceMappingDocument.getOrigin(),
								waitingEntry.sourceMappingDocument.determineEntityName( waitingEntry.jaxbSubEntityMapping )
						);
					}
				}
			}
			throw new HibernateException(
					"Not all named supertypes (extends) were found : " + toBeLinkedQueue.keySet()
			);
		}

		return entityHierarchyList;
	}

	/**
	 * Called for each mapping document.
	 *
	 * @param mappingDocument The {@code hbm.xml} document to index
	 */
	public void indexMappingDocument(MappingDocument mappingDocument) {
		BOOT_LOGGER.indexingMappingDocumentForHierarchyOrdering( String.valueOf( mappingDocument.getOrigin() ) );
		final var mappingBinding = mappingDocument.getDocumentRoot();

		// iterate all root class definitions at the hibernate-mapping level
		for ( var jaxbRootEntity : mappingBinding.getClazz() ) {

View on GitHub (pinned to fad1729dce)

Solutions

  1. Correct the extends attribute in the hbm.xml <subclass/>/<joined-subclass/> so it names an entity mapped earlier in the same or an already-processed document.

Example fix

Correct the extends attribute in the hbm.xml <subclass/>/<joined-subclass/> so it names an entity mapped earlier in the same or an already-processed document.

When it happens

Trigger: An hbm.xml / orm.xml mapping document violates a mapping rule during bootstrap.

Common situations: Legacy XML mappings with invalid combinations (column+formula, mixed inheritance, missing identifiers, bad extends references).


AI-assisted analysis of hibernate/hibernate-orm@fad1729dce (2026-08-22). Data as JSON: /api/errors/9ddc14633856512d. Report an issue: GitHub.