linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pedro Monjo Florit <pedro.monjo@futurlink.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Multiple Bluetooth connections
Date: Tue, 15 Mar 2005 19:48:42 +0100	[thread overview]
Message-ID: <42372E0A.80002@futurlink.com> (raw)

Hi,

In the application that I am developing, I want to send simultaneous 
OBEX messages to different OBEX servers over Bluetooth. I am using 
OpenOBEX for this purpose. There are two problems I am facing.

On the one hand, it seems that there is only room to establish one 
Bluetooth connection at a time. If I start many OBEX pushes 
simultaneously, only the first one succeeds. The others fail usually 
with error "Device or resource busy" (errno=16); sometimes even with 
"Software caused connection abort" (errno=103). Once the first 
connection is established and while sending OBEX data, I can establish 
another connection.

I just want to make clear that the problem is with the establishment of 
the connection. I am fully aware that it is possible to handle various 
on-going connections with no problems and I have succeeded with that. Is 
there a limitation with Bluetooth or BlueZ that allows only one RFCOMM, 
L2CAP or HCI connection establishment?

On the other hand, some connections die before sending the data, but it 
seems that the file descriptor of this connection does not receive any 
notification (I use select() on all file descriptors, with the file 
descriptor in the read mask). I know that this could be due to a problem 
with my program, a problem with OpenOBEX or the BlueZ version I am using 
(it is not the latest). In any case, to track down the cause, I would 
like to know how can I monitor the Bluetooth connections (at any level, 
but preferably RFCOMM) that a process (or the whole system) has. What I 
am looking for is a tool like netstat.

Thanks & regards,

Pedro Monjo


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2005-03-15 18:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 18:48 Pedro Monjo Florit [this message]
2005-03-15 19:27 ` [Bluez-users] Multiple Bluetooth connections sir
2005-03-16  9:42 ` Marcel Holtmann
2005-03-16 11:23   ` Pedro Monjo Florit
2005-03-16 11:44     ` Marcel Holtmann
     [not found]   ` <marcel@holtmann.org>
2005-03-16 10:40     ` Peter Stephenson
2018-10-30 10:24     ` [PATCH v2] Bluetooth: Support fast advertising interval Bharat Bhusan Panda
2018-11-13  9:00       ` Panda, Bharat B
2018-11-23 10:52         ` Panda, Bharat B
2018-12-07 12:34           ` Panda, Bharat B
2018-12-18 23:30       ` Marcel Holtmann
2019-02-04  9:10         ` Panda, Bharat B

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42372E0A.80002@futurlink.com \
    --to=pedro.monjo@futurlink.com \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).