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 121928 - "Undeploy and Deploy" blocks EQ (doing network I/O?)
Summary: "Undeploy and Deploy" blocks EQ (doing network I/O?)
Status: RESOLVED FIXED
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:
Depends on:
Blocks:
 
Reported: 2007-11-14 17:42 UTC by _ tboudreau
Modified: 2008-01-16 21:24 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump (23.53 KB, text/plain)
2007-11-14 17:43 UTC, _ tboudreau 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ tboudreau 2007-11-14 17:42:15 UTC 
I am trying to deploy an application on netbeansday.org (server in the U.S.) on a very high latency connection from Brazil - but I have also noticed this 
behavior to a lesser degree with local deployment or deployment on a less slow connection.  In this case, the latency is so high that I actually cannot refresh 
the node for this server in the services tab - but the server is running - I just confirmed that by ssh'ing into the server.

After invoking Undeploy and Deploy, the UI was blocked for four minutes.  The AWT thread is in the following method.  I would guess this is waiting for 
some network I/O to complete.


"AWT-EventQueue-1" prio=6 tid=0x00515540 nid=0x198de00 waiting for monitor entry [0xb3698000..0xb3698d10]
        at org.netbeans.modules.j2ee.sun.ide.dm.SunDeploymentManager.getTargets(SunDeploymentManager.java:634)
        - waiting to lock <0x0d31bd98> (a org.netbeans.modules.j2ee.sun.ide.dm.SunDeploymentManager)
        at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.checkIssue2999(DirectoryDeploymentFacade.java:128)
        at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.setDeploymentManager(DirectoryDeploymentFacade.java:120)
        at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.<init>(DirectoryDeploymentFacade.java:92)
        at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.get(DirectoryDeploymentFacade.java:83)
        at org.netbeans.modules.j2ee.sun.ide.j2ee.OptionalFactory.getIncrementalDeployment(OptionalFactory.java:88)
        at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.getIncrementalDeployment(ServerInstance.java:537)
        - locked <0x0d319038> (a org.netbeans.modules.j2ee.deployment.impl.ServerInstance)
        at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.canFileDeploy(Deployment.java:313)
        at org.netbeans.modules.web.project.WebActionProvider.setDirectoryDeploymentProperty(WebActionProvider.java:1156)
        at org.netbeans.modules.web.project.WebActionProvider.getTargetNames(WebActionProvider.java:356)
        at org.netbeans.modules.web.project.WebActionProvider$1.run(WebActionProvider.java:214)
        at org.netbeans.modules.web.project.WebActionProvider.invokeAction(WebActionProvider.java:240)
        at org.netbeans.modules.project.ui.actions.ProjectAction.actionPerformed(ProjectAction.java:116)
        at org.netbeans.modules.project.ui.actions.LookupSensitiveAction.actionPerformed(LookupSensitiveAction.java:155)
        at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1882)
        at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2202)
Comment 1 _ tboudreau 2007-11-14 17:43:07 UTC 
Created attachment 52992 [details]
Thread dump
Comment 2 Vince Kraemer 2007-11-15 15:30:57 UTC 
this looks like an easy issue to resolve.
Comment 3 _ tboudreau 2007-11-15 17:35:58 UTC 
I'd suggest if at all possible to try to incorporate a fix into 6.0.  This is likely to be painful for anyone doing remote deployment - too often, internally we test 
only on local servers on a fast connection.