Message metadata not found at startup
-------------------------------------
Key: QPID-1877
URL: https://issues.apache.org/jira/browse/QPID-1877
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.6
Reporter: Aidan Skinner
Fix For: 0.6
This is sometimes seen in AlertingTest because it's one of the few non-store
tests that uses a persistant store, although I don't think it's anything
related to that test itself.
main 2009-05-25 13:15:57,358 INFO [qpid.server.virtualhost.VirtualHost] Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@b40ec4 with routing key
'queue' to exchange:org.apache.qpid.server.virtualhost.virtualh...@13576a2
main 2009-05-25 13:15:57,366 INFO [qpid.server.virtualhost.VirtualHost] Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@ff8c74 with routing key
'ping' to exchange:org.apache.qpid.server.virtualhost.virtualh...@13576a2
main 2009-05-25 13:15:57,554 INFO [qpid.server.store.DerbyMessageStore]
Configuring Derby message store for virtual host test
main 2009-05-25 13:15:58,086 INFO [qpid.server.store.DerbyMessageStore]
Recovering persistent state...
Error initialising message broker: org.apache.qpid.AMQException: Metadata not
found for message with id 31
main 2009-05-25 13:15:58,229 ERROR [Qpid.Broker] Error initialising message
broker: org.apache.qpid.AMQException: Metadata not found for message with id 31
org.apache.qpid.AMQException: Metadata not found for message with id 31
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)
main 2009-05-25 13:15:58,287 INFO [qpid.test.utils.QpidTestCase] broker failed
to become ready
--
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:dev-subscr...@qpid.apache.org
