Hi Andreas,
I assume you have more than one persistence context. In this case you have
to add the @PersistenceContext annotation to your onSuccess() method.
Otherwise the system doesn't know which persistence context it should use.
(The related code is in JpaInternalUtils.getEntityManager() and
In my opinion, soft referencing page objects is highly appropriate usage
here. If there's pressure on the available memory, it makes sense to trade
performance for memory instead of exiting with OoM. This is simple
condition to detect and should be visible with any reasonable monitoring
tool. If yo
Possibly we need something more advanced; our own reference type that can
react to memory pressure by discarding pages that haven't been used in
configurable amount of time.
Or perhaps we could just assume that any page that has been used once need
to be used in the future and get rid of the SoftR
Hi,
i got a ejb with two entities.
All is working fine, but if i persist the entity, it got this error:
Unable to locate a single EntityManager. You must provide the
persistence unit name as defined in the persistence.xml using the
@PersistenceContext annotation.
@Inject
@PersistenceCo
Hello,
I recently came accross the implementation of PageSourceImpl where
PageImpl instances are softly refereneced into the pageCache:
private final Map> pageCache =
CollectionFactory.newConcurrentMap();
This implementation caused troubles, when you bring your system into
memory preassure
