OPMN vs Standalone OC4j (memory leak)

I run the same servlet application using standalone OC4J instance on solaris without any problem.
Trying to run the same application deployed in oracle enterprise (opmn) console causes memory leak. I see a lot of new classes allocated on each servlet invocation related to oracle.xml.* package and org.apache.axis.* (servlet uses axis to download attachment).
Did anybody see similar issues. Any thought are welcome.
thanks
Roman

To answer myself in case somebody was interested how to resolve this issue :
Using different xml parser (for ex. crimson, but most likely any other would be fine too) eleminated the problem.
i.e. adding the followning java system property
-Djavax.xml.parsers.SAXParserFactory=org.apache.crimson.jaxp.SAXParserFactoryImpl

Similar Messages

D8B3 - Standalone WLS memory leaks

I have a standalone WLS with FMWTOOLS_MAIN.D8B3_GENERIC_100218.1734.D08B03
Created with wlsconfig.sh
observing the following message in the log very frequently..almost for every request or so..
[2010-05-12T07:58:10.548-06:00] [AdminServer] [WARNING] [] [oracle.adf.share.ADFContext] [tid: Timer-18] [userId: SCMOPERATIONS] [ecid: 0000IYClSEJAPPB5JZd9if1BuLjB0000mq,1:21250] [APP: EarFscmAnalytics] Automatically initializing a DefaultContext for getCurrent.[[
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
Any idea on what this means? How to fix it?
Thanks, -Ram

Did you get a resolution for this? I am seeing the same issue. Thx.

Missing opmn.xml in OC4J standalone

Hi, I just downloaded the latest standalone version of OC4J. When I unpack it, there is no opmn.xml file in the archive at all.
I need to set some JVM options, and all instructions say to use this file. Is there some other way to set java options with the standalone version?
Thx in advance,
Davis

Davis,
You do not need opmn.xmml file for the standalone OC4J, and you can pass all the VM parameters on command line or add them in the start up batch file.
Please review this link.
Hope this helps.
Deepak

Memory leak in redeploy

I am doing some memory profiling for an application running inside OC4J standalone. When the application is redeployed to OC4J, OC4J does not release memory for servlets and all the instances that's defined as class variables, e.g. private static Object s_instace. So if the application is redeployed 5 times, I saw 5 instances in the memory while gabarge collection can not collect them, and eventually the application runs out of memory if redeployed multiple times without restarting OC4J. I am wondering if anyone has encountered this issue before?

Hello cguo:
Thanks for reporting the problem.
This is a recognized minor problem in oc4j standalone (and hence also in application server.) It is believed that the memory leak is not big enough to be a serious concern, unless an application is redeployed many times in a production environment, which is an unlikely. In any case, this bug should be fixed in the next oc4j production. Please try the next oc4j production release when it comes (when? I am not sure) and tell me if the problem still persists.

Memory Leak Issue in OBIEE 11g

Hi,
We have OBIEE 11.1.1.5 installed on a 32-bit Windows Server. We had almost 10GB of free space yesterday, but after a few users logged in, the free space started coming down until we were left with no space at all.
Since then we have removed all the files that we could and created more and more space, but OBIEE seems to be eating it all up. I have seen a few posts for such issues with the Linux Systems. Has anyone faced this with windows? Also, is there any solution for this.
Thanks,
Naman

Hi Naman,
Oracle has provided set of patches to avoid memory leaks.
1) For memory leak with OPMN, apply the following patches:
Patch:12920592: OPMN HAS MEMORY LEAK
Patch:12989751: OPMN MEMORY STILL GAINS AFTER APPLYING PATCH#12920592
2) For the Presentation Server (sawserver) issue, apply the patch:
Patch:13102881: DATALAYOUT METADATA IMPLEMENTATION HEAP INTENSIVE
Rgds,
Dpka

Memory leak and char[] ?

Hello all,
I'm not sure whether this post should be here or in WebLogic section, so correct me if I'm wrong.
I'm working on JDeveloper 11.1.1.3 while deployments are made on standalone WebLogic 10.3.3. This thing occurred in previous versions also.
With every deployment WebLogic increases it's used memory until the famous PermGen space error, which is after about 5-6 deployments.
I'm doing my best to understand how to use memleak detection tools. I've switched JDev and WL from Sun jdk which was used before to JRockit, same thing happens. Both JDev's memory profiler and JRockit mission control show something that I really do not understand. char[] uses around 30% of heap space and keeps growing with deployments, next is String with 8%. I never use char in app.
Am I looking at the wrong thing? Is it normal for char[] to increase on WebLogic on deployments? Does anyone know how to check other things and what to check? Someone on other forums mentioned it would be useful to check if ApplicationContext keeps initializing over again on deployments. Does anyone know how to check this?
One more thing, I have successfully deployed app on Tomcat, and Tomcat said there is a memory leak in app, but could not tell anything specific.
I'm kinda lost in this :(

It is normal for the PermGen space of the Sun's JVM to get filled after several re-deployments. PermGen stands for "permanent generational". This space is used by classes that is unlikely to need to be garbage-collected, so they are placed in this memory space that is never garbage-collected (for example, the Class instances). When you redeploy an application, a new class loader instance is used and it instantiates new Class instances that fill up the PermGen space. But why this happens on JRockit either, I could not explain.
We have experienced memory leaks related to classes and components that use native memory. For example, we have had significant memory leak when using Oracle's JDBC OCI driver. We were not able to solve this problem, so we switched to JDBC Thin driver (which is very performant and stable today comparing to some years ago). If you are using Oracle JRockit, you can monitor the overall memory usage by the following JRockit command executed at OS command line:
jrcmd <jrockit_pid> print_memusage>where <jrockit_pid> should be replaced by the JVM process ID.
If you suspect existence of native memory leaks, then have a look at the article Thanks for the memory for explanations about how Java uses native memory.
Dimitar

OBIEE 11.1.1.5 Memory Leak issues

Hardware: 64 bit Red Hat Linux Enterprise server 5.2(Tikanga)
Software: OBIEE 11.1.1.5 64 bit
Issue: The memory usage on the server slowly creeps up and occupies almost all of the available memory, then starts swapping.
In our case we have a 48GB RAM 2CPU Linux box on which OBIEE 11.1.1.5 was installed and once we startup Weblogic Server, NodeManager, Managed Server, and OPMN, the memory usage starts at ~4GB and slowly creeps up to ~45GB. The processes do not release the memory back even after shutting down all the services (OPMN, Managed Server, Weblogic Server and Node Manager).
The memory is released only after the Linux box is rebooted.
We have the same software on different boxes which have 8GB RAM and the behavior is same there too. It occupies all of 8GB RAM and then swaps over another 4GB space. Is there a software leak with OBIEE 11.1.1.5 or is it a configuration issue?
We found similar issues reported in forums at Memory Leak on OBIEE webserver 11G (linux version) But there was no resolution.

All,
We're having a similar issue, or at least we think we are on our 64-bit VM Windows environment, running OBIEE 11.1.1.3. Our PROD environment was OS level patched last Tuesday and rebooted, and now it's super slow and using way more RAM than before. Even if we reboot the server, our Managed server (bi_server1) is not working properly. Basically in DEV the Admin and Managed servers are using around 900 MB or RAM, in our PROD env that isn't working properly, the Admin server seems fine at about 900 MB of RAM, but our Managed server is up around 1.4 GB and now taking about 45 minutes to start instead of around 6. We also logged an SR about a week ago to no avail so far, and as you said, it's been going back and forth with the OBIEE and WebLogic teams. If anyone knows anything about this it would be great to hear it!
Thanks,
Josh
Edited by: JFuter on Aug 24, 2011 1:39 PM

Marshelling Web Service Response Memory Leak

