JMS OutOfMemory

[Jeff Storey]

Currently, I have a multi-user app and the server needs to send status messages back to a client. It currently does so via JMS queues. However, after a while of running, I get an OutOfMemoryError related to JMS (and this is the only JMS bit in my application). I've read that I can alleviate this problem using the VM argument -Xss to allocate more space for native threads, but will this problem just get larger as more messages get put on the queue, or is it once the message is read by a client it is removed by the queue? If I need to remove them some other way, how can I do that?

Thanks,
Jeff

[Trimoorthy Kotte]

When a client reads the message the message will be deleted from the queue. JMS outofMemoryerror occur due to the fact that , JMS server implementation by the app server you are using might be holding all the message in the JVM memory itself (apart from persisting the message to file/database). If you have provision on your JMserver to use paging store configuration, then it will help you solve this problem. (WebLogic supports this)

The solution (xss) you are trying to implement resolves StackOb=verFlow exceptions but not outOfMemory errors.

[Jeff Storey]

Thanks for the help. I'm using JBoss, but I couldn't find a PageSize parameter in any of the config files, so I'm guessing this version does not support it. I think the problem was actually related to another problem, but I will keep this solution in mind for the future. Thanks!