Archived:Lack of thread safety in Java ME TCP implementation on Series 40 1st and 2nd Edition (Known Issue)
Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.
Article Metadata
Compatibility
Platform(s): Series 40 1st Edition, Series 40 2nd Edition
Article
Created: User:Technical writer 1
(21 Apr 2006)
Last edited: hamishwillee
(28 Jun 2012)
Overview
There is a known race condition in the Java networking code for TCP, UDP, and SSL. In certain situations the code gets into an unstable state and remains unstable until all the operations have completed.
Description
There is a known race condition in the Java networking code for TCP(, UDP, and SSL) in S40 devices. If more than one thread does any combination of these (not necessarily on the same socket): opening, reading, writing; the code gets in to an unstable state and the phone is likely to crash if any of these happen:
- The connection drops (red end key, loss of signal, etc.)
- Problems with a socket (remote host closes TCP connection or refuses new TCP connection, SSL certificate problems, etc.)
- Almost anything else that would throw an IOException
Solution
No solution exists for Series 40 1st Edition and Series 40 2nd Edition. Avoid running multiple socket operations simultaneously.
This issue is fixed in the Series 40 3rd Edition devices.
(no comments yet)