Weblogic 8.1 SP4 getting Java.lang.outofMemory exception

Dear experts,
We are running WL8.1 SP4 on our Solaris 5.9 Server.
We want to do MQ implementatin on this server and for the same some kernel parameters were changed.
now our system has below parameters in /etc/system:
set semsys:seminfo_semmsl=1000
set semsys:seminfo_semvmx=32767
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmseg=2048
set shmsys:shminfo_shmmni=2048
set semsys:seminfo_semmni=1024
set semsys:seminfo_semaem=16384
set semsys:seminfo_semmap=1026
set semsys:seminfo_semmns=16384
set semsys:seminfo_semopm=100
set semsys:seminfo_semmnu=16384
set semsys:seminfo_semume=256
set msgsys:msginfo_msgmni=50
set msgsys:msginfo_msgmap=1026
set msgsys:msginfo_msgmax=4096
set msgsys:msginfo_msgmnb=65535
set msgsys:msginfo_msgtql=4096
set msgsys:msginfo_msgssz=16
set msgsys:msginfo_msgseg=8192
set rlim_fd_cur=10000
set rlim_fd_max=10000
and below in /etc/profile:
ulimit -s unlimited
ulimit -d unlimited
but as soon as server was rebooted and we tried to start the weblogic we got java.lang.outofmemory exception.
details as below:
admin_trace:
java.lang.OutOfMemoryError
     at java.util.zip.ZipFile.open(Native Method)
     at java.util.zip.ZipFile.<init>(ZipFile.java:112)
     at java.util.zip.ZipFile.<init>(ZipFile.java:72)
     at weblogic.servlet.internal.WebAppHelper.makeImplicitMapFromJars(WebAppHelper.java:479)
     at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:5436)
     at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:5253)
     at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:545)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:496)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:637)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:619)
     at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3191)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1581)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
     at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2513)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2463)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
--------------- nested within: ------------------
weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.OutOfMemoryError]
     at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
     at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2395)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
managed2_trace:
[java.lang.OutOfMemoryError].
java.lang.OutOfMemoryError
     at java.util.zip.ZipFile.open(Native Method)
     at java.util.zip.ZipFile.<init>(ZipFile.java:112)
     at java.util.zip.ZipFile.<init>(ZipFile.java:72)
     at weblogic.servlet.internal.WebAppHelper.makeImplicitMapFromJars(WebAppHelper.java:479)
     at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:5436)
     at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:5253)
     at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:545)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:496)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:637)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:619)
     at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3191)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1581)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
     at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3029)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
     at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.OutOfMemoryError]
     at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
     at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
     at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3034)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
     at weblogic.Server.main(Server.java:32)
>
need help to identify what exactly went wrong and where.
Thanks

Hi,
As you are using WLS8.1 It means your JDK will be JDK1.4 and there is a Bug already available with JDK1.4 for the Same issue ... Please find the below link:
http://bugs.sun.com/bugdatabase/view_bug.do;:YfiG?bug_id=4705373 (For Sun JDK1.4)
AND
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6373059 (For Sun JDK 1.5.0_05)
Please try to switch to JRockit JDK.
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are Here)

Similar Messages

Why do I get a java.lang.OutOfMemory exception

Thanks, in advance, for you help.
I just wrote a fairly large program. Every time I run it, I get a java.lang.OutOfMemory exception. I have no idea how to debug my code. Why would I get such an exception and how would I debug it?

put more debug statements
and see which line its giving that exception and see whether some where u have any line which is kind of looping or memory allocation .
As i havent seen ur code thats vague idea iam giving
java.lang.OutOfMemory exception is Thrown when the JVM cannot allocate an object because it is out of memory, and no more memory could be made available by the garbage collector.
hope this might help

Java.lang outofmemory exception in IR

Hi
We are on XI 3.0 SP13 and involved in creating a message mapping. We have a big XCBL PO structure as the target - and while we do the mapping effort, every now and then, we get a java.lang outofmemory exception ( display error ) when we save the mapping.
I notice that my CPU util is 100% and is taken up by javaw.exe. I have a 1.6 G RAM desktop - but still face this problem. Any suggestions as to how to overcome this memory problem ? Am I missing any setting in my desktop ?? Or do we have to live with this problem since the target structure is a generic/big structure ??
Thank you in advance for your time.

