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<venkatd...@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<venkatd...@hotmail.com>
Sent: Friday, July 26, 2024 12:06 PM
To:users@tomcat.apache.org <users@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:venkatd...@hotmail.com Shanthisowjanyadama9<venkatd...@hotmail.com>
Sent: Friday, July 26, 2024 1:45 AM
To:users@tomcat.apache.org <users@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
