openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <>
Subject [jira] Commented: (OPENJPA-1701) Calling em.refresh(...) causes a WARNING message to be logged
Date Thu, 24 Jun 2010 20:38:49 GMT


Rick Curtis commented on OPENJPA-1701:

I found in my testing that if I call em.refresh() and <CacheRetrieveMode> is unspecified,
or is set to USE the warning message is logged. In an application that calls em.refresh often
this would flood their logs with useless messages. I mulled over the idea of changing the
message from a WARNING to TRACE, but even as a developer I don't think this message would
be of much use.

> Calling em.refresh(...) causes a WARNING message to be logged
> -------------------------------------------------------------
>                 Key: OPENJPA-1701
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 2.1.0
>         Environment: A nice 'feature' was added in revision 929744 which results in a
WARNING being logged [1] every time em.refresh(..) is called. It appears that in that revision
the default value for cacheRetrieveMode in FetchConfiguration was changed from NULL to USE.
> I haven't spent enough time looking at the code yet to figure out if the proper solution
is to remove the warning, or made the default NULL again.
> [1] WARN   [main] openjpa.Runtime - The setting of CacheRetrieveMode.USE is ignored and
set to BYPASS for refresh operation.
>            Reporter: Rick Curtis

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message