Memory leak in NFS server

Hi all,
I have a problem with 2 SunFire 240 (4Gb of Ram) with solaris 10 in a Veritas Cluster.
These nodes are 2 NFS server and they have 10 nfs client.
We have a memory leak on these servers. The memory utilization increase day by day.
The memory seems to be allocated by the kernel and not from some process.
So I would like to know if this is a common issue (NFS?) or this is a single case.
Thanks in advance for you help
Regards
Daniele
Edited by: Danx on Jan 2, 2008 5:23 PM

That message relates to how the application deals with its threads, which for a the most part isn't actually an issue. However, since it does have the potential to cause a leak under certain circumstances we did make a change in 10.3 to address that issue, so I suggest you upgrade to that release.

Similar Messages

Memory Leak in Java Server

Howdy Folks- I wrote a server monitor in java, which I was expecting to run for months at a time without restarting. Apparently there is some slow memory leak which results in an OutOfMemoryError after a few weeks. It's in a production system, so I can't readily add debug statements to the code, and the OutOfMemoryError apparently screwed up the logging, so I didn't get a stack trace in my logs, just an "OutOfMemoryError" went to standard out.
I'm assuming the problem lies in the code, specifically probably some discarded reference that is not being properly garbage collected? I am using a few different ArrayLists to store some historical information, and I call clear() on these frequently. Is there any known issue with ArrayList or HashMap that the "clear()" method doesn't result in garbage collection of the objects that were in it? I am also doing a "remove(int)" sometimes as well. Any chance the objects cleared or removed would not be garbage collected?
thanks
Bleu

Howdy Folks- I wrote a server monitor in java, which I
was expecting to run for months at a time without
restarting. Apparently there is some slow memory leak
which results in an OutOfMemoryError after a few
weeks. It's in a production system, so I can't
readily add debug statements to the code, and the
OutOfMemoryError apparently screwed up the logging, so
I didn't get a stack trace in my logs, just an
"OutOfMemoryError" went to standard out.Are you even attempting to catch Errors? Catching Exceptions will not help with this. It should print the stack trace. When it OOMs it doesn't mess up what's already allocated, it just can't allocate more.
I'm assuming the problem lies in the code,
specifically probably some discarded reference that is
not being properly garbage collected? Most likely, there are references that are never being cleared in your code. Without seeing the code or at least having a better description, I don't think anyone here can help you. Can you set up a test senario and use an Optimizer to see what's going on?
I am using a
few different ArrayLists to store some historical
information, and I call clear() on these frequently.
Is there any known issue with ArrayList or HashMap
that the "clear()" method doesn't result in garbage
collection of the objects that were in it? Not that I know of, no. I doubt that is the problem.

Memory leak in weblogic server 5.1 sp 9?

We have been getting an out of memory error at production sites after
several days of running. We changed the starup file to include the
verbose:gc parameter and we are running jdk1.3.1_02. Over time the full
garbage collection message shows that the heap size after garbage collection
is growing until the server runs out of memory. Can anyone tell me the best
way to identify the problem?
Thanks,
Derek

had the same problem on 1.2 and sp 9. upgraded to 1.3_02 and sp11 and the
problem was solved....
"Derek Gibbs" <[email protected]> wrote in message
news:[email protected]..
We have been getting an out of memory error at production sites after
several days of running. We changed the starup file to include the
verbose:gc parameter and we are running jdk1.3.1_02. Over time the full
garbage collection message shows that the heap size after garbagecollection
is growing until the server runs out of memory. Can anyone tell me thebest
way to identify the problem?
Thanks,
Derek

Memory Leak Problem at Adobe LiveCycle Server 9.0

Hi All,
We want to upgrade our system to 9.0. During the performance test we have found memory Leak problem at ALS 9.0. I explain the detailed problematic issue below. Is there any body who has any suggest?
We have Adobe Livecycle ES2 9.0 SP2 installed on WAS 6.1. But also WAS on Windows Server 2008 R2. We call java web services from .Net Web service for generating PDFs.
On Java side “com/adobe/internal/pdftoolkit/services/javascript/GibsonMemoryTracking” class is causing Memory Leak problem at server.
Our .Net Codes. I copied below. First we generate PDF then we convert this pdf to static pdf.
First We call the GeneratePDF function.
public static bool GeneratePdf(Document document, byte[] pdfTemplate)
        try
            //Create a FormDataIntegrationService object and set authentication values
            FormDataIntegrationService formDataIntegrationClient = new FormDataIntegrationService();
            formDataIntegrationClient.Credentials = new System.Net.NetworkCredential(Settings.ALCUserName, Settings.ALCPassword);
            //Import XDP XML data into an XFA PDF document
            ALCFormDataIntegrationService.BLOB inXMLData = new ALCFormDataIntegrationService.BLOB();
            //Populate the BLOB object
            inXMLData.binaryData = System.Text.Encoding.UTF8.GetBytes(document.XmlData);
            //Create a BLOB that represents the input PDF form
            ALCFormDataIntegrationService.BLOB inPDFForm = new ALCFormDataIntegrationService.BLOB();
            inPDFForm.binaryData = pdfTemplate;
            //Import data into the PDF form
            ALCFormDataIntegrationService.BLOB results = formDataIntegrationClient.importData(inPDFForm, inXMLData);
            document.PdfData = results.binaryData;
            Utility.Log("GeneratePdf", "Pdf generated successfully.", LogLevel.Info);
            return true;
        catch (Exception ex)
            document.ReturnCode = "22";
            document.ReturnMsg = "Exception on generating the pdf";
            Utility.Log("GeneratePdf", "Exception: " + ex.Message, LogLevel.Error);
            return false;
Then We call the ConvertPDF function.
public static bool ConvertPdf(Document document)
        try
            //Create a OutputServiceService object
            OutputServiceService outputClient = new OutputServiceService();
            outputClient.Credentials = new System.Net.NetworkCredential(Settings.ALCUserName, Settings.ALCPassword);
            //Create a BLOB object
            ALCOutputService.BLOB inData = new ALCOutputService.BLOB();
            //Populate the BLOB object
            inData.binaryData = document.PdfData;
            //Set rendering run-time options
            RenderOptionsSpec renderOptions = new RenderOptionsSpec();
            renderOptions.cacheEnabled = true;
            //Create a non-interactive PDF document
            ALCOutputService.BLOB results = outputClient.transformPDF(inData, TransformationFormat.PDF, PDFARevisionNumber.Revision_1, false, null, PDFAConformance.B, false);
            document.PdfData = results.binaryData;
            Utility.Log("ConvertPdf", "Pdf converted successfully.", LogLevel.Info);
            return true;
        catch (Exception ex)
            document.ReturnCode = "22";
            document.ReturnMsg = "Exception on converting dynamic pdf to static pdf";
            Utility.Log("ConvertPdf", "Exception: " + ex.Message, LogLevel.Error);
            return false;
Our System Configuration:
Expiry date: Never Version: 9.0.0.0,
GM Patch Version: SP2
Service Pack Version: unknown
ADOBE® LIVECYCLE® PDF Generator ES2
9.0.0.0
SP2
ADOBE® LIVECYCLE® Reader Extensions ES2
9.0.0.0
SP2
ADOBE® LIVECYCLE® Output ES2
9.0.0.0
SP2
We changed some configuration which is suggested by Adobe. But this change does not solve our problem.
Changed Configurations via ADMINUI
Memory Leak Problem which is viewed via wily tool:

Hi Mahir,
Can you attach the results of this performance test where we can see how GibsonMemoryTracking class is causing the memory leak issue.
Also do you see any stackTrace in the LiveCycle server logs related to memory / heap when you run this performance test ?
Thanks,
Simer

SQL Server 2012- Memory Leak Issue

Team,
We are running a Mission Critical Application on SQL Server 2012 SP2(11.0.5058) which is configured on Always ON Synchronous mode. Offlate due to heavy development work, Application team have come up with stating memory issues. I have analysed all the areas
and everything looks normal. Please suggest if we have to patch the latest CU4 for SQL Server 2012 SP2.
The checks were performed on the below areas:
- Errorlog, System Logs - No errors reported.
- There are close to 8 Databases hosted on the instances which are all configured for AlwaysON. SQL Server is running on VM Infrastructure and the total physical memory allocated is 96GB out of which SQL is capped for 92GB.
-The Page Life Expectancy is healthy and is showing a greater number. There are no Signal waits either or pending memory grants.
- The writes are more than reads for one of the databases which is flagged with application team. There are no blockings & Deadlocks.
Please suggest me the future course of action and your inputs are much appreciated.
Best Regards,
Sharath

