Hi Michael
Its great to know about your use of Shoal and specifically the
DistributedStateCache. You are right in your observation that the
current implementation is akin to an example for lightweight use cases
and we have hardly spent time on it to make it robust to compete with
other caching products. That is the focus of Shoal 2.0 that we are
beginning work on for a new approach at caching with high end
deployments in mind.
Could you consider contributing your version of the code to Shoal? That
way it can make it into the mainstream Shoal distro. Please let me know
and we can work on how to get you commit access and testing it for
continued stability of the code base.
I would be very interested in knowing your reasons for using this cache
as a substitute for Coherence as we know that the Coherence product has
been around a lot longer and deployed a lot more than Shoal DSC. Knowing
about the merits and demerits of Coherence versus Shoal would help us a
lot. Shoal's focus has been mostly on ensuring the Group Management
Services ( GMS) become robust and hence lack of development on the
esoteric caching area.
Upcoming work on 2.0 would address this shortcoming in a big way. :-)
Cheers
Shreedhar
Michael Ammer wrote:
>
> Hi
>
>
>
> I am using shoal in a java application server as a substitute for
> oracle coherence for a number of reasons. I first started using shoal
> about a year ago as a distributed cache.
>
>
>
> I saw today that there was a new version available as of sep 17, and I
> just took a quick glance at the source, but I have a few questions.
>
>
>
> I use shoal in a different manner than most I guess, so I have made
> some major modifications to the source in the version I'm using.
> However, I would of course much rather be using the official release
> since I don't have time to maintain the shoal code myself.
>
>
>
> My first question is concerning
> com.sun.enterprise.ee.cms.impl.jxta.DistributedStateCacheImpl
>
> All the methods using cache.get() also iterate over the entire
> keyset() of the concurrent hashtable. I have corrected this in my
> version since my cache grows to anywhere from 1 to 100 megabyte. I
> read somewhere that this is just an example class showing developers
> how to implement their own cache, but I can't imagine this cache being
> anywhere near the performance of say jboss.
>
>
>
> This is just one of the many things I had to change to be able to use
> this product in a production environment.
>
>
>
> I am a big fan of JXTA and love using it in production, so I would
> like to see the same speed and stability in this product aswell.
>
>
>
> /Michael
>
>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4633 (20091124) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com