Hey Reading the explanation of your problem, I would suspect that it is a design issue and hardware limitations. Here is what I think. You probably have a single processor machine and while publishing the messages in the loop you taking most of the resources of the machine. Also, since message processing is asynchronous by nature, I doubt there is a way to reliably send a message and expect it's retrival before the next message arrives. I also don't think that your out of memory problem has to do with the amount of messages, since JBossMQ should start softening them once it reaches certain limit. Check how you are handling a connection. The only reason why I am saying that is I just got back from the customer call and observed the out of memory problem due to the fact that client would open up a new connection to send a message every time without disposing the old one. There was more open sockets on the server then it could handle and thus it choked. Hope it helps, but then again, these are just thoughts.
Regards Oleg Zhurakousky View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3950420#3950420 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3950420 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
