Uploaded image for project: 'Hibernate ORM'
  1. HHH-12392

Caching SchemaResolver delegate with multiple data sources

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.2.14, 5.2.15
    • Fix Version/s: 5.2.16, 5.3.0.CR2, 5.1.14
    • Component/s: hibernate-core
    • Labels:
      None
    • Bug Testcase Reminder (view):

      Bug reports should generally be accompanied by a test case!

    • Worked in:
    • backPortable:
      Backport?
    • Last commented by a user?:
      true
    • Sprint:

      Description

      With multiple data sources, when the first data source to be loaded has a Java 1.7-compatible driver, the SchemaNameResolverJava17Delegate is chosen and cached. If another data source has a driver is not Java 1.7-compatible, the cached resolver is still used, and fails with an AbstractMethodError.

      There is a workaround to set hibernate.schema_name_resolver to SchemaNameResolverFallbackDelegate.

        Attachments

          Issue links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: