activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hackingbear <hackingb...@gmail.com>
Subject Number of JMS connections per app server
Date Fri, 26 Jun 2009 16:12:33 GMT

Hi,

Our server currently creates one JMS connection and then create sessions for
each listener. So it means all listeners are sharing the sae connection. I
believe this is the standard JMS practice. The question whether such
arrangement would affect performance. i.e. could a slow listener blocks the
traffic of other incoming and outgoing JMS messages?

I would understand that JMS broker should multiplex the messages into the
final TCP/IP connection. but the application codes and the JMS broker are
running in Java which would be much slower than raw TCP/IP connections. so
even if the listeners are running in multiple thread, but would one
sending/receiver still block others more than necessary?

Should I change the use more than one JMS connections in a server?

Thanks a lot!

-- 
View this message in context: http://www.nabble.com/Number-of-JMS-connections-per-app-server-tp24223068p24223068.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message