to:selvar...@headstrong.com]
>> Subject: Re: Tomcat error while starting related to java
>>
>> remaining jar files are in my classpath..
>
> If that means you're using the CLASSPATH environment variable, you've made
> a fatal error - that should never be set when runn
> From: selvajava [mailto:selvar...@headstrong.com]
> Subject: Re: Tomcat error while starting related to java
>
> remaining jar files are in my classpath..
If that means you're using the CLASSPATH environment variable, you've made a
fatal error - that should never be s
)
>>>>>> at
>>>>>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>>>>>> at
>>>>>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091)
>>>>>> at
>
selvajava wrote:
> Thanks for this help.. But I have done little deferent.. I have moved this
> jar from webapps/lib to global lib folder.. Now this error not showing...
Does that mean that your application is now working?
> Is that the solution?? What could be the reason??
It depends. Have yo
e Method)
>>>>at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>at java.lang.reflect.Me
selvajava wrote:
> Thanks Bla
>
> Yes, I know its related to web apps.. I validated my xml file. But no
> error.. I am looking clue less
The error below appears in the stacktrace
> Caused by: java.lang.NoClassDefFoundError:
> org/apache/commons/lang/NullArgumentException
Is the jar containi
.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.sc
Hi Selvajava,
Read the stack trace carefully. It seems that the class
com.headstrong.tablecomponent.util.ConfigFileParser is digesting an XML
file (probably TableProperties.xml), and during that process the
exception is thrown - probably due to malformed XML.
It seems that it doesn't have an
er.java:1666)
at
com.headstrong.tablecomponent.util.ConfigFileParser.parseConfigFile(ConfigFileParser.java:115)
... 28 more
--
View this message in context:
http://www.nabble.com/Tomcat-error-while-starting-related-to-java-tp22429031p22429031.html
Sent from the Tomcat - User mailing li
