Uploaded image for project: 'Commons Pool'
  1. Commons Pool
  2. POOL-300

Abandoned object stack traces may not be written

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.0, 2.1, 2.2, 2.3, 2.4.1
    • 2.4.2
    • None

    Description

      When writing stack traces for abandoned object tracking, DefaultPooledObject does not flush the Printwriter. The default Printwriter in AbandonedConfig is System.out without autoflush enabled. This means that stack traces may not be effectively logged (if there is just one, for example).

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            psteitz Phil Steitz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment