Could you please be a bit more specific ?<div>Are there any test to confirm the closing of the bug ?</div><div>Is it in trunk ?</div><div><br></div><div>That sounds like a really good news ;-)</div><div><br></div><div>phil<br>
<br><div class="gmail_quote">On Thu, Jan 28, 2010 at 6:10 PM, Galder Zamarreno <span dir="ltr"><<a href="mailto:galder@jboss.org">galder@jboss.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
This is done now.<br>
<div><div></div><div class="h5"><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 on JIRA<br>
>> are limited.<br>
>> I would really need this - performance impact is high - and hope 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 store.<br>
>>> I don't know if JBoss Cache had the same issue or not, but for many<br>
>>> use-cases (including ours) one will need both TX and 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 Dyck<<a href="mailto:pvdyck@gmail.com">pvdyck@gmail.com</a>> 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 CacheStore, so I<br>
>>>> would like it to be a "performance bug".<br>
>>>> WDYT ... especially regarding the planning of the next release ?<br>
>>>> Phil<br>
>>>> On Tue, Jan 26, 2010 at 11:28 AM, Amin Abbaspour<<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<<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 sounds to<br>
>>>>>> flush to normal store at the TX commit but when one knowingly sets<br>
>>>>>> store as async, he accepts the risk of consistence in favor of 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 Dyck<<a href="mailto:pvdyck@gmail.com">pvdyck@gmail.com</a>><br>
>>>>>> wrote:<br>
>>>>>>> I do confirm this behavior.<br>
>>>>>>> Transactions and asynchronous updates may seem antagonistic, but they<br>
>>>>>>> are<br>
>>>>>>> not on a multi-level cache.<br>
>>>>>>> I plan to use a synchronous transactional disk cache and a second non<br>
>>>>>>> transactional asynchronous s3 cache, to get the best of both worlds.<br>
>>>>>>> Since the asynchronous aspect of the s3 cache will not allow me to get<br>
>>>>>>> any<br>
>>>>>>> feedback (aka Future), I want it to 'write-behind' in the background<br>
>>>>>>> (and<br>
>>>>>>> hope everything goes well).<br>
>>>>>>> I will wait for the qi4j v1 release (probably Monday), adapt infinispan<br>
>>>>>>> to<br>
>>>>>>> the blobstore of jClouds and take a closer look at this in a couple 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>
>>>>>>>> <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 inside a<br>
>>>>>>>> transaction boundary it is always stored synchronously! Why is it so?<br>
>>>>>>>> How can I have both locking and async store. FYI I use 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>
</div></div><font color="#888888">--<br>
Galder Zamarreńo<br>
Sr. Software Engineer<br>
Infinispan, JBoss Cache<br>
</font><div><div></div><div class="h5">_______________________________________________<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>