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.
Attempting to debug or execute a webapp (Tomcat isn't running already), I get a window indicating: "Exception occurred in Request Processor".. The details from the ide.log are as follows: *********** Exception occurred ************ at Mon Mar 01 13:55:01 EST 2004 Annotation: Exception occurred in Request Processor java.lang.NullPointerException at org.netbeans.modules.tomcat5.ide.StartTomcat$StartRunnable.run(StartTomcat.java:353) at org.openide.util.Task.run(Task.java:136) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:330) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:686) [org.netbeans.modules.tomcat5] INFORMATIONAL *********** Exception occurred ************ at Mon Mar 01 13:56:09 EST 2004 java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:452) at java.net.Socket.connect(Socket.java:402) at sun.net.NetworkClient.doConnect(NetworkClient.java:139) at sun.net.www.http.HttpClient.openServer(HttpClient.java:402) at sun.net.www.http.HttpClient.openServer(HttpClient.java:618) at sun.net.www.http.HttpClient.<init>(HttpClient.java:306) at sun.net.www.http.HttpClient.<init>(HttpClient.java:267) at sun.net.www.http.HttpClient.New(HttpClient.java:339) at sun.net.www.http.HttpClient.New(HttpClient.java:320) at sun.net.www.http.HttpClient.New(HttpClient.java:315) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:510) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:487) [catch] at org.netbeans.modules.tomcat5.TomcatManagerImpl.run(TomcatManagerImpl.java:369) at org.netbeans.modules.tomcat5.TomcatManagerImpl.list(TomcatManagerImpl.java:223) HTH!
New info: It appears to be something with compatibility with my pre-existing NB user work directory. This occurred after installing the latest build (200402261900). After removing my user dir (named 'dev'), I restarted NB and it successfully re-imported my old 3.5 prefs (I painstakingly created my own color scheme).. After the import, this deploy process is working flawlessly. I'm not sure what the odds are that this happen for other people, or what the difference was that 'broke the camels back', but perhaps a couple of extra exception handlers would be nice.. at least to tell me "your Tomcat configuration is corrupt"... or something.. Either way, thought this was good news. Ciao!
Thanks. The exception is on the line when IDE calls the "catalina.bat exec_startup" so it was likely something wrong with the installation. I will examine this for promo-D then.
*** Issue 41515 has been marked as a duplicate of this issue. ***
Indeed, this perticular error disapears when I choose a new and separate user dir. However, I now get a new error: web browser failed for http://localhost:8084XAT for string "8084XAT" XAT is the name of my web module context. The server is running on port 8084 (I can see the tomcat default page) but the module has not been deployed. Both execution and debuging processes give the same error.
*** Issue 47347 has been marked as a duplicate of this issue. ***
*** Issue 46951 has been marked as a duplicate of this issue. ***
*** Issue 47235 has been marked as a duplicate of this issue. ***
Assigning to Stepan.
*** Issue 47521 has been marked as a duplicate of this issue. ***
Upgrading to P2, looks like 9 out of 10 users run into this.
This problem occurs when version of bundled Tomcat changes between releases. In the NB user directory are stored settings, which hold also paths to TOMCAT_HOME and TOMCAT_BASE directories, this paths however do not exist anymore. Here is a workaround. 1) Go to your NB user directory. 2) Remove the "config\.nbattrs" file, if exists.
This fix solves this problem for upgrades to next releases. Not for upgrades from previous releases, however meaningful message will be provided in such cases.
Created attachment 17140 [details] commit log
*** Issue 40862 has been marked as a duplicate of this issue. ***
VERIFIED