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.

Bug 144194 - Deploy J2EE EAR to GlassFish V2u2 Takes Minutes
Summary: Deploy J2EE EAR to GlassFish V2u2 Takes Minutes
Status: RESOLVED DUPLICATE of bug 150869
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
: 143511 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-08-17 06:13 UTC by willfarnaby
Modified: 2008-10-25 05:13 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description willfarnaby 2008-08-17 06:13:22 UTC
NetBeans 6.5 Beta

I have a J2EE application, containing a Web App with 2 Web Services and an EJB 3.0 module with two session beans and
some JPA entities.

Deployment from NetBeans to GlassFish V2u2, localhost, can take up to 7 minutes to complete. The range seems to be 2 to
8 minutes.

Very detrimental to productive work.
Comment 1 Petr Hejl 2008-08-18 12:14:06 UTC
Can't reproduce the issue. Is it really valid for all platforms? Can you provide the project for testing?
Comment 2 Vince Kraemer 2008-08-19 03:20:25 UTC
There was an issue with ear deployment in 6.1 that was addressed.  if this has regressed, i would love to find out about
it and fix it... again. 
Comment 3 willfarnaby 2008-08-22 07:40:24 UTC
I will keep my eye on this, as I will be redeploying my J2EE App (EAR) quite a bit, and try to provide more succinct info.
Comment 4 Vince Kraemer 2008-08-26 00:39:57 UTC
About how big is the ear file for this app?

I am doing some tests that show the build/deploy time for an app that has a 2,905 KB ear file to be about 10 seconds on
my laptop.

Comment 5 willfarnaby 2008-08-26 01:04:13 UTC
About the same size, ~ 3 MB, with 2 SS EJB 3.0, 2 Web Services (POJOs that call the EJBs), and a handful of (Open)JPA
Entities. Please keep this issue open for the time being. BTW, I've never experienced anything close to a 10 second
deployment.
Comment 6 Vince Kraemer 2008-08-26 03:08:00 UTC
what jdk are you using?

is your project "local" to your machine or is it on some shared drive?

Stuff like the IDE log file and the server log file would be really helpful info for diagnosing this issue.  If you
attach them to this issue, please trim them to cover a start-up and first deploy... if you can.

See http://www.netbeans.org/issues/show_bug.cgi?id=136307.  The seampagination app was over 10MB and I was able to get
it to deploy in about 6 seconds....
Comment 7 Vince Kraemer 2008-08-26 18:02:04 UTC
OK.  I did some more testing... I did not have any WS stuff in the app... so I added some WS (and clients).  My undeploy
and deploy actions were taking about 15 seconds.
Comment 8 willfarnaby 2008-08-26 21:57:02 UTC
Deployment is entirely local (on my dev workstation).

java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
Comment 9 Petr Hejl 2008-08-27 10:44:21 UTC
*** Issue 143511 has been marked as a duplicate of this issue. ***
Comment 10 _ pcw 2008-08-28 01:32:10 UTC
I'm seeing Undeploy/Redeploy times of 2 seconds for an Ear w/ 2 ejb modules, 3 web apps, multiple web services &
multiple entity classes.  Latest 6.5 trunk, GF V2 UR2 running on a Sun Ultra20M2 / Solaris 10, JDK 1.6.0_06.  None of
the modules are very big though.

Reporter:

1. Please update Platform and OS fields of this issue to accurately reflect the system where you see this problem.
2. Can you tell if the time is being consumed by NetBeans or by GlassFish or something else (e.g. excessive disk access,
pegged CPU)?
3. Can you reproduce this problem and take a couple of thread dumps for each process during the long deploy process and
attach those dumps to this issue.
   To get the traces, get the process ID's by starting NetBeans and GlassFish and use jps -m.
   To generate a stack trace, use (from command line) "jstack [pid] > dumpX.txt" where X is 1...N.
   Generate 2-3 traces per process spread out across the delay.  
   You can put them into a single attachment if you clearly delimit the separation of the thread dumps from each other.

Thanks
Comment 11 Vince Kraemer 2008-09-05 01:21:02 UTC
this may be related to this forum thread on the GF side... http://forums.java.net/jive/thread.jspa?messageID=297108

BTW: is directory deployment enabled or disabled?
Comment 12 Exceptions Reporter 2008-09-09 13:59:21 UTC
This issue has already 5 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=89338
Comment 13 Vince Kraemer 2008-10-25 05:13:57 UTC
marking as a dup of another recently filed issue.  it is also incomplete... If you have more info you can add that info
here or in the "dup"

*** This issue has been marked as a duplicate of 150869 ***