Stephen Pietrowicz wrote: > > After looking through the archives, we tried setting > "producerFlowControl=false", which fixed the problem.
Stephen, thanks for that tip...by setting producerFlowControl="false" in activemq.xml, that seems to have solved the issue! Seems like memory is now the only limit (easily fixed). Thanks very much for pointing me in the producerFlowControl direction! I guess I'm still a bit curious how to get each producerTemplate.sendBody(endpoint, message) to send/commit the message "immediately" as opposed to having them all buffer up or queue up until the currently executing transaction finishes. I tried using cacheLevelName=CACHE_NONE to see if I could get it to use a separate connection/session, but that didn't seem to affect anything. Any tips on how to produce in separate transactions would be much appreciated! Thanks again. -- View this message in context: http://www.nabble.com/BUG%3A-JMS-consumer-hangs-while-producing-profusely-tp23833387p23838176.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
