This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
PermGen Space OutOfMemory Error is seen in NetBeans log file. I havent been able to consistently reproduce this issue, but I have run into this issue several times with several different builds. Keith Babo and Suresh Potiny are aware of the issue and could be contacted for additional information.
can't really work on this without more detail. assigning to venkat to resolve with bug filer since both are in monrovia.
We dont have too much information to provide other than that we see this error periodically. Keith suggested I use JDK1.6 so we could get some diagnostic information - but I havent been able to successfully build and deploy my projects when using JDK1.6. Discussion is ongoing.
I ran into the PermGen Space OutOfMemoryError in NetBeans while building my Comp App project. log file is attached.
Created attachment 34337 [details] the log file from \Alaska\userdir\var\log
Ran into the issue again while validating a BPEL File. Log file is attached (messages.log_09212006_1430_validating_BPEL)
Created attachment 34347 [details] error log
Using JDK's JVM Heap Dump option, I was able to get two memory dumps - Please note that I did *not* get these when the Permgen Space OutOfMemory Error was thrown. In fact I am not aware when these were created. I have attached the dumps for analysis (the attachments are big - ~ 15 Mb)
Hemant, Can you attach the project that caused this problem? Thanks, -- Tientien Li
OK, found a possible cause of this problem. The bpel project build ant task uses a special class loader which is not released after the build. So after repeating about 20 clean/build of the synch sample bpel project. I was able to reproduce the PermGen out of memory error: *********** Exception occurred ************ at 8:13 AM on Sep 26, 2006 java.lang.OutOfMemoryError: PermGen space *********** Exception occurred ************ at 8:14 AM on Sep 26, 2006 java.lang.OutOfMemoryError: PermGen space *********** Exception occurred ************ at 8:14 AM on Sep 26, 2006 java.lang.OutOfMemoryError: PermGen space class loader which is not released after build. Reassigned this ticket to Sreeni..
Created attachment 34523 [details] each step is a new clean/build of the synch sample bpel project
Ran into this issue twice today - I am attaching the message log file and the associated Memory Dump
Created attachment 34684 [details] log file from 09/28/2006 at 1130
Created attachment 34685 [details] from 09/28/2006 at 1340
I cannot upload the memory dumps to IssueZilla because files are too big. I have kept the memory dumps here - ftp://ftp.seebeyond.com/pub/hemant/HPROF/ If the files get deleted as part of periodical cleanup, please contact me (hemant.bedekar@sun.com) and I will upload the files again.
Okay, here's a recipe for reproducing the problem, using only a simple Web Project (nothing from BPEL) in NetBeans 5.0 with jdk 1.5.0_06: 1. Create a new web project 2. Windows...Runtime...Servers...Bundled Tomcat...Properties...Platform...VM Options: -Dcom.sun.management.jmxremote 3. Start the internal tomcat server 4. $JAVA_HOME/bin/jconsole.exe 5. In JConsole, connect to the catalina VM (org.apache.cataline.startup.Bootstrap start) 6. In the Memory tab, select "Memory Pool 'Perm Gen'" from the "Chart" combo box 7. Deploy the webapp in NB 8. Go to Step 7 Each time you deploy, your PermGen space usage will monotonically increase. The effect is more pronounced if you add libraries to your webapp (like JSF)
Rich, is that really a bug in NetBeans? It looks like Tomcat is where the bug is, right? It's the one that is running out of Perm Gen space - or am I not understanding something correctly here? FYI, from the Tomcat bug database: http://issues.apache.org/bugzilla/show_bug.cgi?id=33711
profiled the memory leak that’s happening during bpel project build. This is what I observed. If the following Netbeans APIs calls are made from the ant tasks. 1) Calling Lookup method on the Lookup obtained from Lookups.metaInfServices(); from Ant task 2) Create WeakReference/ WeakListner during build in the code Both the APIs seems to add reference to ActiveQueue which helds reference to the Build classloader and never releases after the build. To fix this problem - Replaced Lookups.metaInfServices() with javax.imageio.spi.ServiceRegistry in bpel project code and Removed the WeakReference creation in org.netbeans.modules.xml.xam.dom. AbstractDocumentModel (XAM) I have checked in the bpel project code in release55_dev branch and have requested Chris Webster to make the AbstractDocumentModel .
Created attachment 34743 [details] weak reference creating ActiveQueue
Created attachment 34744 [details] MetaInfServices.Lookup() creating activequeue
Perhaps my general webapp issue is a completely different thing? Shall I file a separate issue? Gregg- My problem is certainly not the referenced tomcat bug, as a simple webapp created from NB templates doesn't match any of the 3 necessary criteria. It may be a different tomcat bug altogether, but I suspect there's an equal chance that the tomcatint module is responsible for signaling to tomcat in some way that the webapp is being overwritten, and the old context can be undeployed and its classloader released.
Hi, Rich. I would agree with your assessment that whatever the cause of what you are seeing, it is not that known Tomcat bug that I listed in my comment. I'm still not completely convinced, though, that what you are seeing is a bug in NetBeans. I recreated part of your experiment and started up Tomcat and attached to it with JConsole. Using Tomcat's Manager user interface (instead of NetBeans) I repeatedly redployed (the button is labeled "Reload" in the Tomcat Manager UI) a simple web application and I saw perm gen increase in size (by about 8K) each time. In either case, I think what we're seeing is different than what was described in this IZ, so in answer to your question, I would vote "yes," please open a new IZ.
Gregg- I posted Issue 86407.
This issue is with respective to Memory leak happening in bpel project build perspective as mentioned by Tientien Li(tli). 1) Create Sample Synchronous Bpel project ( or any Bpel project) 2) Build and Clean ( repeat more than 20 times) It was failing after 35 runs for me.
Modifying the Bpel project build to use classes loaded by Netbeans classloader rather than creating a new classloader for every build with fixed Jars in the classpath seems to solve this problem. I am still testing the fix.
The fix is checked into release55_dev. The fix is to use classes loaded from netbeans instead of creating anttasks fresh for each new build. Code changes: project/antsrc/org/netbeans/modules/bpel/project/antlib.xml project/antsrc/org/netbeans/modules/bpel/project/anttasks/IDEBPELCatalogModel.java project/antsrc/org/netbeans/modules/bpel/project/anttasks/IDEGenerateJBIDescriptor.java project/antsrc/org/netbeans/modules/bpel/project/anttasks/IDEJBIGenerator.java project/antsrc/org/netbeans/modules/bpel/project/anttasks/IDEValidateBPELProject.java project/build.xml project/antsrc/org/netbeans/modules/bpel/project/anttasks/BPELCatalogModel.java project/antsrc/org/netbeans/modules/bpel/project/anttasks/GenerateJBIDescriptor.java project/antsrc/org/netbeans/modules/bpel/project/anttasks/JBIGenerator.java project/antsrc/org/netbeans/modules/bpel/project/anttasks/ValidateBPELProject.java project/nbproject/project.properties project/nbproject/private/private.xml project/src/org/netbeans/modules/bpel/project/resources/build-impl.xsl project/src/org/netbeans/modules/bpel/project/resources/build.xsl project/test/unit/src/org/netbeans/modules/bpel/project/anttasks/TestCreateBPELModel.java project/test/unit/src/org/netbeans/modules/bpel/project/anttasks/testBuilds/testModel.xml project/test/unit/src/org/netbeans/modules/bpel/project/anttasks/testBuilds/testRole.xml project/test/unit/src/org/netbeans/modules/bpel/project/anttasks/testBuilds/testValidation.xml
This change looks fine to me.
I did clean and build on Synchronous sample project 100 times and Outof memory error didnt happen. You can try this on any bpel project. Please use next enterprise pack release build for testing.
This is marked as fixed in 5.5, but the integration seems to have been done to release55_dev, not to release55. Is it really fixed in released EntPack 5.5? A user on nbusers is reporting this problem with Netbeans IDE 5.5 (Build 200610171010).
I could not see any response to the last message. Reopening this bug to make sure we track the situation. hemant_bedekar could you please confirm the bug is fixed?
Mikhail, would you please verify whether bug is still reproducible in Gavotte ?
Could not reproduce the bug with Gavotte milestone build 6 Closing as fixed
Created attachment 43037 [details] Screenshot
NetBeans IDE Dev (Build 200705300000) 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 Windows XP version 5.1 running on x86 en_US (nb); Cp1252 Outof memory error didnt happen after Clean/Build bpel project (more then 10 times) see attacment with memory pool of this action. It looks good