Hi Jon, I haven't had the opportunity to compile to the latest Alpha just yet, but I am planning on doing that this weekend once I tie up some loose ends. Once I am on Alpha I will keep an eye out for this, I did some tidying up of the code above with wrapping the streams in using blocks, removing the finally, and checking for null in a couple of places. This will not remove the premature termination of the connection but I after about 6 hours of investigation with this I think the following is whats happening:
1. The connection is getting prematurely terminated. 2. This causes an exception of type WebException with message "An error occurred while processing the request." which aligns with the following MSDN article: http://msdn.microsoft.com/en-us/library/system.net.httpwebrequest.endgetresponse.aspx but the reason is uknown... 3. Since I am calling EndGetResponse in an async callback from a seperate thread the exception is occuring on a background worker thread 4. Since the exception occurs on a background worker thread I am not seeing the error in this instance, additionally inside my try/catch block I was attempting to pull out the error message from the WebResponse which was null 5. Since another error occured inside my try/catch it was fatal and uncaught therefore terminating the application. So, all in all I do not believe it was not Java related. Although I am still unclear why LogCat had no data on the exception...Additionally the debugger would not offer my a callstack when the exception occured so I could not trace the issue. -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/GetResponseStream-ReadToEnd-Fatal-Exception-tp5627778p5631328.html Sent from the Mono for Android mailing list archive at Nabble.com. _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
