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.
dev build 200806111204 1) The first time I deploy the application "Tomcat 6.0 Log" reads: 16-Jun-2008 12:14:37 PM org.apache.catalina.core.StandardContext filterStart SEVERE: Exception starting filter Webpage java.lang.NullPointerException [...] 2) I kill the "<ApplicationName> (run)" window and try deploying a second time. This time it hangs with: compile: compile-jsps: Checking data source definitions for missing JDBC drivers... 3) This is reproducible 100% of the time. Now, I appreciate the fact that my application is buggy and is failing to deploy, but Netbeans should be robust enough to recover from this instead of getting into a bad state.
I'm sorry, I tracked the hang back to my anti-virus NOD32. It's http monitoring service interferes with Netbeans-Tomcat communication. I worked around the problem by disabling http monitoring for java.exe That being said, there is still a legitimate bug report behind all of this: once a deploy fails once, redeploying that same webapp will always fail. For example, I have a webapp that fails to deploy because an exception gets thrown on startup. I fix the problem and try to redeploy, it fails with: Incrementally deploying http://localhost:8080/DesktopBeautifier.Server Completed incremental distribution of http://localhost:8080/DesktopBeautifier.Server Incrementally redeploying http://localhost:8080/DesktopBeautifier.Server Reload is in progress... reload?path=/DesktopBeautifier.Server Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/DesktopBeautifier.Server] has not been started Deployment error: The module has not been deployed. See the server log for details. ... If I shut down Tomcat, and retry the deploy operation it works perfectly. My guess is that the incremental redeploy or the reload operation is failing when it shouldn't.
Can you retest and provide more info on this? Message should be much more descriptive now. Thanks.
Sorry, I don't remember how I reproduced this in the first place. You can close it as WORKSFORME.
No reproducible usecase. Closing as WORKSFORME.