Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-8255

Wrong exception propagation on reaching Broker Connection Limit

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 5.15.13
    • Fix Version/s: None
    • Component/s: Broker, JMS client
    • Labels:
      None
    • Environment:

      Description

      Hi,

      I am trying to add exception handling at activemq client side around connection setup. Based on my experiment I found that whenever Broker reaches the maximum connection limit, client receives 3 types of generic exceptions - SSLHandshakeException, SocketException & TransportDisposedIOException. These exceptions could occur if there is connectivity issue or truststore/certificate related issue. This has made exception handling impossible as it is not possible to know if the error is retry-able (recoverable) or not.

      The ask here is to provide better signal from Broker (or client library) so that application can handle recoverable and non recoverable errors differently.

      Suggestion options

      1. Let connection.start() throw ExceededMaximumConnectionsException
      2. Let client provide exception via listeners
      3. Or provide new API to get current number of client connections.

      Thanks

       

       

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              shash4mq Shashank Krishnaswamy
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: