Open GoogleCodeExporter opened 9 years ago
Updating...
Today I ran the same test under version 2.1.1 SNAPSHOT.47 and it still
happened. The
"No such service is known. (...)" message seemed to appear faster than before,
though
it might be just coincidence.
I also tested it all under Linux to see what happened and it all seemed to work
(since this seems like a concurrecy issue, it's hard to be sure, but I tried to
break
it unsuccessfully for a while and it stood up working).
I'm guessing the MS stack doesn't do well on some concurrent situation of
inquiring
while accepting connections and melts down. Should that be the case, I guess
the
question left would be if there's a way the application could detect that melt
down
(so an automated restart of the application can be provided, for example), or
perhaps
some way to detect it and restart it all from under the covers. In my case, the
worst
of all is that the server keeps working completely unaware it's unable to
neither see
nor hear anything anymore.
I don't think I'd be able to fix this by myself, but I'be happy to perform the
tests
on anything someone with the proper skills would do to fix it, though.
Thanks to anyone who had the patience to read it all. Sorry if I got way too
verbose
with it.
Original comment by andre....@gmail.com
on 10 Jun 2009 at 2:16
Lets try a short reply:
Can you use some other more stable USB Dongle on Windows, Like one from MS
Microsoft Wireless Transceiver for Bluetooth v3.0
Does it makes the differences?
Original comment by skarzhev...@gmail.com
on 10 Jun 2009 at 4:30
Hi skarzhevskyy,
Thanks for the reply.
Unfortunately I haven't seen one of these 3.0 devices around here to buy it and
try
it yet. But I did try more than one brand of 2.0 devices unsuccessfully. I'll
try to
put my hands on one of the devices on that list on the site, and I believe I
can
manage to try it on some widcomm device too, would that help on anything?
But are the devices really that platform dependent? As I said, on Bluez all the
same
devices worked fine, and the problem just rises on Windows XP when I put the
server
under stress, otherwise it works smoothly too.
Original comment by andre....@gmail.com
on 10 Jun 2009 at 1:49
I think that there are some problem in MS stack......
I also used D-Link DBT-120 under stress. It is not Bluetooth v2.0 + ERD but
works
fine under stress on MS...
Original comment by skarzhev...@gmail.com
on 10 Jun 2009 at 2:02
I was actually hoping to use one of those extended range 2 Km devices. It was
only
when I started having these problems that I started testing it on different
devices
to get a big picture of what was the issue. I guess MS don't want a Windows XP
version of any more complex BT applications.
A couple of last questions:
1) By looks on the log after the stack starts failing, shouldn't the
deviceInquiryStartedCallback be called with false instead of true, and only
after the
part where the WSALookupServiceBegin returns?
2) Would it be possible to perform some action after WSALookupServiceBegin
fails with
that "No such service is known." message, maybe something like close everything
up an
restart the BT service to make the stack return to a funcional state? Since at
this
point nothing else is working anymore, I don't see why dropping it all would
hurt anyone.
Original comment by andre....@gmail.com
on 10 Jun 2009 at 2:57
I don't know how to restart MS stack other then reboot computer.
And the function WSALookupServiceBegin returns only after discovery is
completed to
the best of my knowledge..... You can try to debug it and see. Pay attention
to the
time in the log
Original comment by skarzhev...@gmail.com
on 10 Jun 2009 at 3:22
Actually, I meant the restart of the BlueCove parts. I noticed there's a
shutdown
hook which I assume does some cleaning up before the VM exits, and since most
of the
time just restarting the application seems to fix this inconsistent state, I
figured
it might be because some of this cleaning (or perhaps the initilization of the
library again) actually restores the MS Stack to a usefull state. Otherwise I
guess a
full computer restart would be needed.
If that's the case, I think cleaning up and starting all over would be
preferable
over the blind and deaf state the application got stuck (completely unaware
that it
is in it).
Original comment by andre....@gmail.com
on 10 Jun 2009 at 6:01
I figured it could be a workaround for the situation, since MS is busy trying
to get
rid of XP and shove Vista down our throats and if they bothered to fix this, it
probably wouldn't be released for XP.
Original comment by andre....@gmail.com
on 10 Jun 2009 at 6:05
Original issue reported on code.google.com by
andre....@gmail.com
on 8 Jun 2009 at 10:53Attachments: