3 Replies Latest reply on Feb 1, 2016 5:22 PM by jbertram

    paging hornetq

    yoav-golan

      this is the standalone file messaging part of my jboss 7.1

      I don't see here the paging-directory tag . could it be paging is not configured on my server although <address-settings> part is exist ?

       

       

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

                  <hornetq-server>

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

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

                      <jmx-management-enabled>true</jmx-management-enabled>

                      <journal-type>ASYNCIO</journal-type>

                      <journal-sync-non-transactional>false</journal-sync-non-transactional>

        <journal-file-size>10240000</journal-file-size>

                      <journal-min-files>2</journal-min-files>

                      <connectors>

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

                              <param key="use-nio" value="false"/>

                          </netty-connector>

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

                      </connectors>

                      <acceptors>

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

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

                              <param key="use-nio" value="false"/>

                          </netty-acceptor>

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

                      </acceptors>

                      <security-settings>

                          <security-setting match="#">

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

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

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

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

                          </security-setting>

                      </security-settings>

                      <address-settings>

                     

                          <address-setting match="jms.topic.ca">

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

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

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

                              <max-size-bytes>4294967296</max-size-bytes>

                              <page-size-bytes>2508560</page-size-bytes>

        <page-max-cache-size>2</page-max-cache-size>

                              <address-full-policy>PAGE</address-full-policy>

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

                          </address-setting>

                          <!--default for catch all-->

                          <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>512857600</max-size-bytes>

                              <page-size-bytes>51285760</page-size-bytes>

                              <address-full-policy>PAGE</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"/>

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

                              </entries>

                          </connection-factory>

                          <connection-factory name="RemoteConnectionFactory">

                              <connectors>

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

                              </connectors>

                              <entries>

                                  <entry name="RemoteConnectionFactory"/>

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

                              </entries>

                          </connection-factory>

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

                              <transaction mode="none"/>

                              <connectors>

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

                              </connectors>

                              <entries>

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

                              </entries>

                          </pooled-connection-factory>

                      </jms-connection-factories>

        <jms-destinations>

                          <jms-topic name="ca.adminevents">

                              <entry name="topic/caAdmin"/>

                              <entry name="java:jboss/exported/topic/caAdmin"/>

                          </jms-topic>

                          <jms-topic name="ca">

                              <entry name="topic/ca"/>

                              <entry name="java:jboss/exported/topic/ca"/>

                          </jms-topic>

                          <jms-queue name="CaToBONY">

             <entry name="queue/CaToBONY"/>

             <durable>false</durable>

           </jms-queue>

           <jms-queue name="BONYToCa">

             <entry name="queue/BONYToCa"/>

             <durable>false</durable>

           </jms-queue>

           <jms-queue name="CaToGSCC">

             <entry name="queue/CaToGSCC"/>

             <durable>false</durable>

           </jms-queue>

           <jms-queue name="GSCCToCa">

             <entry name="queue/GSCCToCa"/>

             <durable>false</durable>

           </jms-queue>

           <jms-queue name="CalypsoToSwift">

             <entry name="queue/CalypsoToSwift"/>

             <durable>false</durable>

           </jms-queue>

           <jms-queue name="SwiftToCa">

             <entry name="queue/SwiftToCa"/>

             <durable>false</durable>

           </jms-queue>

           <jms-queue name="DLQ">

                              <entry name="queue/DLQ"/>

                              <durable>false</durable>

                          </jms-queue>

        <jms-queue name="ExpiryQueue">

                              <entry name="queue/ExpiryQueue"/>

                              <durable>false</durable>

                          </jms-queue>

                      </jms-destinations>

                  </hornetq-server>

              </subsystem>

        • 1. Re: paging hornetq
          jbertram

          The directory settings don't need to be set explicitly.  They'll happily default to the server's "data" directory.

          • 2. Re: paging hornetq
            yoav-golan

            thanks , yes I just read this

            my problem is that after a few hours one of my topic consumers , stop consuming messages.

            I read that this could be because of wrong ack-batch-size setting

            how can I see what is the acm-batch-size setting of this client on run time (I don't have the code ) ?

            • 3. Re: paging hornetq
              jbertram

              how can I see what is the acm-batch-size setting of this client on run time (I don't have the code ) ?

              If you don't have the actual client code but you want to see what it is setting for the ack-batch-size then I think you could decompile the client's class file(s).