Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.
SocketConnection is terminated with IOException when access point is disconnected (Known Issue)
In Symbian^3, there are certain issues related to connecting localhost with SocketConnection.
- First, connecting to localhost by using SocketConnection causes the default access point (mobile network or WLAN) to connect alongside with the actual localhost connection.
- Second, if the user stops an active socket connection from Connection Manager or the access point goes down due to being out of coverage, the socket connection is also terminated and IOException will be thrown by the MIDlet. It will not be possible to reconnect the socket until the MIDlet is restarted.
In previous Editions prior to Symbian^3, the established socket connection would stay connected even if the access point was disconnected.
Steps to reproduce the problem
- Create a MIDlet which connects localhost as follows:
- Create a native application which will work as a server that listens to the localhost port (here: 7990).
- Connect the MIDlet to localhost. The default access point is started.
- Connection is established and socket is connected.
- Go to Connection Manager and disconnect the default access point.
These issues are expected to be fixed in future firmware releases for the affected devices.