Hi James, Thanks for the info, I understand what is happening now and can work around it in my application.
James.Strachan wrote: > > So the reason for this is that currently there is a single thread per > connection processing server side operations. Normally these > operations are pretty fast; but if a producer is blocked, currently we > block the producer thread (to stopt it potentially sending more > messages and causing more trouble). > > So if you are getting into scenarios of blocking producers, its > probably worth having a separate connection for all your consumers. > Is the single thread per connection on the broker a deliberate design choice for ActiveMQ? It would appear to violate the JMS spec in this situation of blocked producers. Would it be possible to change ActiveMQ to have a separate thread for consumers on a per connection basis in the broker? James.Strachan wrote: > > Another option is to try out 4.2-SNAPSHOT which has spooling to disk > as an option (as an alternative to blocking producers). > We won’t be able to use the spooling to disk in 4.2 for this part of our application as it is performance critical and cannot allow messaging to be disk bound, but this does seems like a good option to have for other situations. Thanks, Tony -- View this message in context: http://www.nabble.com/Consumer-blocking-when-session-created-on-same-connection-as-blocked-producer-tf3294332s2354.html#a9183644 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
