KIJ000331 - Lack of thread safety in TCP implementation

Lack of thread safety in TCP implementation		KIJ000331
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.
Reported against	Series 40 1st Edition, Series 40 2nd Edition
Date identified	April 21, 2006
Symptoms	-
Detailed 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
How to reproduce	-
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.

Related Discussions
Thread	Thread Starter	Forum	Replies	Last Post
unablet to get response from server using tcp	qasitouch	Mobile Java Networking & Messaging & Security	4	2006-12-22 05:12
GDSMS Example 'Lack of Resources' error	Nokia_Archive	General Symbian C++	2	2003-07-29 11:51
7210, 3530 support http?	tangxj	Mobile Java General	3	1970-01-01 02:00
Destructor of Server in Server / Client	kovacc	General Symbian C++	1	2002-10-09 07:17
2.0 SDK documentation Correction: SNAP-Mobile-URLs JAD parameter	staceyduke	SNAP Mobile	0	2008-05-21 18:56