Well, a loggingDelegatorCacheStore is maybe a better idea for this purpose.<div>Sound like a 3 minutes job... But it's not gonna help me.</div><div>Right now, I am not in the CacheStore, I am deep into JClouds ListeningChainingIAmPlayingInThisThreadLookNoNotThisOneTheOtherOneOOpsSorryItIsDeadNow ;-)</div>
<div><br></div><div>phil <br><br><div class="gmail_quote">On Sat, Jan 30, 2010 at 11:58 AM, Amin Abbaspour <span dir="ltr"><<a href="mailto:a.abbaspour@gmail.com">a.abbaspour@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Phil,<br>
<br>
Why don't you just create a dummy cache-store which does nothing but<br>
log? I think we need this fake story for unit-tests too.<br>
<font color="#888888"><br>
Amin<br>
</font><div><div></div><div class="h5"><br>
On Sat, Jan 30, 2010 at 1:53 PM, Philippe Van Dyck <<a href="mailto:pvdyck@gmail.com">pvdyck@gmail.com</a>> wrote:<br>
> Indeed Manik, I am using the CloudCacheStore... am I lost on a dead branch<br>
> of code ?<br>
> Can I help ? Is the JClouds 1.0-beta3 development on a different branch than<br>
> the snapshot ?<br>
><br>
> Cheers,<br>
> phil<br>
> On Sat, Jan 30, 2010 at 11:11 AM, Manik Surtani <<a href="mailto:manik@jboss.org">manik@jboss.org</a>> wrote:<br>
>><br>
>> Phil,<br>
>> I presume you're using the new CloudCacheStore? I hope to see a JClouds<br>
>> 1.0-beta3 out this weekend which will be the version used for<br>
>> CloudCacheStore (instead of a JClouds snapshot, which may be the root cause<br>
>> of your 403's).<br>
>> Cheers<br>
>> Manik<br>
>> On 30 Jan 2010, at 09:58, Philippe Van Dyck wrote:<br>
>><br>
>> Amin,<br>
>> I did some tests too. Unfortunately, they were inconclusive...<br>
>> Using JClouds BlobStore CacheStore I end up with a lot of 'other' problems<br>
>> (right now, I am getting 403 from S3).<br>
>> Since IMO, it is unrelated to the async behavior, I cannot help until I<br>
>> solve the previous bugs.<br>
>> Futures are everywhere in the code now (at least in the BlobStore) and it<br>
>> makes debugging a lot harder since I cannot step easily into code.<br>
>> As soon as I solve the BlobStore issues, I'll get back to this one and<br>
>> post my results...<br>
>> phil<br>
>><br>
>> On Sat, Jan 30, 2010 at 9:24 AM, Amin Abbaspour <<a href="mailto:a.abbaspour@gmail.com">a.abbaspour@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> I did some tests. Unfortunately my results are not much satisfactory.<br>
>>><br>
>>> I do confirm that now changes are synced in a separate<br>
>>> CoalescedAsyncStore thread, but the aggregate process we discussed<br>
>>> before here ( <a href="https://jira.jboss.org/jira/browse/ISPN-116" target="_blank">https://jira.jboss.org/jira/browse/ISPN-116</a> ) does not<br>
>>> work anymore. I can see that not the only final value but all<br>
>>> modifications are flushed. (i.e. sync at then end of a 100<br>
>>> modifications period results in 100 stores)<br>
>>><br>
>>> The other issue is that only cache.put() worked for me this way, and<br>
>>> it ignored all modification via replace for example.<br>
>>><br>
>>> Let me know if you have done similar tests and your results plz.<br>
>>><br>
>>> Thanks<br>
>>> Amin<br>
>>><br>
>>><br>
>>> On Fri, Jan 29, 2010 at 7:56 PM, Amin Abbaspour <<a href="mailto:a.abbaspour@gmail.com">a.abbaspour@gmail.com</a>><br>
>>> wrote:<br>
>>> > Thanks Galder for such a quickly fix.<br>
>>> ><br>
>>> > like Philippe I was not expecting this major issue to be fixed so<br>
>>> > fast. I have not tested it myself yet, but will check and inform my<br>
>>> > test result tomorrow.<br>
>>> ><br>
>>> > Amin<br>
>>> ><br>
>>> > On Fri, Jan 29, 2010 at 4:15 PM, Manik Surtani <<a href="mailto:manik@jboss.org">manik@jboss.org</a>> wrote:<br>
>>> >><br>
>>> >> On 29 Jan 2010, at 12:21, Philippe Van Dyck wrote:<br>
>>> >><br>
>>> >> Thanks Galder, I could have.<br>
>>> >> As you noticed in the thread, this bug is a blocker for me and since<br>
>>> >> qi4j<br>
>>> >> 1.0 was released two days ago, I am now only waiting for the latest<br>
>>> >> release<br>
>>> >> of JClouds (beta3) to integrate all of them.<br>
>>> >> So having it solved so quickly (!!! :-) ) did change a lot of my<br>
>>> >> schedule<br>
>>> >> these last days and when I asked the previous question I was far away<br>
>>> >> from<br>
>>> >> any fully fledged browser...<br>
>>> >> Until Jira fully integrates with mailing lists, there will be a lag<br>
>>> >> between<br>
>>> >> a "this is done now" message and the "here is the svn log" explanation<br>
>>> >> for<br>
>>> >> anybody with a crappy phone like me ;-)<br>
>>> >> Actually, having Jira manage (or observe) the mailing list could be a<br>
>>> >> very<br>
>>> >> good idea... linking code changes to specific parts of discussions and<br>
>>> >> having Jira to automagically tag it as 'bug' 'task' or 'improvement'<br>
>>> >> would<br>
>>> >> be very nice (Jira could also add links to code...)!<br>
>>> >><br>
>>> >> Only once JIRA actually fixes and commits bugs (and makes me coffee)<br>
>>> >> will I<br>
>>> >> be truly impressed! :)<br>
>>> >><br>
>>> >> phil<br>
>>> >><br>
>>> >> On Fri, Jan 29, 2010 at 12:19 PM, Galder Zamarreno <<a href="mailto:galder@jboss.org">galder@jboss.org</a>><br>
>>> >> wrote:<br>
>>> >>><br>
>>> >>><br>
>>> >>> On 01/28/2010 06:15 PM, Philippe Van Dyck wrote:<br>
>>> >>> > Could you please be a bit more specific ?<br>
>>> >>> > Are there any test to confirm the closing of the bug ?<br>
>>> >>> > Is it in trunk ?<br>
>>> >>><br>
>>> >>> Dude, you could at least check the jira and its svn tab!<br>
>>> >>><br>
>>> >>><br>
>>> >>><br>
>>> >>> <a href="https://jira.jboss.org/jira/browse/ISPN-340?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel" target="_blank">https://jira.jboss.org/jira/browse/ISPN-340?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel</a><br>
>>> >>><br>
>>> >>> ><br>
>>> >>> > That sounds like a really good news ;-)<br>
>>> >>> ><br>
>>> >>> > phil<br>
>>> >>> ><br>
>>> >>> > On Thu, Jan 28, 2010 at 6:10 PM, Galder Zamarreno<<a href="mailto:galder@jboss.org">galder@jboss.org</a>><br>
>>> >>> > wrote:<br>
>>> >>> ><br>
>>> >>> >> This is done now.<br>
>>> >>> >><br>
>>> >>> >> On 01/26/2010 01:10 PM, Amin Abbaspour wrote:<br>
>>> >>> >>> Created <a href="https://jira.jboss.org/jira/browse/ISPN-340" target="_blank">https://jira.jboss.org/jira/browse/ISPN-340</a><br>
>>> >>> >>> You can vote.<br>
>>> >>> >>><br>
>>> >>> >>> On Tue, Jan 26, 2010 at 3:21 PM, Sanne Grinovero<br>
>>> >>> >>> <<a href="mailto:sanne.grinovero@gmail.com">sanne.grinovero@gmail.com</a>> wrote:<br>
>>> >>> >>>> +1<br>
>>> >>> >>>> I don't know if it's correct to consider it a bug, but choices<br>
>>> >>> >>>> on<br>
>>> >>> >>>> JIRA<br>
>>> >>> >>>> are limited.<br>
>>> >>> >>>> I would really need this - performance impact is high - and hope<br>
>>> >>> >>>> they<br>
>>> >>> >>>> could fix it before 4.0<br>
>>> >>> >>>><br>
>>> >>> >>>> Regards,<br>
>>> >>> >>>> Sanne<br>
>>> >>> >>>><br>
>>> >>> >>>> 2010/1/26 Amin Abbaspour<<a href="mailto:a.abbaspour@gmail.com">a.abbaspour@gmail.com</a>>:<br>
>>> >>> >>>>> Yes Philippe, I think it is a bug.<br>
>>> >>> >>>>><br>
>>> >>> >>>>> This totally ruins all attempts to create a write-behind async<br>
>>> >>> >>>>> store.<br>
>>> >>> >>>>> I don't know if JBoss Cache had the same issue or not, but for<br>
>>> >>> >>>>> many<br>
>>> >>> >>>>> use-cases (including ours) one will need both TX and<br>
>>> >>> >>>>> write-behind<br>
>>> >>> >>>>> simultaneously.<br>
>>> >>> >>>>><br>
>>> >>> >>>>> OK, I will open a bug in Jira for 4.0.0-GA.<br>
>>> >>> >>>>><br>
>>> >>> >>>>> Amin<br>
>>> >>> >>>>><br>
>>> >>> >>>>> On Tue, Jan 26, 2010 at 2:12 PM, Philippe Van<br>
>>> >>> >>>>> Dyck<<a href="mailto:pvdyck@gmail.com">pvdyck@gmail.com</a>><br>
>>> >>> >> wrote:<br>
>>> >>> >>>>>> Sounds like a good idea.<br>
>>> >>> >>>>>> How do you qualify it ? Bug ? (perf) Improvement ?<br>
>>> >>> >>>>>> It has a major impact on performance when using the S3<br>
>>> >>> >>>>>> CacheStore,<br>
>>> >>> >>>>>> so<br>
>>> >>> >> I<br>
>>> >>> >>>>>> would like it to be a "performance bug".<br>
>>> >>> >>>>>> WDYT ... especially regarding the planning of the next release<br>
>>> >>> >>>>>> ?<br>
>>> >>> >>>>>> Phil<br>
>>> >>> >>>>>> On Tue, Jan 26, 2010 at 11:28 AM, Amin Abbaspour<<br>
>>> >>> >> <a href="mailto:a.abbaspour@gmail.com">a.abbaspour@gmail.com</a>><br>
>>> >>> >>>>>> wrote:<br>
>>> >>> >>>>>>><br>
>>> >>> >>>>>>> Hi,<br>
>>> >>> >>>>>>><br>
>>> >>> >>>>>>> Should I open a jira task for this?<br>
>>> >>> >>>>>>><br>
>>> >>> >>>>>>> Amin<br>
>>> >>> >>>>>>><br>
>>> >>> >>>>>>> On Sat, Jan 23, 2010 at 4:59 PM, Amin Abbaspour<<br>
>>> >>> >> <a href="mailto:a.abbaspour@gmail.com">a.abbaspour@gmail.com</a>><br>
>>> >>> >>>>>>> wrote:<br>
>>> >>> >>>>>>>> I guess this is a somehow a bug or typo.<br>
>>> >>> >>>>>>>><br>
>>> >>> >>>>>>>> Transactions and stores are two separate concepts. While it<br>
>>> >>> >>>>>>>> sounds<br>
>>> >>> >> to<br>
>>> >>> >>>>>>>> flush to normal store at the TX commit but when one<br>
>>> >>> >>>>>>>> knowingly<br>
>>> >>> >>>>>>>> sets<br>
>>> >>> >>>>>>>> store as async, he accepts the risk of consistence in favor<br>
>>> >>> >>>>>>>> of<br>
>>> >>> >> speed.<br>
>>> >>> >>>>>>>><br>
>>> >>> >>>>>>>> I expect this to be fixed (or at least discussed) before GA.<br>
>>> >>> >>>>>>>><br>
>>> >>> >>>>>>>> Amin<br>
>>> >>> >>>>>>>><br>
>>> >>> >>>>>>>> On Sat, Jan 23, 2010 at 3:48 PM, Philippe Van<br>
>>> >>> >>>>>>>> Dyck<<a href="mailto:pvdyck@gmail.com">pvdyck@gmail.com</a><br>
>>> >>> >>><br>
>>> >>> >>>>>>>> wrote:<br>
>>> >>> >>>>>>>>> I do confirm this behavior.<br>
>>> >>> >>>>>>>>> Transactions and asynchronous updates may seem<br>
>>> >>> >>>>>>>>> antagonistic, but<br>
>>> >>> >> they<br>
>>> >>> >>>>>>>>> are<br>
>>> >>> >>>>>>>>> not on a multi-level cache.<br>
>>> >>> >>>>>>>>> I plan to use a synchronous transactional disk cache and a<br>
>>> >>> >>>>>>>>> second<br>
>>> >>> >> non<br>
>>> >>> >>>>>>>>> transactional asynchronous s3 cache, to get the best of<br>
>>> >>> >>>>>>>>> both<br>
>>> >>> >> worlds.<br>
>>> >>> >>>>>>>>> Since the asynchronous aspect of the s3 cache will not<br>
>>> >>> >>>>>>>>> allow me<br>
>>> >>> >>>>>>>>> to<br>
>>> >>> >> get<br>
>>> >>> >>>>>>>>> any<br>
>>> >>> >>>>>>>>> feedback (aka Future), I want it to 'write-behind' in the<br>
>>> >>> >> background<br>
>>> >>> >>>>>>>>> (and<br>
>>> >>> >>>>>>>>> hope everything goes well).<br>
>>> >>> >>>>>>>>> I will wait for the qi4j v1 release (probably Monday),<br>
>>> >>> >>>>>>>>> adapt<br>
>>> >>> >> infinispan<br>
>>> >>> >>>>>>>>> to<br>
>>> >>> >>>>>>>>> the blobstore of jClouds and take a closer look at this in<br>
>>> >>> >>>>>>>>> a<br>
>>> >>> >>>>>>>>> couple<br>
>>> >>> >> of<br>
>>> >>> >>>>>>>>> weeks.<br>
>>> >>> >>>>>>>>> Phil<br>
>>> >>> >>>>>>>>><br>
>>> >>> >>>>>>>>> On Sat, Jan 23, 2010 at 12:58 PM, Amin Abbaspour<br>
>>> >>> >>>>>>>>> <<a href="mailto:a.abbaspour@gmail.com">a.abbaspour@gmail.com</a>><br>
>>> >>> >>>>>>>>> wrote:<br>
>>> >>> >>>>>>>>>><br>
>>> >>> >>>>>>>>>> Hi All,<br>
>>> >>> >>>>>>>>>><br>
>>> >>> >>>>>>>>>> Regarding<br>
>>> >>> >>>>>>>>>><br>
>>> >>> >><br>
>>> >>> >> <a href="http://community.jboss.org/wiki/Write-ThroughAndWrite-BehindCaching" target="_blank">http://community.jboss.org/wiki/Write-ThroughAndWrite-BehindCaching</a><br>
>>> >>> >>>>>>>>>> , Even if Syncer is in Async mode, but if we modify a key<br>
>>> >>> >>>>>>>>>> inside a<br>
>>> >>> >>>>>>>>>> transaction boundary it is always stored synchronously!<br>
>>> >>> >>>>>>>>>> Why is<br>
>>> >>> >>>>>>>>>> it<br>
>>> >>> >> so?<br>
>>> >>> >>>>>>>>>> How can I have both locking and async store. FYI I use<br>
>>> >>> >>>>>>>>>> JBossTM<br>
>>> >>> >>>>>>>>>> Standalone.<br>
>>> >>> >>>>>>>>>><br>
>>> >>> >>>>>>>>>> Regards,<br>
>>> >>> >>>>>>>>>> Amin Abbaspour<br>
>>> >>> >>>>>>>>>> _______________________________________________<br>
>>> >>> >>>>>>>>>> infinispan-dev mailing list<br>
>>> >>> >>>>>>>>>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >>> >>>>>>>>>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> >>> >>>>>>>>><br>
>>> >>> >>>>>>>>><br>
>>> >>> >>>>>>>>> _______________________________________________<br>
>>> >>> >>>>>>>>> infinispan-dev mailing list<br>
>>> >>> >>>>>>>>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >>> >>>>>>>>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> >>> >>>>>>>>><br>
>>> >>> >>>>>>>><br>
>>> >>> >>>>>>> _______________________________________________<br>
>>> >>> >>>>>>> infinispan-dev mailing list<br>
>>> >>> >>>>>>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >>> >>>>>>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> >>> >>>>>><br>
>>> >>> >>>>>><br>
>>> >>> >>>>>> _______________________________________________<br>
>>> >>> >>>>>> infinispan-dev mailing list<br>
>>> >>> >>>>>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >>> >>>>>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> >>> >>>>>><br>
>>> >>> >>>>><br>
>>> >>> >>>>> _______________________________________________<br>
>>> >>> >>>>> infinispan-dev mailing list<br>
>>> >>> >>>>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >>> >>>>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> >>> >>>><br>
>>> >>> >>>> _______________________________________________<br>
>>> >>> >>>> infinispan-dev mailing list<br>
>>> >>> >>>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >>> >>>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> >>> >>><br>
>>> >>> >>> _______________________________________________<br>
>>> >>> >>> infinispan-dev mailing list<br>
>>> >>> >>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >>> >>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> >>> >><br>
>>> >>> >> --<br>
>>> >>> >> Galder Zamarreńo<br>
>>> >>> >> Sr. Software Engineer<br>
>>> >>> >> Infinispan, JBoss Cache<br>
>>> >>> >> _______________________________________________<br>
>>> >>> >> infinispan-dev mailing list<br>
>>> >>> >> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >>> >> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> >>> >><br>
>>> >>> ><br>
>>> >>> ><br>
>>> >>> ><br>
>>> >>> > _______________________________________________<br>
>>> >>> > infinispan-dev mailing list<br>
>>> >>> > <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >>> > <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> >>><br>
>>> >>> --<br>
>>> >>> Galder Zamarreńo<br>
>>> >>> Sr. Software Engineer<br>
>>> >>> Infinispan, JBoss Cache<br>
>>> >>> _______________________________________________<br>
>>> >>> infinispan-dev mailing list<br>
>>> >>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> >><br>
>>> >> _______________________________________________<br>
>>> >> infinispan-dev mailing list<br>
>>> >> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> >><br>
>>> >> --<br>
>>> >> Manik Surtani<br>
>>> >> <a href="mailto:manik@jboss.org">manik@jboss.org</a><br>
>>> >> Lead, Infinispan<br>
>>> >> Lead, JBoss Cache<br>
>>> >> <a href="http://www.infinispan.org" target="_blank">http://www.infinispan.org</a><br>
>>> >> <a href="http://www.jbosscache.org" target="_blank">http://www.jbosscache.org</a><br>
>>> >><br>
>>> >><br>
>>> >><br>
>>> >><br>
>>> >> _______________________________________________<br>
>>> >> infinispan-dev mailing list<br>
>>> >> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> >><br>
>>> ><br>
>>><br>
>>> _______________________________________________<br>
>>> infinispan-dev mailing list<br>
>>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>><br>
>> _______________________________________________<br>
>> infinispan-dev mailing list<br>
>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>><br>
>> --<br>
>> Manik Surtani<br>
>> <a href="mailto:manik@jboss.org">manik@jboss.org</a><br>
>> Lead, Infinispan<br>
>> Lead, JBoss Cache<br>
>> <a href="http://www.infinispan.org" target="_blank">http://www.infinispan.org</a><br>
>> <a href="http://www.jbosscache.org" target="_blank">http://www.jbosscache.org</a><br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> infinispan-dev mailing list<br>
>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
><br>
<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a></div></div></blockquote></div><br></div>