You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Wayne Fisher (JIRA)" <ji...@apache.org> on 2012/07/24 18:43:34 UTC
[jira] [Commented] (CB-587) CallbackServer.run() SocketException
on ICS 4.0.4
[ https://issues.apache.org/jira/browse/CB-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421524#comment-13421524 ]
Wayne Fisher commented on CB-587:
---------------------------------
Any progress or update on this issue?
A customer reported an issue to me related to this issue. This customer was unable to use the camera functionality of my app. When this exception occurs, it appears to take out all (or at least most of) PhoneGap's functionality.
This customer also had an in-app purchase not come through to him which is also likely related to this issue. My in-app purchases are implemented as a PhoneGap plugin, so if PhoneGap has died, then the plugin is also likely dead.
One difference for this customer is that he has 4.0.3 running on his Xoom instead of the 4.0.4 that is running on mine.
> 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: Anis Kadri
> Priority: Minor
> 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