You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "venkatdama@hotmail.com Shanthisowjanyadama9" <ve...@hotmail.com> on 2024/07/26 01:45:25 UTC
Tomcat 9.0.80 Server Issues.
Hi Tomcat Uses group,
My Java Spring MVC application works great with Tomcat 9.0.50, when I moved Tomcat version from 9.0.50 to 9.0.80 my spring MVC java web application was broken, JAAS authentication is not working as it expected, all of a sudden chrome browser(s) caching web application and response headers not expiring like before, I am looking for a workaround for this issue here. I am also wondering why backward compatibility is not maintained in Tomcat Server end when I switch from one version of Tomcat to another version. Your help here is greatly appreciated.
Best Regards
Venkat
Re: Tomcat 9.0.80 Server Issues.
Posted by Christopher Schultz <ch...@christopherschultz.net>.
Chuck and Venkat,
On 7/25/24 22:48, Chuck Caldarale wrote:
>> On Jul 25, 2024, at 20:45, venkatdama@hotmail.com Shanthisowjanyadama9 <ve...@hotmail.com> wrote:
>>
>> I am also wondering why backward compatibility is not maintained
>> in Tomcat Server end when I switch from one version of Tomcat to
>> another version.
>
> Compatibility is maintained, except when relevant standards are being
> violated, especially when related to security. In some such cases,
> the old, invalid behavior can be re-enabled with configuration tags.
> Check the Tomcat 9.0 documentation to see if anything might be useful
> in your case.
>
> Most “compatibility” problems are actually application bugs, such as
> hanging onto references to response or request objects after a
> response has been committed.
+1
I have an application originally built for Tomcat 4.something that has
never had any compatibility issues between then and Tomcat 9.
I've even recently been deploying it on Tomcat 10.1 and allowing Tomcat
to "migrate" the entire application to Jakarta EE APIs and it runs
flawlessly.
Any apparent incompatibilities are likely to fall in one of several
categories:
1. Use of Servlet Spec features, etc. that have been deprecated
and should not be used. The fix here is to write standards-compliant
applications using the current specifications and the nuances
thereof. For example, some APIs are still present but should never
be used (e.g. SingleThreadServlet or whatever, or getRealPath).
2. Significant non-standard configuration, usually trying to work-around
some abuse of one or more specifications. If you are tweaking the
handling of URI characters, slash processing, etc. then it's time
to fix your application so that it doesn't rely on those risky
configurations.
3. Use of Tomcat-specific APIs, internals, or libraries. Just don't
do this. You don't want to be locked-in to any specific vendor, do
you? I avoid vendor lock-in, even if the "vendor" is ASF.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 9.0.80 Server Issues.
Posted by Chuck Caldarale <n8...@gmail.com>.
> On Jul 25, 2024, at 20:45, venkatdama@hotmail.com Shanthisowjanyadama9 <ve...@hotmail.com> wrote:
>
> My Java Spring MVC application works great with Tomcat 9.0.50, when I moved Tomcat version from 9.0.50 to 9.0.80 my spring MVC java web application was broken,
So you moved from a 3-year old version of Tomcat to one that’s almost a year old? Why not use the current release? Also, let us know the platform you’re running on, including the JVM version.
> JAAS authentication is not working as it expected,
What was the expectation? What is the newly observed behavior? Be specific.
> all of a sudden chrome browser(s) caching web application and response headers not expiring like before,
There was considerable tightening up of header processing during the two years between 9.0.50 and 9.0.80 (and beyond), so if your application was generating invalid ones, you may be encountering that. Any entries in the Tomcat logs that would be relevant? Any examples of headers you think should be honored but aren’t now?
> I am looking for a workaround for this issue here.
First, move to the current Tomcat 9.0.x version, not one that’s a year old. Second, examine the Tomcat logs closely to see if there’s any information in there corresponding to the problems you’re having.
> I am also wondering why backward compatibility is not maintained in Tomcat Server end when I switch from one version of Tomcat to another version.
Compatibility is maintained, except when relevant standards are being violated, especially when related to security. In some such cases, the old, invalid behavior can be re-enabled with configuration tags. Check the Tomcat 9.0 documentation to see if anything might be useful in your case.
Most “compatibility” problems are actually application bugs, such as hanging onto references to response or request objects after a response has been committed.
- Chuck
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 9.0.91 Server version breaks my application and changes behavior in terms of handling requests from Chrome Browser
Posted by Venkat Dama <ve...@hotmail.com>.
Hi Chris,
Hi Chris,
JAAS authentication is not working as it expected in Tomcat 9.0.91, it works well in Tomcat 9.0.50, I am not using any Tomcat Specific libraries in my application, I also use URIEncdoing="UTF-8" and alllowEncodedSlash="true" in Connector tag.
When I clear the browser cache in chrome browser and testing my web application using Tomcat 9.0.91 version by entering wrong password and right user name first it throws error properly which is correct, then second time when I enter correct user ID/Password it takes me into the web application correctly, here I am navigating different pages via tabs/buttons with in a application, one of the navigation causes to closes the application somehow (session not ended here) and takes me to the login screen, when I try to re-enter the same Username and Password as I entered second time (right user name/password) in the above scenario, application throws me j_security_check 404 page not found error, when I either remove j_security_check padding from the URL and click the refresh tab on the browser, application relaunches and works as it expected, other scenario is to clear the cache from the browser, close the browser, re-open the browser and re-launch the application by entering correct user name/password on login screen then everything works as it expected. This behavior does not happen in Tomcat server 9.0.50. Why I am seeing behavior changed and application is breaking only by switching Tomcat server version from 9.0.50 to 9.0.91. Any help here is greatly appreciated to resolve the issue.
Best Regards
________________________________
From: Venkat Dama <ve...@hotmail.com>
Sent: Friday, July 26, 2024 6:55 PM
To: Tomcat Users List <us...@tomcat.apache.org>
Subject: Re: Tomcat 9.0.80 Server Issues.
Hi Tomcat Users Group,
When I clear the browser cache in chrome browser and testing my web application using Tomcat 9.0.91 version by entering wrong password and right user name first it throws error properly which is correct, then second time when I enter correct user ID/Password it takes me into the web application correctly, here I am navigating different pages via tabs/buttons with in a application, one of the navigation causes to closes the application somehow (session not ended here) and takes me to the login screen, when I try to re-enter the same Username and Password as I entered second time (right user name/password) in the above scenario, application throws me j_security_check 404 page not found error, when I either remove j_security_check padding from the URL and click the refresh tab on the browser, application relaunches and works as it expected, other scenario is to clear the cache from the browser, close the browser, re-open the browser and re-launch the application by entering correct user name/password on login screen then everything works as it expected. This behavior does not happen in Tomcat server 9.0.50. Why I am seeing behavior changed and application is breaking only by switching Tomcat server version from 9.0.50 to 9.0.91. Any help here is greatly appreciated to resolve the issue.
Best Regards
Venkat
________________________________
From: Venkateswararao Dama <ve...@hotmail.com>
Sent: Friday, July 26, 2024 12:06 PM
To: users@tomcat.apache.org <us...@tomcat.apache.org>
Subject: Re: Tomcat 9.0.80 Server Issues.
Hi Tomcat Users Group,
Even Tomcat 9.0.91 version with JDK 17 and application running on Windows 2022 server has same caching issues, in 9.0.91 version of Tomcat Callback handlers are working as it expected in JAAS authentication according to Tomcat 9.0.91 change log, is this true, in Tomcat 9.0.91 why response headers are in Private mode instead of expiring Jan 1st 1970, shall I adjust response headers to private mode, max-expires to 6000. How to handle response headers in my Spring MVC application from expire mode to private, even though I am using expires zero, whey it is ignoring, what tag I need to use to get back to backward compatibility in my Spring MVC application not caching from browsers, JAAS authetification validates User Name/Password properly from Tomcat container. Please help me here when you get a chance, your help here mostly appreciated.
Best Regards
Venkat
________________________________
From: venkatdama@hotmail.com Shanthisowjanyadama9 <ve...@hotmail.com>
Sent: Friday, July 26, 2024 1:45 AM
To: users@tomcat.apache.org <us...@tomcat.apache.org>
Subject: Tomcat 9.0.80 Server Issues.
Hi Tomcat Uses group,
My Java Spring MVC application works great with Tomcat 9.0.50, when I moved Tomcat version from 9.0.50 to 9.0.80 my spring MVC java web application was broken, JAAS authentication is not working as it expected, all of a sudden chrome browser(s) caching web application and response headers not expiring like before, I am looking for a workaround for this issue here. I am also wondering why backward compatibility is not maintained in Tomcat Server end when I switch from one version of Tomcat to another version. Your help here is greatly appreciated.
Best Regards
Venkat
Re: Tomcat 9.0.80 Server Issues.
Posted by "Terence M. Bandoian" <te...@tmbsw.com>.
I think this is called thread hijacking which is frowned upon on this
list. Try re-sending the message with a new thread.
-Terence Bandoian
On 7/26/2024 9:04 PM, Dick Hildreth wrote:
> I'm running Tomcat 10.1 on OpenJDK JVM version 22.0.0+8-16, using hSQLdb
> 2.7.3 connected via commons-dbcp2-2.12.0 and commons-pool-2.12.0.
>
> It works fine for a while, as previous versions of this combination had,
> but after a relatively short time (unknown whether it's clock time or usage
> instances), the database connection is lost. Restarting Tomcat is all
> that's required to get everything working again.
>
> Are there any suggestions as to what I might do?
> Thanks,
> Dick
>
> On Fri, Jul 26, 2024 at 1:56 PM Venkat Dama<ve...@hotmail.com> wrote:
>
>> Hi Tomcat Users Group,
>>
>>
>> When I clear the browser cache in chrome browser and testing my web
>> application using Tomcat 9.0.91 version by entering wrong password and
>> right user name first it throws error properly which is correct, then
>> second time when I enter correct user ID/Password it takes me into the web
>> application correctly, here I am navigating different pages via
>> tabs/buttons with in a application, one of the navigation causes to closes
>> the application somehow (session not ended here) and takes me to the login
>> screen, when I try to re-enter the same Username and Password as I entered
>> second time (right user name/password) in the above scenario, application
>> throws me j_security_check 404 page not found error, when I either remove
>> j_security_check padding from the URL and click the refresh tab on the
>> browser, application relaunches and works as it expected, other scenario is
>> to clear the cache from the browser, close the browser, re-open the browser
>> and re-launch the application by entering correct user name/password on
>> login screen then everything works as it expected. This behavior does not
>> happen in Tomcat server 9.0.50. Why I am seeing behavior changed and
>> application is breaking only by switching Tomcat server version from 9.0.50
>> to 9.0.91. Any help here is greatly appreciated to resolve the issue.
>>
>> Best Regards
>> Venkat
>>
>> ________________________________
>> From: Venkateswararao Dama<ve...@hotmail.com>
>> Sent: Friday, July 26, 2024 12:06 PM
>> To:users@tomcat.apache.org <us...@tomcat.apache.org>
>> Subject: Re: Tomcat 9.0.80 Server Issues.
>>
>> Hi Tomcat Users Group,
>>
>> Even Tomcat 9.0.91 version with JDK 17 and application running on Windows
>> 2022 server has same caching issues, in 9.0.91 version of Tomcat Callback
>> handlers are working as it expected in JAAS authentication according to
>> Tomcat 9.0.91 change log, is this true, in Tomcat 9.0.91 why response
>> headers are in Private mode instead of expiring Jan 1st 1970, shall I
>> adjust response headers to private mode, max-expires to 6000. How to handle
>> response headers in my Spring MVC application from expire mode to private,
>> even though I am using expires zero, whey it is ignoring, what tag I need
>> to use to get back to backward compatibility in my Spring MVC application
>> not caching from browsers, JAAS authetification validates User
>> Name/Password properly from Tomcat container. Please help me here when you
>> get a chance, your help here mostly appreciated.
>>
>> Best Regards
>> Venkat
>>
>> ________________________________
>> From:venkatdama@hotmail.com Shanthisowjanyadama9<ve...@hotmail.com>
>> Sent: Friday, July 26, 2024 1:45 AM
>> To:users@tomcat.apache.org <us...@tomcat.apache.org>
>> Subject: Tomcat 9.0.80 Server Issues.
>>
>> Hi Tomcat Uses group,
>>
>> My Java Spring MVC application works great with Tomcat 9.0.50, when I
>> moved Tomcat version from 9.0.50 to 9.0.80 my spring MVC java web
>> application was broken, JAAS authentication is not working as it expected,
>> all of a sudden chrome browser(s) caching web application and response
>> headers not expiring like before, I am looking for a workaround for this
>> issue here. I am also wondering why backward compatibility is not
>> maintained in Tomcat Server end when I switch from one version of Tomcat to
>> another version. Your help here is greatly appreciated.
>>
>> Best Regards
>> Venkat
>>
Re: Tomcat 9.0.80 Server Issues.
Posted by Dick Hildreth <di...@gmail.com>.
I'm running Tomcat 10.1 on OpenJDK JVM version 22.0.0+8-16, using hSQLdb
2.7.3 connected via commons-dbcp2-2.12.0 and commons-pool-2.12.0.
It works fine for a while, as previous versions of this combination had,
but after a relatively short time (unknown whether it's clock time or usage
instances), the database connection is lost. Restarting Tomcat is all
that's required to get everything working again.
Are there any suggestions as to what I might do?
Thanks,
Dick
On Fri, Jul 26, 2024 at 1:56 PM Venkat Dama <ve...@hotmail.com> wrote:
> Hi Tomcat Users Group,
>
>
> When I clear the browser cache in chrome browser and testing my web
> application using Tomcat 9.0.91 version by entering wrong password and
> right user name first it throws error properly which is correct, then
> second time when I enter correct user ID/Password it takes me into the web
> application correctly, here I am navigating different pages via
> tabs/buttons with in a application, one of the navigation causes to closes
> the application somehow (session not ended here) and takes me to the login
> screen, when I try to re-enter the same Username and Password as I entered
> second time (right user name/password) in the above scenario, application
> throws me j_security_check 404 page not found error, when I either remove
> j_security_check padding from the URL and click the refresh tab on the
> browser, application relaunches and works as it expected, other scenario is
> to clear the cache from the browser, close the browser, re-open the browser
> and re-launch the application by entering correct user name/password on
> login screen then everything works as it expected. This behavior does not
> happen in Tomcat server 9.0.50. Why I am seeing behavior changed and
> application is breaking only by switching Tomcat server version from 9.0.50
> to 9.0.91. Any help here is greatly appreciated to resolve the issue.
>
> Best Regards
> Venkat
>
> ________________________________
> From: Venkateswararao Dama <ve...@hotmail.com>
> Sent: Friday, July 26, 2024 12:06 PM
> To: users@tomcat.apache.org <us...@tomcat.apache.org>
> Subject: Re: Tomcat 9.0.80 Server Issues.
>
> Hi Tomcat Users Group,
>
> Even Tomcat 9.0.91 version with JDK 17 and application running on Windows
> 2022 server has same caching issues, in 9.0.91 version of Tomcat Callback
> handlers are working as it expected in JAAS authentication according to
> Tomcat 9.0.91 change log, is this true, in Tomcat 9.0.91 why response
> headers are in Private mode instead of expiring Jan 1st 1970, shall I
> adjust response headers to private mode, max-expires to 6000. How to handle
> response headers in my Spring MVC application from expire mode to private,
> even though I am using expires zero, whey it is ignoring, what tag I need
> to use to get back to backward compatibility in my Spring MVC application
> not caching from browsers, JAAS authetification validates User
> Name/Password properly from Tomcat container. Please help me here when you
> get a chance, your help here mostly appreciated.
>
> Best Regards
> Venkat
>
> ________________________________
> From: venkatdama@hotmail.com Shanthisowjanyadama9 <ve...@hotmail.com>
> Sent: Friday, July 26, 2024 1:45 AM
> To: users@tomcat.apache.org <us...@tomcat.apache.org>
> Subject: Tomcat 9.0.80 Server Issues.
>
> Hi Tomcat Uses group,
>
> My Java Spring MVC application works great with Tomcat 9.0.50, when I
> moved Tomcat version from 9.0.50 to 9.0.80 my spring MVC java web
> application was broken, JAAS authentication is not working as it expected,
> all of a sudden chrome browser(s) caching web application and response
> headers not expiring like before, I am looking for a workaround for this
> issue here. I am also wondering why backward compatibility is not
> maintained in Tomcat Server end when I switch from one version of Tomcat to
> another version. Your help here is greatly appreciated.
>
> Best Regards
> Venkat
>
Re: Tomcat 9.0.80 Server Issues.
Posted by Venkat Dama <ve...@hotmail.com>.
Hi Tomcat Users Group,
When I clear the browser cache in chrome browser and testing my web application using Tomcat 9.0.91 version by entering wrong password and right user name first it throws error properly which is correct, then second time when I enter correct user ID/Password it takes me into the web application correctly, here I am navigating different pages via tabs/buttons with in a application, one of the navigation causes to closes the application somehow (session not ended here) and takes me to the login screen, when I try to re-enter the same Username and Password as I entered second time (right user name/password) in the above scenario, application throws me j_security_check 404 page not found error, when I either remove j_security_check padding from the URL and click the refresh tab on the browser, application relaunches and works as it expected, other scenario is to clear the cache from the browser, close the browser, re-open the browser and re-launch the application by entering correct user name/password on login screen then everything works as it expected. This behavior does not happen in Tomcat server 9.0.50. Why I am seeing behavior changed and application is breaking only by switching Tomcat server version from 9.0.50 to 9.0.91. Any help here is greatly appreciated to resolve the issue.
Best Regards
Venkat
________________________________
From: Venkateswararao Dama <ve...@hotmail.com>
Sent: Friday, July 26, 2024 12:06 PM
To: users@tomcat.apache.org <us...@tomcat.apache.org>
Subject: Re: Tomcat 9.0.80 Server Issues.
Hi Tomcat Users Group,
Even Tomcat 9.0.91 version with JDK 17 and application running on Windows 2022 server has same caching issues, in 9.0.91 version of Tomcat Callback handlers are working as it expected in JAAS authentication according to Tomcat 9.0.91 change log, is this true, in Tomcat 9.0.91 why response headers are in Private mode instead of expiring Jan 1st 1970, shall I adjust response headers to private mode, max-expires to 6000. How to handle response headers in my Spring MVC application from expire mode to private, even though I am using expires zero, whey it is ignoring, what tag I need to use to get back to backward compatibility in my Spring MVC application not caching from browsers, JAAS authetification validates User Name/Password properly from Tomcat container. Please help me here when you get a chance, your help here mostly appreciated.
Best Regards
Venkat
________________________________
From: venkatdama@hotmail.com Shanthisowjanyadama9 <ve...@hotmail.com>
Sent: Friday, July 26, 2024 1:45 AM
To: users@tomcat.apache.org <us...@tomcat.apache.org>
Subject: Tomcat 9.0.80 Server Issues.
Hi Tomcat Uses group,
My Java Spring MVC application works great with Tomcat 9.0.50, when I moved Tomcat version from 9.0.50 to 9.0.80 my spring MVC java web application was broken, JAAS authentication is not working as it expected, all of a sudden chrome browser(s) caching web application and response headers not expiring like before, I am looking for a workaround for this issue here. I am also wondering why backward compatibility is not maintained in Tomcat Server end when I switch from one version of Tomcat to another version. Your help here is greatly appreciated.
Best Regards
Venkat
Re: Tomcat 9.0.80 Server Issues.
Posted by Christopher Schultz <ch...@christopherschultz.net>.
Venkat,
On 7/26/24 08:06, Venkateswararao Dama wrote:
> Even Tomcat 9.0.91 version with JDK 17 and application running on
> Windows 2022 server has same caching issues
Okay.
> in 9.0.91 version of Tomcat Callback handlers are working as it
> expected in JAAS authentication according to Tomcat 9.0.91 change
> log, is this true
Is that a question or a statement? Are you saying that JAAS *is*
working, or *is not* working?
> in Tomcat 9.0.91 why response headers are in Private mode instead of
> expiring Jan 1st 1970, shall I adjust response headers to private
> mode, max-expires to 6000.
Is this related to JAAS, or unrelated? It's best to handle one issue at
a time. So if the HTTP response headers are the biggest problem for you,
let's start there. If something else is more important, let's deal with
that, first.
So what's your biggest issue?
> How to handle response headers in my Spring MVC application from
> expire mode to private, even though I am using expires zero, whey it
> is ignoring, what tag I need to use to get back to backward
> compatibility in my Spring MVC application not caching from browsers,
> JAAS authetification validates User Name/Password properly from
> Tomcat container. Please help me here when you get a chance, your
> help here mostly appreciated.
What behavior are you expecting (specifically)? What behavior are you
seeing?
What other differences do you have between your working environment and
your non-working environment?
For example, if you are using TLS in your working production environment
but your non-working testing environment has no TLS, that's important
information to have.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 9.0.80 Server Issues.
Posted by Venkateswararao Dama <ve...@hotmail.com>.
Hi Tomcat Users Group,
Even Tomcat 9.0.91 version with JDK 17 and application running on Windows 2022 server has same caching issues, in 9.0.91 version of Tomcat Callback handlers are working as it expected in JAAS authentication according to Tomcat 9.0.91 change log, is this true, in Tomcat 9.0.91 why response headers are in Private mode instead of expiring Jan 1st 1970, shall I adjust response headers to private mode, max-expires to 6000. How to handle response headers in my Spring MVC application from expire mode to private, even though I am using expires zero, whey it is ignoring, what tag I need to use to get back to backward compatibility in my Spring MVC application not caching from browsers, JAAS authetification validates User Name/Password properly from Tomcat container. Please help me here when you get a chance, your help here mostly appreciated.
Best Regards
Venkat
________________________________
From: venkatdama@hotmail.com Shanthisowjanyadama9 <ve...@hotmail.com>
Sent: Friday, July 26, 2024 1:45 AM
To: users@tomcat.apache.org <us...@tomcat.apache.org>
Subject: Tomcat 9.0.80 Server Issues.
Hi Tomcat Uses group,
My Java Spring MVC application works great with Tomcat 9.0.50, when I moved Tomcat version from 9.0.50 to 9.0.80 my spring MVC java web application was broken, JAAS authentication is not working as it expected, all of a sudden chrome browser(s) caching web application and response headers not expiring like before, I am looking for a workaround for this issue here. I am also wondering why backward compatibility is not maintained in Tomcat Server end when I switch from one version of Tomcat to another version. Your help here is greatly appreciated.
Best Regards
Venkat