Home/ Questions/Q 8161031
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T18:24:41+00:00

After adding a second persistence unit and changing my application’s data sources to XADataSource

  • 0

After adding a second persistence unit and changing my application’s data sources to XADataSource (MySQL), I’m now getting a confusing warning in the glassfish log about isolation levels on my parent entity:

WARN  o.e.p.s.f.j.ejb_or_metadata : Parent Entity BaseEntity has an isolation
level of: PROTECTED which is more protective then the subclass Contact with
isolation: null so the subclass has been set to the isolation level PROTECTED.

After some research, I think that this isolation level warning message is coming from EclipseLink’s caching mechanism. But I am not specifying an isolation level anywhere in my app, so it appears that something in my configuration has triggered the BaseEntity class to have an isolation level of ‘PROTECTED’. The documentation is silent on what might cause it to be automatically assigned to that level — see user guide.

Minor testing with a single user has shown that the application seems to work as expected, but this warning message doesn’t make me feel comfortable rolling it out to the masses.

Can anyone shed some light into this message? Are my concerns valid?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    After some research, I discovered that this warning had nothing to do with using the XADataSource. I had earlier began some exploration into EclipseLink’s Multitenancy, and it turned out that this was the culprit.

    Referring to http://wiki.eclipse.org/EclipseLink/Examples/JPA/Multitenant#Persistence_Usage_for_Multiple_Tenants:

    When using this architecture there is a shared cache available for regular entity types but the Multitenant types must be PROTECTED in the cache so the MULTITENANT_SHARED_EMF property must be set to true.

    FYI — In reviewing the code, there are 3 other cases in ClassDescriptor.initializeCaching() in which the cache isolation is downgraded to PROTECTED:

    1. If the entity has a DatabaseMapping marking it as non-cacheable.
    2. If the entity has a ForeignReferenceMapping that doesn’t have an isolation level of shared.
    3. If the entity has a AggregateObjectMapping that doesn’t have an isolation level of shared.
    • 0