No. It's use-case specific. You'll have to benchmark it out on your hardware with your specific use cases.
One important thing to consider is that you've planned accordingly for producer flow control, ie, that you're not going to get in a situation where you have multiple producers/consumers on a connection, but you hit producer flow control which blocks the entire connection. See http://activemq.apache.org/producer-flow-control.html for more On Mon, Jul 29, 2013 at 6:32 AM, Oleg Dulin <oleg.du...@gmail.com> wrote: > Is there any guidelines on how many sessions per connection, and how many > producers/consumers per session I can have ? > > On 2013-07-25 22:24:45 +0000, Christian Posta said: > > --001a1133fb5450436104e25d7e16 >> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> >> >> >> There are no hard and fast rules. >> >> >> >> Guess it depends on the complexity of the app, the number of >> >> consumers/producers, message throughput requirements, etc. >> >> >> >> One connection can support lots of sessions and each session can support >> >> lots of producers and consumers... >> >> >> >> >> >> On Thu, Jul 25, 2013 at 5:14 PM, Oleg Dulin <oleg.du...@gmail.com> wrote: >> >> >> >> > Can I have a single connection for the entire application ? >> >> > >> >> > Is there an argument for multiple ? >> >> > >> >> > What's the right approach ? >> >> > >> >> > -- >> >> > Regards, >> >> > Oleg Dulin >> >> > http://www.olegdulin.com >> >> > >> >> > >> >> > >> >> >> >> >> >> -- >> >> *Christian Posta* >> >> http://www.christianposta.com/**blog <http://www.christianposta.com/blog> >> >> twitter: @christianposta >> >> >> >> --**001a1133fb5450436104e25d7e16-- >> >> >> >> > > -- > Regards, > Oleg Dulin > http://www.olegdulin.com > > > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
