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 36473 - null pointer exception - tomcat will not start
Summary: null pointer exception - tomcat will not start
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-07 16:40 UTC by hall9792
Modified: 2006-06-05 00:50 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
ide.log (247.60 KB, text/plain)
2003-10-07 16:42 UTC, hall9792 		Details
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 hall9792 2003-10-07 16:40:25 UTC 
I receive the following error message as the ide 
starts up.  Note that this problem occurred soon 
after I updated the ide with two modules using 
the update center under the tools menu:  RMI and 
JNDI.
--------------------------------------------
java.lang.NullPointerException
	at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40Insta
llation.noBootStrapJar
(Tomcat40Installation.java:396)
	at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40Insta
llation.createInternalInstallation
(Tomcat40Installation.java:453)
	at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40Serve
rInstall.makeInstallation
(Tomcat40ServerInstall.java:46)
	at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40Serve
rInstall.restored(Tomcat40ServerInstall.java:31)
	at 
org.netbeans.modules.j2ee.impl.ServerRegistryImpl.
initPlugin(ServerRegistryImpl.java:159)
	at 
org.netbeans.modules.j2ee.impl.ServerRegistryImpl.
initLayerFile(ServerRegistryImpl.java:143)
	at 
org.netbeans.modules.j2ee.impl.ServerRegistryImpl.
setListener(ServerRegistryImpl.java:167)
	at 
org.netbeans.modules.j2ee.impl.ServerRegistryImpl.
getDefaultWebInstance(ServerRegistryImpl.java:331)
	at 
org.netbeans.modules.j2ee.ui.ServerRegistryNode.cr
eateKeyNodes(ServerRegistryNode.java:140)
	at 
org.netbeans.modules.j2ee.ui.ServerRegistryNode$Re
gistryChildren.createNodes
(ServerRegistryNode.java:308)
	at 
org.openide.nodes.Children$Keys$KE.nodes
(Children.java:1983)
	at 
org.openide.nodes.ChildrenArray.nodesFor
(ChildrenArray.java:109)
	at org.openide.nodes.Children$Info.nodes
(Children.java:1077)
	at 
org.openide.nodes.Children.justComputeNodes
(Children.java:583)
	at org.openide.nodes.ChildrenArray.nodes
(ChildrenArray.java:54)
	at org.openide.nodes.Children.getNodes
(Children.java:325)
	at org.openide.nodes.Children.findChild
(Children.java:265)
	at 
org.openide.nodes.FilterNode$Children.findChild
(FilterNode.java:1057)
	at 
org.openide.nodes.FilterNode$Children.findChild
(FilterNode.java:1057)
	at 
org.openide.nodes.FilterNode$Children.findChild
(FilterNode.java:1057)
	at 
org.openide.nodes.FilterNode$Children.findChild
(FilterNode.java:1057)
	at org.openide.nodes.NodeOp.findChild
(NodeOp.java:221)
	at org.openide.nodes.NodeOp.findPath
(NodeOp.java:239)
	at org.openide.nodes.NodeOp.findPath
(NodeOp.java:267)
	at 
org.openide.explorer.ExplorerManager.findPath
(ExplorerManager.java:700)
	at 
org.openide.explorer.ExplorerManager$6.run
(ExplorerManager.java:642)
	at org.openide.util.Task.run
(Task.java:136)
	at 
org.openide.util.RequestProcessor$Task.run
(RequestProcessor.java:328)
[catch] at 
org.openide.util.RequestProcessor$Processor.run
(RequestProcessor.java:670)
Comment 1 hall9792 2003-10-07 16:42:29 UTC 
Created attachment 11812 [details]
ide.log
Comment 2 hall9792 2003-10-07 19:56:39 UTC 
Upon further review, I discovered that my entire tomcat 
subdirectories have disappeared.  I may have made a rookie mistake to 
cause this, but I do not know what it would be.

I have since uninstalled/reinstalled the IDE and I am back in 
business.  By the way, this was very easy to do, thank you very much.
Comment 3 Milan Kuchtiak 2004-01-12 12:36:06 UTC 
This issue wont be fixed, because Tomcat4 plugin was replaced by
Tomcat5 plugin. The given exception cannot happen again.