Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (athena.apache.org: domain of zhihua.che@gmail.com
 designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
Date: Tue, 26 Jun 2012 21:46:48 +0800
Message-ID: 
 <CABexPfGP51B415AaQTC-KqjPZuFy7cHv4aRAFqV_f7Jv6DssRg@mail.gmail.com>
Subject: ThreadSafe/Multiple Session/Connection handling
From: Zhihua Che <zhihua.che@gmail.com>
To: users <users@qpid.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi,
    I'm employing qpid in my current project and need some tips for
common programming practice.

1, Are Sender/Receiver/Session/Connection  thread-safe?
    ie, Is it ok for multiple threads to send messages through the
same sender, or to create senders/receivers through the same session.
2, When do I need to create a separate session?
    I know it's feasible to create more than one session in one
application/process, but, I wonder when it's reasonable to create two
session, instead of only one.
3, How do I handle the connection lost or sending/receiving failure?
    In my application, sending/receiving fails occasionally with an
exception throw. What can I do to fix it and take another try
initiatively at  runtime if I refuse to exit the process?
    Is it reasonable to open the connection again and create new
senders and receivers to take a new try?
    I know there is reconnect option for the Connection. But It cannot
keep connection alive forever, right?
    Furthermore, I find qpid client api doesn't offer a connection
pool mechanism, Does that mean I need to implement one by myself if I
want or the connection pool is not recommended?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org