Prevent new SpecificPools after ConnectionPool::shutdown()

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Networking
    • Server Programmability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As is, the ConnectionPool is more than happy to make a new pool after its shutdown method. shutdown() itself just fails the existing pools. We should probably not do that.

            Assignee:
            Unassigned
            Reporter:
            Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: