-
Notifications
You must be signed in to change notification settings - Fork 60
socketexception, trying to play video, embedded in couchapp #91
Comments
I've managed to get a full stacktrace |
Found the problem: This actually refers to an android bug: |
Unfortunately, the app does not crash and there is no stack trace, so I cannot
precisely tell, where it actually happens. Only thing I have are messages in the log.
here is the related log output from eclipse
...................
03-19 17:58:19.862: W/System.err(3446): [Tue Mar 19 17:58:19 CET 2013] TJWS: IO error: java.net.SocketException: sendto failed: ECONNRESET (Connection reset by peer) in processing a request from /127.0.0.1:8888 / java.net.Socket
03-19 17:58:19.862: V/TDDatabase(3446): Buffer size is 128
03-19 17:58:19.892: W/System.err(3446): [Tue Mar 19 17:58:19 CET 2013] TJWS: IO error: java.net.SocketException: sendto failed: ECONNRESET (Connection reset by peer) in processing a request from /127.0.0.1:8888 / java.net.Socket
03-19 17:58:19.892: E/MediaPlayer(3446): error (1, -2147483648)
03-19 17:58:19.892: E/MediaPlayer(3446): Error (1,-2147483648)
...................
adb logcat show this
...................
D/dalvikvm( 3446): GC_FOR_ALLOC freed 263K, 9% free 7989K/8716K, paused 15ms, total 15ms
I/ChromiumHTTPDataSourceSupport( 128): We requested a content range, but server didn't support that. (responded with 200)
E/NuCachedSource2( 128): source returned error -32, 0 retries left
W/System.err( 3446): [Tue Mar 19 17:58:19 CET 2013] TJWS: IO error: java.net.SocketException: sendto failed: ECONNRESET (Connection reset by peer) in processing a request from /127.0.0.1:8888 / java.net.Socket
E/MediaPlayer( 3446): error (1, -2147483648)
...................
The page I try to load, obviously has a video and it works fine in a test application with a webview. However the test app does not include it's own webserver, but loads the page through a server on another machine.
I am still unsure, if this is actually a problem with the acme server that touchdb uses, or with some part of the client. The output from adb logcat indicates that there might be something wrong with the acme server.
The text was updated successfully, but these errors were encountered: