OpenJPA
  1. OpenJPA
  2. OPENJPA-1701

Calling em.refresh(...) causes a WARNING message to be logged

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.0
    • Fix Version/s: 2.1.0
    • Component/s: jpa
    • Labels:
      None
    • Environment:

      Activity

      Rick Curtis created issue -
      Hide
      Rick Curtis added a comment -

      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.

      Show
      Rick Curtis added a comment - 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.
      Rick Curtis made changes -
      Field Original Value New Value
      Assignee Rick Curtis [ curtisr7 ]
      Hide
      Rick Curtis added a comment -

      Committed revision 957709 to trunk.

      Show
      Rick Curtis added a comment - Committed revision 957709 to trunk.
      Rick Curtis made changes -
      Status Open [ 1 ] Resolved [ 5 ]
      Fix Version/s 2.1.0 [ 12314542 ]
      Resolution Fixed [ 1 ]
      Hide
      Michael Dick added a comment -

      Closing issues which have been resolved for some time. If the problem persists, please reopen.

      Show
      Michael Dick added a comment - Closing issues which have been resolved for some time. If the problem persists, please reopen.
      Michael Dick made changes -
      Status Resolved [ 5 ] Closed [ 6 ]
      Transition Time In Source Status Execution Times Last Executer Last Execution Date
      Open Open Resolved Resolved
      8d 23h 59m 1 Rick Curtis 24/Jun/10 21:44
      Resolved Resolved Closed Closed
      87d 18h 55m 1 Michael Dick 20/Sep/10 16:39

        People

        • Assignee:
          Rick Curtis
          Reporter:
          Rick Curtis
        • Votes:
          0 Vote for this issue
          Watchers:
          0 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development