Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11037

Intermittent Agroal warnings during startup

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 15.0.0.Beta1, 15.0.0.Final
    • 14.0.0.Final
    • Agroal
    • None

    Description

      Sometimes during startup, Agroal spams the log with this:

      2018-09-18 10:35:46,226 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state CHECKED_IN
2018-09-18 10:35:46,226 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,226 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,227 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,227 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,227 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,227 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,228 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,228 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,228 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,228 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,229 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,229 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,229 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,229 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,229 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,229 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,230 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,230 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,230 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,230 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,230 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,230 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,231 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,232 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED
2018-09-18 10:35:46,233 WARN  [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED

      I'm not sure why, and it doesn't always happen.

      My pool configuration is:

      <connection-pool max-size="${database.maxPool:20}" background-validation="30000" idle-removal="30"/>

      But this also occurs when background-validation and idle-removal are omitted.

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. AG-94 "Closing connection in incorrect state" log spam

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              rdicroce Richard DiCroce (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: