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 (nike.apache.org: domain of barry.l.propes@citi.com
 designates 67.231.145.106 as permitted sender)
From: "Propes, Barry L " <barry.l.propes@citi.com>
To: "'Tomcat Users List'" <users@tomcat.apache.org>
Subject: RE: Internal Servlet Error
Thread-Topic: Internal Servlet Error
Thread-Index: AQHOT6aHhEp85SkGmEunqWwvQNkiPpkDns+A//+4w/A=
Date: Mon, 13 May 2013 17:02:12 +0000
Message-ID: <C3CE3C9461724341BB14DD344A030034134097@exgtmb27.nam.nsroot.net>
References: <1368427927.2106.YahooMailNeo@web190506.mail.sg3.yahoo.com>
 <519111BB.3060109@christopherschultz.net>
In-Reply-To: <519111BB.3060109@christopherschultz.net>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Yeah, it's clear from what's typed below his DB driver is way out of whack =
with this ancient version of Tomcat.

It probably got updated along the way by network sorts while the Tomcat ver=
sion stayed put.

Go to current, and with current Tomcat, also get a current JDK - I imagine =
the one you have is ancient as well.

=20

-----Original Message-----
From: Christopher Schultz [mailto:chris@christopherschultz.net]=20
Sent: Monday, May 13, 2013 11:16 AM
To: Tomcat Users List
Subject: Re: Internal Servlet Error

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Jeny,

On 5/13/13 2:52 AM, Jeny V wrote:
> I'm having some real issues , running programs in Tomcat on my=20
> machine.
>=20
> I just copied a jakarta folder named "jakarta-tomcat-3.3.1a" on to my=20
> D: drive (Path : D:\Program Files\jakarta-tomcat-3.3.1a) .

I'm going to go ahead and echo the few responses you're already gotten so f=
ar and tell you that you really need to discard that version of Tomcat. I d=
on't care if you have an application that "works" on it (obviously in some =
other environment) and are afraid to upgrade. That version is so old, we do=
n't even have the documentation online anymore for how many unfixed securit=
y vulnerabilities may or may not be present in that version.

The Java Servlet Specification is nominally backward-compatible, so you sho=
uld be able to download the latest version of Tomcat, configure it properly=
, and run your webapp without too many problems.

> I can run simple jsp programs with no database connection. But=20
> whenever I try to execute programs with database connections,=20
> following error encounters:
>=20
> Error: 500
>=20
>=20
> Internal Servlet Error:
>=20
> javax.servlet.ServletException: [Microsoft][ODBC Driver Manager] The=20
> specified DSN contains an architecture mismatch between the Driver and=20
> Application at [...]

The error is obvious from this message, but if you don't recognize the impo=
rtant words ("architecture mismatch") then you could be lost.

The problem is that you are using a 32-bit ODBC driver on a 64-bit JVM (or =
maybe a 64-bit ODBC driver on a 32-bit JVM: you didn't specify what kind of=
 JVM you were using, though I suspect you have a 64-bit JVM and a hideously=
 old driver that you've been lugging-around with your Tomcat 3 install). Yo=
u need to take one of the following actions:

1. Install a 32-bit JVM and use that. This will solve the architecture mism=
atch by switching the JVM. This may have an impact on your webapp (mostly a=
 smaller maximum heap size) so you may not want to do this.

2. Install a 32-bit version of your ODBC driver and use that. This will sol=
ve the architecture mismatch by switching the driver. You may not be able t=
o find a compatible 64-bit driver so you may not be able to do this.

3. Discard your ODBC driver entirely and use a pure-Java JDBC driver.
Pretty much every database has one of these things available one way or ano=
ther. This avoids the architecture mismatch entirely and it will likely res=
ult in better performance and stability of your web application. I highly r=
ecommend that you take this course of action.

What database are you using?

> Please do reply or help me with this problem as I tried so many times=20
> to fix the problem by trying various solutions.

In the future, it would be best to let everyone know what solutions you hav=
e tried and what the results were (other than just "it didn't work").

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJRkRG6AAoJEBzwKT+lPKRYaaoQAJyFeYHGRmZomqFan7W2jdHv
u7TZwFKlLAfkMfJaQQibprnuLZpW4flC5gdM0Rbj14EtfDauEMCSfe++oo6YlvqQ
F0Mih9ReRt7wSxVLNG58hUqcM6Hg3evEtwWoq9yd5I9YHYdl8Cz0X035/tdUHOUz
2RKBqQbFKr3A8m1k6Q6IYjsRKvPFDwyu0ekRYMrvSdtFZkiYPvzzwW1FpXdQ0Rwh
mHmVPrZzoIjiVXLWzT+kfFfrdrK6yBopieYZvOufEei88ZRvaI6u5LrXEpN6GEhX
DNkFoDWjPYXuKdQS+JBdwFX16DIKl7nIqI5nZ2sZthjPVqK64+r26R5tp+WEX5rp
ADkKyb6iGnwpAxy6l4LBGdanpDug0hC2beeOUtmcQkujJoychlvvF5L69VGpeEU1
JSQR0bQJGJIF9rP/PyAjBLzAUSI9sqh8IUZ+Bm+JrpAgiAWNSmKzeCW2te5r/GcF
Nt5ZpKBqMC2UHPNMRxKjIfuGc0gTApX467tVQ5zaouNbWO/lSOMrhZCgF8SD/OcF
fiQGrfeCDirHKIR6sczu3r07fGShTNCA47svAFV3/K31ou5dZT6SM3IvVqo2ZXog
whHWIXLxGl9SZrJToAJYcjlR2nRSb/yKygiE9Z2csgt34fUj9vQmWFo93ueph+j1
p8A0RhUfe4Kx6KzJ5lmP
=3DLZlk
-----END PGP SIGNATURE-----

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


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