You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Kevin Sutter (JIRA)" <ji...@apache.org> on 2010/02/17 23:39:27 UTC
[jira] Created: (OPENJPA-1518) Remove WARN messages for uncacheable
finder select statements
Remove WARN messages for uncacheable finder select statements
-------------------------------------------------------------
Key: OPENJPA-1518
URL: https://issues.apache.org/jira/browse/OPENJPA-1518
Project: OpenJPA
Issue Type: Bug
Components: jdbc
Affects Versions: 2.0.0-beta
Reporter: Kevin Sutter
Assignee: Pinaki Poddar
Fix For: 2.0.0
http://n2.nabble.com/2-0-0-Beta-Caching-Question-td4588375.html#a4588375
>From the description in this forum post, it looks like we are logging a WARN message every time we determine that a finder select statement can't be cached (for whatever reason).
Two things...
o This message should probably not be a WARN message. It's a TRACE message, at best. We attempt to cache whenever we can, but if we can't cache something for whatever reason, customers don't want to see these WARN messages. But, if we're trying to debug a caching situation, then having the TRACE message might prove useful.
o I looked (very) briefly at the code and it's not clear as to why this particular finder can't be cached. Some additional data in the TRACE message may help with making the finder cacheable. Or, at least help explain why it's not cacheable.
Since Pinaki seems to have integrated these caching messages, I figured he would be a good initial assignee for the JIRA... :-)
Thanks,
Kevin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-1518) Remove WARN messages for
uncacheable finder select statements
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods resolved OPENJPA-1518.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0.0)
2.0.0-beta2
Fixed by r911496 that was committed using OPENJPA-924
> Remove WARN messages for uncacheable finder select statements
> -------------------------------------------------------------
>
> Key: OPENJPA-1518
> URL: https://issues.apache.org/jira/browse/OPENJPA-1518
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.0.0-beta
> Reporter: Kevin Sutter
> Assignee: Pinaki Poddar
> Fix For: 2.0.0-beta2
>
>
> http://n2.nabble.com/2-0-0-Beta-Caching-Question-td4588375.html#a4588375
> From the description in this forum post, it looks like we are logging a WARN message every time we determine that a finder select statement can't be cached (for whatever reason).
> Two things...
> o This message should probably not be a WARN message. It's a TRACE message, at best. We attempt to cache whenever we can, but if we can't cache something for whatever reason, customers don't want to see these WARN messages. But, if we're trying to debug a caching situation, then having the TRACE message might prove useful.
> o I looked (very) briefly at the code and it's not clear as to why this particular finder can't be cached. Some additional data in the TRACE message may help with making the finder cacheable. Or, at least help explain why it's not cacheable.
> Since Pinaki seems to have integrated these caching messages, I figured he would be a good initial assignee for the JIRA... :-)
> Thanks,
> Kevin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.