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
remaining jar files are in my classpath..
Now application is working. But while starting tomcat I am getting following
message.. I dont know exactly what need to configure in log4j.xml
Listening for transport dt_socket at address: 5005
log4j:WARN No appenders could be found for logger
(org.apach
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
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...
Is that the solution?? What could be the reason??
Pid-2 wrote:
>
> selvajava wrote:
>> Thanks Bla
>>
>> Yes, I know its related to web apps.. I
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
Thanks Bla
Yes, I know its related to web apps.. I validated my xml file. But no
error.. I am looking clue less
Ognjen Blagojevic-3 wrote:
>
> Hi Selvajava,
>
> Read the stack trace carefully. It seems that the class
> com.headstrong.tablecomponent.util.ConfigFileParser is digesting an
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