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 installed 404CR2, ejb3 profile. Started the server - started ok. Created a new web project. When I run the web app the deployment fails: Building jar: C:\Documents and Settings\pb97924\WebApplication9\dist\WebApplication9.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\pb97924\WebApplication9\nbproject\build-impl.xml:431: 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: 10 seconds) In the log I see: [exec] org.netbeans.modules.j2ee.deployment.impl.ServerException: JBoss Application Server 4 Start Failed. HTTP Connector port 8080 is a dy in use. [exec] at org.netbeans.modules.j2ee.deployment.impl.ServerInstance._start(ServerInstance.java:1042) [exec] at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.startTarget(ServerInstance.java:976) [exec] at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.startTarget(ServerInstance.java:794) [exec] at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.start(ServerInstance.java:672) [exec] at org.netbeans.modules.j2ee.deployment.impl.TargetServer.startTargets(TargetServer.java:378) [exec] [catch] at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:93) [exec] at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:76) [exec] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) [exec] at org.apache.tools.ant.Task.perform(Task.java:364) etc. The IDE is apparently checking if the server is running and it thinks it is not. The check takes some time (hour cursor badge in registry).... then when it finishes I run the web app again and it is deployed OK. When I run it after a while I get the same error - again after the hour glass badge disapears Run works OK.
Is the server state recognized (the Runtime tab shows the green arrow) well -right after the server is started manually? -after the IDE times out? Or does it look like the IDE is thinking that the server is not running?
btw, it looks like the j2eeserver's call of isRunning() returns false although it should not and the server start then fails because is checks the ports. The question is why isRunning returns false (maybe times out) and why it takes so long time to recognize the state.
I restarted my computer (nothing on 8080). Start clean build of NB 5.5. Add jboss 4.0.4.CR2. Start it from IDE, after it starts the registry shows it is running. Create web app. Wait a bit. Run the web app. I docked the server registry into navigator to watch it. I get the error described earlier. Just as the IDE builds the web app and tries to deploy it I see that the jboss node get the hour glass icon badge (I guess it is checking if the server is running). When the icon badge dissapears from the server node the IDE thinks the server is not running. I ckick refresh on server node. See that it is not running. Click refresh again -- now I see that it IS running. Now I immediately Run the web app again and it deploys OK.
This makes the IDE completely unusable for development with jboss. I do a clean build of IDE, register jboss (404CR2), start jboss from netbeans. I create project and want to deploy and I cannot. I KNOW the server is running, I see it in IDE: 12:11:10,208 INFO [Server] JBoss (MX MicroKernel) [4.0.4.CR2 (build: CVSTag=JBoss_4_0_4_CR2 date=200603311500)] Started in 31s:45ms and when I deploy by copying the war file to server/deploy it works. But there is no way to convince the server registry about this or to deploy to it. This is a P1 for me.
Interestingly, when I stop IDE it is trying to stop jboss. So at that point the IDE recognizes it was running. I am puzzled.
It works ok with GA release of Jboss 4.0.4, it was only broken for CR2. Because I was the only one to reproduce this issue (AFAIK) I am closing it.