why I not set thread-pool-max-size in hornetq，I find hornetq threads is always 400 or so

[gaoyonglu]

Hi,

When I do Pressure test， I find in hornetq,I no set thread-pool-max-size,the hornetq threads  is always  400 or so.

but I find thread-pool-max-size default is -1,no limit.

Then Error:No managed connections available within configured blocking timeout (30000 [ms])

But when I set thread-pool-max-size is 50000.I find the hornetq threads can growth to 1800,then error can not create new native thread.

I want to know Why I do Pressure test the hornetq threads can not growth without set thread-pool-max-size.

My

<subsystem xmlns="urn:jboss:domain:messaging:1.3">

            <hornetq-server>

                <thread-pool-max-size>50000</thread-pool-max-size>

                <persistence-enabled>true</persistence-enabled>

                <journal-type>NIO</journal-type>

                <journal-min-files>10</journal-min-files>

                <security-enabled>false</security-enabled>

                <connectors>

                    <netty-connector name="netty" socket-binding="messaging"/>

                    <netty-connector name="netty-throughput" socket-binding="messaging-throughput">

                        <param key="batch-delay" value="50"/>

                    </netty-connector>

                    <in-vm-connector name="in-vm" server-id="0"/>

                </connectors>

                <acceptors>

                    <netty-acceptor name="netty" socket-binding="messaging"/>

                    <netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">

                        <param key="batch-delay" value="50"/>

                        <param key="direct-deliver" value="false"/>

                    </netty-acceptor>

                    <in-vm-acceptor name="in-vm" server-id="0"/>

                </acceptors>

                <security-settings>

                    <security-setting match="#">

                        <permission type="send" roles="guest"/>

                        <permission type="consume" roles="guest"/>

                        <permission type="createNonDurableQueue" roles="guest"/>

                        <permission type="deleteNonDurableQueue" roles="guest"/>

                    </security-setting>

                </security-settings>

                <address-settings>

                    <address-setting match="#">

                        <dead-letter-address>jms.queue.DLQ</dead-letter-address>

                        <expiry-address>jms.queue.ExpiryQueue</expiry-address>

                        <redelivery-delay>0</redelivery-delay>

                        <max-size-bytes>10485760</max-size-bytes>

                        <address-full-policy>BLOCK</address-full-policy>

                        <message-counter-history-day-limit>10</message-counter-history-day-limit>

                    </address-setting>

                </address-settings>

                <jms-connection-factories>

                    <connection-factory name="InVmConnectionFactory">

                        <connectors>

                            <connector-ref connector-name="in-vm"/>

                        </connectors>

                        <entries>

                            <entry name="java:/ConnectionFactory"/>

                        </entries>

                    </connection-factory>

                    <connection-factory name="RemoteConnectionFactory">

                        <connectors>

                            <connector-ref connector-name="netty"/>

                        </connectors>

                        <entries>

                            <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>

                        </entries>

                    </connection-factory>

                    <pooled-connection-factory name="hornetq-ra">

                        <transaction mode="xa"/>

                        <connectors>

                            <connector-ref connector-name="in-vm"/>

                        </connectors>

                        <entries>

                            <entry name="java:/JmsXA"/>

                        </entries>

                    </pooled-connection-factory>

                </jms-connection-factories>

                  <jms-destinations>

                      <jms-queue name="/queue/xxxxx">

                        <entry name="/queue/xxxx"/>

                        <entry name="java:jboss/exported/jms/queue/xxxxxx"/>

                      </jms-queue>

                  <jms-queue name="/queue/xx">

                      <entry name="/queue/xx"/>

                      <entry name="java:jboss/exported/jms/queue/xx"/>

                  </jms-queue>

                  <jms-queue name="/queue/vvv">

                      <entry name="/queue/vvv"/>

                      <entry name="java:jboss/exported/jms/queue/vvv"/>

                  </jms-queue>

                  <jms-queue name="/queue/ccc">

                      <entry name="/queue/ccc"/>

                      <entry name="java:jboss/exported/jms/queue/ccc"/>

                  </jms-queue>

                  <jms-queue name="/queue/ttt">

                      <entry name="/queue/tttt"/>

                      <entry name="java:jboss/exported/jms/queue/ttt"/>

                  </jms-queue>

                </jms-destinations>

                </hornetq-server>

        </subsystem>

[gaoyonglu]

I make a mistake.the server side thread-pool-max-size default is 30 not -1. so why thread numbers not growth.

the client thread-pool-max-size si -1