From: Steve L. (JIRA) <ji...@sm...> - 2010-10-29 14:42:11
|
[ http://jira.smartfrog.org/jira/browse/SFOS-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12303#action_12303 ] Steve Loughran commented on SFOS-1476: -------------------------------------- Large IO operations are failing -integer size limits? //client thinks it is about to put up 3GB of content [sf-startdaemon-debug] 2010/10/29 15:37:16:148 BST [INFO ][Thread-412] HOST morzine.hpl.hp.com:rootProcess:bulkioput - Uploading 3221225472 bytes to http://127.0.0.1:5050/upload //server gets -1 bytes and no content-type [sf-startdaemon-debug] 2010/10/29 15:37:16:150 BST [INFO ][170524181@JettySocketThread-5] org.smartfrog.services.www.bulkio.server.AbstractBulkioServlet - PUT operation receiving -1 bytes of type null [sf-startdaemon-debug] 2010/10/29 15:37:16:150 BST [INFO ][170524181@JettySocketThread-5] org.smartfrog.services.www.bulkio.server.AbstractBulkioServlet - Checksum : 0 [sf-startdaemon-debug] 2010/10/29 15:37:16:150 BST [INFO ][170524181@JettySocketThread-5] org.smartfrog.services.www.bulkio.server.AbstractBulkioServlet - #summary [sf-startdaemon-debug] bytes.read=0 [sf-startdaemon-debug] bytes.expected=-1 [sf-startdaemon-debug] content.length=-1 [sf-startdaemon-debug] content.type=null [sf-startdaemon-debug] checksum=0 tests proceed to fail > add tests for big data upload/download and long-lived connections > ----------------------------------------------------------------- > > Key: SFOS-1476 > URL: http://jira.smartfrog.org/jira/browse/SFOS-1476 > Project: SmartFrog > Issue Type: New Feature > Components: _service_www > Affects Versions: 3.18.x > Reporter: Steve Loughran > Assignee: Steve Loughran > Original Estimate: 1 day > Remaining Estimate: 1 day > > We want to see how the various web servers handle big data uploads and downloads (in the GB range) and long-lived connections. The goal here is to be confident that Jetty and JAX-RS can handle large quantities of data and long lived connections, even with proxies and the like in the way. > Proposed > -client upload code you can create and configure to upload or download generating data on the fly > -matching servlet to return the #of bytes uploaded and some simple CRC-class of hash of the data (feature creep) > -servlet to serve up a specified amount of data > -client to expect that much downloaded. > -client to work over HTTPS as well as HTTP, take a certificate > -client to support a throttle option that takes a bandwidth and holds back > -SF component to deploy this upload code as a workflow > -test against Jetty to run this against a local jetty instance > -ability to test against more complex deployments, such as with proxies, NAT, firewalls. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.smartfrog.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |