Bluetooth Android server asserts if disposed too quickly after listen()

On Android:

If one initiates a QBluetoothServer::listen() and then quickly destroys the server, the internal ServerAcceptanceThread asserts because isRunning() is still true in it's destructor, in spite of the close() call. The close() may have been called manually or by the server destructor.

This seems to happen when the Java-side run() is in the middle of
time-consuming synchronous "listenUsing*RfcommWithServiceRecord()" call and therefore the interruption and stop is not immediate but will happen only after that function returns.