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 29689 - java.lang.NullPointerException at org.netbeans.modules.tomcat.tomcat40.Tomcat40DataObject.setNewContext(Tomcat40DataObject.java:650)
Summary: java.lang.NullPointerException at org.netbeans.modules.tomcat.tomcat40.Tomca...
Status: RESOLVED DUPLICATE of bug 29755
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: Other Linux
: P3 blocker (vote)
Assignee: issues@serverplugins
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-21 08:35 UTC by johnzoet
Modified: 2006-06-05 00:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description johnzoet 2002-12-21 08:35:10 UTC 
Every now and then I get "Exception occurred in Request Processor" 
Most of the time this happens when switching to an other project. 
Sometimes this happens if I set the context of a web application 
and then execute a JSP page. 
The complete error message is: 
Annotation: Exception occurred in Request Processor 
java.lang.NullPointerException 
	at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40DataObject.setNewContext(Tomcat40DataObject.java:650) 
	at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.setTestComponent(Tomcat40Installation.java:656) 
	at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.incrementalDeploy(Tomcat40Installation.java:596) 
	at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40Instance.deploy(Tomcat40Instance.java:260) 
	at 
org.netbeans.modules.j2ee.impl.DefaultServerInstanceManager.doDeploy(DefaultServerInstanceManager.java:136) 
	at 
org.netbeans.modules.j2ee.impl.DefaultServerInstanceManager.startExecution(DefaultServerInstanceManager.java:150) 
	at 
org.netbeans.modules.j2ee.impl.DefaultServerInstanceManager.serverInstanceStartExecution(DefaultServerInstanceManager.java:101) 
	at 
org.netbeans.modules.j2ee.impl.DefaultExecPerformer.startExecution(DefaultExecPerformer.java:105) 
	at 
org.netbeans.modules.web.execution.WebDefaultExecPerformer.startExecution(WebDefaultExecPerformer.java:256) 
	at 
org.netbeans.modules.j2ee.impl.ServerExecutor.execute(ServerExecutor.java:74) 
	at 
org.netbeans.modules.j2ee.impl.ServerExecutor.execute(ServerExecutor.java:64) 
	at 
org.netbeans.modules.j2ee.impl.ExecSupport.start(ExecSupport.java:125) 
	at 
org.netbeans.modules.j2ee.impl.ServerExecSupport.start(ServerExecSupport.java:141) 
	at 
org.openide.actions.ExecuteAction.execute(ExecuteAction.java:139) 
	at 
org.openide.actions.ExecuteAction.execute(ExecuteAction.java:236) 
	at 
org.openide.actions.ExecuteAction.performAction(ExecuteAction.java:101) 
	at 
org.openide.util.actions.NodeAction.performAction(NodeAction.java:179) 
	at 
org.openide.util.actions.NodeAction.actionPerformed(NodeAction.java:170) 
	at 
org.netbeans.core.ModuleActions$1.run(ModuleActions.java:100) 
	at org.openide.util.Task.run(Task.java:136) 
[catch] at 
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:599)
Comment 1 Marian Mirilovic 2003-01-02 09:48:33 UTC 
reassigne to tomcat module
Comment 2 akemr 2003-01-31 13:59:50 UTC 
Same stack trace as in #29755

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