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.
This is a Sun Bug (6475838) filed against VWP. It seems to be another threading related problem. I was not able to reproduce it on another XP machine. The plugin code in question is pure NB. -------------------------------------------------------- NetBeans 0918 Shortfin 0926 J2EE 1.4 Source Structure: Jakarta BluePrints WinXP Jdk 1.6.0-rc-b98 JBoss 4.0.4 GA JBoss: Multiple deployments of same application fails. Steps: 1. create simple app. 2. deploy to jboss 3. add a new component to app and press the green arrow Deployment fails. init: deps-module-jar: deps-ear-jar: deps-jar: library-inclusion-in-archive: library-inclusion-in-manifest: Compiling 1 source file to C:\Documents and Settings\lfitzger\multi1\build\web\WEB-INF\classes compile: compile-jsps: Building jar: C:\Documents and Settings\lfitzger\multi1\dist\multi1.war do-dist: dist: Starting server JBoss Application Server 4 JBoss Application Server 4 Start Failed. HTTP Connector port 8080 is already in use. C:\Documents and Settings\lfitzger\multi1\nbproject\build-impl.xml:469: Deployment error: JBoss Application Server 4 Start Failed. HTTP Connector port 8080 is already in use. See the server log for details. BUILD FAILED (total time: 23 seconds) messages.log shows: INFORMATIONAL *********** Exception occurred ************ at 1:41 PM on Sep 27, 2006 org.netbeans.modules.j2ee.deployment.impl.ServerException: JBoss Application Ser ver 4 Start Failed. HTTP Connector port 8080 is already in use. at org.netbeans.modules.j2ee.deployment.impl.ServerInstance._start(Serve rInstance.java:1127) at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.startTarget( ServerInstance.java:1061) at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.startTarget( ServerInstance.java:872) at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.start(Server Instance.java:750) at org.netbeans.modules.j2ee.deployment.impl.TargetServer.startTargets(T argetServer.java:394) [catch] at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy (Deployment.java:99) at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:82) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe cutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.jav a:240) at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.jav a:293) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:13 1) *** (#1 of 1): 2006-09-27 10:44:58 PDT Can you please try this again with the newer NB/VWP? I tried to reproduce the problem but it worked just fine for me. Thanks, -- Marco *** (#1 of 2): 2006-10-02 11:39:09 PDT I can still reproduce it in: NetBeans 0926 Shortfin 1003_1 J2EE1.4 Source Structure: Jakarta BluePrints WinXP Jdk 1.6.0-rc-b98 JBoss 4.0.4 GA *** (#2 of 2): 2006-10-03 08:33:40 PDT >Lark, > >is your JBoss instance marked as running after the first deployment? > >Thanks, >-- Marco Good question. No, it was not. Lark
OK, so NetBeans thinks that the server is not running, can you please check whether it is really running or not - I mean, try to access the server with the browser.
Can you also make sure that this issue is not caused by your firewall settings?
1. Prior to the deployment, the jBoss server is up and running. The browser shows the previous run. 2. The firewall should have no affect since it worked the first time but I will give it another run to verify.
I have confirmed that disabling the firewall has no affect. One thing to note is that after the deployment fails, jBoss is still up and running with the first deploy.
seems to be a duplicate *** This issue has been marked as a duplicate of 86461 ***