Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-1048

Lock.obtain(timeout) behaves incorrectly for large timeouts

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.2
    • Fix Version/s: 2.3
    • Component/s: core/store
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      Because timeout is a long, but internal values derived from timeout
      are ints, its possible to overflow those internal values into negative
      numbers and cause incorrect behavior.

      Spinoff from this thread:

      http://www.gossamer-threads.com/lists/lucene/java-user/54376

        Attachments

          Activity

            People

            • Assignee:
              mikemccand Michael McCandless
              Reporter:
              mikemccand Michael McCandless

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment