ActiveMQ
  1. ActiveMQ
  2. AMQ-1445

RecoveryListenerAdapter - Message id ID... could not be recovered from the data store!

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 5.0.0
    • Fix Version/s: 5.1.0
    • Component/s: Message Store
    • Labels:
      None

      Description

      My application works correctly with JDBC persistence using derby, or indeed with no persistence turned on.

      If I use the AMQ store however, very early on in the application's run, I get the following error, and then my application hangs. This happens for both the VM and TCP transports.

      [VMTransport] 35346 ERROR org.apache.activemq.store.amq.RecoveryListenerAdapter - Message id ID:tamarama-60079-1191564856100-2:2:3:3:4 could not be recovered from the data store!

      I have attached a debug trace of the application, which shows the lifetime of message tamarama-60079-1191564856100-2:2:3:3:4.

        Activity

        David Sitsky created issue -
        Hide
        David Sitsky added a comment -

        Forgot to mention: I observed this behaviour with revision 582029.

        Show
        David Sitsky added a comment - Forgot to mention: I observed this behaviour with revision 582029.
        Rob Davies made changes -
        Field Original Value New Value
        Assignee Rob Davies [ rajdavies ]
        Hide
        Rob Davies added a comment -

        Fixed by revision 582574

        Show
        Rob Davies added a comment - Fixed by revision 582574
        Rob Davies made changes -
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Hide
        David Sitsky added a comment -

        Hi Rob,

        Many thanks - I can confirm that this has fixed the issue.

        Cheers,
        David

        Show
        David Sitsky added a comment - Hi Rob, Many thanks - I can confirm that this has fixed the issue. Cheers, David
        Hide
        Lari Hotari added a comment - - edited

        I have this same problem with ActiveMQ 5.0.0 version that I downloaded 2 days ago. I don't think that this is fixed in the release build.

        The log has only this row:
        2008-01-18 17:29:10,769 [/127.0.0.1:2257] ERROR RecoveryListenerAdapter - Message id ID:mycomputer-2250-1200669948525-0:1:30:8:1 could not be recovered from the data store!

        ActiveMQ stalls after I do this: send 300 message to a queue, another app replies to each message to another queue. There's a short delay and I after I try again it will always stall after the 1. message. Really strange. Restarting ActiveMQ doesn't help. The data directory has to be deleted.
        The messages sent to the queue are non-persistent. I'm using Kaha store.

        Both sides are using Jencks + ActiveMQ RA + Spring TransactionTemplate + JdbcTemplate. The receiving side uses Jencks POJO (inbound) + JDBCTemplate (Jencks outbound configuration), inside XA transaction using Spring Transaction configuration for Jencks. I tested with non-persistent and persistent messages and the result is the same.

        I also tried Jdbc persistence (derby), but then some messages are lost (EOFException on client before problem, server side says that some acknowledge cannot be matched).

        Maybe Jencks is causing problems? Are there test cases that use Jencks + ActiveMQ RA?

        Show
        Lari Hotari added a comment - - edited I have this same problem with ActiveMQ 5.0.0 version that I downloaded 2 days ago. I don't think that this is fixed in the release build. The log has only this row: 2008-01-18 17:29:10,769 [/127.0.0.1:2257] ERROR RecoveryListenerAdapter - Message id ID:mycomputer-2250-1200669948525-0:1:30:8:1 could not be recovered from the data store! ActiveMQ stalls after I do this: send 300 message to a queue, another app replies to each message to another queue. There's a short delay and I after I try again it will always stall after the 1. message. Really strange. Restarting ActiveMQ doesn't help. The data directory has to be deleted. The messages sent to the queue are non-persistent. I'm using Kaha store. Both sides are using Jencks + ActiveMQ RA + Spring TransactionTemplate + JdbcTemplate. The receiving side uses Jencks POJO (inbound) + JDBCTemplate (Jencks outbound configuration), inside XA transaction using Spring Transaction configuration for Jencks. I tested with non-persistent and persistent messages and the result is the same. I also tried Jdbc persistence (derby), but then some messages are lost (EOFException on client before problem, server side says that some acknowledge cannot be matched). Maybe Jencks is causing problems? Are there test cases that use Jencks + ActiveMQ RA?
        Lari Hotari made changes -
        Status Resolved [ 5 ] Reopened [ 4 ]
        Resolution Fixed [ 1 ]
        Show
        Lari Hotari added a comment - Some other people also have this problem: http://www.nabble.com/5.0-release-having-%22RecoveryListenerAdapter%22-error-that-stop-msg-fetching-tp14423016s2354p14423016.html
        Lari Hotari made changes -
        Link This issue is related to AMQ-1544 [ AMQ-1544 ]
        Hide
        Lari Hotari added a comment -

        maybe this is the same problem. it also contains a test case.

        Show
        Lari Hotari added a comment - maybe this is the same problem. it also contains a test case.
        Hide
        Rob Davies added a comment -

        Resolved in trunk

        Show
        Rob Davies added a comment - Resolved in trunk
        Rob Davies made changes -
        Fix Version/s 5.1.0 [ 11802 ]
        Resolution Fixed [ 1 ]
        Fix Version/s 5.0.0 [ 11712 ]
        Status Reopened [ 4 ] Resolved [ 5 ]
        Jeff Turner made changes -
        Project Import Fri Nov 26 22:32:02 EST 2010 [ 1290828722158 ]

          People

          • Assignee:
            Rob Davies
            Reporter:
            David Sitsky
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development