Actual issue is- Application team have reported a memory leak and their builds have significantly slowed down. They suspect that its Database memory leak. However I have verified from database end and gave the above inputs.
The AOAGs are good. I was looking for any pointers whether there are any bugs which is related to memory leaks in SQL Server 2012. I know all of them are addressed with SQL Server 2012 SP2.
Application team has NO idea about SQL Server do they ? And to say SQL Server has memory leak you have to actually prove it did they showed any proof. Its common for application team to say SQL Server is leaking memory because they are unaware about fact
by default SQL Server would take as much memory as possible and would release when SQLOS asks it to do so. This might give sign that it is leaking memory BUT IT IS NOT.
As you already said AOAG is working fine so I am presuming there is nothing much to worry. To monitor memory usage in SQL Server 2012 you can use below counters
SQL Server: Memory Manager-- Target Server Memory (KB)
SQL Server: Memory Manager--Total Server Memory (KB)
SQL Server: Memory Manager- Free Memory (KB)
SQL Server: Memory Manager--Database Cache Memory (KB)
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Memory leak in "Tenured Generation" heap (JVM 1.5)?!

For about over a year, I'm trying to hunt down the memory leak in our server application. But after all the improvements I've made (especially with 'forgotten' listeners that didn't exist anymore), I'm confident that the application doesn't have a memory leak anymore. At least the new "jconsole.exe" tool of JDK 1.5 shows me a very intersting behaviour:
Even if the server app is doing nothing than one thread polling a database table for possible new jobs to process, the memory slightly increases over time ... very slightly. It's just like the screenshot at
http://java.sun.com/j2se/1.5.0/docs/guide/management/jconsole.html#memory
where you might find a very slight tendency up. I run jconsole the whole day to track the application on a computer where no jobs got processed, so the application only sit there there whole day and just one thread has a loop that polls a database table via JDBC and doesn't get a result. The result is, that the memory chart is like the chart in the screenshot of the link above just with much more jaggies. About every 20 minutes, garbage collection seems to kick in, as the jaggie line drops about several megabytes just to increase again slowly.
Of course the thread loop creates objects but it doesn't hold any (debugged it several times and it is quite easy code). So this behaviour makes sense. But it doesn't make sense that the memory usage overall slowly increases over many hours (ultimativaly leading to an OutOfmemoryError).
So far, I still thought, it must be a memory leak in my application. But then, I played with jConsole and noticed this: if I just display the Memory Pool "Eden Space", the jagged line always drops down to the same level, i.e. no memroy leak. The "Survivor Space" is also constant in average (no memory leak). But the "Tenured Generation" line shows this memroy leak behaviour (slowly increases). This space is described as:
Tenured Generation (heap): pool containing objects that have existed for some time in the survivor space.
So, I'm not so sure anymore if this memory must be in my application. Unfortunately, jConsole doesn't show some kind of object tree that can be browsed and I would see what kind of object (collection) increase.
I tried profiling my application, but the profiled app runs so slowly that it would need many days or weeks until it's possible to identify some bad objects.
Is there another way to identify such memory waisters?

Write a main() that does the polling in a tight loop 1000 times. Then System.gc(); Thread.sleep(1000); System.exit(). Run the thing with -Xrunhprof. Observe the "live bytes" and "live objs" columns in the generated java.hprof.txt file. Anything that strikes as suspicious? If every polling round leaks one object, there's likely to be 1000 (or N*1000) of something live. Make sure the leak is in the polling routine by running it 1,000,000 rounds and getting an OutOfMemory.

Memory leak puzzle

Hello guys,
I'm having a very, very difficult time debugging this memory leak on my server. I'm pretty sure it's related to berkeley DB XML, bu I just couldn't prove this in numbers.
My server: Debian GNU/Linux 2.4.27-2-386 #1 Wed Aug 17 09:33:35 UTC 2005 i686 GNU/Linux, 512 MB of RAM, Pentium 4-class processor.
Here's the behaviour. I start Tomcat 5.5.15, the application is loaded, current memory status:
delegaciainterativa:~# free -m
total used free shared buffers cached
Mem: 440 346 94 0 14 282
-/+ buffers/cache: 49 391
Swap: 909 4 905
So, I've got 94 MBs of free memory. Now, here's this JSP I'm running:
<%@ page language="java" %>
<%@ page session="true" %>
<%@ page import="br.gov.al.delegaciainterativa.admin.*"%>
<%@ page import="br.gov.al.delegaciainterativa.controles.*"%>
<%@ page import="br.gov.al.delegaciainterativa.admin.areas.*"%>
<%@ page import="br.gov.al.delegaciainterativa.controles.BdbXmlAmbiente"%>
<%@ page import="java.util.*"%>
<%@ page import="javax.servlet.RequestDispatcher"%>
<%@ page import="com.sleepycat.dbxml.XmlContainer"%>
<%@ page import="com.sleepycat.dbxml.XmlDocument"%>
<%@ page import="com.sleepycat.dbxml.XmlException"%>
<%@ page import="com.sleepycat.dbxml.XmlIndexDeclaration"%>
<%@ page import="com.sleepycat.dbxml.XmlIndexSpecification"%>
<%@ page import="com.sleepycat.dbxml.XmlQueryContext"%>
<%@ page import="com.sleepycat.dbxml.XmlQueryExpression"%>
<%@ page import="com.sleepycat.dbxml.XmlResults"%>
<%@ page import="com.sleepycat.dbxml.XmlTransaction"%>
<%@ page import="com.sleepycat.dbxml.XmlUpdateContext"%>
<%@ page import="com.sleepycat.dbxml.XmlValue"%>
<%@ page import="com.sleepycat.dbxml.XmlUpdateContext"%>
<%@ page import="com.sleepycat.dbxml.XmlQueryContext"%>
<%@ include file="config.jsp"%>
<%!
 final String _grupoPagina = "visualizaLogsUsuario";
%>

<%
 HttpSession sessao = request.getSession(true);
 BdbXmlAmbiente bdbxmlAmbiente = new BdbXmlAmbiente();
 XmlContainer container = bdbxmlAmbiente.abrirContainer(Config.getNomeContainerBO());
 String fullquery = "";
 fullquery = "for $i in collection('"+ Config.getNomeContainerBO() +"')/BO \n";
 fullquery += "where $i/cadastro/fim/data/date >= '2006-00-00' \n";
 fullquery += "return $i";
ArrayList docs = new ArrayList();
XmlResults results = null;
 XmlValue value = null;
 XmlDocument document = null;
try {
 XmlQueryContext context = bdbxmlAmbiente.getEnvironmentInit().getManager().createQueryContext();
 context.setEvaluationType(XmlQueryContext.Eager);
 XmlQueryExpression xqe = bdbxmlAmbiente.getEnvironmentInit().getManager().prepare(fullquery, context);
 results = xqe.execute(context);
 out.println("fez busca, deletando...");
while (results.hasNext()) {
 value = results.next();
document = value.asDocument();
 document.fetchAllData();
 out.println(document.getName() + " ");
//out.println("total: " + results.size() + "");
} catch (Throwable e) {
 out.println(e);
e.printStackTrace();
} finally {
 results.delete();
%>
This basically loads about 1600 small documents (~5KB) from the container, and guess how memory is now:
delegaciainterativa:~# free -m
total used free shared buffers cached
Mem: 440 429 11 0 14 282
-/+ buffers/cache: 132 308
Swap: 909 4 905
That's about 83Mbs consumed!! And if I perform other searches like this, this keeps eating up more and more memory, then swapping and getting slow... and sometimes crashing Tomcat.
Here's the big mistery: the memory NEVER GETS RELEASED. Even calling delete(), as I did explicitily, it doesnt release the memory. It keeps increasing as searches are performed.
Now, let's go to the profiler. I've installed JProfiler and run it on this server, and here're the results: http://freeunix.com.br/All_Objects.html
Even more puzzling, I havent got any impressive amount of memory consumption.
So, what can I do to figure this out? The only way to release memory is to restart the server once and a while, which far from ideal.
I'd really would appreciate any help about this, since I'm on production with this server.
cheers,
-- Breno Jacinto

Hello George,
 I tried this:
<%
 HttpSession sessao = request.getSession(true);
 BdbXmlAmbiente bdbxmlAmbiente = new BdbXmlAmbiente();
 XmlContainer container = bdbxmlAmbiente.abrirContainer(Config.getNomeContainerBO());
 String fullquery = "";
 fullquery = "for $i in collection('"+ Config.getNomeContainerBO() +"')/BO \n";
 fullquery += "where $i/cadastro/fim/data/date >= '2006-00-00' \n";
 fullquery += "return $i";
 ArrayList docs = new ArrayList();
 XmlResults results = null;
 XmlValue value = null;
 XmlDocument document = null;
 try {
 XmlQueryContext context = bdbxmlAmbiente.getEnvironmentInit().getManager().createQueryContext();
 context.setEvaluationType(XmlQueryContext.Eager);
 XmlQueryExpression xqe = bdbxmlAmbiente.getEnvironmentInit().getManager().prepare(fullquery, context);
 results = xqe.execute(context);
 out.println("fez busca, deletando...");
 while (results.hasNext()) {
 value = results.next();
 document = value.asDocument();
 document.fetchAllData();
 out.println(document.getName() + " ");
 value.delete();
 document.delete();
 //out.println("total: " + results.size() + "");
 context.delete();
 xqe.delete();
 results.delete();
 } catch (Throwable e) {
 out.println(e);
 e.printStackTrace();
%>
 Don't you think that it's too much to consume ~80 MBs of RAM, in a search that returns ~1600 5 KB documents? And worse, this amount is never released.
 I'm wondering if there's any configuration issue here? Such as JVM's Heap size, or BDBXML Environment Initialization?
thanks,
-- Breno

Memory Leak - GC scope

Hi,
I have a pervasive memory leak in my server application. I have used JProfiler to track it down and indeed after 10 or so hours of execution I can see clearly the Java classes which are increasing in count. For my application they are (in order of total memory size used):
byte[]
<class>[]
String
QueueLink(custom class)
Knowing where my system leaks memory is nice, but on trawling the code I cannot really see why it really leaks and therefore am unable to fix it. One thing I do not quite get about Java is the garbage collector scope. If I have a loop, like so below:
while (true)
Object o = new Object();
...do something with 'o'
then for every loop iteration 'o' is initialize to a new Object. But the old reference of o (from the previous iteration) is for all intents a purposes gone. BUT, does this get collected by the GC or does it only get collected when the scope leaves the while loop? If the latter then UNTIL the loop terminates I will "leak" memory, which would go part way to explaining my problem.
Any ideas, any suggestions on how I can fix my leak(s)?
Regards,
NC

... then for every loop iteration 'o' is initializeto a
new Object. But the old reference of o (from the
previous iteration) is for all intents a purposes
gone. BUT, does this get collected by the GC ordoes
it only get collected when the scope leaves thewhile
loop?It has nothing to do with variable scope in this
case. The object that 'o' used to reference is no
longer reachable (unless something else in that loop
made another reference to it, such as adding it to a
collection which is still reachable), so it is
eligible for GC.The question is, will it be GCed.
I remember hearing a few years back that the VM--or certain VMs--might not collect any eligible local variables until after the method completes, or something to that effect. If so, then an infinite while(true) { new Object(); } loop will exhaust the heap rather quickly. Even if that was true back then, I doubt it's true of Sun's VM today.

Dequeue memory leak ?

Hi
I have the following code to dequeue a message:
public static AqMsg2 deQueueMsg(Connection p_cn, String p_queueowner, String p_queuename) throws SQLException {
//Disable autocommit
p_cn.setAutoCommit(false);
//Get a reference to the queue
AqMsg2 v_AqMsg2 = null;
AQSession aqs = null;
AQQueue aqq = null;
AQMessage aqm = null;
AQDequeueOption dq_option = new AQDequeueOption();
dq_option.setDequeueMode(AQDequeueOption.DEQUEUE_REMOVE);
dq_option.setWaitTime(AQDequeueOption.WAIT_FOREVER);
AQDriverManager.registerDriver(new AQOracleDriver());
aqs = AQDriverManager.createAQSession(p_cn);
aqq = aqs.getQueue(p_queueowner, p_queuename );
//Retrieve the message from the queue
aqm = ((AQOracleQueue)aqq).dequeue(dq_option, AqMsg2.getFactory());
AQObjectPayload payload = aqm.getObjectPayload();
v_AqMsg2 = (AqMsg2) payload.getPayloadData();
//Return the payload-Object class
return v_AqMsg2;
The line
aqm = ((AQOracleQueue)aqq).dequeue(dq_option, AqMsg2.getFactory());
is somehow giving a memory leak. For each time the method is called the total memory used by the jvm is getting bigger, and the GC ain't freeing it.
I surpose that the dequeue method in AQOracleQueue is using a OracleCallableStatement and a resultset.
Is both of these closed when the methodcall is done ?
Is this a bug or is it something in my code ?
Ole
null

Hi all,
I am planning to use JAVA AQ API to dequeue the messages. I would like to know where exactly the memory leak occurs.
For example, I run my java class (In the java class will contain dequeue process using JAVA AQ API) in server A to make a JDBC connection call to server B to kick off the dequeuing process. The server B has an oracle database with version: 9.0.1.5. Does the memory leak occurs in Server A where I kick off the process or in server B where the queue is actually resides.
Is there specific version of 9i that the memory leak happens?
Thanks in advance for any advice.

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 issue with link server between SQL Server 2012 and Oracle

Hi,
We are trying to use the linked server feature with SQL Server 2012 to connect SQL server and Oracle database. We are concerned about the existing memory leak issue. For more context please refer to the link.
http://blogs.msdn.com/b/psssql/archive/2009/09/22/if-you-use-linked-server-queries-you-need-to-read-this.aspx
The above link talks about the issues with SQL Server versions 2005 and 2008, not sure if this is still the case in 2012. I could not find any article that talks about if this issue was fixed by Microsoft in later version.
We know that SQL Server process crashes because of the third-party linked server provider which is loaded inside SQL Server process. If the third-party linked server provider is enabled together with the
Allow inprocess option, the SQL Server process crashes when this third-party linked server experiences internal problems.
We wanted to know if this fixed in SQL Server 2012 ?

So your question is more of a information type or are you really facing OOM issue.
There can be two things for OOM
1. There is bug in SQL Server which is causing the issue which might be fixed in 2012
2. The Linked server provider used to connect to Oracle is not upto date and some patch is missing or more recent version is to be used. Did you made sure that you are using latest version.
What is Oracle version you are trying to connect(9i,10g, R2...)
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

What is the best way to deal with memory leak issue in sql server 2008 R2

What is the best way to deal with memory leak issue in sql server 2008 R2.

What is the best way to deal with memory leak issue in sql server 2008 R2.
I have heard of memory leak in OS that too because of some external application or rouge drivers SQL server 2008 R2 if patched to latest SP and CU ( may be if required) does not leaks memory.
Are you in opinion that since SQL is taking lot of memory and then not releasing it is a memory leak.If so this is not a memory leak but default behavior .You need to set proper value for max server memory in sp_configure to limit buffer pool usage.However
sql can take more memory from outside buffer pool if linked server ,CLR,extended stored procs XML are heavily utilized
Any specific issue you are facing
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Memory leak on SunOne Web Server 6.1 on application reload

Hi!
I am pretty sure that i have found a memory management problem in
SunOne Web Server 6.1 .
It started with an OutOfMemory error we got under heavy load . After
some profiling with Jprofiler i didn't find any memory leaks in the
application.Even under heavy load (generated by myself) i can't find
anything ,more, i can't reproduce the error! The memory usage is
about 20Mb and does not go up .
However it is pretty simple to see the following behavior:
[1] Restart the server (to have a clear picture) and wait a little for
memory usage to stabilize.
[2] In the application dir. touch .reload or one of the classes:
The memory usage goes up by another 50Mb (huge amount of mem. taking
into account the fact that it used only 20Mb under any load befor).
Do this another time and another 20Mb gone etc..
The JProfiler marks the memory used by classes . And it can be
clearly seen the GC can't release most of it.
I AM sure this is not the application that takes all the memory.
Another hint : after making the server to reload application i can see
that the number of threads ON EVERY RELOAD is going up by ~10-20
threads .The # of threads goes lower over time but not the mem usage.
My system:
Sparc Solaris 9 ,Java 1.4.2_04-b05, Sun ONE Web Server 6.1SP5
Evgeny

my guess is that - because of '.reload' , web container tries to
recompile all the classes that you use within your web application and
hence the memory growth is spiking up.What do you mean by "tries to recompile"?The classes in
Web-inf are already compiled! And i have only ~5 jsp's .
(the most part of the applic. is a complicated business logic)
If you are talking about reloading them ,yes,that's the purpose of .reload,
isn't it? :).But it seems that container uses the memory for it's own
classes: the usage of memory for my classes don't really grow
that much (if at all) after reload (according to profiler)
Also the real problem is that the memory usage grows to much for
too long (neither seen it going down) and thus ends with OutOfMemory.
if you are seeing the memory growth to be flat in stress environment,
then I am not sure that why do you think that there is a memory leak ?There is no memory leak in stress environment.
There is memory leak while reloading the application.
It is a memory hog for sure (~20-30Mb for every reload).
Memory leak?It seems that way because i can't see memory usage go
down and after a lot of reloads OutOfMemory is thrown.
also, what is jvm heap that you use ? did you try jvm tune options like -
XX:+AggressiveHeap ?256Mb.I can set it bigger ,but how do i know that it will not just delay
the problem ?
Thanks for response.
Evgeny

Maximize server uptime - memory leak?

Since we stabilized the newly introduced WLI 8.1 application we are now fine tuning the JVM. We are facing some kind of memory leak which forces us to reboot the WLS instances daily.
I'm now asked to identify some strategies how we could let the WLI instances run for longer than 1 day. My goal is 7 days, so that the machines must only be touched once a week. The relevant JVM settings are like this:
-Xms2048m -Xmx2048m -Xmanagement -Djrockit.managementserver.port=30011 -XgcPrio:throughput
I've choosen the "throughput" strategy as we have here a systems which acts asynchronously most of the time (WLI). I have attached two JRA records. The first ("1day") shows a system which has an uptime of now 16 hours. The heap utilization is almost all the time between 90%-100%. Things get worse after a while. In the consequence we are rebooting the server when we see more and more timeout-exceptions in our WLI layer and heavy GC activity ("average time spent in GC")
The other record ("leakdetector") shows a system which is now running for almost 3 hours. Here I connected the memory leak detector. The graph looks a bit better / more balanced. Means, that after 3 hours the avg heap util remains between the margins of 40-50 %. The trend of the bottom margin however clearly indicates an increasing memory footprint.
To understand this in more detail I started using the memory leak analyzer. So far I got no benefit from using the tool, though it looks very impressive. However, when I connect the memory leak analyzer I can observe some strange heap graph changes. I suppose the memory leak detector has some impact onto the GC strategies, doesn't it? My heap graph looks totally different with no leak detector attached. What can be the reason on this?
Also I'm quite a bit confused why the "Growth" indicator always stays at 0 bytes/sec, even when I can see that objects are getting bigger and bigger. What is the secret here?
i appreciate every comment you have on my case,
thanks a lot

You might also look at approaching the problem for a different perspective. Which transactions, requests, components are creating the most amount of memory? What concurrent requests where active when the memory jumped or an OOME was thrown. I have found this approach effective in getting a good idea on where to focus memory diagnostics after ruling of course a resource capacity issue.
The following article discusses the difference between a leak and a capacity problem.
http://www.jinspired.com/products/jxinsight/outofmemoryexceptions.html
Also you should try high level monitoring to see whether there are global patterns in metric data that provides clues. This blog entry shows what is possible with professional performance management tools with visualizations going beyond pie charts and table views.
Beautiful Evidence: Metric Monitoring
http://blog.jinspired.com/?p=33
There are also many low level memory inspection tools on the market that might help quickly navigate the heap and identify the problem though I think the JRA tool has probably most of the same features.
Regards,
William Louth
JXInsight Product Architect
CTO, JInspired
"Java EE tuning, testing, tracing, and monitoring with JXInsight"
http://www.jinspired.com

Microsoft Jdbc driver for SQL Server memory leak

I'm using Microsoft Jdbc driver and see there's some leak after running application for a while. I'm sure that it's from Jdbc driver because I sitch to Jtds and the issue went away. My question is is there anybody knows which web sites talk about memory leak issue in Microsoft Jdbc driver for SQL Server?
Appreciate your help

I'm using Microsoft Jdbc driver and see there's some leak after running application for a while. I'm sure that it's from Jdbc driver because I sitch to Jtds and the issue went away. My question is is there anybody knows which web sites talk about memory leak issue in Microsoft Jdbc driver for SQL Server?
Appreciate your help

Memory leak in NFS server

Similar Messages

Maybe you are looking for