Uploaded image for project: 'Sentry'
  1. Sentry
  2. SENTRY-296

Sentry Service Client does not allow for connection pooling

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.4.0
    • Fix Version/s: 1.6.0
    • Component/s: None
    • Labels:

      Description

      The Sentry Service Client does not allow for connection pooling because there is no way to:
      1) Detect that a connection is broken
      2) Re-open a broken connection

      This would allow for Sentry Service clients to implement connection pooling like:

      if (!client.isOpen()) {
        client.reopen();
      }
      

      Currently, the only way to ensure connections are not broken is to open a new connection before every RPC.

        Attachments

        1. SENTRY-296.012.patch
          34 kB
          Dapeng Sun
        2. SENTRY-296.011.patch
          34 kB
          Dapeng Sun
        3. SENTRY-296.010.patch
          34 kB
          Dapeng Sun
        4. SENTRY-296.009.patch
          35 kB
          Dapeng Sun
        5. SENTRY-296.008.patch
          39 kB
          Dapeng Sun
        6. SENTRY-296.007.patch
          39 kB
          Dapeng Sun
        7. SENTRY-296.006.patch
          38 kB
          Dapeng Sun
        8. SENTRY-296.005.patch
          231 kB
          Colin
        9. SENTRY-296.004.patch
          231 kB
          Colin
        10. SENTRY-296.003.patch
          230 kB
          Colin
        11. SENTRY-296.002.patch
          232 kB
          Colin
        12. SENTRY-296.001.patch
          226 kB
          Dapeng Sun

          Issue Links

            Activity

              People

              • Assignee:
                colin Colin
                Reporter:
                lskuff Lenni Kuff
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: