[JCLOUDS-181] Blobstores that lack proper support for 100-Continue don't work with JDK7

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6.1
• Fix Version/s: 1.6.2, 1.7.0
• Component/s: jclouds-blobstore
• Assignee: Andrew Phillips
• Reporter: Diwaker Gupta
• Created: 10/Jul/13 18:16
• Updated: 25/Jun/15 21:16
• Resolved: 13/Nov/13 23:49

Description

jclouds added the "Expect: 100-Continue" to the putBlob API for most blobstores sometime back. Handling of 100-continue differs between JDK6 and JDK7 in that unlike JDK6, JDK7 will expect a response from the server and will only time out IF a read timeout has been set on the underlying HTTP connection [1].

As a result, if applications set Constants.PROPERTY_SO_TIMEOUT and use a blobstore that doesn't properly support the Expect header (i.e., doesn't respond with 100-Continue) on JDK7, the putBlob operation will essentially hang forever.

Specifically, both HPCS and Google Cloud Storage are impacted by this.

[1] http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/7-b147/sun/net/www/protocol/http/HttpURLConnection.java?av=f#1008

Issue Links

• is duplicated by: JCLOUDS-905 Expect: 100-Continue + SSL = timeout
• relates to: JCLOUDS-905 Expect: 100-Continue + SSL = timeout