1 2 Previous Next 25 Replies Latest reply on Feb 23, 2011 1:23 AM by Clebert Suconic

    Failed to ack

    Dariusz Szablinski Newbie

      I'm currently evaluating HornetQ BETA-5. It looks pretty promising. However I'm facing following problem:
      I have 3 separate, stand-alone instances, installed on the same Windows XP machine (Java 1.6.0_16). I've configured one of them to forward messages to the other two using following (HTTP) bridge configuration:

      
      <?xml version="1.0" encoding="UTF-8"?>
      <configuration xmlns="urn:hornetq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:hornetq /schema/hornetq-configuration.xsd">
       <clustered>true</clustered>
       <connectors>
       <connector name="netty">
       <factory-class>org.hornetq.integration.transports.netty.NettyConnectorFactory</factory-class>
       <param key="hornetq.remoting.netty.host" value="${hornetq.remoting.netty.host:localhost}" type="String"/>
       <param key="hornetq.remoting.netty.port" value="5445" type="Integer"/>
       </connector>
       <!-- Connector to the other node -->
       <connector name="remote-connector-pl">
       <factory-class>org.hornetq.integration.transports.netty.NettyConnectorFactory</factory-class>
       <param key="hornetq.remoting.netty.httpenabled" value="true" type="Boolean"/>
       <param key="hornetq.remoting.netty.port" value="8081" type="Integer"/>
       </connector>
       <connector name="remote-connector-ch">
       <factory-class>org.hornetq.integration.transports.netty.NettyConnectorFactory</factory-class>
       <param key="hornetq.remoting.netty.httpenabled" value="true" type="Boolean"/>
       <param key="hornetq.remoting.netty.port" value="8082" type="Integer"/>
       </connector>
       </connectors>
       <acceptors>
       <acceptor name="netty">
       <factory-class>org.hornetq.integration.transports.netty.NettyAcceptorFactory</factory-class>
       <param key="hornetq.remoting.netty.host" value="${hornetq.remoting.netty.host:localhost}" type="String"/>
       <param key="hornetq.remoting.netty.port" value="5445" type="Integer"/>
       </acceptor>
       <acceptor name="netty-http-acceptor">
       <factory-class>org.hornetq.integration.transports.netty.NettyAcceptorFactory</factory-class>
       <param key="hornetq.remoting.netty.httpenabled" value="true" type="Boolean"/>
       <param key="hornetq.remoting.netty.port" value="8080" type="Integer"/>
       </acceptor>
       </acceptors>
       <security-enabled>false</security-enabled>
      
       <queues>
       <queue name="jms.queue.QueueLocalIn">
       <address>jms.queue.QueueLocalIn</address>
       </queue>
       <queue name="jms.queue.QueueLocalOut">
       <address>jms.queue.QueueLocalOut</address>
       </queue>
       <queue name="jms.queue.ForwardingQueueLocal">
       <address>jms.queue.ForwardingQueueLocal</address>
       </queue>
       </queues>
       <diverts>
       <divert name="local-divert">
       <address>jms.queue.QueueLocalIn</address>
       <forwarding-address>jms.queue.QueueLocalOut</forwarding-address>
       <filter string="country IS NULL OR country NOT IN ('PL', 'CH')"/>
       <exclusive>true</exclusive>
       </divert>
      
       <divert name="remote-divert">
       <address>jms.queue.QueueLocalIn</address>
       <forwarding-address>jms.queue.ForwardingQueueLocal</forwarding-address>
       <filter string="country IN ('PL', 'CH')"/>
       <exclusive>true</exclusive>
       </divert>
       </diverts>
       <bridges>
       <bridge name="my-bridge-pl">
       <queue-name>jms.queue.ForwardingQueueLocal</queue-name>
       <forwarding-address>jms.queue.ForwardingQueueRemote</forwarding-address>
       <filter string="country='PL'"/>
       <transformer-class-name>zoo.daroo.hornetq.example.dee.DeETransformer</transformer-class-name>
       <reconnect-attempts>-1</reconnect-attempts>
       <connector-ref connector-name="remote-connector-pl"/>
       </bridge>
       <bridge name="my-bridge-ch">
       <queue-name>jms.queue.ForwardingQueueLocal</queue-name>
       <forwarding-address>jms.queue.ForwardingQueueRemote</forwarding-address>
       <filter string="country='CH'"/>
       <transformer-class-name>zoo.daroo.hornetq.example.dee.DeETransformer</transformer-class-name>
       <reconnect-attempts>-1</reconnect-attempts>
       <connector-ref connector-name="remote-connector-ch"/>
       </bridge>
       </bridges>
       <address-settings>
       <!--default for catch all-->
       <address-setting match="#">
       <clustered>false</clustered>
       <dead-letter-address>jms.queue.DLQ</dead-letter-address>
       <expiry-address>jms.queue.ExpiryQueue</expiry-address>
       <redelivery-delay>0</redelivery-delay>
       <max-size-bytes>-1</max-size-bytes>
       <page-size-bytes>10485760</page-size-bytes>
       <distribution-policy-class>org.hornetq.core.server.impl.RoundRobinDistributor</distribution-policy-class>
       <message-counter-history-day-limit>10</message-counter-history-day-limit>
       </address-setting>
       </address-settings>
       <paging-directory>../data/paging</paging-directory>
       <bindings-directory>../data/bindings</bindings-directory>
       <journal-directory>../data/journal</journal-directory>
       <large-messages-directory>../data/large-messages</large-messages-directory>
      </configuration>
      
      


      The bridge seems to be working - I can retrieve the messages from the other two nodes, but when I shutdown the first instance (where there is this bridge configuration), using STOP.bat, I'm getting bunch of exceptions on console:

      [New I/O client worker #5-1] 14:37:41,205 SEVERE [org.hornetq.core.server.cluster.impl.BridgeImpl] Failed to ack
      java.lang.IllegalStateException: Cannot find add info 638
       at org.hornetq.core.journal.impl.JournalImpl.appendUpdateRecord(JournalImpl.java:886)
       at org.hornetq.core.persistence.impl.journal.JournalStorageManager.storeAcknowledge(JournalStorageManager.java:302)
       at org.hornetq.core.server.impl.QueueImpl.acknowledge(QueueImpl.java:673)
       at org.hornetq.core.server.cluster.impl.BridgeImpl.sendAcknowledged(BridgeImpl.java:380)
       at org.hornetq.core.client.impl.ClientSessionImpl.commandConfirmed(ClientSessionImpl.java:815)
       at org.hornetq.core.remoting.impl.ChannelImpl.clearUpTo(ChannelImpl.java:741)
       at org.hornetq.core.remoting.impl.ChannelImpl.handlePacket(ChannelImpl.java:569)
       at org.hornetq.core.remoting.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:397)
       at org.hornetq.core.remoting.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:349)
       at org.hornetq.core.client.impl.ConnectionManagerImpl$DelegatingBufferHandler.bufferReceived(ConnectionManagerImpl.java:1142)
       at org.hornetq.integration.transports.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:64)
       at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:105)
       at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
       at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:803)
       at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:385)
       at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:324)
       at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:306)
       at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:223)
       at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:87)
       at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
       at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:803)
       at org.hornetq.integration.transports.netty.NettyConnector$HttpHandler.messageReceived(NettyConnector.java:500)
       at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:105)
       at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
       at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:803)
       at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:385)
       at org.jboss.netty.handler.codec.replay.ReplayingDecoder.unfoldAndfireMessageReceived(ReplayingDecoder.java:513)
       at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:497)
       at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:434)
       at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:87)
       at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
       at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:562)
       at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:342)
       at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:329)
       at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:330)
       at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:282)
       at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:203)
       at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:113)
       at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:53)
       at org.hornetq.integration.transports.netty.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:174)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
       at java.lang.Thread.run(Unknown Source)
      


      Is this caused by something wrong in my configuration or a bug in HornetQ?

      BTW. I also had this exception when I tried to retrieve messages (just after consumer.receive(1000))from my QueueLocalOut having session configured to Session.AUTO_ACKNOWLEDGE. When I changed it to Session.CLIENT_ACKNOWLEDGE and started ACKing manually it won't happened again.


      Cheers!


        • 1. Re: Failed to ack
          Tim Fox Master

          You mention you have installed three different instances on the same machine - have you made sure each instance is using it's own data directory for persistence?

          If you have three instances all pointing at the same data directory, then they'll be overwriting each others data and all sorts of strange things will happen.

          • 2. Re: Failed to ack
            Dariusz Szablinski Newbie

            Yes, I'm sure they use different data directories. The instances are installed in separate directories. Each of them has data directories defined as:

            <paging-directory>../data/paging</paging-directory>
             <bindings-directory>../data/bindings</bindings-directory>
             <journal-directory>../data/journal</journal-directory>
             <large-messages-directory>../data/large-messages</large-messages-directory>
            


            Besides, I've just did experiment and cleaned up ../data content in each instance folder. After instances start data files and sub-dirs structure were recreated and files were locked by started processes.

            • 3. Re: Failed to ack
              Tim Fox Master

              I wonder if this is the compacting bug that Clebert fixed in TRUNK a couple of weeks ago?

              Clebert, wdyt?

              • 4. Re: Failed to ack
                Clebert Suconic Master

                 

                "timfox" wrote:
                I wonder if this is the compacting bug that Clebert fixed in TRUNK a couple of weeks ago?

                Clebert, wdyt?



                Yes, I believe it is the bug I've fixed.

                Can you try trunk?

                • 5. Re: Failed to ack
                  Dariusz Szablinski Newbie

                  I tried TRUNK. Unfortunatelly I'm not able to verify if it helped, because now I'm getting OutOfMemoryException

                  [New I/O server worker #2-1] 17:50:15,384 SEVERE [org.hornetq.integration.transports.netty.HornetQChannelHandler] Got exception on Netty ch
                  annel
                  java.lang.OutOfMemoryError: Java heap space
                   at org.hornetq.integration.transports.netty.ChannelBufferWrapper.readSimpleString(ChannelBufferWrapper.java:275)
                   at org.hornetq.core.remoting.impl.wireformat.SessionCreateConsumerMessage.decodeBody(SessionCreateConsumerMessage.java:123)
                   at org.hornetq.core.remoting.impl.wireformat.PacketImpl.decode(PacketImpl.java:188)
                   at org.hornetq.core.remoting.impl.PacketDecoder.decode(PacketDecoder.java:359)
                   at org.hornetq.core.remoting.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:332)
                   at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:417)
                   at org.hornetq.integration.transports.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:64)
                   at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:391)
                   at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
                   at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
                   at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
                   at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:345)
                   at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:332)
                   at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:323)
                   at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:275)
                   at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:196)
                   at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
                   at org.hornetq.integration.transports.netty.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:210)
                   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
                   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
                   at java.lang.Thread.run(Unknown Source)
                  


                  I left memory options on default settings in run.bat (-Xms512M -Xmx1024M) and each of java.exe processes indeed occupies 1GB RAM.

                  • 6. Re: Failed to ack
                    Clebert Suconic Master

                    did you reset your journal files when you moved to trunk?

                    • 8. Re: Failed to ack
                      Clebert Suconic Master

                      It's probably a different issue then?

                      We would need more information to identify what's happening.

                      • 9. Re: Failed to ack
                        Dariusz Szablinski Newbie

                        Yes, this is another issue which exists when I use binaries built from today's TRUNK. However I can see that my primal issue still exists in the latest code. When I shutdown the instance responsible for routing (with
                        and ) messages to the other two instances I'm getting "Failed to ack" error. But first I'd like to get rid of OoM Exceptions, because this time they could be a reason why messages are not ACKed.

                        What more info will help you to investigate the problems?

                        • 10. Re: Failed to ack
                          Dariusz Szablinski Newbie

                          ... the instance with

                          <divers/>
                          

                          and
                          <bridges/>
                          


                          • 11. Re: Failed to ack
                            Clebert Suconic Master

                            You are not getting any other warnings on log? You should at least see a Memory Warning on logs.


                            What revision you have now?

                            • 12. Re: Failed to ack
                              Clebert Suconic Master

                              Do you think you can replicate that in a simple test?


                              I will try running the examples now also.

                              • 13. Re: Failed to ack
                                Clebert Suconic Master

                                Another possibility...

                                Did you upgrade the libraries on the client also?


                                Since this is the trunk, we probably didn't upgrade the versionID, so the check for version done at our side wouldn't work... if you mixed the versions you could have something weird happening on the wire.

                                • 14. Re: Failed to ack
                                  Dariusz Szablinski Newbie

                                  No, I didn't upgraded client libs. I did it now and this solved OOM problem, but I'm still getting "Failed to ack" during primary instance shutdown.

                                  My revision is: 8025

                                  1 2 Previous Next