Uploaded image for project: 'z - Hibernate 2'
  1. HB-1285

Would it be possible to stop logging StaleObjectStateException at ERROR

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Trivial
    • Resolution: Duplicate
    • Affects Version/s: 2.1.4
    • Fix Version/s: None
    • Component/s: core
    • Labels:
      None
    • Last commented by a user?:
      true

      Description

      Would it be possible to stop logging StaleObjectStateException at the error level - maybe use warning instead? Whilst StaleObjectStateExceptions are not recoverable, they occur during normal usage, and end up cluttering log files.

      Here's an example from one of our logs:

      2004-10-19 12:19:49,718 [RMI TCP Connection(4)-192.168.128.102] ERROR net.sf.hibernate.impl.SessionImpl: Could not synchronize database state with session
      net.sf.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) for com.illumining.client.domain.impl.DiscussionMessageImpl instance with identifier: 21
      at net.sf.hibernate.persister.AbstractEntityPersister.check(AbstractEntityPersister.java:501)
      at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:672)
      at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:642)
      at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:52)
      at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2414)
      at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2368)
      at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2236)

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              andy AndyA
              Participants:
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: