Problem while starting Apache Tomcat 4.1.16

[felix thomas]

hi,
My Tomcat does not start but gives me the following error

java.lang.NoSuchMethodError: java.util.logging.Logger.logp(Ljava/util/logging/Level;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String V
at org.apache.commons.logging.impl.Jdk14Logger.log(Jdk14Logger.java:126)
at org.apache.commons.logging.impl.Jdk14Logger.info(Jdk14Logger.java:192)
at org.apache.commons.modeler.Registry.loadRegistry(Registry.java:264)
at org.apache.catalina.mbeans.MBeanUtils.createRegistry(MBeanUtils.java:1624)
at org.apache.catalina.mbeans.MBeanUtils.<clinit>(MBeanUtils.java:161)
at org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.<clinit>(GlobalResourcesLifecycleListener.java:115)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:33)
at sun.reflect.InflatableConstructorAccessorImpl.newInstance(InflatableConstructorAccessorImpl.java:38)
at java.lang.reflect.Constructor.newInstance(Constructor.java:273)
at java.lang.Class.newInstance0(Class.java:290)
at java.lang.Class.newInstance(Class.java:249)
at org.apache.commons.digester.ObjectCreateRule.begin(ObjectCreateRule.java:253)
at org.apache.commons.digester.Digester.startElement(Digester.java:1237)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:459)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:221)
at org.apache.xerces.impl.XMLNamespaceBinder.emptyElement(XMLNamespaceBinder.java:595)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:747)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1477)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
at org.apache.commons.digester.Digester.parse(Digester.java:1495)
at org.apache.catalina.startup.Catalina.start(Catalina.java:449)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:30)
at sun.reflect.InflatableMethodAccessorImpl.invoke(InflatableMethodAccessorImpl.java:48)
at java.lang.reflect.Method.invoke(Method.java:306)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
I have declared all the variables in the autoexec.bat
namely
SET CATALINA_HOME=C:\TOMCAT
set JAVA_HOME=C:\jdk1.4
I have even included c:\tomcat\common\lib in the classpath
still the dos prompt comes and goes out.
I am on Window98 SE
what could be the problem??
I am frustrated already since i am trying to start from 5 days.
Please somebody help

[Nitin Barhanpurkar]

I have faced similar type of problems in past, root cause being different.
Please make a fresh Tomcat installation, and without deploying any code of yours, start the Tomcat. If it starts, problem could be in your code.

[William Brogden]

Windows 98 has a known problem with environment space that may be related. Did you increase the environment memory?
It is hard to tell whats really happening when the window disappears. I suggest you modify startup.bat so the last line reads something like:

 call "%EXECUTABLE%" run %CMD_LINE_ARGS% 

(thats "run" instead of "start") so tomcat will start in the same window and you can read the messages.

[Mike Curwen]

Did everyone miss this?
java.lang.NoSuchMethodError: java.util.logging.Logger.logp(Ljava/util/logging/Level;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;PV

You're using a 1.4.1 logging call. Do you have the latest 1.4.1 JRE on your system?