RE: [jbosscache-dev] Changes in JBoss Cache HEAD
by Galder Zamarreno
Count with me for the reading and testing the tutorials :)
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
IT executives: Red Hat still #1 for value http://www.redhat.com/promo/vendor/
-----Original Message-----
From: jbosscache-dev-bounces(a)lists.jboss.org [mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of Manik Surtani
Sent: 02 January 2007 14:31
To: jbosscache-dev(a)lists.jboss.org
Subject: [jbosscache-dev] Changes in JBoss Cache HEAD
Hi guys.
All the major changes in HEAD are complete, and comprise of:
- Cache
- Changed Cache not to implement Node
- Updated methods on Cache and CacheSPI
- Node
- New object model as per http://jboss.org/index.html?
module=bb&op=viewtopic&t=97406
- Updated methods on the public interfaces (Node and NodeSPI)
- Renamed TreeCacheMarshaller/TreeCacheMarshaller200 to
CacheMarshaller/CacheMarshaller200 to be better in line
- Relocated the move() API from node level to cache level (it was
causing problems on the node level anyway)
Still TBD:
1. A few bugs with replicated move()
2. Some other CC failures
3. Update documentation, javadocs, tutorials and examples
4. PojoCache issues
5. State transfer issues
I'll be looking into 1 and 2 this week, the main aim being trying to
release ALPHA2 by the end of this week. 3 as well, if I have time
(main prio on the Javadocs). Once I get started on the user
documentation, tutorials and examples, I'd appreciate some help proof
reading and testing these, esp. on different environments.
Ben and Vlad, could you guys look into 4 and 5 this week? I'd like
to get this tagged by end of Thu if possible, to give QA as much time
as possible.
Cheers, and happy new year! :-)
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
18 years, 12 months
RE: [jbosscache-dev] Changes in JBoss Cache HEAD
by Vladimir Blagojevic
There is an intermittent state transfer concurrent activation failure.
What else did you have in mind? I also wanted to go through all the
tests and see how can we adapt them so we can run tests on multiple
jgroups configs.
Basic jbcache-315 implentation is running as well. However, it somehow
conflicts with buddy state transfer - there is a deadlock. I will have
to postpone integration of 315 to after alpha2.
> -----Original Message-----
> From: jbosscache-dev-bounces(a)lists.jboss.org
> [mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of
> Manik Surtani
> Sent: Tuesday, January 02, 2007 8:31 AM
> To: jbosscache-dev(a)lists.jboss.org
> Subject: [jbosscache-dev] Changes in JBoss Cache HEAD
>
> Hi guys.
>
> All the major changes in HEAD are complete, and comprise of:
>
> - Cache
> - Changed Cache not to implement Node
> - Updated methods on Cache and CacheSPI
> - Node
> - New object model as per http://jboss.org/index.html?
> module=bb&op=viewtopic&t=97406
> - Updated methods on the public interfaces (Node and NodeSPI)
> - Renamed TreeCacheMarshaller/TreeCacheMarshaller200 to
> CacheMarshaller/CacheMarshaller200 to be better in line
> - Relocated the move() API from node level to cache level (it
> was causing problems on the node level anyway)
>
> Still TBD:
>
> 1. A few bugs with replicated move()
> 2. Some other CC failures
> 3. Update documentation, javadocs, tutorials and examples 4.
> PojoCache issues
> 5. State transfer issues
>
> I'll be looking into 1 and 2 this week, the main aim being
> trying to release ALPHA2 by the end of this week. 3 as well,
> if I have time (main prio on the Javadocs). Once I get
> started on the user documentation, tutorials and examples,
> I'd appreciate some help proof reading and testing these,
> esp. on different environments.
>
> Ben and Vlad, could you guys look into 4 and 5 this week?
> I'd like to get this tagged by end of Thu if possible, to
> give QA as much time as possible.
>
> Cheers, and happy new year! :-)
> --
> Manik Surtani
>
> Lead, JBoss Cache
> JBoss, a division of Red Hat
>
> Email: manik(a)jboss.org
> Telephone: +44 7786 702 706
> MSN: manik(a)surtani.org
> Yahoo/AIM/Skype: maniksurtani
>
>
>
>
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>
18 years, 12 months
Changes in JBoss Cache HEAD
by Manik Surtani
Hi guys.
All the major changes in HEAD are complete, and comprise of:
- Cache
- Changed Cache not to implement Node
- Updated methods on Cache and CacheSPI
- Node
- New object model as per http://jboss.org/index.html?
module=bb&op=viewtopic&t=97406
- Updated methods on the public interfaces (Node and NodeSPI)
- Renamed TreeCacheMarshaller/TreeCacheMarshaller200 to
CacheMarshaller/CacheMarshaller200 to be better in line
- Relocated the move() API from node level to cache level (it was
causing problems on the node level anyway)
Still TBD:
1. A few bugs with replicated move()
2. Some other CC failures
3. Update documentation, javadocs, tutorials and examples
4. PojoCache issues
5. State transfer issues
I'll be looking into 1 and 2 this week, the main aim being trying to
release ALPHA2 by the end of this week. 3 as well, if I have time
(main prio on the Javadocs). Once I get started on the user
documentation, tutorials and examples, I'd appreciate some help proof
reading and testing these, esp. on different environments.
Ben and Vlad, could you guys look into 4 and 5 this week? I'd like
to get this tagged by end of Thu if possible, to give QA as much time
as possible.
Cheers, and happy new year! :-)
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
18 years, 12 months
LRU Eviction policy question
by Darshan Bildikar
Hello All,
I'm new to JBoss cache and sorry if this question has already been asked
before. I tried to find answers on the list with no success.
My problem is like this:-
I want to configure my cache such that
1) It contains no more than 10K objects at any given time
2) An object remains in the cache (either in memory / PERSISTENT store) for
MAX 200 seconds. It must be automatically REMOVED from the cache after 200
seconds lapse.
I am using an LRU eviction policy with a File cache loader. I have the
following question.
My region configuration looks like this
<region name="/test">
<attribute name="maxNodes">10000</attribute>
<attribute name="timeToLiveSeconds">100</attribute>
<attribute name="maxAgeSeconds">200</attribute>
</region>
I assume that this means "Evict my object to persistent store if maxNodes >
10000 OR maxAgeSeconds > 200"
What I however want is: After 10000 entries any new entry it is serialized
to the persistent store. However, after 200 seconds (irrespective of whether
it's in the persistent store or in memory) it needs to be REMOVED from the
cache. Is there a configuration that will help me do this?
I'm sorry if this question has been asked before. Appreciate any pointers.
BR
Darshan
Human beings, who are almost unique in having the ability to learn from the
experience of others, are also remarkable for their apparent disinclination
to do so
18 years, 12 months