Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <471F53E9.8050505@schoenhaber.de>
Date: Wed, 24 Oct 2007 16:17:13 +0200
From: =?UTF-8?B?TWFya3VzIFNjaMO2bmhhYmVy?=
 <mailing-tomcat-user@schoenhaber.de>
Reply-To: users@tomcat.apache.org
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.8.1.8pre) Gecko/20071022 Thunderbird/2.0.0.6 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: users@tomcat.apache.org
Subject: Re: tomcat 5.0.25 migration to tomcat 6.0.14
References: <FE719C0A0E18E841930BA074F41FB29D024EE34A@mail.airscorp.com>
In-Reply-To: <FE719C0A0E18E841930BA074F41FB29D024EE34A@mail.airscorp.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Dustin Fortin wrote:

> Do I need to start from scratch and completely ditch the t5 server.xml?
> I really hope not because there are a ton of database resources I would
> have to test and be 100% sure on before throwing this into production.
> I will do this if you feel it necessary, but if possible I'd rather find
> a conversion solution instead of starting from scratch.

I share Christopher's opinion an this: start from scratch.

As an alternative (if you think the pain when starting from scratch is
too much to bare) you could remove non-essential stuff (including the
Resources) until either
a) the error goes away or
b) server.xml is small enough and doesn't contain any sensitive
information that you can post it here for others to take a look at it.

If a) happens, re-add stuff until the error come back. That'll give you
a more precise hint at what might be wrong.
In case of b), well, we'll see.

Regards
  mks

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org