bug in MapContainerImpl.java

[Chris Zeng <pl...@21cn.com>]

I found there is an bug in write method in the MapContainerImpl.java。When I
used IndexTypes.DISK_INDEX. If we add some data in MapContainer, then we
delete the last we added and add one.The index will be looped.The reason is
the inconsistence of index between memory and file. Imagine we add 'A', 'B',
'C' the three elements in the MapContainer, the the last element is 'C',
when we delete 'C', In memory the next info in the index of 'B'  points to
'C', and in file, it points to "-1". Then we add an new element "D". Then
D's next is point to itself.
-- 
View this message in context: http://www.nabble.com/bug-in-MapContainerImpl.java-tf4873211s2354.html#a13944544
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: bug in MapContainerImpl.java

[Rob Davies <ra...@gmail.com>]

Hi Chris

could you raise a jira issue for this: http://issues.apache.org/ 
activemq/browse/AMQ
You'll have to log in to create a new issue


cheers,

Rob

http://open.iona.com/ -Enterprise Open Integration
http://rajdavies.blogspot.com/



On Nov 26, 2007, at 6:53 AM, Chris Zeng wrote:

>
> I found there is an bug in write method in the  
> MapContainerImpl.java。When I
> used IndexTypes.DISK_INDEX. If we add some data in MapContainer,  
> then we
> delete the last we added and add one.The index will be looped.The  
> reason is
> the inconsistence of index between memory and file. Imagine we add  
> 'A', 'B',
> 'C' the three elements in the MapContainer, the the last element is  
> 'C',
> when we delete 'C', In memory the next info in the index of 'B'   
> points to
> 'C', and in file, it points to "-1". Then we add an new element  
> "D". Then
> D's next is point to itself.
> -- 
> View this message in context: http://www.nabble.com/bug-in- 
> MapContainerImpl.java-tf4873211s2354.html#a13944544
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>