[jboss-user] [JBoss Messaging] - Re: High volume usage patterns and best practices

"xxbrandonoxx" wrote : I am trying to implement a system that will require consistently high volume with long running and constantly connected clients. To date I have followed the samples included with JBoss Messaging and am creating a new connection+session+temp_response_queue on a per request basis. It was suggested that some of this is actually an anti-pattern. | Yes, that would certainly constitute an anti-pattern anonymous wrote : | This actually works fairly well and sufficiently fast on my local development environment aka, laptop, but breaks down when I promote it to a clustered development environment that is otherwise identical. I fairly quickly run out of memory, and get a 25+% failure rate even at low volumes. I am inclined to believe it is in part due to the way in which I am accessing the queue's and topics. | | I would like advice on the best way to handle the "pooling" of some of these objects (connections and sessions) for reuse. Is this advisable at all? If so, is there solution examples anyone is aware of? I would hate to have to create my own pooling logic with all the inherent issues in high volume systems. | You should have a look at the wiki, docs etc, this is a very common question. http://wiki.jboss.org/wiki/JBossJMSRA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177366#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...