Memory leak in RMI registry ? (JRE 1.3.1_11)

Hello. I have a CLI that creates a server which calls some JNI to get
objects for a flat file database and return them. Each time I run the CLI I create a new server and bind it the RMI registry. I created a script that excecutes
the CLI in a forever loop. While this is running I notice the RMI registry program
slowly grows over time until it uses all of the system resources. I keep track of the
servers I create in a Vector and remove them once they are complete. I don't
explicitly remove them from the RMI registry because I assume they would get
garbage collected once all references to them where gone. Has anyone seen
this behavior ? Any ideas what could be happening ? Thanks.
BTW - I am running on Solaris.

The only way out of the RMI Registry is the unbind() method.
If you never unbind anything from the RMI REgistry and keep adding bindings it will grow forever.
You've got your implementation back to front. If you unbind from the Registry then allow DGC to take its course your server will eventually get an Unreferenced callback, which is the signal to remove it from local storage. Alternatively you could just unbind() and remove from local storage immediately. To be frank I am amazed that you didn't try this before posting here.

Similar Messages

Potential Memory Leak in rmi

We have a service that is being monitored via JMX. The JVM heap usage is growing and even major collections are not able to remove the garbage. Inspecting the heap shows garbage consisting of RMI related references (mostly, if not all, related class loaders). The only way to alleviate the issue is to issue explicit gc call through JMX (that removes all accumulated garbage). Our gc related options are:
-XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly
And we have not touched either of: DisableExplicitGC or sun.rmi.dgc.server.gcInterval
I believe the problem is supposed to addressed by the code in sun.misc.GC.Daemon:
public void run() { for (;;) { long l; synchronized (lock) { l = latencyTarget; if (l == NO_TARGET) { /* No latency target, so exit */ GC.daemon = null; return; } long d = maxObjectInspectionAge(); if (d >= l) { /* Do a full collection. There is a remote possibility * that a full collection will occurr between the time * we sample the inspection age and the time the GC * actually starts, but this is sufficiently unlikely * that it doesn't seem worth the more expensive JVM * interface that would be required. */ System.gc(); d = 0; } /* Wait for the latency period to expire, * or for notification that the period has changed */ try { lock.wait(l - d); } catch (InterruptedException x) { continue; } } } }
For some reason the above System.gc is not being invoked (that has been verified by looking at gc logs). Anyone has a suggestion as to how to address the issue?

Thanks for pointing to MOS notes, they were quite helpful. Though sometime on our system, ohasd.bin consumes more resources. Is it safe to kill it?
Also, we have observed that there are multiple oraagents belonging to different users such as root,grid and oracle.
grid 14620 1 0 20:32 ? 00:00:14 /u01/app/11.2.0/grid/bin/oraagent.bin
root 14625 1 0 20:32 ? 00:00:02 /u01/app/11.2.0/grid/bin/orarootagent.bin
root 14627 1 0 20:32 ? 00:00:00 /u01/app/11.2.0/grid/bin/cssdagent
grid 14803 1 0 20:32 ? 00:00:06 /u01/app/11.2.0/grid/bin/oraagent.bin
oracle 14807 1 0 20:32 ? 00:01:53 /u01/app/11.2.0/grid/bin/oraagent.bin
root 14811 1 0 20:32 ? 00:00:38 /u01/app/11.2.0/grid/bin/orarootagent.bin
When these are killed, not all are re-spawned automatically - typically oraagent belonging to "oracle" user is left out. Is this an expected behaviour or it will cause some instability in the clusterware?
Thanks

RMI memory leak

