Re: WOHttpIO - Dreained socket
Re: WOHttpIO - Dreained socket
- Subject: Re: WOHttpIO - Dreained socket
- From: David LeBer <email@hidden>
- Date: Sat, 22 Sep 2007 15:09:55 -0400
On 22-Sep-07, at 2:46 PM, Pascal Robert wrote:
Le 07-09-22 à 13:38, Chuck Hill a écrit :
I have seen this before, but I don't recall why. Is the app using
streamed uploads? This might be the user hitting stop.
Should throw a "java.io.IOException: Connection reset by peer:
Amount read didn't match content-length" error when someone stop
the request during a file upload.
BUT I'm rewriting the server part of a Flex app, and when I'm
calling the DirectAction from the Flex app, and I got the same
error as David :
sept. 22 14:44:54 FlexFileUploadServer[5002] (WOHttpIO.java:396)
DEBUG com.webobjects.appserver._private.WOHttpIO - Drained socket
sept. 22 14:44:54 FlexFileUploadServer[5002] (WOHttpIO.java:396)
DEBUG com.webobjects.appserver._private.WOHttpIO - Drained socket
David, does your app use DA for file upload ?
Nope.
I was seeing this all over the place, but I've 're-factored'
extensively and now I just see it on WOFileUploads (non-streaming -
NSData and component action based).
I did a test app, and I'm seeing it there as well. Both are Wonder
based, so maybe it's there or maybe my environment?
As I said, everything seems to be working OK, it's just a little
disconcerting to see that in the log.
;david
--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site: http://codeferous.com
blog: http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden