You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Rick Curtis (JIRA)" <ji...@apache.org> on 2010/06/15 22:45:22 UTC
[jira] Created: (OPENJPA-1701) Calling em.refresh(...) causes a
WARNING message to be logged
Calling em.refresh(...) causes a WARNING message to be logged
-------------------------------------------------------------
Key: OPENJPA-1701
URL: https://issues.apache.org/jira/browse/OPENJPA-1701
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.
[jira] Assigned: (OPENJPA-1701) Calling em.refresh(...) causes a
WARNING message to be logged
Posted by "Rick Curtis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis reassigned OPENJPA-1701:
------------------------------------
Assignee: Rick Curtis
> Calling em.refresh(...) causes a WARNING message to be logged
> -------------------------------------------------------------
>
> Key: OPENJPA-1701
> URL: https://issues.apache.org/jira/browse/OPENJPA-1701
> 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
> Assignee: Rick Curtis
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-1701) Calling em.refresh(...) causes a
WARNING message to be logged
Posted by "Rick Curtis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882317#action_12882317 ]
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: https://issues.apache.org/jira/browse/OPENJPA-1701
> 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.
[jira] Resolved: (OPENJPA-1701) Calling em.refresh(...) causes a
WARNING message to be logged
Posted by "Rick Curtis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis resolved OPENJPA-1701.
----------------------------------
Fix Version/s: 2.1.0
Resolution: Fixed
Committed revision 957709 to trunk.
> Calling em.refresh(...) causes a WARNING message to be logged
> -------------------------------------------------------------
>
> Key: OPENJPA-1701
> URL: https://issues.apache.org/jira/browse/OPENJPA-1701
> 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
> Assignee: Rick Curtis
> Fix For: 2.1.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.