My program use RMI, and I remark memory leak, then I tried RMI sample from jbuilder6, I modified this sample, to send 1Mb file via RMI.
I write how much RAM are used
before 168 mb
rmiregistry 172Mb used 8 Mb
RMIserver 189Mb 18 Mb
RMIclient up to 227Mb 38Mb
end when RMIclient exit 212Mb where is 23 Mb??? 212-189 ????
This is my changes, and all program are after that:
public String getDate() {
System.out.println("SimpleRMIImpl.getDate()");
String s=null;
try {
InputStream fileIn = new FileInputStream("Readme.txt2");
byte buff[] = new byte[fileIn.available()];
int i = fileIn.read(buff);
s = new String(buff);
} catch(FileNotFoundException e) {
e.printStackTrace();
} catch(IOException e) {
e.printStackTrace();
return new String(s);
All program:
package com.borland.samples.rmi;
import java.rmi.*;
import java.rmi.registry.*;
import java.rmi.server.*;
import java.util.Date;
public class SimpleRMIClient
public static void main(String[] argv) {
String serverName = "";
System.setSecurityManager(new RMISecurityManager());
if (argv.length != 1) {
try {
serverName = java.net.InetAddress.getLocalHost().getHostName();
catch(Exception e) {
e.printStackTrace();
else {
serverName = argv[0];
if (serverName == "") {
System.out.println("usage: java SimpleRMIClient <IP address of host running RMI server>");
System.exit(0);
try {
//bind server object to object in client
SimpleRMIInterface myServerObject = (SimpleRMIInterface) Naming.lookup("//"+serverName+"/SimpleRMIImpl instance");
//invoke method on server object
String d = myServerObject.getDate();
System.out.println("Date on server is " + d);
catch(Exception e) {
System.out.println("Exception occured: " + e);
System.exit(0);
System.out.println("RMI connection successful");
package com.borland.samples.rmi;
import java.rmi.*;
import java.rmi.server.UnicastRemoteObject;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.io.InputStream;
import java.io.FileInputStream;
public class SimpleRMIImpl extends UnicastRemoteObject implements SimpleRMIInterface
public SimpleRMIImpl(String name) throws RemoteException {
super();
try {
Naming.rebind(name, this);
catch (Exception e) {
if (e instanceof RemoteException)
throw (RemoteException)e;
else
throw new RemoteException(e.getMessage());
public String getDate() {
System.out.println("SimpleRMIImpl.getDate()");
String s=null;
try {
InputStream fileIn = new FileInputStream("Readme.txt2");
byte buff[] = new byte[fileIn.available()];
int i = fileIn.read(buff);
s = new String(buff);
} catch(FileNotFoundException e) {
e.printStackTrace();
} catch(IOException e) {
e.printStackTrace();
return new String(s);
package com.borland.samples.rmi;
public interface SimpleRMIInterface extends java.rmi.Remote
public String getDate() throws java.rmi.RemoteException;
package com.borland.samples.rmi;
import java.rmi.*;
import java.rmi.server.UnicastRemoteObject;
public class SimpleRMIServer
public static void main(String[] argv) {
System.setSecurityManager(new RMISecurityManager());
try {
SimpleRMIImpl implementation = new SimpleRMIImpl("SimpleRMIImpl instance");
System.out.println("SimpleRMIImpl ready");
catch (Exception e) {
System.out.println("Exception occurred: " + e);
Can you explain why this program use so much memory?
Valdas

Memory Usage and its distribution are done by the JVM....u cannot posibly account for each Mega bit of memory while it is used. Also, the File Copying Operation Involves JVM interacting with the OS which in turn interacts with the peripeherals such as ur harddisk, which are comparetively slower then the Processor speed. So the bottom line is ur same program will work at different RAM levels in diff machines with diff hardwares......If u system is indeed working too much then u can check out and sut down many services that u might have otherwise started...posiiblity of a Virus should not be ruled out either.....and the code itself is no problem at all although u might increase a bit by using some FIleReader, BufferredReader/Writer and other faster Streams.
Hope it helps,
Cheers,
Manja

Memory Leak issue 1.5.4.59.40-no-jre jdk1.6.0_12 jre6

Me and 2 other develops have been using SQL developer since it was created but we are getting really frustrated with the memory leaks we are experencing.
We will start up sql developer and if we just leave it alone within a couple hours it will have taken up 650Megs of ram and be completely locked up. If we are working in sql developer the time can be even faster till it lockups up. We have been experencing the issue for very long time but seems to have gotten worse in the last to updates.
I have tried to search the web and form for information to the memory problem to no avail. We are running oracle 10g and windows XP with 2gigs of ram.
Can some one point me to some information or have any idea what is going on?
Edit--
I just realized that I was not using the latest version that I have downloaded. Trying sqldeveloper-1.5.4.59.40-no-jre will advise as to results.
Edited by: ObeTheDuck on Mar 17, 2009 8:47 AM
2nd Edit--
1.5.4.59.40-no-jre has the same issue. 2hrs and it has locked up and is no longer listed as a running app and can only be seen under the process thread in windows task manager with 50% CPU use on a dual-core cpu and 626megs ram being used. Have to kill and restart ... <sigh>
Edited by: ObeTheDuck on Mar 17, 2009 10:45 AM

Thanks for the info so far....
We really do like sql developer as a tool and has been execeding helpful and useful as our development tool.
I am proud to say we have been using it since the 2nd month is was available and have been encourged and happy with most of the improvements.
I am looking forward to trying the modeling tool soon.
If I can get back to having a stable work enviorment for a work day that will be fine for now. It's just been reduced down to 2hrs which is a bit much.
Anyway...
1. We don't have any in house extentions that we need. I am speaking of the one that come bundled with the tool. Or at least I thought that they came bundled.
Several are migration tools which we don't need. One is TenTime tool which I don't think we need.
Last is the versioning extention, this sounds like something we want to use, but stability is more important at the moment. So unchecked they have all been.
2. Sue you asked about a clean install. Is that simply an unpacking a new folder copy and then not migrate settings when running?
3. I will be glad to uninstall java a switch to different version of the jdk which one is consider to be the most stable atm?
Thanks,
Obe

ClassDefiner.defineClass() leaking memory in a RMI method invocation.

Hi,
My application uses RMI for communicating between two java processes.
I'm observing some kind of memory leak in one of the classes in RMI
library. When observed through OptimizeIT, I see a large number of
Object[] being created by the ClassDefiner.defineClass() &
ClassDefiner$1().run().
These Object[] arrays keep accumulating, never get garbage collected.
Attached is the screen shot of OptimizeIT, which shows object allocation
hierarchy.
Any help in this regard would be appreciated.
The JDK version being used is, 1.4.2_05.
thanks in advance.
Vijayendra

Update -
The reason for this was found to be "-Xnoclassgc" After removing this option from the startup script, I didn't notice any increase in object[]/int[] count.
Hoping this would fix the issue.

RMI method invocation leading to Memory Leak

My application uses RMI for communicating between two java processes.
I'm observing some kind of memory leak in one of the classes in RMI
library. When observed through OptimizeIT, I see a large number of
Object[] being created by the ClassDefiner.defineClass() &
ClassDefiner$1().run().
These Object[] arrays keep accumulating, never get garbage collected.
Attached is the screen shot of OptimizeIT, which shows object allocation
hierarchy.
Any help in this regard would be appreciated.
The JDK version being used is, 1.4.2_05.
thanks in advance.
Vijayendra

The reason for this was found to be "-Xnoclassgc" After removing this option from the startup script, I didn't notice any increase in object[]/int[] count.
Hoping this would fix the issue.

JRE issues - Memory leak

We have a memory leak in an enterprise java application.
I need a way to reset the JVM. When i start the program, and clients connect to it, the memory keeps going up. as a quick fix we figured we could stop that program and restart it (giving us time to find the leak).
The memory starts where it left off. ??? any ideas how to reset the mem usage? clear the heap?
Please helpp... thanks...

Thanks for the response.
do you know the different between running the JVM on a 64-bit machine vs. on 32-bit machine? both windows.

New Memory Leak Detector released

This week we released an updated version of the Memory Leak Detector. It now features a much improved graphical user interface as well as more powerful ways to track down memory leaks.
The tool is designed to help you find memory leaks in production type environments without causing much overhead. It allows you to attach to a running JRockit process, analyze the heap, and detach, leaving the process running at full speed again.
There is an article on dev2dev which describes the tool in more detail: http://dev2dev.bea.com/pub/a/2005/06/memory_leaks.html
Download the free tool today at: http://dev2dev.bea.com/wljrockit/tools.html
Comments are always welcome here in the forum.
Regards,
/Staffan Larsen

FYI, the console ist providing this stack trace in the details window:
java.io.IOException: Unsupported JVM on host 'localhost' at port 7090.
Make sure you are running the correct version of JRockit.
     at com.jrockit.memleak.model_impl.MemleakUtil.handleConnectionException(Unknown Source)
     at com.jrockit.memleak.model_impl.MemleakUtil.doConnect(Unknown Source)
     at com.jrockit.memleak.model_impl.MemleakUtil.access$000(Unknown Source)
     at com.jrockit.memleak.model_impl.MemleakUtil$1.run(Unknown Source)
     at foxtrot.AbstractWorkerThread$2.run(AbstractWorkerThread.java:49)
     at java.security.AccessController.doPrivileged(Native Method)
     at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:45)
     at foxtrot.workers.DefaultWorkerThread.run(DefaultWorkerThread.java:153)
     at java.lang.Thread.run(Unknown Source)
Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
     java.io.EOFException]
     at com.sun.jndi.rmi.registry.RegistryContext.lookup(Unknown Source)
     at com.sun.jndi.toolkit.url.GenericURLContext.lookup(Unknown Source)
     at javax.naming.InitialContext.lookup(Unknown Source)
     at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(Unknown Source)
     at javax.management.remote.rmi.RMIConnector.findRMIServer(Unknown Source)
     at javax.management.remote.rmi.RMIConnector.connect(Unknown Source)
     at javax.management.remote.rmi.RMIConnector.connect(Unknown Source)
     at com.jrockit.memleak.comm.RemoteMLSController.getServerConnection(RemoteMLSController.java:152)

How to configure license file for Memory Leak tool and WL Server 9.2?

(I posted to general JRockit forum before realizing existence of this forum which is probably more applicable.)
Here's our problem:
Running latest version of WL 9.2 MP3 and JRockit Mission Control 3.0.1
Able to run Mission Control, and connect to the WL Server and to run View Console with no problems.
I can't get Memory Leak tool to run because it complains about needing a license file.
First I tried with off the shelf WL 9.2 MP3.
Get error:
A license for Memory Leak Detector could not be found on the JRockit at (1.5) weblogic.Server (192).
Error: Can not find component Memory Leak Detector for JRockit * in the license file. Please check http://www.jrockit.com/license for license updates.
So I downloaded license file from JRockit download site - wls92.zip. It contains several files, but no clear instructions on what to do with these files. I copied one of these files "LIC-WLSP92.txt" to my JRockit home as C:\bea\JROCKI~1\jre\license.bea
Tried again. Restarted WL server. Restarted JRockit Mission Control.
Get error: A license for Memory Leak Detector could not be found on the JRockit at (1.5) weblogic.Server (3052).
The license file does not exist at: C:\bea\JROCKI~1\jre\license.bea
Any advise on how to install license or who to contact for help?

Installed Mission Control 3.0.3.
Got following message when I attempted to run Memory Leak:
A license for Memory Leak Detector could not be found on the JRockit at (1.5) weblogic.Server (192).
Error: Can not find component Memory Leak Detector for JRockit * in the license file.
Please check http://www.jrockit.com/license for license updates.
I believe that we're using the latest downloads of WebLogic 9.2.x and JRockit.
WebLogic is running using 9.2.3 and JRockit build R27.4.0-90_CR358515-94243-1.5.0_12-20080118-1154-windows-ia2
Contents of C:\bea\jrockit_150_12\jre\license.bea:
<?xml version="1.0" encoding="ISO-8859-1"?>
<bea-licenses>
<license-group format="1.0" product="JRockit" release="*">
</license-group>
</bea-licenses>
Could WebLogic be misconfigured?
Any diagnostics to help figure out the licensing?
Any other ideas?

Memory leak in Solaris - SunOS 5.7, jre1.3.1

Hi,
I hava a java application that spawns about 100 threads. Each thread sends a request to WebLogic server 6.1. We are using Oracle 8.1.7. They are all running in a Sun box, 2 CPUs and 6gig memory.
JRE = 1.3.1
SunOS = 5.7
Weblogic = 6.1
Oracle = 8.1.7
(All running on the same box)
When we start the client application, running top shows that ,
the client JVM process - uses 40 MB of memory
WebLogic - uses 250 MB of memory
But the available memory comes down drastically (almost by 350 MB), and on bringing both the client and weblogic down, we are not able to get this 350 MB back
Running JProbe, doen not show any memory leak in our application
we are using the hotspot client version
-Xms = 128m
-Xmx = 128m
Any help is appreciated

It looks like i am also facing the same problem with my application . If by some chance you were able to solve this problem do send a mail to [email protected] I just posted the question. while searching the web i found your question which looks similar but not answered. Hope you could give me some input
Thanks

Memory Leak with 4.5.1/Java/Solaris

Hi,
We are currently running a Java Application using RMI/Weblogic 4.5.1/Solaris 5.7/Java 1.22.
Behavior that has been observered during the day is that memory usage reaches a stage in which it begins increasing and GC doesn't recover any memory, until the heap reaches an extremly large size, then recovers a significant amount of memory.
We have even seen the java process grab more memory than specified in the -Xmx parameter and experience a java.lang.OutOfMemory error.
I have seen postings that describe similar issues in this newsgroup, but none that define a solution.
This problem is intermittent, and our application can run an entire day without experiencing this memory leak. On the other hand there are days when the memory leak occurrs even when the system is idle overnight.
Please let me know any information you have gathered on this subject.
Regards,
Mark Evans

try increasing your virtual memory on your NT system...
"Parasher K. Joshi" <[email protected]> wrote:
>
Hi,
I observed the same confusing stuff in my tests. But I run weblogic 4.5.1 on Windows NT with JDK 1.2.2-w
Usually, I would get a "Low virtual memory" message from windows
and if I click ok & shuffle thourgh my windows I would be ok.
But since last 2 days, I would keep the server running overnight.
When I return in morning,
I would find a "Low virtual memory" message and
on clicking OK. I would find another message tell me that java.exe (which was running weblogic) crashed!!
Now today I tried to watch the memory usage in Task Manager. And I found the most wierd thing.
I saw that even when the system was doing virtually nothing,
except print a string at intervals, the memory usage would go
up steadyly.
Even doing a forced finalization and gc did not seem to stop it.
BUT, BY CHANCE I HAPPEN TO MINIMISE AND MAXIMISE THE WEBLOGIC
CONSOLE OUTPUT WINDOW.
WHAT I SAW IN THE TASK MANAGER AMAZED ME!
THE MEMORY USAGE IN TASK MANAGER HAD GONE DOWN TO 24XXKB, WHILE
IT WAS ABOUT 20000K OR EVEN MORE.
This seems to support the fact that during my test, I would
get the "low virtual memory" message and if OKed it and shuffled
though application windows (maybe minimise, maximise the weblogic
console output window in process), I would be able to complete
my application. But when the message appears during night runs,
nothing is done and by morning, when I reach to work,
I would see that weblogic had crashed!!
You may try that and see if it helps you.
Parasher
Mark Evans <[email protected]> wrote:
Hi,
We are currently running a Java Application using RMI/Weblogic 4.5.1/Solaris 5.7/Java 1.22.
Behavior that has been observered during the day is that memory usage reaches a stage in which it begins increasing and GC doesn't recover any memory, until the heap reaches an extremly large size, then recovers a significant amount of memory.
We have even seen the java process grab more memory than specified in the -Xmx parameter and experience a java.lang.OutOfMemory error.
I have seen postings that describe similar issues in this newsgroup, but none that define a solution.
This problem is intermittent, and our application can run an entire day without experiencing this memory leak. On the other hand there are days when the memory leak occurrs even when the system is idle overnight.
Please let me know any information you have gathered on this subject.
Regards,
Mark Evans

Memory leak with my JAI code.

Hi guys,
I have this method below which is creating a memory leak, can anyone please point out possible reasons why there is a problem here:
private PlanarImage getPlanarImageFromIItem(IItem iitem)throws Exception
     InputStream stream = iitem.getBinaryContent().getContentStream();
     SeekableStream seekableItemStream = SeekableStream.wrapInputStream(stream,false); // read backwards
     PlanarImage planarImage = JAI.create("Stream", seekableItemStream);
     Raster raster = planarImage.getData(); // This forces a read
     seekableItemStream.close();
     stream.close();
     return planarImage;
}Here, IItem is a custom class which represents a wallpaper picked up from a CMS. This method converts that to a planarimage and returns it, without a call to this method, the memory leak goes away...so its definite that the leak is here.
Also, can anyone suggest ways of possibly rewriting this method in a better way?
Thanks!

For the code in the first post, the stacktrace is as below:
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.awt.image.DataBufferByte.<init>(Unknown Source)
at com.sun.media.jai.codecimpl.PNGImage.createRaster(PNGImageDecoder.java:1305)
at com.sun.media.jai.codecimpl.PNGImage.parse_IEND_chunk(PNGImageDecoder.java:816)
at com.sun.media.jai.codecimpl.PNGImage.<init>(PNGImageDecoder.java:445)
at com.sun.media.jai.codecimpl.PNGImageDecoder.decodeAsRenderedImage(PNGImageDecoder.java:74)
at com.sun.media.jai.opimage.CodecRIFUtil.create(CodecRIFUtil.java:88)
at com.sun.media.jai.opimage.PNGRIF.create(PNGRIF.java:48)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at javax.media.jai.FactoryCache.invoke(FactoryCache.java:122)
at javax.media.jai.OperationRegistry.invokeFactory(OperationRegistry.java:1674)
at javax.media.jai.ThreadSafeOperationRegistry.invokeFactory(ThreadSafeOperationRegistry.java:473)
at javax.media.jai.registry.RIFRegistry.create(RIFRegistry.java:332)
at com.sun.media.jai.opimage.StreamRIF.create(StreamRIF.java:102)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at javax.media.jai.FactoryCache.invoke(FactoryCache.java:122)
at javax.media.jai.OperationRegistry.invokeFactory(OperationRegistry.java:1674)
at javax.media.jai.ThreadSafeOperationRegistry.invokeFactory(ThreadSafeOperationRegistry.java:473)
at javax.media.jai.registry.RIFRegistry.create(RIFRegistry.java:332)
at javax.media.jai.RenderedOp.createInstance(RenderedOp.java:819)
at javax.media.jai.RenderedOp.createRendering(RenderedOp.java:867)
at javax.media.jai.RenderedOp.getData(RenderedOp.java:2265)
at com.wwe.cds.affiliates.cingular.CingularImageGroupListInterceptor.getPlanarImageFromIItem()

Memory leak with 1.6.0_07 in applet using Swing

Java Plug-in 1.6.0_07
Using JRE version 1.6.0_07 Java HotSpot(TM) Client VM
Windows XP - SP2
I have a commercial application that has developed a memory leak with the introduction of the latest plugin. The applets chew up memory and eventually freeze. They did not before. Using jvisualm I see a build up of native arrays, primarily int[][] and char[]. I'm still investigating. Anyone have a similar experience?
The Applet uses a swing interface, uses buffered images and swing timers, and regularly performs http connections to the server which result in actions via the SwingUtil.invokeLater() method.

I am Using Internet Explorer Browser Version 6.0.Huge security hole.
Its not throwing Error / Exception Wrap a try/catch at the highest level possible.
Catch 'Throwable'. And log/display it somewhere.

Oracle JDBC Thin Driver Memory leak in scrollable result set

Hi,
I am using oracle 8.1.7 with oracle thin jdbc driver (classes12.zip) with jre 1.2.2. When I try to use the scrollable resultset and fetch records with the default fetch size, I run into memory leaks. When the records fetched are large(10000 records) over a period of access I get "outofmemory" error because of the leak. There is no use increasing the heap size as the leak is anyhow there.
I tried using optimizeit and found there is a huge amout of memory leak for each execution of scrollable resultsets and this memory leak is propotional to the no of records fetched. This memory leak is not released even when i set the resultset,statement objects to null. Also when i use methods like scrollabelresultset.last() this memory leak increases.
So is this a problem with the driver or i am doing some wrong.
If some of you can help me with a solution to solve this it would be of help. If needed i can provide some statistics of these memory leaks using optimize it and share the code.
Thanks
Rajesh

This thread is ancient and the original was about the 8.1.7 drivers. Please start a new thread. Be sure to include driver and database versions, stack traces, sample code and why you think there is a memory leak.
Douglas

Memory leak using thin client

Subject: Memory Leak while using thin client.
From: [email protected] (Alon Albert)
Newsgroups: weblogic.developer.interest.jndi
I have a small test program that causes a memory leak while connecting
to a weblogic server. The code is appended to the end of the msg. The
problem is definatly caused by the InitialContext creation.
Even if I explicitly call the InitialContext.close() method, the
problem persists. I realize I can avoid the problem by using a one
time connection outside the loop but keep in mind that this is only a
test program. The full application REQUIRES me to do a full
reconnection each time it is accessed.
I have read in a previous simmilar post that the problem mught be RMI
related. Is anything I can do about this?
package jmxleak;
import java.net.*;
import java.util.*;
import javax.management.*;
import javax.naming.*;
public class Main {
String host;
String username;
String password;
MBeanServer mbs;
public static void main(String[] args) {
while (true) {
Main main = new Main(args[0], args[1], args[2]);
main.connect();
main = null;
System.out.println("Collecting garbage.");
System.gc();
public Main(String host, String username, String password) {
this.host = host;
this.username = username;
this.password = password;
private void connect() {
try {
System.out.print("Connecting..., ");
Thread.currentThread().setContextClassLoader(new
URLClassLoader(new URL[] { new URL("http://" + host + "/classes/")}));
Hashtable env = new Hashtable();
env.put("java.naming.factory.initial",
"weblogic.jndi.WLInitialContextFactory");
env.put("java.naming.provider.url", "t3://" + host);
if (username.length() > 0 && password.length() > 0) {
env.put("java.naming.security.principal", username);
env.put("java.naming.security.credentials", password);
System.out.print("Creating context..., ");
InitialContext ctx = new InitialContext(env);
catch (Exception e) {
e.printStackTrace();

Subject: Memory Leak while using thin client.
From: [email protected] (Alon Albert)
Newsgroups: weblogic.developer.interest.jndi
I have a small test program that causes a memory leak while connecting
to a weblogic server. The code is appended to the end of the msg. The
problem is definatly caused by the InitialContext creation.
Even if I explicitly call the InitialContext.close() method, the
problem persists. I realize I can avoid the problem by using a one
time connection outside the loop but keep in mind that this is only a
test program. The full application REQUIRES me to do a full
reconnection each time it is accessed.
I have read in a previous simmilar post that the problem mught be RMI
related. Is anything I can do about this?
package jmxleak;
import java.net.*;
import java.util.*;
import javax.management.*;
import javax.naming.*;
public class Main {
String host;
String username;
String password;
MBeanServer mbs;
public static void main(String[] args) {
while (true) {
Main main = new Main(args[0], args[1], args[2]);
main.connect();
main = null;
System.out.println("Collecting garbage.");
System.gc();
public Main(String host, String username, String password) {
this.host = host;
this.username = username;
this.password = password;
private void connect() {
try {
System.out.print("Connecting..., ");
Thread.currentThread().setContextClassLoader(new
URLClassLoader(new URL[] { new URL("http://" + host + "/classes/")}));
Hashtable env = new Hashtable();
env.put("java.naming.factory.initial",
"weblogic.jndi.WLInitialContextFactory");
env.put("java.naming.provider.url", "t3://" + host);
if (username.length() > 0 && password.length() > 0) {
env.put("java.naming.security.principal", username);
env.put("java.naming.security.credentials", password);
System.out.print("Creating context..., ");
InitialContext ctx = new InitialContext(env);
catch (Exception e) {
e.printStackTrace();

Memory leak in RMI registry ? (JRE 1.3.1_11)

Similar Messages

Maybe you are looking for