You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by B T <bt...@live.com> on 2013/05/24 17:09:59 UTC
6.0.16 vs 6.0.37 puzzle
Hello,
I was wondering if anyone here might have some insight in different behaviors between 6.0.16 and 6.0.37.
I've been using version 6.0.16 (With CentOS 5) for quite some time - and it has worked very well. I was in the process of testing a new configuration and was exploring the possibility of upgrading to the latest 6.0.37 on CentOS 6.3.
After installing 6.0.37 (on CentOS 6.3), all of my .jsp pages now render as blank (.html still get served correctly). I then removed 6.0.37 and installed the old 6.0.16 (on the same CentOS 6.3 box) and things work well.
To explain the "blank" comment further, I open a browser, and I can pull up a simple .html page just fine. Once I go to a simple .jsp page, the entire browser screen is blank. The .java and the .class do get generated correctly in the working directory.
Also, to complicate things even further, 6.0.37 *works* with my codebase on my Windows 7 PC.
Does anyone have any insight into what could be so different between the Linux 6.0.16 Tomcat release and its 6.0.37 couterparts ?
Thanks -
BT
Re: 6.0.16 vs 6.0.37 puzzle
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
BT,
On 5/24/13 3:04 PM, B T wrote:
> Thanks for your guys' feedback ... I had removed 6.0.37 and
> installed 6.0.16. I then put back 6.0.37 (in a different directory)
> and tried it again and it somehow magically worked with 6.0.37
> (after it had already worked on 6.0.16). So now it works on both.
> I'm not really sure what it was, and even though it works now, I
> still do not have a warm feeling about this.
Did you install one on top of the other or anything like that? That
could certainly break everything.
> I think I may just revert to 6.0.16 and continue to use that.
Be sure to read the security announcements before deciding to do that.
> Perhaps when I get more time, I can pick the code apart to figure
> out exactly what was not working right. I was hoping to do that
> when considering a migration to Tomcat 7 though, not for a minor
> version change like this. I use lots of JSTL (WEB-INF\lib\jstl.jar
> and standard.jar) and postgresql (\lib\postgresql.jar) for the db -
> perhaps 6.0.37 did not like something there.
Over the past 2 years or so, I have upgraded several web applications
from Tomcat 5.5 -> 6.0.x -> 7.0.x and have had no problems whatsoever
at any stage.
Before that, I upgraded from Tomcat 4.1.x -> 5.5 which was a bit more
difficult because of the switch from "everything in server.xml" to
"start using context.xml, dude". When I say "difficult", it really
wasn't that difficult.
- -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/
iQIcBAEBCAAGBQJRn9sYAAoJEBzwKT+lPKRYJK8QAIU+zFJ/IUEvG9hsWQpyXiC+
X9bA5JMQVb/XQTGorNQuTwGUSjRqlhzps1QCMQvyCMwTh4aToF61qntKKin7VXGu
aYh4QMVx3D2i46hRHAmE5N1cAScQjV1Ga28ns+WZE4ovVeRuKwW40iafu/KVcR0S
4KhyZW6mJPrFxn6FDxMRvmUfbQiQ5i77GqNYbYm+g+vZJXbs1W09yZcQzNFS/7yJ
k5Xi7tr9PlQSuSyMT3/FRoha593gqhXMz1Y+Q0aknVmV5zV4+/UeP8BhjEEYnn3/
bHM0K/TABH3nQhD2t6/hpT9tpRZY2dIsNYPu4g3ISasciEnEtOTTr17Sey5ItHZD
J7B1sNJU95tM/ZmZcqxY3HWo0ekVD2x8nyHooU3NFF9Au2/AwGG73x2eAzYx1zay
h+upXiv4ZGSrPpH4oP2WKun17ZHRuD7vYXdS/fYifUPCYJix7hpnlTHSJh+1v062
FrQOEoCqZpwCKmyHEQ6LfItXUdKD6zkDV2gzO6Iuv2CcVm2zJHUULE2N+8uLeRN2
zZpf4x+t6vS/sPPhWLMMzp5x+MZliEJjKc3tTKj07oiNF7TLH9nrddRzFW6DvE5g
STgOT0Ac4CihYq0lZwq7qdPCPJjiLormE38wfvqIjA9EzCWChdNU4gJFsiLGnHzw
2dibdgPB9Y9wqHjDaDGr
=x+Js
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: 6.0.16 vs 6.0.37 puzzle
Posted by B T <bt...@live.com>.
> Date: Fri, 24 May 2013 09:32:46 -0700
> From: its_toasted@yahoo.com
> To: users@tomcat.apache.org
> Subject: Re: 6.0.16 vs 6.0.37 puzzle
>
> On 5/24/2013 9:04 AM, Christopher Schultz wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > BT,
> >
> > On 5/24/13 11:09 AM, B T wrote:
> >> I was wondering if anyone here might have some insight in
> >> different behaviors between 6.0.16 and 6.0.37.
> >>
> >> I've been using version 6.0.16 (With CentOS 5) for quite some time
> >> - and it has worked very well. I was in the process of testing a
> >> new configuration and was exploring the possibility of upgrading to
> >> the latest 6.0.37 on CentOS 6.3.
> >>
> >> After installing 6.0.37 (on CentOS 6.3), all of my .jsp pages now
> >> render as blank (.html still get served correctly). I then removed
> >> 6.0.37 and installed the old 6.0.16 (on the same CentOS 6.3 box)
> >> and things work well.
> >>
> >> To explain the "blank" comment further, I open a browser, and I
> >> can pull up a simple .html page just fine. Once I go to a simple
> >> .jsp page, the entire browser screen is blank. The .java and the
> >> .class do get generated correctly in the working directory.
> >>
> >> Also, to complicate things even further, 6.0.37 *works* with my
> >> codebase on my Windows 7 PC.
> >>
> >> Does anyone have any insight into what could be so different
> >> between the Linux 6.0.16 Tomcat release and its 6.0.37 couterparts
> >> ?
> >
> > So:
> > 1. Tomcat 6.0.37 + Linux = JSPs produce no output
> > 2. Tomcat 6.0.37 + Windows = works just fine
> > ?
> >
> > That's odd. I have 6.0.36 running in production with no issues;
> > haven't moved-up to 6.0.37 just yet.
> >
> > Can you strip-away as much as possible from your project while still
> > getting it to behave in this weird way, then post some code -- or
> > better yet -- a WAR file with source?
> >
> > - -chris
>
> Yep, I'm running 6.0.37 on all production boxes (CentOS 5.9 and CentOS
> 6.4) and the latest JRE 6 with no issues.
>
> . . . . just my two cents
> /mde/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Thanks for your guys' feedback ... I had removed 6.0.37 and installed 6.0.16. I then put back 6.0.37 (in a different directory) and tried it again and it somehow magically worked with 6.0.37 (after it had already worked on 6.0.16). So now it works on both. I'm not really sure what it was, and even though it works now, I still do not have a warm feeling about this. I think I may just revert to 6.0.16 and continue to use that. Perhaps when I get more time, I can pick the code apart to figure out exactly what was not working right. I was hoping to do that when considering a migration to Tomcat 7 though, not for a minor version change like this. I use lots of JSTL (WEB-INF\lib\jstl.jar and standard.jar) and postgresql (\lib\postgresql.jar) for the db - perhaps 6.0.37 did not like something there. btw: Mark, the View Source showed 8 blank lines when it didn't work - and that's it - no other errors in any of the logs either. Nothing in the Browser error console. Thanks again -BT
Re: 6.0.16 vs 6.0.37 puzzle
Posted by Mark Eggers <it...@yahoo.com>.
On 5/24/2013 9:04 AM, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> BT,
>
> On 5/24/13 11:09 AM, B T wrote:
>> I was wondering if anyone here might have some insight in
>> different behaviors between 6.0.16 and 6.0.37.
>>
>> I've been using version 6.0.16 (With CentOS 5) for quite some time
>> - and it has worked very well. I was in the process of testing a
>> new configuration and was exploring the possibility of upgrading to
>> the latest 6.0.37 on CentOS 6.3.
>>
>> After installing 6.0.37 (on CentOS 6.3), all of my .jsp pages now
>> render as blank (.html still get served correctly). I then removed
>> 6.0.37 and installed the old 6.0.16 (on the same CentOS 6.3 box)
>> and things work well.
>>
>> To explain the "blank" comment further, I open a browser, and I
>> can pull up a simple .html page just fine. Once I go to a simple
>> .jsp page, the entire browser screen is blank. The .java and the
>> .class do get generated correctly in the working directory.
>>
>> Also, to complicate things even further, 6.0.37 *works* with my
>> codebase on my Windows 7 PC.
>>
>> Does anyone have any insight into what could be so different
>> between the Linux 6.0.16 Tomcat release and its 6.0.37 couterparts
>> ?
>
> So:
> 1. Tomcat 6.0.37 + Linux = JSPs produce no output
> 2. Tomcat 6.0.37 + Windows = works just fine
> ?
>
> That's odd. I have 6.0.36 running in production with no issues;
> haven't moved-up to 6.0.37 just yet.
>
> Can you strip-away as much as possible from your project while still
> getting it to behave in this weird way, then post some code -- or
> better yet -- a WAR file with source?
>
> - -chris
Yep, I'm running 6.0.37 on all production boxes (CentOS 5.9 and CentOS
6.4) and the latest JRE 6 with no issues.
. . . . just my two cents
/mde/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: 6.0.16 vs 6.0.37 puzzle
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
BT,
On 5/24/13 11:09 AM, B T wrote:
> I was wondering if anyone here might have some insight in
> different behaviors between 6.0.16 and 6.0.37.
>
> I've been using version 6.0.16 (With CentOS 5) for quite some time
> - and it has worked very well. I was in the process of testing a
> new configuration and was exploring the possibility of upgrading to
> the latest 6.0.37 on CentOS 6.3.
>
> After installing 6.0.37 (on CentOS 6.3), all of my .jsp pages now
> render as blank (.html still get served correctly). I then removed
> 6.0.37 and installed the old 6.0.16 (on the same CentOS 6.3 box)
> and things work well.
>
> To explain the "blank" comment further, I open a browser, and I
> can pull up a simple .html page just fine. Once I go to a simple
> .jsp page, the entire browser screen is blank. The .java and the
> .class do get generated correctly in the working directory.
>
> Also, to complicate things even further, 6.0.37 *works* with my
> codebase on my Windows 7 PC.
>
> Does anyone have any insight into what could be so different
> between the Linux 6.0.16 Tomcat release and its 6.0.37 couterparts
> ?
So:
1. Tomcat 6.0.37 + Linux = JSPs produce no output
2. Tomcat 6.0.37 + Windows = works just fine
?
That's odd. I have 6.0.36 running in production with no issues;
haven't moved-up to 6.0.37 just yet.
Can you strip-away as much as possible from your project while still
getting it to behave in this weird way, then post some code -- or
better yet -- a WAR file with source?
- -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/
iQIcBAEBCAAGBQJRn49xAAoJEBzwKT+lPKRYBBAP/1t8BgiC80PuARDcjHrftyRm
72fOh5CDtiyzUcQZ40aEdi2QQD+YO9XUBMSrwoRC5G6t3/Y4iVPBXcyKGoWrBoFf
Xh+s6iCgAgH6tPUzXIRSfAnj+N80QMVJBiOaxQP4BPCtgKKMKjAD9HAw4fGsGyIf
5o81CyR37UQWHp2TY50XIRl3kcPjD9gKVdVePXx0UH1P2kNsfSTU9YvSastZpZ7/
GQOjLXKnIYDEqhdj4PD7smD8kDQGe1S98g0vk40mU3YfQTcakLjABwhVngAYY8DX
fP3YqXx6bz6bqvA+HwqxoXco3zgDbUMkwBtkHRekszgKJNHVqTCKRkO/aEgHPR3I
ZkUhHr+45IsRnPwupiXlFmhL5s7GsqiJd3Nu07RdTqu/s9RqH0TW3Ac3n8hkd/P8
2x5wyPSxVS8eB95Mtm7a2P4v+5crYaUwhVtOAkCQJGxMWolgS5ROMXp9U3mqHhwl
PAQRyZAGTnKNn2eVV8k/GZ5iM8XBaFyphiRhonDldpU4jnXPRYSa/BHYJmHrmJnz
tAI65Tw2eVvcrFl7/Zk6AWj3VhiD/tzH+EtUM76sa2eIEqUvr81emEW9++wSsEi8
nnA1jGQFcMdxIYKV26U3PwCx0xMKvkmHssaGhDEKR8QWHEqQwiI/kNXFWVQcS4lS
QyyCj4x7byuUvn2pEcPf
=7aHj
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: 6.0.16 vs 6.0.37 puzzle
Posted by Konstantin Kolinko <kn...@gmail.com>.
2013/5/24 B T <bt...@live.com>:
> Hello,
>
> I was wondering if anyone here might have some insight in different behaviors between 6.0.16 and 6.0.37.
>
> I've been using version 6.0.16 (With CentOS 5) for quite some time - and it has worked very well. I was in the process of testing a new configuration and was exploring the possibility of upgrading to the latest 6.0.37 on CentOS 6.3.
>
> After installing 6.0.37 (on CentOS 6.3), all of my .jsp pages now render as blank (.html still get served correctly). I then removed 6.0.37 and installed the old 6.0.16 (on the same CentOS 6.3 box) and things work well.
>
> To explain the "blank" comment further, I open a browser, and I can pull up a simple .html page just fine. Once I go to a simple .jsp page, the entire browser screen is blank. The .java and the .class do get generated correctly in the working directory.
>
> Also, to complicate things even further, 6.0.37 *works* with my codebase on my Windows 7 PC.
>
> Does anyone have any insight into what could be so different between the Linux 6.0.16 Tomcat release and its 6.0.37 couterparts ?
>
1. Do you have default web application (aka ROOT)?
(Error pages will not be able to render themselves if the request
cannot be mapped to a web application. You will see it as a blank
page, though with correct HTTP response code).
2. Configure an access log, if you do not have one. (E.g. uncomment it
in server.xml).
What HTTP response status is recorded in the log? 200? 400? 500?
If a request is incorrect it may result in a blank page (as processing
is stopped early as "error 400, incorrect request").
3. Anything in other logs?
4. How did you install 6.0.37?
Did you run it with correct permissions? (E.g. if one starts Tomcat as
root, shuts it down, and then tries to start it again as a non-root
user, permissions on directories created during the first run will
prevent it from functioning correctly).
5. Do you run with SecurityManager being enabled?
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: 6.0.16 vs 6.0.37 puzzle
Posted by "Mark H. Wood" <mw...@IUPUI.Edu>.
I would first look in the Tomcat log files to see if anything useful
is recorded at the time of the blank response. I'd also ask the
browser to display the page source to see if it's actually empty or
contains something (perhaps quite a lot of something) that renders as
an empty page. It might be instructive to look at the browser's error
console too.
--
Mark H. Wood, Lead System Programmer mwood@IUPUI.Edu
Machines should not be friendly. Machines should be obedient.