Weblogic JMS Performance Tuning Tips
Here are a couple of real-life tips on tuning JMS performance. Problem: The creates and sends JMS messages on an outgoing queue for consumption by another application. It was observed that when the consuming application was offline for a period of time the number of messages that could be retained on the queue before the JVM heap was filled up was quite low. This was tested to be roughly 7000 messages, after which OutOfMemory exceptions begin to occur. Given that the consuming application could realistically be offline for a period, hence the use of an asynchronous queue, we needed to increase the number of messages that could realistically be stored in the queue. The exception we get is shown below: Start server side stack trace: java.lang.OutOfMemoryError: Start server side stack trace: java.lang.OutOfMemoryError <<no stack trace available>> End server side stack trace at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:1...