AlertingTest is showing Reference Counting bug in Broker or DerbyStore
----------------------------------------------------------------------

                 Key: QPID-1870
                 URL: https://issues.apache.org/jira/browse/QPID-1870
             Project: Qpid
          Issue Type: Bug
          Components: Java Broker, Java Broker MessageStore - DerbyStore
            Reporter: Martin Ritchie


Summary:

Whilst the test does not consume all its messages, running on a cruise control 
box causes it to reload those messages which in this instance failed to occur 
correctly.

At this stage we cannot tell what went wrong but either the broker's reference 
counting is at fault or the Store failed to remove the enqueue record but did 
remove the meta data.




Error initialising message broker: org.apache.qpid.AMQException: Metadata not 
found for message with id 240
main 2009-05-21 04:06:04,477 ERROR [Qpid.Broker] Error initialising message 
broker: org.apache.qpid.AMQException: Metadata not found for message with id 240
org.apache.qpid.AMQException: Metadata not found for message with id 240
        at 
org.apache.qpid.server.store.DerbyMessageStore.getMessageMetaData(DerbyMessageStore.java:1238)
        at 
org.apache.qpid.server.queue.WeakReferenceMessageHandle.loadMessageMetaData(WeakReferenceMessageHandle.java:78)
        at 
org.apache.qpid.server.queue.WeakReferenceMessageHandle.getContentHeaderBody(WeakReferenceMessageHandle.java:64)
        at 
org.apache.qpid.server.queue.WeakReferenceMessageHandle.getBodySize(WeakReferenceMessageHandle.java:107)
        at org.apache.qpid.server.queue.AMQMessage.<init>(AMQMessage.java:204)
        at 
org.apache.qpid.server.store.DerbyMessageStore.deliverMessages(DerbyMessageStore.java:1421)
        at 
org.apache.qpid.server.store.DerbyMessageStore.recover(DerbyMessageStore.java:326)
        at 
org.apache.qpid.server.store.DerbyMessageStore.configure(DerbyMessageStore.java:174)
        at 
org.apache.qpid.server.virtualhost.VirtualHost.initialiseMessageStore(VirtualHost.java:281)
        at 
org.apache.qpid.server.virtualhost.VirtualHost.<init>(VirtualHost.java:207)
        at 
org.apache.qpid.server.virtualhost.VirtualHost.<init>(VirtualHost.java:150)
        at 
org.apache.qpid.server.registry.ConfigurationFileApplicationRegistry.initialiseVirtualHosts(ConfigurationFileApplicationRegistry.java:71)
        at 
org.apache.qpid.server.registry.ConfigurationFileApplicationRegistry.initialise(ConfigurationFileApplicationRegistry.java:63)
        at 
org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:100)
        at 
org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:88)
        at org.apache.qpid.server.Main.startup(Main.java:269)
        at org.apache.qpid.server.Main.execute(Main.java:193)
        at org.apache.qpid.server.Main.<init>(Main.java:93)
        at org.apache.qpid.server.Main.main(Main.java:440)

Error initialising message broker: org.apache.qpid.AMQException: Metadata not 
found for message with id 240
main 2009-05-21 04:06:04,477 ERROR [Qpid.Broker] Error initialising message 
broker: org.apache.qpid.AMQException: Metadata not found for message with id 240
org.apache.qpid.AMQException: Metadata not found for message with id 240
        at 
org.apache.qpid.server.store.DerbyMessageStore.getMessageMetaData(DerbyMessageStore.java:1238)
        at 
org.apache.qpid.server.queue.WeakReferenceMessageHandle.loadMessageMetaData(WeakReferenceMessageHandle.java:78)
        at 
org.apache.qpid.server.queue.WeakReferenceMessageHandle.getContentHeaderBody(WeakReferenceMessageHandle.java:64)
        at 
org.apache.qpid.server.queue.WeakReferenceMessageHandle.getBodySize(WeakReferenceMessageHandle.java:107)
        at org.apache.qpid.server.queue.AMQMessage.<init>(AMQMessage.java:204)
        at 
org.apache.qpid.server.store.DerbyMessageStore.deliverMessages(DerbyMessageStore.java:1421)
        at 
org.apache.qpid.server.store.DerbyMessageStore.recover(DerbyMessageStore.java:326)
        at 
org.apache.qpid.server.store.DerbyMessageStore.configure(DerbyMessageStore.java:174)
        at 
org.apache.qpid.server.virtualhost.VirtualHost.initialiseMessageStore(VirtualHost.java:281)
        at 
org.apache.qpid.server.virtualhost.VirtualHost.<init>(VirtualHost.java:207)
        at 
org.apache.qpid.server.virtualhost.VirtualHost.<init>(VirtualHost.java:150)
        at 
org.apache.qpid.server.registry.ConfigurationFileApplicationRegistry.initialiseVirtualHosts(ConfigurationFileApplicationRegistry.java:71)
        at 
org.apache.qpid.server.registry.ConfigurationFileApplicationRegistry.initialise(ConfigurationFileApplicationRegistry.java:63)
        at 
org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:100)
        at 
org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:88)
        at org.apache.qpid.server.Main.startup(Main.java:269)
        at org.apache.qpid.server.Main.execute(Main.java:193)
        at org.apache.qpid.server.Main.<init>(Main.java:93)
        at org.apache.qpid.server.Main.main(Main.java:440)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to