[
https://issues.apache.org/jira/browse/CB-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne Fisher reopened CB-587:
-----------------------------
I had some difficulty reproducing the issue even when going back to the v1.7.0
example that I first used.
Then I realized that the WIFI on my Xoom has been more stable lately (don't
know why). Working on the theory that it is related to WIFI stability, I was
then able to reproduce the issue using both the v1.7.0 and v2.0.0 example apps.
I reproduced it in two ways.
First, I started the example app and tapped on "Toggle Accelerometer" to be
able to see the live updating of the accelerometer readings. Then I used the
settings app to turn off WIFI. Eclipse then caught the SocketException and the
accelerometer readings stopped being updated. I then let the app run and let
the exception occur and crash the thread and the accelerometer data remained
frozen.
Second, with WIFI back on, I restarted the app and started the accelerometer
again. I then took my Xoom outside and walked away from my access point until
it lost the network connection. The accelerometer data stopped updating around
the same time as the WIFI connection was lost. Bringing the Xoom back in and
view the LogCat, I saw the SocketException in the log.
So, it appears that the issue is related to the loss of the WIFI connection.
An interesting thing I noticed though, is that it is not all dead. The compass
reading continues to update even after the SocketException has occurred.
> CallbackServer.run() SocketException on ICS 4.0.4
> --------------------------------------------------
>
> Key: CB-587
> URL: https://issues.apache.org/jira/browse/CB-587
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 1.4.0, 1.7.0
> Environment: Motorola Xoom ICS 4.0.4.
> PhoneGap 1.7.0rc1 example application.
> Reporter: Wayne Fisher
> Assignee: Joe Bowser
> Priority: Minor
> Fix For: 2.1.0
>
> Attachments: log.txt
>
>
> I have recently started to see SocketExceptions from CallbackServer.run() on
> my Motorola Xoom. I don't know exactly when it started, but it would appear
> to line up with the update of the Xoom to ICS 4.0.4 that occurred a couple of
> weeks (or so) ago. I don't recall seeing it on the previous version of ICS
> (4.0.3?).
> The exception information from LogCat follows:
> {quote}
> 04-26 15:57:58.730: W/System.err(10655): java.net.SocketException: sendto
> failed: ETIMEDOUT (Connection timed out)
> 04-26 15:57:58.730: W/System.err(10655): at
> libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:496)
> 04-26 15:57:58.730: W/System.err(10655): at
> libcore.io.IoBridge.sendto(IoBridge.java:465)
> 04-26 15:57:58.740: W/System.err(10655): at
> java.net.PlainSocketImpl.write(PlainSocketImpl.java:507)
> 04-26 15:57:58.740: W/System.err(10655): at
> java.net.PlainSocketImpl.access$100(PlainSocketImpl.java:46)
> 04-26 15:57:58.740: W/System.err(10655): at
> java.net.PlainSocketImpl$PlainSocketOutputStream.write(PlainSocketImpl.java:269)
> 04-26 15:57:58.740: W/System.err(10655): at
> java.io.OutputStream.write(OutputStream.java:82)
> 04-26 15:57:58.740: W/System.err(10655): at
> java.io.DataOutputStream.writeBytes(DataOutputStream.java:156)
> 04-26 15:57:58.740: W/System.err(10655): at
> org.apache.cordova.CallbackServer.run(CallbackServer.java:275)
> 04-26 15:57:58.740: W/System.err(10655): at
> java.lang.Thread.run(Thread.java:856)
> 04-26 15:57:58.740: W/System.err(10655): Caused by:
> libcore.io.ErrnoException: sendto failed: ETIMEDOUT (Connection timed out)
> 04-26 15:57:58.740: W/System.err(10655): at
> libcore.io.Posix.sendtoBytes(Native Method)
> 04-26 15:57:58.750: W/System.err(10655): at
> libcore.io.Posix.sendto(Posix.java:146)
> 04-26 15:57:58.750: W/System.err(10655): at
> libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:177)
> 04-26 15:57:58.750: W/System.err(10655): at
> libcore.io.IoBridge.sendto(IoBridge.java:463)
> 04-26 15:57:58.750: W/System.err(10655): ... 7 more
> {quote}
> This may be related to another issue that I have noticed with ICS 4.0.4 which
> is that it drops the WIFI connection a lot. It drops it *WAY* more
> frequently than the previous version did even with "Keep Wi-Fi on during
> sleep" set to "Always".
> My app is based on PhoneGap v1.4.0. I see this exception with my app on the
> Xoom. I have not seen it on my Samsung Galaxy S with 2.3.3 on it.
> The LogCat information above is from the 1.7.0rc1. For this test I simply
> created a new Android application in Eclipse using the Android example code
> as is. The exception happens even without interacting with the example app.
> Just leave it sit there and eventually... boom.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
