activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (AMQ-1446) org.apache.activemq.store.memory.MemoryPersistenceAdapter - Expected an instance of MemoryMessageStore but was: org.apache.activemq.store.memory.MemoryTransactionStore$2@a0f3d1
Date Fri, 05 Oct 2007 09:52:23 GMT

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

Rob Davies reassigned AMQ-1446:
-------------------------------

    Assignee: Rob Davies

> org.apache.activemq.store.memory.MemoryPersistenceAdapter - Expected an instance of MemoryMessageStore
but was: org.apache.activemq.store.memory.MemoryTransactionStore$2@a0f3d1
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1446
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1446
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.0.0
>            Reporter: David Sitsky
>            Assignee: Rob Davies
>             Fix For: 5.0.0
>
>
> I have an application which ran with persistence off, but with transactions.  I noticed
just before stopping the broker, I see the following messages:
> WARN  org.apache.activemq.store.memory.MemoryPersistenceAdapter - Expected an instance
of MemoryMessageStore but was: org.apache.activemq.store.memory.MemoryTransactionStore$2@a0f3d1
> WARN  org.apache.activemq.store.memory.MemoryPersistenceAdapter - Expected an instance
of MemoryMessageStore but was: org.apache.activemq.store.memory.MemoryTransactionStore$1@e7332d
> WARN  org.apache.activemq.store.memory.MemoryPersistenceAdapter - Expected an instance
of MemoryMessageStore but was: org.apache.activemq.store.memory.MemoryTransactionStore$1@d10008
> It doesn't seem to have affected anything, but I thought it was worth reporting.  I see
this in revision 582029.

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


Mime
View raw message