-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 11/1/2010 11:16 AM, David kerber wrote:
> On 11/1/2010 11:05 AM, Christopher Schultz wrote:
> Christoph,
>
> On 10/29/2010 4:51 AM, Christoph Kukulies wrote:
I ran a tomcat 5.5 on an older debian formerly and after an upgrade to
5
On 11/1/2010 11:05 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph,
On 10/29/2010 4:51 AM, Christoph Kukulies wrote:
I ran a tomcat 5.5 on an older debian formerly and after an upgrade to
5.0.6 (debian lenny)
Wait, what? You "upgraded" from 5.5 to 5.0?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph,
On 10/29/2010 4:51 AM, Christoph Kukulies wrote:
> I ran a tomcat 5.5 on an older debian formerly and after an upgrade to
> 5.0.6 (debian lenny)
Wait, what? You "upgraded" from 5.5 to 5.0? That sounds like a downgrade
to me.
> Anyway, to
On 10/29/2010 5:40 AM, Christoph Kukulies wrote:
...
Ooops. Sorry, I noticed that I had already copied over my 5.5 system.xml
into the conf directory.
Using the original server.xml now works.
Yeah, that bit me too, when I migrated from 5.5.x to 6.0.x.
D
---
Am 29.10.2010 11:12, schrieb Mark Thomas:
On 29/10/2010 09:51, Christoph Kukulies wrote:
Anyway, to come to the point, I downloaded the tomcat 6.0.29 tar ball
and installed it under /opt/tomcat,
wrote a little startup script that simply invoked bin/startup.sh resp.
shutdown.
Didn't set any spec
On 29/10/2010 09:51, Christoph Kukulies wrote:
> Anyway, to come to the point, I downloaded the tomcat 6.0.29 tar ball
> and installed it under /opt/tomcat,
> wrote a little startup script that simply invoked bin/startup.sh resp.
> shutdown.
>
> Didn't set any special environment variables like JA
I ran a tomcat 5.5 on an older debian formerly and after an upgrade to
5.0.6 (debian lenny), my tomcat installation is messed up.
I'm running the tomcat behind an apache2 with some connectors. The mess
must have to do something with the
(braindead imho) split up between /usr/share/tomcat5.5 and
