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
Similar Messages
-
How to increase the memory for my weblogic server in Jdeveloper 12.1.2.0.0 ?
Hey everyone,
So as my title says, i'm trying to increase the memory for my weblogic server in my windows 7 64 bit machine, with 8GB ram.
The values appear to be: JAVA Memory arguments: -Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=512m
I've done some search from this forum and i've added this to my jdev.conf:
AddVMOption -XX:MaxPermSize=1536M (in this one i've only changed the value)
AddVMOption -Xmx1536M
AddVMOption -Xms1536M
And i've changed this: MEM_ARGS="-Xms1024m -Xmx1024m" in my startNodeManager.sh file
I'm still getting the same line in my server but i need to change the values since i'm not getting the server to run my application very well (it gets stucked in loading my databases and graphs) and i think it will continue untill i get a heap exception error.
Any ideas of how to change this?
Regards,
Frederico.Thanks Alejandro .
I'm going to ask you another question and this one is quite important.
Whenever i run my project a couple of times, i'm not able to retrieve the page, it just gets stuck on loading.
It just stops the loading, like its a really really slow page. I'm not using a lot of rows in my database so i don't take to much memory but it doesn't load and i know everything is fine but i just added some graphs after testing it.
Do you know why?
In the console it says that everything is fine and shows the link for the page but it never loads completely until it gives a error because it does not respond in 600 seconds.
Strange right? -
Memory leak in weblogic 6.0 sp2 oracle 8.1.7 thin driver
Hi,
I have a simple client that opens a database connection, selects from
a table containing five rows of data (with four columns in each row)
and then closes all connections. On running this in a loop, I get the
following error after some time:
<Nov 28, 2001 5:57:40 PM GMT+06:00> <Error> <Adapter>
<OutOfMemoryError in
Adapter
java.lang.OutOfMemoryError
<<no stack trace available>>
>
<Nov 28, 2001 5:57:40 PM GMT+06:00> <Error> <Kernel> <ExecuteRequest
failed
java.lang.OutOfMemoryError
I am running with a heap size of 64 Mb. The java command that runs
the client is:
java -ms64m -mx64m -cp .:/opt/bea/wlserver6.0/lib/weblogic.jar
-Djava.naming.f
actory.initial=weblogic.jndi.WLInitialContextFactory
-Djava.naming.provider.url=
t3://garlic:7001 -verbose:gc Test
The following is the client code that opens the db connection and does
the select:
import java.util.*;
import java.sql.*;
import javax.naming.*;
import javax.sql.*;
public class Test {
private static final String strQuery = "SELECT * from tblPromotion";
public static void main(String argv[])
throws Exception
String ctxFactory = System.getProperty
("java.naming.factory.initial");
String providerUrl = System.getProperty
("java.naming.provider.url");
Properties jndiEnv = System.getProperties ();
System.out.println ("ctxFactory : " + ctxFactory);
System.out.println ("ProviderURL : " + providerUrl);
Context ctx = new InitialContext (jndiEnv);
for (int i=0; i <1000000; i++)
System.out.println("Running query for the "+i+" time");
Connection con = null;
Statement stmnt = null;
ResultSet rs = null;
try
DataSource ds = (DataSource) ctx.lookup
(System.getProperty("eaMDataStore", "jdbc/eaMarket"));
con = ds.getConnection ();
stmnt = con.createStatement();
rs = stmnt.executeQuery(strQuery);
while (rs.next ())
//System.out.print(".");
//System.out.println(".");
ds = null;
catch (java.sql.SQLException sqle)
System.out.println("SQL Exception : "+sqle.getMessage());
finally
try {
rs.close ();
rs = null;
//System.out.println("closed result set");
} catch (Exception e) {
System.out.println("Exception closing result set");
try {
stmnt.close ();
stmnt = null;
//System.out.println("closed statement");
} catch (Exception e) {
System.out.println("Exception closing result set");
try {
con.close();
con = null;
//System.out.println("closed connection");
} catch (Exception e) {
System.out.println("Exception closing connection");
I am using the Oracle 8.1.7 thin driver. Please let me know if this
memory leak is a known issue or if its something I am doing.
thanks,
rudyRepost in JDBC section ... very serious issue but it may be due to Oracle or
to WL ... does it happen if you test inside WL itself?
How many iterations does it take to blow? How long? Does changing to a
different driver (maybe Cloudscape) have the same result?
Peace,
Cameron Purdy
Tangosol Inc.
<< Tangosol Server: How Weblogic applications are customized >>
<< Download now from http://www.tangosol.com/download.jsp >>
"R.C." <[email protected]> wrote in message
news:[email protected]...
Hi,
I have a simple client that opens a database connection, selects from
a table containing five rows of data (with four columns in each row)
and then closes all connections. On running this in a loop, I get the
following error after some time:
<Nov 28, 2001 5:57:40 PM GMT+06:00> <Error> <Adapter>
<OutOfMemoryError in
Adapter
java.lang.OutOfMemoryError
<<no stack trace available>>
>
<Nov 28, 2001 5:57:40 PM GMT+06:00> <Error> <Kernel> <ExecuteRequest
failed
java.lang.OutOfMemoryError
I am running with a heap size of 64 Mb. The java command that runs
the client is:
java -ms64m -mx64m -cp .:/opt/bea/wlserver6.0/lib/weblogic.jar
-Djava.naming.f
actory.initial=weblogic.jndi.WLInitialContextFactory
-Djava.naming.provider.url=
t3://garlic:7001 -verbose:gc Test
The following is the client code that opens the db connection and does
the select:
import java.util.*;
import java.sql.*;
import javax.naming.*;
import javax.sql.*;
public class Test {
private static final String strQuery = "SELECT * from tblPromotion";
public static void main(String argv[])
throws Exception
String ctxFactory = System.getProperty
("java.naming.factory.initial");
String providerUrl = System.getProperty
("java.naming.provider.url");
Properties jndiEnv = System.getProperties ();
System.out.println ("ctxFactory : " + ctxFactory);
System.out.println ("ProviderURL : " + providerUrl);
Context ctx = new InitialContext (jndiEnv);
for (int i=0; i <1000000; i++)
System.out.println("Running query for the "+i+" time");
Connection con = null;
Statement stmnt = null;
ResultSet rs = null;
try
DataSource ds = (DataSource) ctx.lookup
(System.getProperty("eaMDataStore", "jdbc/eaMarket"));
con = ds.getConnection ();
stmnt = con.createStatement();
rs = stmnt.executeQuery(strQuery);
while (rs.next ())
//System.out.print(".");
//System.out.println(".");
ds = null;
catch (java.sql.SQLException sqle)
System.out.println("SQL Exception : "+sqle.getMessage());
finally
try {
rs.close ();
rs = null;
//System.out.println("closed result set");
} catch (Exception e) {
System.out.println("Exception closing result set");
try {
stmnt.close ();
stmnt = null;
//System.out.println("closed statement");
} catch (Exception e) {
System.out.println("Exception closing result set");
try {
con.close();
con = null;
//System.out.println("closed connection");
} catch (Exception e) {
System.out.println("Exception closing connection");
I am using the Oracle 8.1.7 thin driver. Please let me know if this
memory leak is a known issue or if its something I am doing.
thanks,
rudy -
I've created a simple servlet to EJB skeleton and built a stress testing
tool to make sequential requests to the servlet which in turn creates an
instance of a stateless session been. Both the servlet and bean do not have
any real logic in them, just some minimal timing output.
When run for a few million iterations, the WebLogic JVM slowly leaks memory
that cannot be reclaimed even with force garbage collection from the
WebLogic console. Below are 3 snippets of code showing the servlet, the EJB
call, and the simple client test.
If anyone else is ecperiencing similar problems or can see a flaw, I'd be
most grateful.
Andy
Servlet code
protected void doGet(HttpServletRequest req, HttpServletResponse res)
throws ServletException, IOException
TestBean bean;
long requestStartTime = System.currentTimeMillis();
res.setContentType("text/html");
PrintWriter out = res.getWriter();
out.println("<html><head><title>Hello World!</title></head>");
out.println("<body><h1>Hello World!</h1></body></html>");
try {
bean = home.create();;
bean.testMethod();
catch (Exception e) {
totalTime += (System.currentTimeMillis() - requestStartTime);
Bean code
public class TestBean implements SessionBean {
private SessionContext ctx;
public void ejbActivate() {
public void ejbPassivate() {
public void ejbCreate() {
public void ejbRemove() {
public void setSessionContext(SessionContext ctx) {
this.ctx = ctx;
public void testMethod() {
Client code
public void simulateLoad()
throws IOException
long totalRequestTime = 0, requestTime, requestStartTime;
long totalResponseTime = 0, responseTime, responseStartTime;
try {
log("Opening connection to "+ url + (debug ? "?debug=true" : ""));
for (int i = 1; i <= numRequests; i++) {
HTTPConnection con = new HTTPConnection("localhost",7001);
HTTPResponse rsp;
byte data[];
if ((i % 10000) == 0) {
log("\nGET Request "+i+" to "+ url + (debug ? "?debug=true" :
requestStartTime = System.currentTimeMillis();
rsp = con.Get("/mcumanager" + (debug ? "?debug=true" : ""));
requestTime = System.currentTimeMillis() - requestStartTime;
responseStartTime = System.currentTimeMillis();
if (rsp.getStatusCode() >= 300) {
log("Received Error: "+rsp.getReasonLine());
log(new String(rsp.getData()));
else
data = rsp.getData();
responseTime = System.currentTimeMillis() - responseStartTime;
totalRequestTime += requestTime;
totalResponseTime += responseTime;
if ((i % 10000) == 0) {
log("GET Response "+i+": "+rsp);
if ((i % 100) == 0) {
log ("Avg request time :
"+((float)totalRequestTime/(float)i)+"ms");
log ("Avg response time :
"+((float)totalResponseTime/(float)i)+"ms");
catch (IOException ioe) {
log(ioe.toString());
ioe.printStackTrace();
catch (ModuleException me) {
log("Error handling request: " + me.getMessage());
me.printStackTrace();
Please read discussion "WLS dies during stress testing" & "performance
degradation PROBLEM" in interest.performance.
Hope it helps.
Cheers - Wei
Andy Riedel <[email protected]> wrote in message
news:[email protected]...
> I have additional information on this problem. I have replicated the exact
> same memory leak issue using the included HelloWorldServlet. I use Jrun's
> ServletKiller stress tool running 16 simultaneous request threads
requesting
> the HelloWorldServlet. This WebLogic 5.1 server will leak memory and
> eventually run out of memory all together with an OutOfMemoryException
after
> about 6-8 hours. This indicates that the bug is in the base HTTP Servlet
> engine code.
>
> I have tried turning off the http log (i.e. access.log) as well as
> notification events from the servlet engine and it still leaks memory.
>
> Andy
>
>
>
> Andy Riedel Chief Architect HearMe Call me through VoiceCONTACTtm -- right
> from your computer. Online Status:
> "Andy Riedel" <[email protected]> wrote in message
> news:[email protected]...
> > I've created a simple servlet to EJB skeleton and built a stress testing
> > tool to make sequential requests to the servlet which in turn creates an
> > instance of a stateless session been. Both the servlet and bean do not
> have
> > any real logic in them, just some minimal timing output.
> >
> > When run for a few million iterations, the WebLogic JVM slowly leaks
> memory
> > that cannot be reclaimed even with force garbage collection from the
> > WebLogic console. Below are 3 snippets of code showing the servlet, the
> EJB
> > call, and the simple client test.
> >
> > If anyone else is ecperiencing similar problems or can see a flaw, I'd
be
> > most grateful.
> >
> > Andy
> >
> >
> > Servlet code
> > -------------
> >
> > protected void doGet(HttpServletRequest req, HttpServletResponse res)
> > throws ServletException, IOException
> > {
> > TestBean bean;
> >
> > long requestStartTime = System.currentTimeMillis();
> >
> > res.setContentType("text/html");
> > PrintWriter out = res.getWriter();
> > out.println("<html><head><title>Hello World!</title></head>");
> > out.println("<body><h1>Hello World!</h1></body></html>");
> >
> > try {
> > bean = home.create();;
> > bean.testMethod();
> > }
> > catch (Exception e) {
> > }
> >
> > totalTime += (System.currentTimeMillis() - requestStartTime);
> > }
> >
> > Bean code
> > -----------
> > public class TestBean implements SessionBean {
> >
> > private SessionContext ctx;
> >
> > public void ejbActivate() {
> > }
> >
> > public void ejbPassivate() {
> > }
> >
> > public void ejbCreate() {
> > }
> >
> > public void ejbRemove() {
> > }
> >
> > public void setSessionContext(SessionContext ctx) {
> > this.ctx = ctx;
> > }
> >
> > public void testMethod() {
> > }
> > }
> >
> > Client code
> > ------------
> > public void simulateLoad()
> > throws IOException
> > {
> > long totalRequestTime = 0, requestTime, requestStartTime;
> > long totalResponseTime = 0, responseTime, responseStartTime;
> >
> > try {
> > log("Opening connection to "+ url + (debug ? "?debug=true" : ""));
> >
> > for (int i = 1; i <= numRequests; i++) {
> >
> > HTTPConnection con = new HTTPConnection("localhost",7001);
> > HTTPResponse rsp;
> > byte data[];
> >
> > if ((i % 10000) == 0) {
> > log("\nGET Request "+i+" to "+ url + (debug ? "?debug=true" :
> > ""));
> > }
> >
> > requestStartTime = System.currentTimeMillis();
> >
> > rsp = con.Get("/mcumanager" + (debug ? "?debug=true" : ""));
> >
> > requestTime = System.currentTimeMillis() - requestStartTime;
> >
> > responseStartTime = System.currentTimeMillis();
> >
> > if (rsp.getStatusCode() >= 300) {
> > log("Received Error: "+rsp.getReasonLine());
> > log(new String(rsp.getData()));
> > }
> > else
> > data = rsp.getData();
> >
> > responseTime = System.currentTimeMillis() - responseStartTime;
> >
> > totalRequestTime += requestTime;
> > totalResponseTime += responseTime;
> >
> > if ((i % 10000) == 0) {
> > log("GET Response "+i+": "+rsp);
> > }
> >
> > if ((i % 100) == 0) {
> > log ("Avg request time :
> > "+((float)totalRequestTime/(float)i)+"ms");
> > log ("Avg response time :
> > "+((float)totalResponseTime/(float)i)+"ms");
> > }
> > }
> > }
> > catch (IOException ioe) {
> > log(ioe.toString());
> > ioe.printStackTrace();
> > }
> > catch (ModuleException me) {
> > log("Error handling request: " + me.getMessage());
> > me.printStackTrace();
> > }
> > }
> >
> >
> >
> >
> >
>
>
-
ThreadLocalObject memory leak detected (Weblogic 8 SP6)
It seems that our application server (which heavily uses Entity and Stateless session beans) constantly creates weblogic.ejb20.internal.BaseEJBObject,ThreadLocalObject's in memory. These objects keep increasing and never go down.
In a typical 90 hr run we create upto 22,000,000 instances of these objects. Could someone explain what these are used for and how to fix this issue.Before you assume you have a memory leak, go to the "Monitoring"->"Performance" page of your server config. Set the page to auto-refresh (I think you can do that in 8.1). While your application is doing its work continuously, every 30 seconds or so, push the "garbage collect" button and watch the "percent free" amount immediately after the GC completes. Keep track of that number. If that number (the one after the GC completes) is continuously going down, and eventually causes an OutOfMemory error, then you have a memory leak. If not, then you probably don't.
-
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
BleuHowdy 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. -
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 PMThat 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.
-
Hello everyone.
I need some help with a problem we are having with our application. It consists on Servlets, JMS with MDBs, Xml parsing...
Our application dequeues messages from an Oracle Queue and sends xml-text message to a servlet. It also receives xml-text and enqueues objects in an Oracle Queue.
And it also has access to Oracle Database (context tables, etc).
We are doing everything on Tru64 Unix (and our tests on Win 2000) and we are using WebLogic 6.1.
Our problem is that we have found that it seems that the garbage collector is not running well. I mean, with the time our system is degrading. The memory use increases. It seems to be a memory leak.
We have used a testing tool, OptimizeIt, and we have found that there are
objects that are increasing the use of memory. If we use the option 'java -verbose' we find that it seems to be Hash objects (HashMap, Hashtable) which are increasing the use of memory. In our code we are not using any hashtable nor any class that extends from it (we have deleted everyone).
Can it be due to a problem with WebLogic? A problem with JMS, queues, etc? A problem with JNDI?
Could anybody please help us?
Thanks in advanced.Yes, we see that there are some entries of the type:
java/util/Hahstable$Entry
java/util/Hahstable
weblogic/jndi/Environment
This entries keep growing and growing with the time.
We have deleted all the Hashtable, Properties and all the kind of Collection objects. I guess WebLogic is using this objects in order to arrange our application runs.
Am I right? Do you know if we can do anything?
Thank you. -
Possible memory leak in Weblogic 7.0
We have developed an EJB application on Weblogic 7.0 running on HP-UX 11.0. Some
JSP/Javabean programs, that lookup EJB compoments for services, are developed
on the Resin web server to serve browser requests. Both Resin and Weblogic are
running on the same HP machine. JDK version is 1.3.1_06 for HP-UX.
The real memory is 2GB. Tha parameters to start Resin server are
-showversion -verbose:gc -Xms384m -Xmx384m -Xoptimize
The parameters to startup Weblogic are in the following:
-server -showversion -verbose:gc -Xms768m -Xmx768m -XX:NewSize=256m -XX:SurvivorRatio=6
-Xoptimize -XdoCloseWithReadPending
In our observations, the peak traffic is during the working hours. Only few users
(less than 40 users) stay in our system in the night and holidays.
And in our observations, the weblogic will do the GC if necessary. But some memory
are lost after each GC even not in the peak time. Thus, after running two or three
days, there are only lillte free memory for use, and the Weblogic begins to take
much time (10-30 seconds ) doing GC more often and often. At last, an OutOfMemory
error generated.
I hope that Weglogic can serve all the time.
Does anybody han as experience on this problem?Thanks for your kinfness.
We have wrote some single-user applications to test the Weblogic 7.0. We doubt
it is JDBC driver's problem.
We downloaded the Informix JDBC driver 2.21_JC2 to replace the older version 2.20_JC1
and retest our applications. The memory usage curve looks much better and the
applications run over three days.
We will continue to observe the execution. Maybe the JDBC driver is the real problem.
"Aravind Krishnasamy" <[email protected]> wrote:
I am not sure whether it's an application problem or application server
problem. Both are possible. I am not familar with HP Java Version.
It may be a problem due to loitering object. You can try doing testing
with
single user and the memory needs for the user.
NoteThe memory level before the test and after the test
Foce GC and you need to GC same level of HEAP Used, Profiling tools will
be
helpful to find application problem
Aravind
"Wen-Hung Yeh" <[email protected]> wrote in message
news:[email protected]...
We have developed an EJB application on Weblogic 7.0 running on HP-UX11.0. Some
JSP/Javabean programs, that lookup EJB compoments for services, aredeveloped
on the Resin web server to serve browser requests. Both Resin and Weblogicare
running on the same HP machine. JDK version is 1.3.1_06 for HP-UX.
The real memory is 2GB. Tha parameters to start Resin server are
-showversion -verbose:gc -Xms384m -Xmx384m -Xoptimize
The parameters to startup Weblogic are in the following:
-server -showversion -verbose:gc -Xms768m -Xmx768m -XX:NewSize=256m-XX:Su
rvivorRatio=6
-Xoptimize -XdoCloseWithReadPending
In our observations, the peak traffic is during the working hours.Only
few users
(less than 40 users) stay in our system in the night and holidays.
And in our observations, the weblogic will do the GC if necessary.But
some memory
are lost after each GC even not in the peak time. Thus, after runningtwo
or three
days, there are only lillte free memory for use, and the Weblogic beginsto take
much time (10-30 seconds ) doing GC more often and often. At last,an
OutOfMemory
error generated.
I hope that Weglogic can serve all the time.
Does anybody han as experience on this problem? -
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,
SharathActual 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 -
Possible memory leak in TagFileTagInfo class
Hello,
Our application is experiencing a memory leak in Weblogic, which is not happening in other application servers.
We are running Weblogic server 10.3 using the distributed jsf 1.2
Eclipse Memory Analyzer clearly points to TagFileTagInfo class as retaining a Map which holds all the memory. Furthermore, it shows that said map (called _tagFileInfoMap) is holding FileTagFileInfo class instances.
It could be possible that our application were doing something wrong, and that would cause the described behavior, however I doubt that as the other application servers where our application is deployed do not present this problem.
Any suggestion on how we should proceed to fix this problem?
Thanks
JuanHi,
Was this issue resolved by using wlappc?
Were you able to compile the tag files with wlappc? I tried compiling the jsps using wlappc, but it seems that the tool expects an ejb-jar file.
Any help on this is greatly appreciated.
Thanks
Hareesh -
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 setting for weblogic startup file in windows xp
Hi,
I want to change memory setting parameters for weblogic server 8.1 because I am using 128MB memory only.
I found some information edit the startWeblogic.cmd file and change the memory parameters with - x option.
but practically I didn't find the -x option in that file. Please tell me how can I change the memory parameters for weblogic server.
Sorry, I dont know whether it is related to this forum or not.
Regards,
sivaramHow can I change the memory of an instance or an instance in weblogic ?
Please Help
Thank you -
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";
%>
<font face="verdana" size="1">
<%
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("<p>fez busca, deletando...</p>");
while (results.hasNext()) {
value = results.next();
document = value.asDocument();
document.fetchAllData();
out.println(document.getName() + "<br>");
//out.println("<p>total: " + results.size() + "</p>");
} 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 JacintoHello 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("<p>fez busca, deletando...</p>");
while (results.hasNext()) {
value = results.next();
document = value.asDocument();
document.fetchAllData();
out.println(document.getName() + "<br>");
value.delete();
document.delete();
//out.println("<p>total: " + results.size() + "</p>");
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
Maybe you are looking for
-
OC4J EJBQL and EJB 2.0 features
Hello Debu Panda and All I've got all howtos and I mangaged to get some parts of OC4J [Oracle9iAS (9.0.3.0.0) Containers for J2EE (build 020323.1689)] working. There are still some issues that are stalling our development. Could you please comment on
-
PRKP-1001 CRS-0215 RAC unable to create instance in 2nd node.
HI, I configured oracle rac 10g on vmware. I configure oracle clusterware,oracle rac 10g software successfully. While creating database at the end ,I got the below error. PRKP-1001 : Error starting instance devdb2 on node rac2 CRS-0215: Could not sta
-
Anyone Used Kik Messenger Yet?
I was thinking about installing Kik. Has anyone used it yet and has the carrier tried to charge you for texting? On the Kik Website it says you can text for free. I just do not want to get a bill six months down line saying that I owe them money for
-
Upload FS Items master using flexible upload-SEM-BCS
I want to upload FS Items master using flexible upload in SEM BCS. I was wondering if i could have a sample upload format of the file. Kindly help. Ramanathan [email protected]
-
Headphone Jack Not Holding Connectors
All of a sudden my headphone jack on my MBP isn't holding headphones or speakers snugly. It feels like I'm having to constantly push the connector back into the jack. Any ideas on what might be causing it and what I can do about it?