Debugging output of connections with unexpected data

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.5.5
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Sometimes our socket sanity checks detect sockets in the pool with remaining data - this should not happen, and may be due to incorrect pool management. Debugging this problem (only in debug mode) requires recv'ing/displaying this info when it exists and outputting the last operation sent over the socket.

            Assignee:
            Mark Benvenuto
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: