Moin Chris,
Christopher Schultz schrieb am 20.12.2010 um 15:18 (-0500):
> On 12/19/2010 7:35 AM, Michael Ludwig wrote:
> > In the case of Xerces, however, it is preferable to put the JAR(s)
> > into %CATALINA_HOME%\endorsed (which may not exist but may be
> > created) so they will be available to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micheal,
On 12/19/2010 7:35 AM, Michael Ludwig wrote:
> In the case
> of Xerces, however, it is preferable to put the JAR(s)
> into %CATALINA_HOME%\endorsed (which may not exist but may
> be created) so they will be available to all of Tomcat and
> ou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lewis,
On 12/18/2010 3:27 PM, McGibbney, Lewis John wrote:
> This version of Jena comes with Xerces-J 2.6.1, it is installed in
> webapp's WEB-INF/classes/plugins/lib-xml, will this location present
> any issue or should I copy it to WEB-INF/lib?
Tom
Hi Lewis,
McGibbney, Lewis John schrieb am 20.12.2010 um 09:42 (+):
> >I'm not sure the thread Tomcat points out wasn't
> >stopped is related to Commons Logging. Could it be
> >that you created the thread in your app?
>
> I think that you are correct here although if I post more of the log
>
>I'm not sure the thread Tomcat points out wasn't
>stopped is related to Commons Logging. Could it be
>that you created the thread in your app?
I think that you are correct here although if I post more of the log for you to
see then maybe we can confirm whether it is a common issue or not
20-Dec
McGibbney, Lewis John schrieb am 19.12.2010 um 18:56 (+):
>
> I managed to get over the parser issue by
> following your suggestions.
Fine!
> I am now encountering errors with the class
> org/apache/common/logging/LogFactory when I try
> to launch webapp on Tomcat.
Commons Logging is freque
erned that in
beating the parser problem I have opened a can of worms. Does anyone have any
comments here please.
Thanks Lewis
From: Michael Ludwig [mil...@gmx.de]
Sent: 19 December 2010 12:35
To: users@tomcat.apache.org
Subject: Re: HTTP Status 500 - S
thank you for this it has been a great help
Lewis
From: Michael Ludwig [mil...@gmx.de]
Sent: 19 December 2010 12:35
To: users@tomcat.apache.org
Subject: Re: HTTP Status 500 - Server Internal Error
McGibbney, Lewis John schrieb am 18.12.2010 um 21:20
McGibbney, Lewis John schrieb am 18.12.2010 um 21:20 (+):
>
> I understand this now, my initial understanding
> was that Tomcat was distributed with a version
> of xerces (or some other) parser implementation
Tomcat isn't, but the Sun JRE is shipping a forked and
modified Apache Xerces. It ha
: 18 December 2010 21:07
To: Tomcat Users List
Subject: Re: HTTP Status 500 - Server Internal Error
On 18/12/2010 19:47, McGibbney, Lewis John wrote:
> Hello List,
>
> I am currently using Apache Nutch 1.2 and Tomcat 6.0.26 (first post on list).
> I recently configured use of a plugin
On 18/12/2010 19:47, McGibbney, Lewis John wrote:
> Hello List,
>
> I am currently using Apache Nutch 1.2 and Tomcat 6.0.26 (first post on list).
> I recently configured use of a plugin within Nutch which has been known to
> cause the above error due to the fact that Tomcat and Jena (a framework
10 19:57
To: Tomcat Users List
Subject: Re: HTTP Status 500 - Server Internal Error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lewis,
On 12/18/2010 2:47 PM, McGibbney, Lewis John wrote:
> I am currently using Apache Nutch 1.2 and Tomcat 6.0.26 (first post on list).
Welcome.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lewis,
On 12/18/2010 2:47 PM, McGibbney, Lewis John wrote:
> I am currently using Apache Nutch 1.2 and Tomcat 6.0.26 (first post on list).
Welcome.
> I recently configured use of a plugin within Nutch which has been
> known to cause the above error
13 matches
Mail list logo
