0 Replies Latest reply: Apr 3, 2012 8:36 AM by Ulrich Kriegel RSS

    Configuration of HornetQ-Paging in JBoss6.1.0.Final

    Ulrich Kriegel Newbie

      In order to send and receive large messages, we would like to use the paging feature of HornetQ.

      However, after changing the address-full-policy to PAGE  in hornetq-configurations.xml (see below)

       

         <address-settings>

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

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

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

            </address-setting>

         </address-settings>

      JBoss brings a lot of errors like that given below during statup and hangs.

       

      13:42:19,714 Information [org.hornetq.ra.inflow.HornetQActivation] Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@51483946 destination=topic/MSOInput destinationType=javax.jms.Topic ack=Auto-acknowledge durable=false clientID=null user=imsk password=**** maxSession=15)

      13:42:19,714 Schwerwiegend [org.hornetq.ra.inflow.HornetQActivation] Unable to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@51483946 destination=topic/MSOInput destinationType=javax.jms.Topic ack=Auto-acknowledge durable=false clientID=null user=imsk password=**** maxSession=15): HornetQException[errorCode=2 message=Cannot connect to server(s). Tried with all available servers.]

                at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:711) [:]

                at org.hornetq.ra.inflow.HornetQActivation.setupSession(HornetQActivation.java:362) [:]

                at org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:294) [:]

                at org.hornetq.ra.inflow.HornetQActivation.handleFailure(HornetQActivation.java:558) [:]

                at org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:601) [:]

                at org.jboss.resource.work.WorkWrapper.run(WorkWrapper.java:172) [:6.1.0.Final]

                at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) [:2.0.0.CR7]

                at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:801) [:2.0.0.CR7]

                at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) [:2.0.0.CR7]

                at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:821) [:2.0.0.CR7]

                at java.lang.Thread.run(Thread.java:722) [:1.7.0_03]

                at org.jboss.threads.JBossThread.run(JBossThread.java:122) [:2.0.0.CR7]

       

       

      With address-full-policy values DROP and BLOCK there are no problems during startup.

       

      Did we miss something to configure?