[olepogam]

Hi,

I have a weird problem !

My MIDlet does a device / service inquiry. I can exit / run the midlet several times the device / service search still works fine (my devices are found, and the service I expose too).

However, once I have made a connection to the server in my midlet (a linux BlueZ one), closed both data streams (datainput / dataoutput) and closed the connector itself, if I exit the midlet and restart it, the device I was connected to does not appear in the list of devices anymore (even in CACHED and PREKNOWN).

Do you think it's a problem when reading the CACHED, or the connection still active even if closed all ? (I've noticed that restarting my Linux box solves the issue, next time I start the MIDlet I can see the device again)

Can anybody help me ? If you need more details I will provide you with some code.

Thanks a lot,
Oli

[edazcnokia]

Hi.
Your problem is obviously outside your midlet. If you fix it restarting the server application then you could try restarting the service instead. I mean close streams and connection in the server, then call Connector.Open and AcceptAndOpen again. This should work.

With BlueZ I had a similar problem (only one connection was possible) that was suppossed to be fixed by closing everything and calling AcceptAndOpen again (this is, publishing the service in the SDDB again), but not... I had to re-create the service for every new connection needed using Connector.Open function.

Edazc

[olepogam]

Hi,

Thanks a lot for your answer. So in your opinion, the problem is in my BlueZ server linux box which is not stopping the connection even when the MIDlet is closed ?

I have tried :
- To kill the server GNU C server and to restart it
- To kill the server, remove the service with sdptool and relaunch the server

Both have not worked.

It has only worked (if I remember correctly) when I have stopped / restarted the device (the bluetooth key) using hciconfig ... This is a worrying solution !!

Could you please tell me how you managed this ??

Thanks a lot,
Oli

[edazcnokia]

Hello. I forgot to tell u that I'm not working directly with BlueZ, but with Avetana JSR-82 libraries which in turn call BlueZ functions. So I speak Java :-).

Originally Posted by olepogam

So in your opinion, the problem is in my BlueZ server linux box which is not stopping the connection even when the MIDlet is closed ?

Yes.

Originally Posted by olepogam

I have tried :
- To kill the server GNU C server and to restart it
- To kill the server, remove the service with sdptool and relaunch the server

I would expect the second option works, since it is equivalent to my solution in Java, when I re-create the notifier using connector.open().

Restarting the device is not a good solution for me either, since this would not allow for concurrent connections, there must be something else. I suggest you to provide some source code of your server, this perhaps helps me or some of our friends in this forum find the solution to the only-one-connection problem.