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 47347 - [40cat] NPE when starting a new created Tomcat Project
Summary: [40cat] NPE when starting a new created Tomcat Project
Status: RESOLVED DUPLICATE of bug 40659
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Sherold Dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-18 09:04 UTC by skesper
Modified: 2006-06-05 00:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description skesper 2004-08-18 09:04:35 UTC
Build:
netbeans-4_0-daily-bin-200408171800-17_Aug_2004_1800.zip

Steps for reproduction:
1. Create a new project using template
"Samples/Web Samples/Tomcat JSP Sample Project"
2. In Project Pane click right mouse button
selecting from context menu "Run Project"
3. Deployment Progress Monitor opens and NPE rises.

Annotation: Exception occurred in Request Processor
java.lang.NullPointerException
	at
org.netbeans.modules.tomcat5.ide.StartTomcat$StartRunnable.run(StartTomcat.java:352)
	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)
Comment 1 Petr Jiricka 2004-08-19 09:03:04 UTC
Same issue again. We already had this several times. I believe that
you used an old user directory which was created by an earlier
NetBeans build, right? When you start with a fresh user directory,
this exception should go away. Could you please verify this?

We really need to handle this more gracefully on our side, as many
users come across this. Stepan, could you please look at this issue?
Thanks.
Comment 2 skesper 2004-08-19 13:57:21 UTC
Ok, I moved away my .netbeans directory and could start up. So I guess
the problem is not a problem by itself but a doc issue telling the
user that if a NPE rises, he/she must delete his/her home directory :) 

If that is handled gracefully I'm satisfied. Shall I change the status
to fixed? I my opinion it is not. 
Comment 3 Petr Jiricka 2004-08-19 14:57:26 UTC
Agree this is not fixed, but it's a duplicate of issue 40659.

*** This issue has been marked as a duplicate of 40659 ***