I believe I have found a memory leak when using the configuration below.
The memory leak occurs when calling a web service. When the web service function is marshelling the response of the function call, an "500 Internal Server Error ... java.lang.OutOfMemoryError" is returned from OC4J. This error may be seen via the TCP Packet Monitor in JDeveloper.
Unfortunately no exception dump is outputted to the OC4J log.
Configuration:
Windows 2000 with 1 gig ram
JDeveloper 9.0.5.2 with JAX/RPC extension installed
OC4J 10.0.3
Sun JVM version 1.4.2_03-b02
To demonstrate the error I created a simple web service and client. See below the client and web service function that demonstrates it.
The web service is made up of a single function called "queryTestOutput".
It returns an object of class "TestOutputQueryResult" which contains an int and an array.
The function call accepts a one int input parameter which is used to vary the size of array in the returned object.
For small int (less than 100). Web service function returns successfully.
For larger int and depending on the size of memory configuration when OC4J is launched,
the OutOfMemoryError is returned.
The package "ws_issue.service" contains the web service.
I used the Generate JAX-RPC proxy to build the client (found in package "ws_issue.client"). Package "types" was
also created by Generate JAX-RPC proxy.
To test the web service call execute the class runClient. Vary the int "atestValue" until error is returned.
I have tried this with all three encodings: RPC/Encoded, RPC/Literal, Document/Literal. They have the
same issue.
The OutOfMemory Error is raised fairly consistently using the java settings -Xms386m -Xmx386m for OC4J when 750 is specified for the input parameter.
I also noticed that when 600 is specified, the client seems to hang. According to the TCP Packet Monitor,
the response is returned. But, the client seems unable to unmarshal the message.
** file runClient.java
// -- this client is using Document/Literal
package ws_issue.client;
public class runClient
public runClient()
* @param args
* Test out the web service
* Play with the atestValue variable to until exception
public static void main(String[] args)
//runClient runClient = new runClient();
long startTime;
int atestValue = 1;
atestValue = 2;
//atestValue = 105; // last one to work with default memory settings in oc4j
//atestValue = 106; // out of memory error as seen in TCP Packet Monitor
// fails with default memory settings in oc4j
//atestValue = 600; // hangs client (TCP Packet Monitor shows response)
// when oc4j memory sessions are -Xms386m -Xmx386m
atestValue = 750; // out of memory error as seen in TCP Packet Monitor
// when oc4j memory sessions are -Xms386m -Xmx386m
try
startTime = System.currentTimeMillis();
Ws_issueInterface ws = (Ws_issueInterface) (new Ws_issue_Impl().getWs_issueInterfacePort());
System.out.println("Time to obtain port: " + (System.currentTimeMillis() - startTime) );
// call the web service function
startTime = System.currentTimeMillis();
types.QueryTestOutputResponse qr = ws.queryTestOutput(new types.QueryTestOutput(atestValue));
System.out.println("Time to call queryTestOutput: " + (System.currentTimeMillis() - startTime) );
startTime = System.currentTimeMillis();
types.TestOutputQueryResult r = qr.getResult();
System.out.println("Time to call getresult: " + (System.currentTimeMillis() - startTime) );
System.out.println("records returned: " + r.getRecordsReturned());
for (int i = 0; i<atestValue; i++)
types.TestOutput t = r.getTestOutputResults();
System.out.println(t.getTestGroup() + ", " + t.getUnitNumber());
catch (Exception e)
e.printStackTrace();
** file wsmain.java
package ws_issue.service;
import java.rmi.RemoteException;
import javax.xml.rpc.ServiceException;
import javax.xml.rpc.server.ServiceLifecycle;
public class wsmain implements ServiceLifecycle, ws_issueInterface
public wsmain()
public void init (Object p0) throws ServiceException
public void destroy ()
System.out.println("inside ws destroy");
* create an element of the array with some hardcoded values
private TestOutput createTestOutput(int cnt)
TestOutput t = new TestOutput();
t.setComments("here are some comments");
t.setConfigRevisionNo("1");
t.setItemNumber("123123123");
t.setItemRevision("arev" + cnt);
t.setTestGroup(cnt);
t.setTestedItemNumber("123123123");
t.setTestedItemRevision("arev" + cnt);
t.setTestResult("testResult");
t.setSoftwareVersion("version");
t.setTestConditions("conditions");
t.setStageName("world's a stage");
t.setTestMode("Test");
t.setTestName("test name");
t.setUnitNumber("UnitNumber"+cnt);
return t;
* Web service function that is called
* Create recCnt number of "records" to be returned
public TestOutputQueryResult queryTestOutput (int recCnt) throws java.rmi.RemoteException
System.out.println("Inside web service function queryTestOutput");
TestOutputQueryResult r = new TestOutputQueryResult();
TestOutput TOArray[] = new TestOutput[recCnt];
for (int i = 0; i< recCnt; i++)
TOArray = createTestOutput(i);
r.setRecordsReturned(recCnt);
r.setTestOutputResults(TOArray);
System.out.println("End of web service function call");
return r;
* @param args
public static void main(String[] args)
wsmain wsmain = new wsmain();
int aval = 5;
try
TestOutputQueryResult r = wsmain.queryTestOutput(aval);
for (int i = 0; i<aval; i++)
TestOutput t = r.getTestOutputResults();
System.out.println(t.getTestGroup() + ", " + t.getUnitNumber());
catch (Exception e)
e.printStackTrace();
** file ws_issueInterface.java
package ws_issue.service;
import java.rmi.Remote;
import java.rmi.RemoteException;
public interface ws_issueInterface extends java.rmi.Remote
public TestOutputQueryResult queryTestOutput (int recCnt) throws java.rmi.RemoteException;
** file TestOutputQueryResult.java
package ws_issue.service;
public class TestOutputQueryResult
private long recordsReturned;
private TestOutput[] testOutputResults;
public TestOutputQueryResult()
public long getRecordsReturned()
return recordsReturned;
public void setRecordsReturned(long recordsReturned)
this.recordsReturned = recordsReturned;
public TestOutput[] getTestOutputResults()
return testOutputResults;
public void setTestOutputResults(TestOutput[] testOutputResults)
this.testOutputResults = testOutputResults;
** file TestOutput.java
package ws_issue.service;
public class TestOutput
private String itemNumber;
private String itemRevision;
private String configRevisionNo;
private String testName;
private String testConditions;
private String stageName;
private String testedItemNumber;
private String testedItemRevision;
private String unitNumber;
private String testStation;
private String testResult;
private String softwareVersion;
private String operatorID;
private String testDate; // to be datetime
private String comments;
private int testGroup;
private String testMode;
public TestOutput()
public String getComments()
return comments;
public void setComments(String comments)
this.comments = comments;
public String getConfigRevisionNo()
return configRevisionNo;
public void setConfigRevisionNo(String configRevisionNo)
this.configRevisionNo = configRevisionNo;
public String getItemNumber()
return itemNumber;
public void setItemNumber(String itemNumber)
this.itemNumber = itemNumber;
public String getItemRevision()
return itemRevision;
public void setItemRevision(String itemRevision)
this.itemRevision = itemRevision;
public String getOperatorID()
return operatorID;
public void setOperatorID(String operatorID)
this.operatorID = operatorID;
public String getSoftwareVersion()
return softwareVersion;
public void setSoftwareVersion(String softwareVersion)
this.softwareVersion = softwareVersion;
public String getStageName()
return stageName;
public void setStageName(String stageName)
this.stageName = stageName;
public String getTestConditions()
return testConditions;
public void setTestConditions(String testConditions)
this.testConditions = testConditions;
public String getTestDate()
return testDate;
public void setTestDate(String testDate)
this.testDate = testDate;
public String getTestName()
return testName;
public void setTestName(String testName)
this.testName = testName;
public String getTestResult()
return testResult;
public void setTestResult(String testResult)
this.testResult = testResult;
public String getTestStation()
return testStation;
public void setTestStation(String testStation)
this.testStation = testStation;
public String getTestedItemNumber()
return testedItemNumber;
public void setTestedItemNumber(String testedItemNumber)
this.testedItemNumber = testedItemNumber;
public String getTestedItemRevision()
return testedItemRevision;
public void setTestedItemRevision(String testedItemRevision)
this.testedItemRevision = testedItemRevision;
public String getUnitNumber()
return unitNumber;
public void setUnitNumber(String unitNumber)
this.unitNumber = unitNumber;
public int getTestGroup()
return testGroup;
public void setTestGroup(int testGroup)
this.testGroup = testGroup;
public String getTestMode()
return testMode;
public void setTestMode(String testMode)
this.testMode = testMode;

Many thanks for your help. This solved the issue for our .NET code, however the leak is still present in the report designer. I was also wondering if you could help further: because of the limits on the java memory process is there a way to ensure that a separate java process is started for each report that is loaded in my report viewers collection? Essentially the desktop application that i have created uses a tab control to display each type report, so each tab goes through the following code when displaying a report and closing a tab:
Is there a way to ensure that a different Java process is kicked off each time that I display a different report? My current code in c# always uses the same Java process so the memory ramps up. The code to load the report and then dispose of the report through closing the tab (and now the Java process) looks like this:
    private void LoadCrystalReport(string FullReportName)
      ReportDocument reportDoc = new ReportDocument();
      reportDoc.Load(FullReportName, OpenReportMethod.OpenReportByTempCopy);
      this.crystalReportViewer1.ReportSource = reportDoc;
    private void DisposeCrystalReportObject()
      if (crystalReportViewer1.ReportSource != null)
        ReportDocument report = (ReportDocument)crystalReportViewer1.ReportSource;
        foreach (Table table in report.Database.Tables)
          table.Dispose();
        report.Database.Dispose();
        report.Close();
        report.Dispose();
        GC.Collect();
Thanks

Huge memory leak in java jvm after update 2 for Snow leopard

Since I updated to Java Update 2 for Snow Leopard my JVM suddenly grows massive (10GB+ real memory - -Xmx=3500m) consuming all memory and rendering my iMac unusable. This does not happen predictably but does happen several times a day now requiring I power off and on again.
I had been living happily with update 1 with no such problem.
I need to either go back to update 1 (should have it on Time Machine) or find a solution for this problem.

Our application is a j2ee-based commercial application facing to specified customers, having about 120 access request an hour.
We ' re doing stress test on the test server. The strange memory leak occurs at 1:20 am this morning while we're out of company , and no job was scheduled to run at that time. So I have the tendency to image that there is something inside oc4j had occured.
I have used OptimizeIt to monitor the heap status. However , as the memory leak problem occurs very occasionally ,and that tool deadly slows our server, we are currently using no profiling tools.

Potential Memory Leak during Marshelling of a Web Service Response

I believe I have found a memory leak when using the configuration below.
The memory leak occurs when calling a web service. When the web service function is marshelling the response of the function call, an "500 Internal Server Error ... java.lang.OutOfMemoryError" is returned from OC4J. This error may be seen via the TCP Packet Monitor in JDeveloper.
Unfortunately no exception dump is outputted to the OC4J log.
Configuration:
Windows 2000 with 1 gig ram
JDeveloper 9.0.5.2 with JAX/RPC extension installed
OC4J 10.0.3
Sun JVM version 1.4.2_03-b02
To demonstrate the error I created a simple web service and client. See below the client and web service function that demonstrates it.
The web service is made up of a single function called "queryTestOutput".
It returns an object of class "TestOutputQueryResult" which contains an int and an array.
The function call accepts a one int input parameter which is used to vary the size of array in the returned object.
For small int (less than 100). Web service function returns successfully.
For larger int and depending on the size of memory configuration when OC4J is launched,
the OutOfMemoryError is returned.
The package "ws_issue.service" contains the web service.
I used the Generate JAX-RPC proxy to build the client (found in package "ws_issue.client"). Package "types" was
also created by Generate JAX-RPC proxy.
To test the web service call execute the class runClient. Vary the int "atestValue" until error is returned.
I have tried this with all three encodings: RPC/Encoded, RPC/Literal, Document/Literal. They have the
same issue.
The OutOfMemory Error is raised fairly consistently using the java settings -Xms386m -Xmx386m for OC4J when 750 is specified for the input parameter.
I also noticed that when 600 is specified, the client seems to hang. According to the TCP Packet Monitor,
the response is returned. But, the client seems unable to unmarshal the message.
** file runClient.java
// -- this client is using Document/Literal
package ws_issue.client;
public class runClient
public runClient()
* @param args
* Test out the web service
* Play with the atestValue variable to until exception
public static void main(String[] args)
//runClient runClient = new runClient();
long startTime;
int atestValue = 1;
atestValue = 2;
//atestValue = 105; // last one to work with default memory settings in oc4j
//atestValue = 106; // out of memory error as seen in TCP Packet Monitor
// fails with default memory settings in oc4j
//atestValue = 600; // hangs client (TCP Packet Monitor shows response)
// when oc4j memory sessions are -Xms386m -Xmx386m
atestValue = 750; // out of memory error as seen in TCP Packet Monitor
// when oc4j memory sessions are -Xms386m -Xmx386m
try
startTime = System.currentTimeMillis();
Ws_issueInterface ws = (Ws_issueInterface) (new Ws_issue_Impl().getWs_issueInterfacePort());
System.out.println("Time to obtain port: " + (System.currentTimeMillis() - startTime) );
// call the web service function
startTime = System.currentTimeMillis();
types.QueryTestOutputResponse qr = ws.queryTestOutput(new types.QueryTestOutput(atestValue));
System.out.println("Time to call queryTestOutput: " + (System.currentTimeMillis() - startTime) );
startTime = System.currentTimeMillis();
types.TestOutputQueryResult r = qr.getResult();
System.out.println("Time to call getresult: " + (System.currentTimeMillis() - startTime) );
System.out.println("records returned: " + r.getRecordsReturned());
for (int i = 0; i<atestValue; i++)
types.TestOutput t = r.getTestOutputResults();
System.out.println(t.getTestGroup() + ", " + t.getUnitNumber());
catch (Exception e)
e.printStackTrace();
** file wsmain.java
package ws_issue.service;
import java.rmi.RemoteException;
import javax.xml.rpc.ServiceException;
import javax.xml.rpc.server.ServiceLifecycle;
public class wsmain implements ServiceLifecycle, ws_issueInterface
public wsmain()
public void init (Object p0) throws ServiceException
public void destroy ()
System.out.println("inside ws destroy");
* create an element of the array with some hardcoded values
private TestOutput createTestOutput(int cnt)
TestOutput t = new TestOutput();
t.setComments("here are some comments");
t.setConfigRevisionNo("1");
t.setItemNumber("123123123");
t.setItemRevision("arev" + cnt);
t.setTestGroup(cnt);
t.setTestedItemNumber("123123123");
t.setTestedItemRevision("arev" + cnt);
t.setTestResult("testResult");
t.setSoftwareVersion("version");
t.setTestConditions("conditions");
t.setStageName("world's a stage");
t.setTestMode("Test");
t.setTestName("test name");
t.setUnitNumber("UnitNumber"+cnt);
return t;
* Web service function that is called
* Create recCnt number of "records" to be returned
public TestOutputQueryResult queryTestOutput (int recCnt) throws java.rmi.RemoteException
System.out.println("Inside web service function queryTestOutput");
TestOutputQueryResult r = new TestOutputQueryResult();
TestOutput TOArray[] = new TestOutput[recCnt];
for (int i = 0; i< recCnt; i++)
TOArray[i] = createTestOutput(i);
r.setRecordsReturned(recCnt);
r.setTestOutputResults(TOArray);
System.out.println("End of web service function call");
return r;
* @param args
public static void main(String[] args)
wsmain wsmain = new wsmain();
int aval = 5;
try
TestOutputQueryResult r = wsmain.queryTestOutput(aval);
for (int i = 0; i<aval; i++)
TestOutput t = r.getTestOutputResults()[i];
System.out.println(t.getTestGroup() + ", " + t.getUnitNumber());
catch (Exception e)
e.printStackTrace();
** file ws_issueInterface.java
package ws_issue.service;
import java.rmi.Remote;
import java.rmi.RemoteException;
public interface ws_issueInterface extends java.rmi.Remote
public TestOutputQueryResult queryTestOutput (int recCnt) throws java.rmi.RemoteException;
** file TestOutputQueryResult.java
package ws_issue.service;
public class TestOutputQueryResult
private long recordsReturned;
private TestOutput[] testOutputResults;
public TestOutputQueryResult()
public long getRecordsReturned()
return recordsReturned;
public void setRecordsReturned(long recordsReturned)
this.recordsReturned = recordsReturned;
public TestOutput[] getTestOutputResults()
return testOutputResults;
public void setTestOutputResults(TestOutput[] testOutputResults)
this.testOutputResults = testOutputResults;
** file TestOutput.java
package ws_issue.service;
public class TestOutput
private String itemNumber;
private String itemRevision;
private String configRevisionNo;
private String testName;
private String testConditions;
private String stageName;
private String testedItemNumber;
private String testedItemRevision;
private String unitNumber;
private String testStation;
private String testResult;
private String softwareVersion;
private String operatorID;
private String testDate; // to be datetime
private String comments;
private int testGroup;
private String testMode;
public TestOutput()
public String getComments()
return comments;
public void setComments(String comments)
this.comments = comments;
public String getConfigRevisionNo()
return configRevisionNo;
public void setConfigRevisionNo(String configRevisionNo)
this.configRevisionNo = configRevisionNo;
public String getItemNumber()
return itemNumber;
public void setItemNumber(String itemNumber)
this.itemNumber = itemNumber;
public String getItemRevision()
return itemRevision;
public void setItemRevision(String itemRevision)
this.itemRevision = itemRevision;
public String getOperatorID()
return operatorID;
public void setOperatorID(String operatorID)
this.operatorID = operatorID;
public String getSoftwareVersion()
return softwareVersion;
public void setSoftwareVersion(String softwareVersion)
this.softwareVersion = softwareVersion;
public String getStageName()
return stageName;
public void setStageName(String stageName)
this.stageName = stageName;
public String getTestConditions()
return testConditions;
public void setTestConditions(String testConditions)
this.testConditions = testConditions;
public String getTestDate()
return testDate;
public void setTestDate(String testDate)
this.testDate = testDate;
public String getTestName()
return testName;
public void setTestName(String testName)
this.testName = testName;
public String getTestResult()
return testResult;
public void setTestResult(String testResult)
this.testResult = testResult;
public String getTestStation()
return testStation;
public void setTestStation(String testStation)
this.testStation = testStation;
public String getTestedItemNumber()
return testedItemNumber;
public void setTestedItemNumber(String testedItemNumber)
this.testedItemNumber = testedItemNumber;
public String getTestedItemRevision()
return testedItemRevision;
public void setTestedItemRevision(String testedItemRevision)
this.testedItemRevision = testedItemRevision;
public String getUnitNumber()
return unitNumber;
public void setUnitNumber(String unitNumber)
this.unitNumber = unitNumber;
public int getTestGroup()
return testGroup;
public void setTestGroup(int testGroup)
this.testGroup = testGroup;
public String getTestMode()
return testMode;
public void setTestMode(String testMode)
this.testMode = testMode;

I use web services a lot and I sympathize with your issue. I
struggle with similar issues and I found this great utility that
will help you confirm if your webservice is returning the data
correctly to Flex. I know you said it works in other applications
but who knows if flex is calling it correctly etc. This utility is
been the most amazing tool in helping me resolve web service
issues.
http://www.charlesproxy.com/
Once you can confirm the data being returned is good you can
try several things in flex. Try changing your result format to
object or e4x etc. See how that plays out. Not sure where your
tapping in to look at your debugger, you might want to catch it
right at the result handler before converting to any collections. .
If nothing here helps maybe post some code to look at. .
.

Whether our application caused the memory leak

whether have the command to find out whether our application caused the memory leak !
We are using Jdev10g + JHeadstart(Release 9.0.5.1, BC4J + Struts + JSP) to build our enterprise application,
but when the application running some days in our Application Server(RedHat AMD64, with 8GB RAM), the memory consumed was growth seriously in production environment (one OC4J instance will caused almost 2G memory ulilization after running 2 days) that is caused us to restart the instance each day ! we doubt and worry
about maybe our application suffer the memory leak problem, so we want to know have the command to find out whether our application caused the memory leak
issue and which program is the major murderer for memory.

Ting,
Unfortunately there is no 'command' that will show you the location of a memory leak. First I would scrutinizing your code for any obvious 'leaks'. Then, you should obtain some statistics about the usage of your system. One important aspect is how long a HttpSession usually lives. If you have thousands of users that stay online the entire day and never 'time out', and if you have users on the system 24 hours a day, then the sheer number of HttpSessions might be a problem.
JHeadstart 9.0.x tends to have rather 'heavy' session objects. This can easily be solved by adding some actions to clear up DataObjects and DataObjectSets of previous 'Groups' when entering a new Group. A good place would be between the 'DynamicActionRouter' and the 'ActionRouters'. Just before entering the 'EmployeeActionRouter', you could remove all DataObjects and DataObjectSets that might be left on the Session by actions of the other ActionRouters.
Also it would be interesting to see if the garbage collector can do its thing when the system is less busy. For instance, if your application has a smaller load during the weekend, what is the memory usage on Sunday at midnight compared to, say, Friday at noon. Has the memory load dropped consistently with the decreased number of online users, or does too much memory stay allocated? If so, then there's more going on than just HttpSession objects.
If all this does not lead to a solution, I suggest using a profiling tool such as OptimizeIt to investigate the memory usage of the application in detail.
Kind regards,
Peter Ebell
JHeadstart Team

ADF 10.1.3.4 Memory Leak

I can re-produce a ADF memory leak in jdeveloper. The problems seems to be when I am running the application locally in the memory profiler, the memory usage keeps growing until the application halts with a outofmemoryexception. The main problem seems to be object references to the jspx page object (_index_jspx._jspService : line 989) under the char[] object when the application get loaded with 20 concurrent users for about 10 mins. I have tried adjusting both heap and max perm gen sizes higher and re-tested but it still seems to get hit with the outofmemoryexception after 10 mins longer duration.
This is 1 very simple ADF page which accesses a read-only ADF BC view object with no other customizations. ADF is NOT scaling well in our load and performance tests.
Here are details about my environment:
Windows XP service pack 2
Intel Core 2 Duo process @3.16Ghz
4 GB of ram
Jdeveloper 10.1.3.4.4270
Jheadstart 10.1.3
Oracle 11g database
I can provide a dump of the memory profiler statistics at the point of failure if it is necessary.
This is a critical issue for our team so please advise me on how to solve this asap. Thanks.

The first thing to check is whether you can reproduce this behavior when you are running your application on a stand alone OC4J and not on the embedded OC4J in JDeveloper.
If you can reproduce this problem then please contact support and open an SR with the test case.
We have many customers using ADF 10.1.3 with more than 20 concurrent users.

Media Encoder is a memory leak - windows

Applies to: Version 5.5.1.12 - 64 bit, Windows (Most likely earlier versions too)
Reproducing the problem:
Start Media Encoder as a standalone application by double clicking the icon.
Close the window (by clicking the 'x' in the top-right corner) of Media Encoder.
It does just that: closes the window. It does not close the process.
The process now has no window-handle, thus the user can not access it.
When user starts the application again, another process is created.
Thus the previous process becomes a memory leak.
Workaround:
Open Windows Task Manager by pressing Ctrl-Alt-Del keys simultaniously then selecting Task Manager
Click the 'Processes' tab
Highlight 'Adobe Media Encoder.exe'
Click 'End Process'
Ignore the warning and kill the process

Bill, Sometimes it takes AME and related components up to 30 seconds to close various processes. If you close the app and immediately start a new instance, the old process sees that AME is still running and may not shut down it's process until you shut down your computer. So give it a little time after shutdown to see if that helps. That said, there are situations that I have seen myself that AME would not close all processes in background. In many of those cases, it had to do with dynamic link and what type of files or assets you opend up and what application launches AME. Sometimes when AME is launched by other applications like Premiere Pro, it leaves a process alive in case PPro is using it. but if you close all Adobe apps, it should close your process as well. Over the past few cycles, we have worked on improving processes. Let me know if the above info doesn't help.

Unable to connect to standalone oc4j 10.1.3 DP4 with JDeveloper 10.1.3

Hi all,
I'm having problems to establish a connection to standalone oc4j 10.1.3 DP4 in JDeveloper 10.1.3 studio release.
I'm using the default settings for my OC4J installation and I tested it with http://localhost:8888.
I also set the host in the configuration panel to localhost and left the url-path empty as default.
The username/password combination I filled in is correct.
I'm getting the following error when I ty to test te connection in Jdeveloper:
Error while getting remote MBeanServer for url: ormi://localhost:23791/default:
Error reading application-client descriptor: Error communicating with server: <no message>oracle.oc4j.security.KeyExchange.createKeyAgreement(KeyExchange.java:210)
oracle.oc4j.security.KeyExchange.getKeyAgreement(KeyExchange.java:195)
oracle.oc4j.security.KeyExchange.getSecretKey(KeyExchange.java:132)
oracle.oc4j.security.ExchangingEncryptor.getEncryptedValue(ExchangingEncryptor.java:150)
com.evermind.server.rmi.RMIProtocol$SecureCredentials.send(RMIProtocol.java:246)
com.evermind.server.rmi.RMIProtocol.sendCredentials(RMIProtocol.java:95)
oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:91)
oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:600)
com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:130)
com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:249)
com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:50)
oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:86)
oracle.oc4j.deployment.ApplicationClientResourceFinder.getFinder(ApplicationClientResourceFinder.java:108)
oracle.oc4j.deployment.ApplicationClientResourceFinder.getLocation(ApplicationClientResourceFinder.java:60)
oracle.oc4j.deployment.ApplicationClientResourceFinder.getEjbBinding(ApplicationClientResourceFinder.java:38)
com.oracle.naming.J2EEContext.addEJBReferenceEntries(J2EEContext.java:498)
com.oracle.naming.J2EEContext.create(J2EEContext.java:84)
oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:82)
oracle.j2ee.naming.ApplicationClientInitialContextFactory.getInitialContext(ApplicationClientInitialContextFactory.java:75)
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
javax.naming.InitialContext.init(InitialContext.java:223)
javax.naming.InitialContext.<init>(InitialContext.java:197)
oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:460)
oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.<init>(CoreRemoteMBeanServer.java:155)
oracle.oc4j.admin.management.mejb.MEjb.<init>(MEjb.java:116)
oracle.oc4j.admin.management.mejb.MEjb.getMBeanServer(MEjb.java:157)
oracle.oc4j.admin.management.mejb.MEjbFactory.getManagement(MEjbFactory.java:54)
oracle.oc4j.admin.deploy.spi.ConnectedDeploymentManagerBase.<init>(ConnectedDeploymentManagerBase.java:215)
oracle.oc4j.admin.deploy.spi.Oc4jDeploymentManager.<init>(Oc4jDeploymentManager.java:68)
oracle.oc4j.admin.deploy.spi.factories.Oc4jDeploymentFactory.getDeploymentManager(Oc4jDeploymentFactory.java:130)
oracle.jdevimpl.cm.dt.J2EEConnectionWrapper._getDeploymentManager(J2EEConnectionWrapper.java:182)
oracle.jdevimpl.cm.dt.J2EEConnectionWrapper.testPresentation(J2EEConnectionWrapper.java:111)
oracle.jdeveloper.cm.dt.wizard.TestConnectionPanelUI.testConnectionImpl(TestConnectionPanelUI.java:202)
oracle.jdeveloper.cm.dt.wizard.TestConnectionPanelUI$1.doWork(TestConnectionPanelUI.java:158)
oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:159)
oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
java.lang.Thread.run(Thread.java:595)
caused by: Incompatible parameters; nested exception is:
javax.naming.CommunicationException: <no message>oracle.oc4j.security.KeyExchange.createKeyAgreement(KeyExchange.java:210)
oracle.oc4j.security.KeyExchange.getKeyAgreement(KeyExchange.java:195)
oracle.oc4j.security.KeyExchange.getSecretKey(KeyExchange.java:132)
oracle.oc4j.security.ExchangingEncryptor.getEncryptedValue(ExchangingEncryptor.java:150)
com.evermind.server.rmi.RMIProtocol$SecureCredentials.send(RMIProtocol.java:246)
com.evermind.server.rmi.RMIProtocol.sendCredentials(RMIProtocol.java:95)
oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:91)
oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:600)
com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:130)
com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:249)
com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:50)
oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:86)
oracle.oc4j.deployment.ApplicationClientResourceFinder.getFinder(ApplicationClientResourceFinder.java:108)
oracle.oc4j.deployment.ApplicationClientResourceFinder.getLocation(ApplicationClientResourceFinder.java:60)
oracle.oc4j.deployment.ApplicationClientResourceFinder.getEjbBinding(ApplicationClientResourceFinder.java:38)
com.oracle.naming.J2EEContext.addEJBReferenceEntries(J2EEContext.java:498)
com.oracle.naming.J2EEContext.create(J2EEContext.java:84)
oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:82)
oracle.j2ee.naming.ApplicationClientInitialContextFactory.getInitialContext(ApplicationClientInitialContextFactory.java:75)
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
javax.naming.InitialContext.init(InitialContext.java:223)
javax.naming.InitialContext.<init>(InitialContext.java:197)
oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:460)
oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.<init>(CoreRemoteMBeanServer.java:155)
oracle.oc4j.admin.management.mejb.MEjb.<init>(MEjb.java:116)
oracle.oc4j.admin.management.mejb.MEjb.getMBeanServer(MEjb.java:157)
oracle.oc4j.admin.management.mejb.MEjbFactory.getManagement(MEjbFactory.java:54)
oracle.oc4j.admin.deploy.spi.ConnectedDeploymentManagerBase.<init>(ConnectedDeploymentManagerBase.java:215)
oracle.oc4j.admin.deploy.spi.Oc4jDeploymentManager.<init>(Oc4jDeploymentManager.java:68)
oracle.oc4j.admin.deploy.spi.factories.Oc4jDeploymentFactory.getDeploymentManager(Oc4jDeploymentFactory.java:130)
oracle.jdevimpl.cm.dt.J2EEConnectionWrapper._getDeploymentManager(J2EEConnectionWrapper.java:182)
oracle.jdevimpl.cm.dt.J2EEConnectionWrapper.testPresentation(J2EEConnectionWrapper.java:111)
oracle.jdeveloper.cm.dt.wizard.TestConnectionPanelUI.testConnectionImpl(TestConnectionPanelUI.java:202)
oracle.jdeveloper.cm.dt.wizard.TestConnectionPanelUI$1.doWork(TestConnectionPanelUI.java:158)
oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:159)
oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
java.lang.Thread.run(Thread.java:595)
caused by: Incompatible parameters [Root exception is oracle.oc4j.security.KeyExchange$KeyExchangeException]
Can anyone help me with this problem??
Thanks in advance.
-Tom

Ok, I have installed the production release. But when I login to the application console I'm getting the following error:
This OC4J is configured to make JMX connections via RMIS and fall back to RMI if the RMIS port is not configured. The RMIS connection on the OC4J instance null on Application Server null is configured but a connection could not be established. The JMX protocol is specified by the oracle.oc4j.jmx.internal.connection.protocol property in opmn.xml
Probably I have to configure more things here. Do you now what, before I delve into the manuals myself..;)

Standalone OC4J 9.0.4 - Loading Native Libraries - Unsatisfied Link Error

Hello,
I incidentally happen to have a similar problem as has been described in several posts in this forum. The problem is that of loading Native libraries in OC4J.
The scenario is
1) Environment is Standalone OC4J 9.0.4, Windows 2000, JDK 1.4.2
2) A Java wrapper loads DLL1 which internally loads DLL2.
(To be more specific the DLL1 is a SAPSSOEXT.DLL and the DLL2 is SAPSECU.DLL. These are used for establishing SSO with SAP portal)
The phase-1 of Java wrapper loading DLL1 is achieved by setting either the PATH or the java.library.path variables.
The phase-2 of DLL1 loading DLL2 is what is failing with an Unsatisfied Link Error.
Since I am using a standalone version and not a OC4J app-server, the OPMN related configuration for specified PATH variables will not be relevant here. Is there any other place where I can configure these.
regards
Shivaram

A small correction to my observation above.
The call to load DLL1 via System.loadLibrary() is successful. However when I attempt to call any method on it it fails with UnsatisfiedLinkError.
Contrary to what was written above the error occured even before DLL1 attempted to load DLL2.
So why is it that the call to loadLibrary is successful but the call to actual function is failing? (This works flawlessly on the command line)
Is this a path problem, if so how do I configure it in OC4J standalone. Variables PATH, java.library.path, LD_LIBRARY_PATH none of them seem to have any effect on this.
I tried debugging using a windows file monitor. The library DLL1 is being read from the correct path and is being opened successfully.
Any suggestions will be greatly appreciated.

OPMN vs Standalone OC4j (memory leak)

Similar Messages

Maybe you are looking for