Hi
actually, this problem has nothing to do with the server at all. Also paging size and your desktop ram do not really matter. By default IB starts with the parameter -Xmx512M, what means that Java gets maximum 512M of RAM. You can change it saving JNLP file to your local file system and changing there this argument to -Xmx 800M or -Xmx 1024M.
The second way is to reduce schema sizes. Usually there are a lot of "annotation" and "documentation" tags. They can be easily removed withoud damaging the mapping(the only problem that in design time you'll not see a documentation for fields). If you want to go this way, you can tell me and I'll find out how it can be done by some tool. Because we had this problem with other customers and as I remember there were some tool made for this purpose.
Although it might help to install the latest SP, because there were made a number of changes to reduce a memory consumption for Message Mapping tool
Best regards
Dmitry

Java.lang.outofmemory exception

Hello,
I have an application, that writes several thousands of records into a file and transfers the same to the server. I am encountering an exception "java.lang.OutOfMemoryError" exception.
I had checked this forum earlier and found a solution that recommended an increase in the memory slot allocated to the JVM. Despite, an increase in this slot from 256MB (eclipse's default) to 1024 MB, my problem still persists. I had updated the eclipse.ini field from "-vmargs -Xms40m -Xmx256m" to "-vmargs -Xms40m -Xmx1024m". Is there anything else that I need to do, to take care of this problem? I am using green threads in the application, does this have anything to do with the above mentioned exception?
Thanks!

I am using
green threads in the application, does this have
anything to do with the above mentioned exception?It wouldn't be hard to find out. Create a new java class where the main method does the same work; writing several thousands of records into a file and transferring it to the server.
Maybe it's all the other variables you have in your application that are cutting into the memory. But can you really reduce them?
Are you loading all thousands of records to memory (I'd imagine in a hashmap or a list) all at once? Like said, do this in smaller chunks, store the records in memory just one at a time and see if that works. It will be slow but it won't run out of memory. Then increase your "batch size" until you find the optimum.

I setup weblogic.servlet.CGIServlet and get java.lang.NoClassDefFoundError?

My WLS is 8.1 SP2. I try to run the CGI/PL program in my server and I install the servlet in the web.xml file. After I run one CGI/PL program I get
" Error 500--Internal Server Error "
And I check with the log file. I get those error message:
<Jan 6, 2005 11:53:52 AM PST> <Error> <HTTP> <BEA-101017> <[ServletContext(id=20
41638322,name=PORTAL,context-path=)] Root cause of ServletException.
java.lang.NoClassDefFoundError
at weblogic.servlet.CGIServlet.init(CGIServlet.java:74)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(Servl
etStubImpl.java:993)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubIm
pl.java:869)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStub
Impl.java:848)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubI
mpl.java:787)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.
java:518)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:362)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
Anyone have idea how does this happen and how to fix it?
Thanks advance
Allen

Hi Allen,
Even I am facing the same problem. Did you received any reply from anyone? or Did you found any solution for the same? I am using WebLogic Server 8.1 SP5
If someone from BEA team helps as this being a reported problem.
Thanks in Advance,
Raghuram

Unable to read big files into string object and java.lang.OutOfMemory Prob

Hi All,
I have an application that uses applet and servlet communication. On the client side I am reading an large xml file of 12MB size (using JFileChooser) and converting the file to an string object using below code. But I am getting java.lang.OutOfMemory on the client side . But the same below code works fine for small xml files which are less than 4MB sizes:
BufferedReader in = new BufferedReader(new InputStreamReader(new FileInputStream(file),"UTF8"), 1024*12);
String s, s2 = new String();
while((s = in.readLine())!= null)
     s2 += s + "\n";
I even tried below code but still java.lang.OutOfMemory is coming:
while (true)
     int i = in.read();
     if (i == -1)
          break;
     sb.append(i);
Please let me know what am I doing wrong here ...
Thanks & Regards,
Sony.

Using a String is bad for the following reason:
When you initially create the String, it has a certain memory size (allocated length if you will). As you keep appending to this String, then memory reallocation will occur over and over, slowing your program down dramatically (ive seen with a 16k x 8 Char file taking 30 secs to read into memory using Strings in this way)
A Better way would be if you knew the number of characters in the XML file (Using some File size method for example) Then you can use a StringBuffer, which will pre allocate enough space (or try to, it may just be that you cannot create a string as large as you need). You can use toString() method to get the resultant in a String Object (the extra allocated space at the end of the Buffer will be removed)
StringBuffer strBuf = new StringBuffer(xxxx);
Where xx is the length (int). Assuming that you are only allowed to enter an int to the constructor then (platform depedant) an int is 2^31 at maximum (or whatever) which allows 2.14e9 characters, therefore an xml file being totally filed would allow a size of ~2048 MB to be read in.
Try it and see.

Unable to read big files into string object & java.lang.OutOfMemory Problem

Hi All,
I have an application that uses applet and servlet communication. On the client side I am reading an large xml file of 12MB size (using JFileChooser) and converting the file to an string object using below code. But I am getting java.lang.OutOfMemory on the client side . But the same below code works fine for small xml files which are less than 4MB sizes:
BufferedReader in = new BufferedReader(new InputStreamReader(new FileInputStream(file),"UTF8"), 1024*12);
String s, s2 = new String();
while((s = in.readLine())!= null)
s2 += s + "\n";
I even tried the below code but still java.lang.OutOfMemory is coming:
while (true)
int i = in.read();
if (i == -1)
break;
sb.append(i);
Please let me know what am I doing wrong here ...

Hi,
I could avoid the java.lang.OutOfMemory error using below code. But using below code I could read small files of sizes less than 4MB
but with large files of 12 MB the below code just simply hangs and I am unable to print the string object namely 's'.
My purpose is to construct an String or StringBuffer object out the user uploaded xml file at the client side and pass that object to server for processing. So how can I construct such object avoid memory problem and increasing the performance of such operations.
BufferedInputStream in = new BufferedInputStream(new FileInputStream(file));
byte[] b = new byte[in.available()];
in.read(b, 0, b.length);
String s = new String(b, 0, b.length);
in.close();
Thanks & Regards,
Sony.

Cannot start OC4J instance - after java.lang.OutOfMemory errors

Hi, I have successfully deployed an application (using Oracle Web Services, J2EE - EJB, TopLink ) to a new OC4J instance that we created. We use the OEM web site to manage the start/stop and deploy operations.
Then we tried to run simultaneously 10 clients....against the server app... ran ok for a while and after approx. 5 to 10 min... java.lang.OutOfMemory errors were being thrown at the client.
After a set of OutOfMemory errors, other clients received errors like the ones show below:
Errors from the top link log
2003.09.24 09:39:59.630--ClientSession(1337286)--Thread[ApplicationServerThread-6,5,main]--EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3.3 (Build 430)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: Bigger type length than Maximum
INTERNAL EXCEPTION: java.sql.SQLException: Bigger type length than Maximum
ERROR CODE: 17412LOCAL EXCEPTION STACK:
EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3.3 (Build 430)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: Bigger type length than Maximum
INTERNAL EXCEPTION: java.sql.SQLException: Bigger type length than Maximum
ERROR CODE: 17412
at oracle.toplink.exceptions.DatabaseException.sqlException(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(Unknown Source)
at oracle.toplink.threetier.ServerSession.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.selectOneRow(Unknown Source)
at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectOneRowFromTable(Unknown Source)
at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectOneRow(Unknown Source)
2003.09.24 09:40:02.365--ClientSession(1337286)--Thread[ApplicationServerThread-6,5,main]--EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3.3 (Build 430)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: Refcursor value is invalid
INTERNAL EXCEPTION: java.sql.SQLException: Refcursor value is invalid
ERROR CODE: 17442LOCAL EXCEPTION STACK:
EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3.3 (Build 430)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: Refcursor value is invalid
INTERNAL EXCEPTION: java.sql.SQLException: Refcursor value is invalid
ERROR CODE: 17442
at oracle.toplink.exceptions.DatabaseException.sqlException(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(Unknown Source)
at oracle.toplink.threetier.ServerSession.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.selectOneRow(Unknown Source)
at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectOneRowFromTable(Unknown Source)
at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectOneRow(Unknown Source)
at oracle.toplink.queryframework.ReadObjectQuery.execute(Unknown Source)
at oracle.toplink.queryframework.DatabaseQuery.execute(Unknown Source)
at oracle.toplink.queryframework.ReadQuery.execute(Unknown Source)
2003.09.24 09:40:03.553--ClientSession(6073931)--Thread[ApplicationServerThread-23,5,main]--EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3.3 (Build 430)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: Protocol violation
INTERNAL EXCEPTION: java.sql.SQLException: Protocol violation
ERROR CODE: 17401LOCAL EXCEPTION STACK:
EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3.3 (Build 430)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: Protocol violation
INTERNAL EXCEPTION: java.sql.SQLException: Protocol violation
ERROR CODE: 17401
at oracle.toplink.exceptions.DatabaseException.sqlException(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(Unknown Source)
at oracle.toplink.threetier.ServerSession.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(Unknown Source)
2003.09.24 09:41:15.173--ServerSession(3066938)--Thread[ApplicationServerThread-19,5,main]--EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3.3 (Build 430)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-01403: no data found
INTERNAL EXCEPTION: java.sql.SQLException: ORA-01403: no data found
ERROR CODE: 1403LOCAL EXCEPTION STACK:
EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3.3 (Build 430)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-01403: no data found
INTERNAL EXCEPTION: java.sql.SQLException: ORA-01403: no data found
ERROR CODE: 1403
at oracle.toplink.exceptions.DatabaseException.sqlException(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(Unknown Source)
at oracle.toplink.threetier.ServerSession.executeCall(Unknown Source)
Im not sure if this is due to a memory leak or something in my app ? Or does Oracle IAS / Toplink have any such issues for which any possible patches are available ?
Could anyone please direct me in the possible right direction !
Thanks,
Krishna

Hi,
We have had this problem too, it only started after we deployed to production and got some load on our application server. We are using JRun as our application server.
We found that Macromedia (JRun) already addressed the issue in general - that if you get java.lang.OutOfMemory errors, then you need to increase the heap size.
Previously we had been using our own caching mechanism and never ran into this problem. Since we decided to go with TopLink (which has caching) we no longer use our own caching mechanism... but now we have this problem.
We have chosen to use FullIdentityMap for caching, but didn't think we would run out of memory in the JVM. Is there a suggested or minimum JVM memory requirement to run TopLink?
Thanks,
Aaron

Java.Lang.NullPoint.Exception in OWB Mapping

Hello Everybody
We are building Data Warehouse using OWB Repository 9.2.0.2.0. When we are validating or deploying the created map we are getting Java.Lang.NullPoint.Exception. This leads to blank screen. We are unable to recover the map. Sometimes, synchronization works to recover the map, but not all the times.
Is there any solution to it?

Mark
Is it possible to solve the problem without migrating? I have the details of error as follows --
java.lang.NullPointerException
java.lang.NullPointerException
     at oracle.wh.service.impl.mapping.metadata.WBMappingGraphImpl.<init>(WBMappingGraphImpl.java:43)
     at oracle.wh.service.impl.mapping.metadata.WBMappingGraphHelper.createMappingGraph(WBMappingGraphHelper.java:31)
     at oracle.wh.ui.mapping.MappingGraphNew.drawStage(MappingGraphNew.java:2660)
     at oracle.wh.ui.mapping.MappingGraphNew.setStage(MappingGraphNew.java:484)
     at oracle.wh.ui.mapping.MappingEditorCanvas.refresh(MappingEditorCanvas.java:287)
     at oracle.wh.ui.common.WhFolderEditor.refreshCanvas(WhFolderEditor.java:951)
     at oracle.wh.ui.common.WhFolderEditor.refresh(WhFolderEditor.java:604)
     at oracle.wh.ui.common.WhFolderEditor$1$MyRefresh.run(WhFolderEditor.java:424)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:154)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:337)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)
I appreciate your feedback.
Cheers, Bana

Java.lang.NullPointer Exception error in webi

Hi All,
When a opening a webi report a user is getting java.lang.NullPointer Exception error in webi for a single report.
Other reports which were build from same universe are working fine. The issue is only with one user and one report.
Environment:
Business Objects XIR3
Java 6 ,update 3
IE version 7
Web Application Server - Apache Tomcat
Thanks in Advance....

Hi,
Check whether the same user is able to open the report in some other machine?
What happens when the user is trying to open other reports? Does he gets the error again?
If the reports is working with other machine, check the java version of the machines.
If the report is working with other users, it not possible that the universe is damaged.
This issue cannot be a rights issue. It has to be something with the report, java, or the universe.
Please check the above details and let me know.
Regards,
Shreyash.

Java.lang.NoClassDefFound Exception ????

hai friends,
plz let me know why we will get java.lang.NoClassDefFound Exception?
thanks in advance

If you are getting it when you run the program from the command line, the most likely reason is you've misspelled the class name or not included its package correctly.
In most other situation it means you've got the classpath wrong.
Google for Java classpath.

Getting java.lang.OutOfMemoryError when updating our application

Hi Experts,
When we update our application which is an heavy EAR file we get the following errors in the logs. But the same applications works well when we deploy it for the first few times why is this happening we have enough space in RAM still we get this error and when we restart our server it again works for sometime.
ServletContext@16428923[app:jccrbxt module:jccrbxt path:/jccrbxt spec-version:null]] Root cause of ServletException.
java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:328)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:285)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at weblogic.servlet.jsp.JspClassLoader.findClass(JspClassLoader.java:48)
at weblogic.servlet.jsp.JspClassLoader.loadClass(JspClassLoader.java:33)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:281)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:243)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:378)
at org.springframework.security.ui.basicauth.BasicProcessingFilter.doFilterHttp(BasicProcessingFilter.java:174)
at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at org.springframework.security.ui.AbstractProcessingFilter.doFilterHttp(AbstractProcessingFilter.java:277)
at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at org.springframework.security.context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionContextIntegrationFilter.java:192)
at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:175)
at org.springframework.security.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:99)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:70)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:527)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)
Thanks

