RE: Internal Servlet Error
Sorry, I must have missed that they had an updated JDk. -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Tuesday, May 14, 2013 11:33 AM To: Tomcat Users List Subject: Re: Internal Servlet Error -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Barry, On 5/13/13 1:02 PM, Propes, Barry L wrote: > 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 version stayed put. No, it's probably correct for that time period. > Go to current, and with current Tomcat, also get a current JDK - I > imagine the one you have is ancient as well. OP reports the Java version is jdk1.7.0_07 - probably 64-bit given the 64-bit Windows 7 OS in use. - -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/ iQIcBAEBCAAGBQJRkmc0AAoJEBzwKT+lPKRYBOIQAK2gJcD3lCjMXqck9qxi9kjs 0jqpSf4j3Ti4Gl8IKnT+enjuKqEDd8dpB4CShY3qFRNJCbkhnmh9g8DDfCFaxpqV BmG07nW4zFm76kbGCl/zipRBkSxPWtSpXl5p1x+7r0ud7QH3HKxPkJ75eOtMzlFU SSHwII9fNy7g5WHrB30LVlsW8pkSn/AuacFjP3hr5/Wqx/T9YmOM7VTJgmc6eucq ynT5le4bSl0b7vi8eBSB9ImRErdONPgamFyWn+BUMvBV/hNkljHMO6UzpUPU3/lz XvC/mVsaNwi77DZ9V3xRO6113dY0rnnpES8n4cvfzICU2KTzF/uesZWksye491q+ QJmVnKsM4UUaNBIvSbvJBy22PwYF0SeldTg2HiSmFoKMqw5mneYLy3g9xptfVX6+ d+2sHOj1OfIDb+7bstV5F2LUgk/JuowGps/b4gYA/0DmsRwYjKw9kxUWc75Vehs3 Dv429FO/CeAyN1Cv28N7heszF15M5RbYxNh3Mj605yGFpSpGSBgmzCuyb8jMw5L0 cujXEWh+1H4EXxh9hfM5rU1dLzhK5kwSUsV4uCGMmT8rcqCBZYXYbeLpeLhP7IKz zS+8TOMGLRXiaPrsVBAIPln1ajUMV/jIwJV0fdZtNQIEK8FrZnWulmC9SdwWuxO0 xU6dMgZJlxz2CHoScO3N =nQBy -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Internal Servlet Error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Barry, On 5/13/13 1:02 PM, Propes, Barry L wrote: > 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 version stayed put. No, it's probably correct for that time period. > Go to current, and with current Tomcat, also get a current JDK - I > imagine the one you have is ancient as well. OP reports the Java version is jdk1.7.0_07 - probably 64-bit given the 64-bit Windows 7 OS in use. - -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/ iQIcBAEBCAAGBQJRkmc0AAoJEBzwKT+lPKRYBOIQAK2gJcD3lCjMXqck9qxi9kjs 0jqpSf4j3Ti4Gl8IKnT+enjuKqEDd8dpB4CShY3qFRNJCbkhnmh9g8DDfCFaxpqV BmG07nW4zFm76kbGCl/zipRBkSxPWtSpXl5p1x+7r0ud7QH3HKxPkJ75eOtMzlFU SSHwII9fNy7g5WHrB30LVlsW8pkSn/AuacFjP3hr5/Wqx/T9YmOM7VTJgmc6eucq ynT5le4bSl0b7vi8eBSB9ImRErdONPgamFyWn+BUMvBV/hNkljHMO6UzpUPU3/lz XvC/mVsaNwi77DZ9V3xRO6113dY0rnnpES8n4cvfzICU2KTzF/uesZWksye491q+ QJmVnKsM4UUaNBIvSbvJBy22PwYF0SeldTg2HiSmFoKMqw5mneYLy3g9xptfVX6+ d+2sHOj1OfIDb+7bstV5F2LUgk/JuowGps/b4gYA/0DmsRwYjKw9kxUWc75Vehs3 Dv429FO/CeAyN1Cv28N7heszF15M5RbYxNh3Mj605yGFpSpGSBgmzCuyb8jMw5L0 cujXEWh+1H4EXxh9hfM5rU1dLzhK5kwSUsV4uCGMmT8rcqCBZYXYbeLpeLhP7IKz zS+8TOMGLRXiaPrsVBAIPln1ajUMV/jIwJV0fdZtNQIEK8FrZnWulmC9SdwWuxO0 xU6dMgZJlxz2CHoScO3N =nQBy -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Internal Servlet Error
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 version
stayed put.
Go to current, and with current Tomcat, also get a current JDK - I imagine the
one you have is ancient as well.
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
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
> machine.
>
> I just copied a jakarta folder named "jakarta-tomcat-3.3.1a" on to my
> 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 far
and tell you that you really need to discard that version of Tomcat. I don'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 don't even
have the documentation online anymore for how many unfixed security
vulnerabilities may or may not be present in that version.
The Java Servlet Specification is nominally backward-compatible, so you should
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
> whenever I try to execute programs with database connections,
> following error encounters:
>
> Error: 500
>
>
> Internal Servlet Error:
>
> javax.servlet.ServletException: [Microsoft][ODBC Driver Manager] The
> specified DSN contains an architecture mismatch between the Driver and
> Application at [...]
The error is obvious from this message, but if you don't recognize the
important 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). You need to
take one of the following actions:
1. Install a 32-bit JVM and use that. This will solve the architecture mismatch
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 solve
the architecture mismatch by switching the driver. You may not be able to 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
another. This avoids the architecture mismatch entirely and it will likely
result in better performance and stability of your web application. I highly
recommend 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
> to fix the problem by trying various solutions.
In the future, it would be best to let everyone know what solutions you have
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
=LZlk
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
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
> machine.
>
> I just copied a jakarta folder named "jakarta-tomcat-3.3.1a" on to
> my 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 far and tell you that you really need to discard that version of
Tomcat. I don'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 don't even have the documentation online anymore
for how many unfixed security vulnerabilities may or may not be
present in that version.
The Java Servlet Specification is nominally backward-compatible, so
you should 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
> whenever I try to execute programs with database connections,
> following error encounters:
>
> Error: 500
>
>
> Internal Servlet Error:
>
> javax.servlet.ServletException: [Microsoft][ODBC Driver Manager]
> The specified DSN contains an architecture mismatch between the
> Driver and Application at [...]
The error is obvious from this message, but if you don't recognize the
important 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). You need to take one of the following actions:
1. Install a 32-bit JVM and use that. This will solve the architecture
mismatch 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 solve the architecture mismatch by switching the driver. You may
not be able to 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 another. This avoids the architecture mismatch entirely and it will
likely result in better performance and stability of your web
application. I highly recommend 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 to fix the problem by trying various solutions.
In the future, it would be best to let everyone know what solutions
you have 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
=LZlk
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Internal Servlet Error
Jeny V wrote: Hi , I'm having some real issues , running programs in Tomcat on my machine. I just copied a jakarta folder named "jakarta-tomcat-3.3.1a" on to my D: drive (Path : D:\Program Files\jakarta-tomcat-3.3.1a) . Do you not read the answers you have already been given ? The current version of Tomcat is 7. See http://tomcat.apache.org. You are trying to use a Tomcat version 3, which is more than 10 years old. Nobody can help you with that version. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
