Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2256

An MQTTInactivityMonitor thread is being generated for every MQTT connection, causing additional resource contention

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • JBoss A-MQ 6.3
    • broker
    • None
    • Hide

      Additional details may be pending:

      1. Configure an activemq broker transport for mqtt_nio+ssl 

      <transportConnector name="mqtt+nio+ssl" uri="mqtt+nio+ssl://0.0.0.0:62062?maximumConnections=200000&amp;wireFormat.maxFrameSize=104857600&amp;transport.subscriptionStrategy=mqtt-virtual-topic-subscriptions"/>

      2. Connect with a large number of clients

      3. Inspect threads via thread dumps or JMX console

      There appears to be a 1:1 relationship between the inactivity monitor thread count and the connection thread count.

      Show
      Additional details may be pending: 1. Configure an activemq broker transport for mqtt_nio+ssl <transportConnector name= "mqtt+nio+ssl" uri= "mqtt+nio+ssl://0.0.0.0:62062?maximumConnections=200000&amp;wireFormat.maxFrameSize=104857600&amp;transport.subscriptionStrategy=mqtt-virtual-topic-subscriptions" /> 2. Connect with a large number of clients 3. Inspect threads via thread dumps or JMX console There appears to be a 1:1 relationship between the inactivity monitor thread count and the connection thread count.

    Description

      We are observing that an MQTTInactivityMonitor is getting created for each MQTT transport connection and this seems to be contributing to overall overhead and also to lock contention between the monitors and the transports.

      Attachments

        Activity

          People

            gtully@redhat.com Gary Tully
            rhn-support-dhawkins Duane Hawkins
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: