Message-ID: <41668ADE.7010004@uni-paderborn.de>
From: Stefan Mischke <survivor@uni-paderborn.de>
MIME-Version: 1.0
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Subject: [Bluez-devel] read_RSSI and others not thread-safe?
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Date: Fri, 08 Oct 2004 14:41:02 +0200

Hello!

I've written a small JBlueZ-like JNI-Library which gives Java access to 
BlueZ. My demo application has one threads for each connection (two at 
the moment) which concurrently do read_RSSI, read_Transmit_Power_Level 
and read_Link_Quality. If by random two threads do one, two or all three 
of these calls at the same time, the result values are equal (although 
they can't be since one connection is really bad). This doesn't happen 
if I declace the three functions "synchronized" in the Java part of the 
JNI. But this should not be necessary, should it? Since my functions 
only use by-value parameters and local variables, they should be 
thread-safe. I also figured out that the BlueZ sockets in these calls 
are unequal, but the result (RSSI value) is equal. Why can this happen?

I wonder if this could also occour on one of the other, more important 
functions like l2cap_read/write. Any idea? Thanks!

Regards
Stefan


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel