Java J2ee Planet

Its one of the scary part i came across when the clients came across with out of memory error. The application was pushing around 40,000 messages to the queue and all the messages have been holded in the memory and finalyy ended up with Out of Memory exception. There are WebLogic settings that take care of this issue. You can set the server to only load up the first N number of messages or X number of bytes to avoid OOM issues. These can be set up by going to the JMSServer config -> Thresholds and Quotas and configure bytes paging or message paging (or both). Recommendation: Set Bytes Threshold High to 1048576, set Bytes Threshold Low to 524288, and set Bytes Paging Enabled to true. Set Messages Threshold High to 1000, set Messsages Threshold Low to 500 and set Messages Paging Enabled to true. This will ensure there is never more than 1 GB and no more than 1000 JMS messages in RAM. Few forums that would help : http://forums.bea.com/thread.jspa?threadID=570000795 Few reasons why OutO