DX Application Performance Management

  • 1.  AGCSmartstoreControllerImpl: Maximum number of connections reached

    Posted May 22, 2017 04:50 PM

    Hi Team

    Anyone has already seen this message in the EM logs (MOM) ?

     

     - AGCSmartstoreControllerImpl: Maximum number of connections reached: 5

     

    Which is the property to increase this parameter?

     

    Thanks and Regards

    Antonello



  • 2.  Re: AGCSmartstoreControllerImpl: Maximum number of connections reached
    Best Answer

    Broadcom Employee
    Posted May 22, 2017 09:00 PM

    Hi Antonello,

    In the EM/MOM IntroscopeEnterpriseManager.properties file is the property "introscope.enterprisemanager.restapi.sql.connectionLimit" i.e.

    # If value of this property is set to positive number then
    # APM Data SQL rest api will be limited to number of paralel connections.
    # Otherwise transfer is unlimited.
    # Default value: 5
    #introscope.enterprisemanager.restapi.sql.connectionLimit=5

     

    It seems like it defaults to 5 when not set so please try to uncomment the property & increase it, or set to 0 which should mean unlimited based on above comments.

    Hope that helps

    Regards,

    Lynn



  • 3.  Re: AGCSmartstoreControllerImpl: Maximum number of connections reached

    Posted Sep 11, 2017 04:19 PM

    Thanks for this.  I noticed in development that when testing I hit the limit of 5, I can get around this by killing the APMSQLServer process and starting it, even though I am not running queries in the background or even have a connection opened.

     

    I don't know if the connections exist, but is there a timeout or a way that these connections could be killed after inactive use?



  • 4.  Re: AGCSmartstoreControllerImpl: Maximum number of connections reached

    Broadcom Employee
    Posted Sep 11, 2017 06:38 PM

    Hi Earl,

    Please see this related thread: APMSQL - Broken connections 

    The old/idle/zombie connection timeout may be controlled by the tcp/ip stack settings on the OS although in above thread user had to use tcpkill.

     

    Regards,

     

    Lynn