[ 
https://issues.apache.org/jira/browse/QPID-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPID-5480:
-----------------------------------

    Attachment: QPID-5480.tar.gz

Attached store: QPID-5480.tar.gz

> [linearstore] Recovery of store failure with "JERR_MAP_NOTFOUND: Key not 
> found in map." error message
> -----------------------------------------------------------------------------------------------------
>
>                 Key: QPID-5480
>                 URL: https://issues.apache.org/jira/browse/QPID-5480
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>            Reporter: Kim van der Riet
>            Assignee: Kim van der Riet
>         Attachments: QPID-5480.tar.gz
>
>
> While running a qpid-txtest soak test, a store was encountered which could 
> not be recovered. The broker stopped with the following error message:
> {color:blue}{{\[Broker\] critical Unexpected error: Error commitjexception 
> 0x0b01 wmgr::dequeue() threw JERR_MAP_NOTFOUND: Key not found in map. 
> (rid=0x3e4f0) 
> (/home/kpvdr/RedHat/qpid/cpp/src/qpid/linearstore/TxnCtxt.cpp:55)}}{color}
> The store in question is attached. An additional similar error message is 
> seen during store shutdown.
> To reproduce:
> 1. Expand the store into a store directory. Note that the store directory is 
> the one that contains the *{{qls}}* directory in the attached archive, and is 
> supplied to the broker using the *{{--store-dir}}* parameter.
> 2. Start the broker so as to recover the store in the store directory:
> {color:blue}{{./qpidd --load-module linearstore.so -m no --auth no 
> --default-flow-stop-threshold 0 --default-flow-resume-threshold 0 
> --default-queue-limit 0 --store-dir <path-to-store-dir> --log-enable info+ 
> --truncate no}}{color}
> The store does not recover, and the broker exits with the above error message.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to