[Priju Jacob Paul]

hi all,
Im working on an BT application.The thing is that i need to send a notification to the other mobile phone user asking him to open my application and connect to mine.
Hence forth i used OBEX to connect and send a message which goes to his inbox.

now,as the obex servers are not able to send messages to the client i need to transfer the connection to RFCOMM and proceed with the chat!

I have done all these part.But the problem is with the swtiching between OBEX and RFCOMM.

Even thogh i disconnect (closing the server and the client) im not able to connect immediately.i get the message like "Maximum amount of bluetooth connections in use.Cant establish a new one"
Why is that so?
Can any of you please suggest me how to recover from this problem.I need to switch the connecting protcols by staying with in the application.If i exit from the application and try again it works fine..
PLEASE HELP ME OUT!!!

Regards

Priju

[jimgilmour1]

Hi,I dont know whose OBEX stack you are using on PC. I am assuming you are using XP SP2 bluecove and de.aventena. I use these because they are free so I will talk about these as I have source code for these.
Typically they are run in a seperate Thread. This thread is not accessible once started therefore after a Thread m.start(); we need an m.join() to get back.
When you opened the session with btgeop:// and recieved a SessionNotifer back as a result from the acceptAndOpen, did you know that is really a btspp:// connection that goes out and has to be replied with btspp://.

Because of this I have cast my returned SessionNotifier as a StreamNotifier.
----------------------------------------------------------------
String url = "btgoep://localhost:" + uuid + ";name=BTTP;authenticate=false;master=false;encrypt=false";


try{

// obtain connection and stream to this service
btServerNotifier = (StreamConnectionNotifier) Connector.open( url );
} catch ( Exception e) {
e.printStackTrace();
}

while (mServerState )
{
StreamConnection btConn = null;
try {
updateStatus("[server:] Now waiting for a client to connect");

btConn = btServerNotifier.acceptAndOpen();
} catch (IOException ioe) {

}
if (btConn != null) processConnection(btConn);
}

}
---------------------------------------------------------------------
This means I can open the connection and hang on to it and I can open and close channel. I do however lose the benifit of the File transfer functions onGet and onPut.

Have you checked the channels with
try { op.close}
catch (IOexception) { System.out.put("the channel was closed");}
To see if its really closed?.

my process code calls a new Thread and needs to .join before I can close and leave the code.
Sorry if this is vague but there is so much variance is systems today.
In Java everyone has there own setup.
Good Luck

Jim

[jimgilmour1]

Reading the specification I see CLDC 1.0 supports

On actual devices this is limited to the non parked
connection use case, which leaves the figure at 7.

Please can you check the values of bluetooth :-
using
public static String propertyValue = LocalDevice localDevice.getProperty("bluetooth.connected.devices.max");
//The maximum number of connected devices supported.
//This number may be greater than 7 if the implementation handles parked connections.
//The string will be in Base 10 digits.

public static String propertyValue = LocalDevice localDevice.getProperty("bluetooth.sd.trans.max");
//Maximum number of concurrent service discovery transactions. The string will be in Base 10 digits.

Well I just hope its java you are working in.
Good Luck
Jim

[Priju Jacob Paul]

Hi Jim,
im sorry for not keeping you updated.anyway thanks a ton for the reply.That project is all up..and for your kind information im not onto Java.Im working in c++.
GoodLuck!
Regards
Priju