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 43121 - Deploy Webapp to internal Tomcat fails with exception mesage
Summary: Deploy Webapp to internal Tomcat fails with exception mesage
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Sherold Dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-12 00:49 UTC by Ben Hutchison
Modified: 2004-09-08 14:20 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 Ben Hutchison 2004-05-12 00:49:49 UTC
When I try to deploy a web app I am developing 
to the internal Tomcat, the deploy progress bar 
only goes half way then stops. A request 
processor exception message popped up, as shown 
below.

Annotation: Exception occurred in Request 
Processor
java.lang.NullPointerException
	at 
org.netbeans.modules.j2ee.deployment.impl.TargetS
erver.saveRootTargetModules
(TargetServer.java:494)
	at 
org.netbeans.modules.j2ee.deployment.impl.TargetS
erver.handleCompletedDistribute
(TargetServer.java:607)
	at 
org.netbeans.modules.j2ee.deployment.impl.TargetS
erver.access$000(TargetServer.java:54)
	at 
org.netbeans.modules.j2ee.deployment.impl.TargetS
erver$DistributeEventHandler.handleProgressEvent
(TargetServer.java:406)
	at 
org.netbeans.modules.tomcat5.progress.ProgressEve
ntSupport.fireHandleProgressEvent
(ProgressEventSupport.java:101)
	at 
org.netbeans.modules.tomcat5.TomcatManagerImpl.ru
n(TomcatManagerImpl.java:465)
	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 Sherold Dev 2004-09-08 14:20:24 UTC
Cannot reproduce, it has been probably already fixed. If it still
occurs, feel free to reopen this issue.