Hi,
Now as you can see that you are getting *"java.lang.OutOfMemoryError: PermGen space"* during the activation on an application it means that you are application needs more space in the non-heap part of the JVM which is PermGen to create the Classes, Class Structures, Methods and Reflection Objects of this applications hence you are getting this issue.
Now how to solve this issue you try the following check list which would help you resolve this issue and overcome same type of issue in future
Point-1). Make Sure that the PermGen Area is not set to a very less value.
Point-2). Usually if an Application has Many JSP Pages in that case every JSP will be converted to a *.class file before JSP Request Process. So a large number of JSPs causes generation of a Large number of *.class files all these classes gets loaded in the PermGen area.
Point-3). While allocating the -XX:MaxPermSize make sure that you follow a rough Formula… which works in most of the Application Servers.
MaxPermSize = (Xmx/3) —- Very Special Cases (One Third of maximum Heap Size)
MaxPermSize = (Xmx/4) —- Recommended (One Fourth Of maximum Heap Size
To get more information on this I would suggest you to have look at the below link which would surely help you in this case
Topic: OutOfMemory Causes and First Aid Steps?
http://middlewaremagic.com/weblogic/?p=4464
Regards,
Ravish Mody

Java.lang.OutOfMemory error while retrieving data from a large table

Hi,
i am trying to fetch data using "executeQuery()" into a ResultSet from the database. But since the data in that table is large. i am recieving "java.lang.OutOfMemory" Error. So, to resolve that, i have used "setMaxRows()" for my statement object. This resolved the error but i don't recieve the entire data. If i call "executeQuery()" again, i recieve the same data. I don't even know a filtering criterion where by i can filter the data for each "executeQuery()"..
How can i resolve this problem
Thanx in advance
--Chaitanya

Either use some criteria you develop related to one of the keys on the table or use some sort of record limiting method.
Note the method of limiting will vary related to the database you are using. You will have to look at the documentation.
For example I am told this will work in MySQL to get 200 records starting at record 100.
SELECT * FROM myTable ORDER BY whatever ASC LIMIT 100,200
Because you are running out of memroy I assume the table is large,
I am not sure what the impact of the above will have on performance because if in the above if the order by is not based on an index at the server level all the records will be selected and sorted before the records are limited.
I would make sure you have an appropriate index.
If you use the advanced search over the user forums using "resultset paging" and possibility the database you are using you should be able to get some ideas.
I hope this makes sense to you.
rykk

Getting java.lang.outofmemoryerror: Java heap space error

I am using coldfusion 8. I frequently get the error 'java.lang.outofmemoryerror: Java heap space'. Can anyone help me?
Error Details :
500
Root cause:
java.lang.outofmemoryerror: Java heap space
javax.servlet.servletException: Root Cause:
java.lang.outofmemoryerror: Java heap space
Thanks in advance,
Regards,
Satheesh.

Well... what does the error message tell you is wrong? You're running out of memory. I presume you understand how computer memory works, if not specifically how Java memory allocation works. So... you have x amount of memory, and you're trying to use >x amount of memory. You can't do that. There are two approaches to dealing with a problem like this:
a) have more memory;
b) use less memory.
What are your JVM memory settings? They're in jvm.config dir, which'll be - by default - in your Jrun4/bin dir for a multi-server install, or somewhere like ColdFusion/runtime/bin or something like that on a stand-alone install.
Next... what are you loading into memory? This is trickier to answer. But every variable you create takes up memory. People often load up the application or session scopes with stuff that's "convenient" to store in shared-scope memory, but really chew through it. Putting CFC instances in the session scope is a really good way to waste memory, as they seem to have quite a large footprint.
It's really impossible to say what's eating the memory based on what info you've given us (basically: none), but you can use things like FusionReactor to examine what's going into memory. Or CF* Enterprise has some of its own memory profiling stuff... I've never used it but it might be of some use.
Have you googled "coldfusion java.lang.outofmemory"?
Adam

Sun identity manager - java.lang.OutOfMemory

Hi, I have one very interesting issue regarding JVM memory. I have one sun idm (version 7) application deployed in sun java web application server. I am facing JVM error - java.lang.OutOfMemory very frequently now days in production server. I am sharing you the details regarding configuration :
Their are 4 app servers - IDMAPP01 IDMAPP02 IDMAPP03 IDMAPP04
current total memory on each of the 4 app server 8 GB
memory allocated to JVM on each server 5 GB
os - solaris
admin task recon are performed only on instance - IDMAPP04
JVM setting is - -Xmx5g -Xms5g -Xmn1500m -XX:MaxPermSize=512m
Log file locations:
/var/opt/SUNWappserver/domain1/logs/vm.log
/var/opt/SUNWappserver/domain1/logs/gc.log
/opt/SUNWappserver/appserver/config/asadminenv.conf
/opt/SUNWappserver/appserver/config/asenv.conf
idm app deployment path:
/var/opt/SUNWappserver/domain1/applications/j2ee-modules/idm
logpath
/var/opt/SUNWappserver/domain1/logs/
Whenever I am getting this issue, we are restarting all the 4 server instances which is impacting business as this is prod server.
Can anyone suggest how can I solve this issue. (please suggest good performance tuning tips without increasing physical memory).
Regards,
Jimmy

886672 wrote:
Hi, I have one very interesting issue regarding JVM memory. I have one sun idm (version 7) application deployed in sun java web application server. I am facing JVM error - java.lang.OutOfMemory very frequently now days in production server. I am sharing you the details regarding configuration :
Their are 4 app servers - IDMAPP01 IDMAPP02 IDMAPP03 IDMAPP04
current total memory on each of the 4 app server 8 GB
memory allocated to JVM on each server 5 GB
what else is running on those servers and how much memory are those applications consuming?
os - solaris
admin task recon are performed only on instance - IDMAPP04
JVM setting is - -Xmx5g -Xms5g -Xmn1500m -XX:MaxPermSize=512mIf IDMAPP04 is doing different things from the other servers, then they should be configured differently. What garbage collector are you using?
>
Log file locations:
/var/opt/SUNWappserver/domain1/logs/vm.log
/var/opt/SUNWappserver/domain1/logs/gc.log
/opt/SUNWappserver/appserver/config/asadminenv.conf
/opt/SUNWappserver/appserver/config/asenv.confYou may want to have a loog at the gc.log file provided you have actually enabled gc logging which you should at least until you have resolved your memory problems.
>
idm app deployment path:
/var/opt/SUNWappserver/domain1/applications/j2ee-modules/idm
logpath
/var/opt/SUNWappserver/domain1/logs/
Whenever I am getting this issue, we are restarting all the 4 server instances which is impacting business as this is prod server.Why? The whole idea behind running recon on a separate server is that you can restart that one without affecting the others.
Can anyone suggest how can I solve this issue. (please suggest good performance tuning tips without increasing physical memory).
Enable gc logging and use a profiler to capture the behaviour of the jvm. You need to understand what it is doing and find where the problem area is before you can recommend what to tune.
Regards,
Jimmy

Weblogic 8.1 SP4 getting Java.lang.outofMemory exception

Similar Messages

Maybe you are looking for