Is this a real memory leak, or is it a sign you are actually consuming resource for your load? If it is just resource consumption, have you tried giving your JVM more heap space via -Xmx160m or whatever is appropriate as per standard Java options? If this is not the issue, have you researched issues with your JDBC driver and possible associated memory leaks, or other related issues?
Check your jdom.jar (jboss/lib). JBoss should use a higher version than 1.0 beta8 (check its info.xml file in the META-INF), since this version is causing memory leaks.
I think this was fixed with JBoss 3.2.1.. don't ask me for the 3.0.x. version ;-)
There is nojdom.jar under the lib dir:
tango octest5: ~/CTSA_Home/WebCon_Middleware/jboss-3.0.4_tomcat-4.1.12/lib > ll
-rw-r--r-- 1 octest5 dba 149233 Nov 2 2002 concurrent.jar
-rw-r--r-- 1 octest5 dba 196399 Nov 2 2002 crimson.jar
-rw-r--r-- 1 octest5 dba 10785 Nov 2 2002 getopt.jar
-rw-r--r-- 1 octest5 dba 30163 Nov 2 2002 gnu-regexp.jar
-rw-r--r-- 1 octest5 dba 33323 Nov 2 2002 jaxp.jar
-rw-r--r-- 1 octest5 dba 4675 Nov 2 2002 jboss-boot.jar
-rw-r--r-- 1 octest5 dba 227835 Nov 2 2002 jboss-common.jar
-rw-r--r-- 1 octest5 dba 380654 Nov 2 2002 jboss-jmx.jar
-rw-r--r-- 1 octest5 dba 134533 Nov 2 2002 jboss-system.jar
-rw-r--r-- 1 octest5 dba 118410 Nov 2 2002 log4j-boot.jar
It is a real leak - after few hours I fet out of memory exception. I am not using JDBC. I use JNI - I load a dll which do the SQL job
This is really difficult. Asking the ejb spec will tell you:
the enterprise bean must not attempt to load a native library.
You are handling with external resources the container doesn't know about. Be careful, since you are probably causing these leaks by yourself!