[ https://jira.jboss.org/jira/browse/ISPN-133?page=com.atlassian.jira.plugi... ] Galder Zamarreno commented on ISPN-133: --------------------------------------- It appears that jclouds httpnio module is no longer in use, not sure why: http://fisheye.jboss.org/browse/Infinispan/trunk/cachestore/cloud/pom.xml... However, the VAM cloud integration tests are currently disabled, not sure why: http://fisheye.jboss.org/changelog/Infinispan/?cs=1435 Revisit this once these tests have been re-enabled or when httpnio module removal has been explained. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/ISPN-133?page=com.atlassian.jira.plugi... ] Galder Zamarreno edited comment on ISPN-133 at 4/19/10 9:24 AM: ---------------------------------------------------------------- ----- "Philippe Van Dyck" <pvdyck at gmail dot com> wrote: Interesting. It seems like it's not only Apache's HTTP client library that did not care much about available() implementations, but also JDK classes as well. I'd rather read on 1k batches than 1 byte batches. See things like this, I'm even less inclined to urgently look into https://jira.jboss.org/jira/browse/ISPN-133. was (Author: galder.zamarreno(a)jboss.com): ----- "Philippe Van Dyck" <pvdyck at gmail dot com> wrote: Interesting. It seems like it's not only Apache's HTTP client library that did not care much about available() implementations, but also JDK classes as well. I'd rather read on 1k batches than 1 byte batches. See things like this, I'm even less inclined to urgently look into https://jira.jboss.org/jira/browse/ISPN-133. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/ISPN-133?page=com.atlassian.jira.plugi... ] Galder Zamarreno edited comment on ISPN-133 at 4/19/10 9:24 AM: ---------------------------------------------------------------- ----- "Philippe Van Dyck" <pvdyck at gmail dot com> wrote: Interesting. It seems like it's not only Apache's HTTP client library that did not care much about available() implementations, but also JDK classes as well. I'd rather read on 1k batches than 1 byte batches. See things like this, I'm even less inclined to urgently look into ISPN-133. was (Author: galder.zamarreno(a)jboss.com): ----- "Philippe Van Dyck" <pvdyck at gmail dot com> wrote: Interesting. It seems like it's not only Apache's HTTP client library that did not care much about available() implementations, but also JDK classes as well. I'd rather read on 1k batches than 1 byte batches. See things like this, I'm even less inclined to urgently look into https://jira.jboss.org/jira/browse/ISPN-133. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-133?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño commented on ISPN-133: --------------------------------------- I've confirmed that HTTP Core ContentInputStream is no longer in use by JClouds. All input streams that JClouds relies on when reading from blobstores are backed by ByteArrayInputStream. So, the workaround should be removable. I've tested this connecting to S3 cache store. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-133?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño updated ISPN-133: ---------------------------------- Summary: Bring back inputStream.available() check (was: Upgrade JClouds to a version that depends on Apache HTTP Core that fixes HTTPCORE-199) Description: A temporary workaround was in place to get around: https://issues.apache.org/jira/browse/HTTPCORE-199 Remove temporary workaround in ISPN-119 as part of this: http://fisheye.jboss.org/browse/Infinispan/trunk/core/src/main/java/org/i... was: https://issues.apache.org/jira/browse/HTTPCORE-199 Remove temporary workaround in ISPN-119 as part of this: http://fisheye.jboss.org/browse/Infinispan/trunk/core/src/main/java/org/i... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-133?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño commented on ISPN-133: --------------------------------------- https://github.com/infinispan/infinispan/pull/111 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-133?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño updated ISPN-133: ---------------------------------- Fix Version/s: 5.0.0.ALPHA2 (was: 5.0.0.BETA1) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira