-
1. Re: Simple JMS Queue - Out of Memory error
tommys Nov 21, 2002 5:33 PM (in response to jklem)Try it with Jboss3.0.4. There are some fixes in there for resource leak. You don't really have to upgrade your server, just copy jbossmq.jar from 3.0.4 to your app lib directory.
Also, check your own code for memory leaks. Are you keeping the messages somewhere but didn't delete them? -
2. Re: Simple JMS Queue - Out of Memory error
adrian.brock Nov 21, 2002 7:23 PM (in response to jklem)Are you using selectors?
There is a fix in 3.0.4
Regards,
Adrian -
3. Re: Simple JMS Queue - Out of Memory error
jklem Nov 23, 2002 12:59 PM (in response to jklem)We upgraded JBoss to 3.0.4 (we moved the whole server rather than just the MQ) and the results were disasterous. We got the Out of Memory error after sending about 5 or 6 total messages through our 3 Queues. We use 2 queues that recieve requests to process data and 1 queue that gathers status messages. For some reason it appears that the 3rd queue is the one that actually fails, or fails first. There is some evidence that the other 2 queues continue to function, at least for a time, even after the 3rd status queue is throwing out of memory errors.
We are not using selectors. The app sends a smallish xml message. Dispatching is handled in the appropriate MDB by using a few simple properties to determine which process will be performed.
-jk -
4. Re: Simple JMS Queue - Out of Memory error
adrian.brock Dec 4, 2002 12:33 PM (in response to jklem)My first guess is you have some infinite loop?
Perhaps you can post a simple example that
reproduces the problem?
Regards,
Adrian -
5. Re: Simple JMS Queue - Out of Memory error
yjing Dec 9, 2002 6:06 PM (in response to jklem)Is it the first time that you use JDK1.4.1 with jboss?
I ran into similar problem with jboss3.0.3/jdk1.4. It was caused by xml SAXParser who is using StringBuffer.setLength(0) in flushCharacters(). After changing StringBuffer.setLength(0) to new StringBuffer(), no "outofMemoryError" anymore.
Yan -
6. Re: Simple JMS Queue - Out of Memory error
j.hedin Dec 16, 2002 3:37 AM (in response to jklem)I have also had problems with OutOfMemoryException and Jboss 3.0.4/jdk1.4.1_01.The JMS queue is used to propagate tiny XML messages. Could the errors not be related to JBossMQ, but to massive parsing of tiny XML messages? How did you fix the SAX parser? Do you use the Sun or Apache one. Did you recompile it?
P.S. To the JBoss group: Thanks for a wounderfull Appservere. D.S. -
7. Re: Simple JMS Queue - Out of Memory error
j.hedin Dec 16, 2002 11:38 AM (in response to jklem)The key to my problems war raising the -Xmx option to the JVM. I have since then successfully sent 200k tiny XML messages though the JBossMQ to EJBs and last MySQL. Works perfectly (if it wasn't for the massive paging of my laptop). Tested on Linux. Havn't tried on the Solaris production enviroment yet.
-
8. Re: Simple JMS Queue - Out of Memory error
yjing Dec 16, 2002 1:28 PM (in response to jklem)My outofMemoryError with jboss3.0.3/jdk1.4.1_01 is caused by jdk1.4.1_01's StringBuffer.setLength(0). Just one 500K jms message will trigger this memory error. The receiver of the message uses JDOM to parse the 500k xml string.
It won't happen with Jdk1.3.5.
I changed JDOM's SAXHandle.java to not use stringBuffer.setLength(0). The problem is solved.
Yan