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.
I'm Downloaded the NetBeans 6.5 RC1 and observe the VERY SLOW creation of initial deploying dir Initial deploying WebSite to C:\Projetos\hg\web\WebSite\dist\gfdeploy Take a 30min.... in my project... with 14MB... and 7k files... Please... correct this for the final realease...
Please provide exact ide revision, jdk version, server type and version. Do you use directory deployment?
JDK 1.6 Update 10 GlassFish U2 Yes , i'm using directory deployment
I set the OS to WinXP... please correct the setting if I have guessed wrong. Also: please try the following test and report the results... steps.. 1. undeploy the app. 2. clean the app. 2.5 restart the server 3. use the deploy item to deploy the app. please attach the ant output from that operation. 4. undeploy the app 5. clean the app 6. restart the server 7. switch to archive deployment Properties item on the server nodes right click menu. options tab of the properties dialog uncheck Directory deployment enabled. 8. use the deploy item to deploy the app. please attach the ant output from that operation, too.
i repeat this steps and the process stop in same location: Initial deploying WebSite to C:\Projetos\hg\web\WebSite\dist\gfdeploy On archive deployment... the deployment occurs in 2 seconds...
BTW: how long does it take to directory deploy the app using a fully updated 6.1 build?
In 6.1 this operation takes 29 seconds...
pre-init: init-private: init-userdir: init-user: init-project: do-init: post-init: init-check: init: deps-jar: deps-j2ee-archive: init: deps-jar: compile: library-inclusion-in-manifest: dist-ear: init: deps-module-jar: deps-ear-jar: init: deps-jar: compile: library-inclusion-in-manifest: dist-ear: deps-jar: library-inclusion-in-archive: library-inclusion-in-manifest: compile: compile-jsps: do-ear-dist: dist-ear: pre-pre-compile: pre-compile: do-compile: post-compile: compile: pre-dist: do-dist-without-manifest: do-dist-with-manifest: Building jar: C:\Projetos\hg\web\EscribaWebSite\dist\Escriba Web Site.ear post-dist: dist: run-debug: Checking for missing drivers Start registering the project's server resources Finished registering server resources Initial deploying EscribaWebSite to C:\Projetos\hg\web\EscribaWebSite\dist\gfdeploy Completed initial distribution of EscribaWebSite Start registering the project's server resources Finished registering server resources moduleID=Escriba_Web_Site deployment started : 0% deployment finished : 100% Deploying application in domain completed successfully Trying to create reference for application in target server completed successfully Trying to start application in target server completed successfully Deployment of application Escriba_Web_Site completed successfully Enable of Escriba_Web_Site in target server completed successfully Enable of application in all targets completed successfully All operations completed successfully connect-debugger: Non-existing path "C:\Projetos\hg\web\EscribaWebSite\${javac.classpath}" provided. Non-existing path "C:\Projetos\hg\web\EscribaWebSite\build\jar" provided. Have no FileObject for C:\Projetos\hg\web\EscribaWebSite\build\jar Attached JPDA debugger to localhost:9009 debug-display-browser: Browsing: http://localhost:80//admin run-debug-appclient: debug: BUILD SUCCESSFUL (total time: 12 minutes 39 seconds)
please attach a couple thread dumps, that you take after the deploy "stalls". please trigger two thread dumps approximately 30 seconds apart.
have you... updated to the freshest release of 6u10 (the FCS bits)? made other environmental changes other than the NB bits?
I just used the seam pagination sample project https://techdayscode.dev.java.net/files/documents/7105/83664/seampagination_080125-220555.zip to see if I could reproduce this... and I wasn't successful. The app ends up being a 10mb ear file. using directory deploy the app deploys in about 15 seconds (according to the ant output). The archive based deploy time is about 15 seconds also... please attach the thread dumps when they become available.
it looks like the issue may have something to do with structure of the app that you are deploying. the thread dumps will help identify the bottleneck and once it is identified, we should be able to integrate a code change to address it.
*** Issue 144194 has been marked as a duplicate of this issue. ***
Hi richard_1383hot... if you have more info about why you have become interested in this issue, please let us know. Since the issue is INCOMPLETE and the original filer hasn't updated it and I haven't been able to reproduce it, I am kind of stalled. Additional information from you may provide info that will let me make progress.
Hi snowyvaley... if you have more info about why you have become interested in this issue, please let us know. Since the issue is INCOMPLETE and the original filer hasn't updated it and I haven't been able to reproduce it, I am kind of stalled. Additional information from you may provide info that will let me make progress.
There is no response from reporter for few months, closing as wontfix
This seems to be back. I would open a new bug because it's probably different, but that this is the bug the exception reporter gave me.
This bug already has 250 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=89338
Created attachment 158703 [details] stacktrace nb got stuck deploying. could not stop tomcat from nb.
This bug already has 300 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=89338
Created attachment 164740 [details] stacktrace deploying my project