OFBiz
  1. OFBiz
  2. OFBIZ-3646

Change log level on never-cache related messages from "warn" to "info"

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Not a Problem
    • Affects Version/s: SVN trunk
    • Fix Version/s: SVN trunk
    • Component/s: framework
    • Labels:
      None

      Description

      When you use caching there are a number of warning messages that are produced indicating that various entity instances will not be cached (because the entity is configured not to cache). Changing these from "warn" to "info" which better reflects what they are and reduces warn threshold log noise.

        Activity

        Hide
        Bob Morley added a comment -

        I guess I would think that there is no potential mistake here. As the application developer you likely always want to fetch from cache (if you are not updating); if that item will never be from the cache (because it is non-cachable) or if the entity just happens not to be in the cache for that request, there isn't much difference. I would not expect the application developer to look at each entity and set the "cache query" appropriately, only to have the underlying entity change and be forced to find all of those queries and change them to be cachable.

        Show
        Bob Morley added a comment - I guess I would think that there is no potential mistake here. As the application developer you likely always want to fetch from cache (if you are not updating); if that item will never be from the cache (because it is non-cachable) or if the entity just happens not to be in the cache for that request, there isn't much difference. I would not expect the application developer to look at each entity and set the "cache query" appropriately, only to have the underlying entity change and be forced to find all of those queries and change them to be cachable.
        Hide
        Scott Gray added a comment -

        I'm not sure, I'm guessing it's logged as a warning because you may be expecting the value to cache but it isn't going to happen. Warnings are about logging potential mistakes that don't actually result in an error. Why not just not use the cache when you shouldn't be?

        Show
        Scott Gray added a comment - I'm not sure, I'm guessing it's logged as a warning because you may be expecting the value to cache but it isn't going to happen. Warnings are about logging potential mistakes that don't actually result in an error. Why not just not use the cache when you shouldn't be?
        Hide
        Bob Morley added a comment -

        Three minor changes and removal of one not used import.

        Show
        Bob Morley added a comment - Three minor changes and removal of one not used import.

          People

          • Assignee:
            Unassigned
            Reporter:
            Bob Morley
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development