What steps will reproduce the problem?
This seems to be a sporadic issue we have noticed on 32-bit and 64-bit Windows.
We see exceptions with the message:
"Exception in thread "BlueCoveEmulatorCommandReceiver"
java.lang.RuntimeException: No such device 0B1000000000
at com.intel.bluetooth.emu.DeviceManagerServiceImpl.pollCommand(DeviceManagerServiceImpl.java:110)
at $Proxy11.pollCommand(Unknown Source)
at
com.intel.bluetooth.EmulatorCommandReceiver.run(EmulatorCommandReceiver.java:59)
"
We have some tests that run using the emulator that then unload the bluecove
library. Despite unloading the library, we see the message above, sometime
after we have made the call to unload the library. What is interesting is we do
not use device ID '0B1000000000' but we use '00000000000' with the emulator.
The sporadic started showing up after migrating to Java 7.
A quick online search showed up similar exceptions. See here:
http://pyx4j.com/cruisecontrol-public/buildresults/bluecove-nightly-linux32?log=
log20090914221216&tab=buildResults
http://pyx4j.com/cruisecontrol-public/buildresults/bluecove-nightly-linux32?log=
log20090913164903
What is the expected output? What do you see instead?
I do not expect to see exceptions being thrown, after the emulator has been
unloaded. If there is an exception, I expect it to happen when the library is
still loaded in memory.
Please use labels and text to provide additional information.
Please use "Attach a file" when uploading stack traces or other big files!
Exception message attached.
Original issue reported on code.google.com by vinod.ch...@gmail.com on 18 Feb 2013 at 6:41
Original issue reported on code.google.com by
vinod.ch...@gmail.comon 18 Feb 2013 at 6:41Attachments: