Hi all,
The version details :
Using CATALINA_BASE: /apps/TOMCAT/tomcat
Using CATALINA_HOME: /apps/TOMCAT/tomcat
Using CATALINA_TMPDIR: /apps/TOMCAT/tomcat/temp
Using JRE_HOME:/usr
Using CLASSPATH:
/apps/TOMCAT/tomcat/bin/bootstrap.jar:/apps/TOMCAT/t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
Given the reasonably encouraging response to Tomcat's YouTube
channel[1] and that fact that many people can't make it to the various
ASF conferences[2] held annually, some members of the community have
decided to resume our short webinar series
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 9/14/16 7:04 PM, André Warnier (tomcat) wrote:
> Mary, have a look here :
> http://tomcat.apache.org/whichversion.html Tomcat 5.5 was first
> released about 10 years ago, and the last modification to it was in
> 2012. The current "stable"
Hi.
I do not understand what happens with query paramers and URI encoding in
Tomcat 8.5.5.
On client side, the query is :
https://localhost:8447/adele_admin/ldapapi/personnes?mot=P%C3%A9net
Where "Pénet" is, as far as I understand, correctly encoded.
On server side, the Connector-s all have
Hello,
I'd rather narrow down the problem a bit more before upgrading (to make
sure that that's the issue).
It happened again, this time I took a thread dump of the instance that went
down (actually, it's only the DB connection pool that becomes unresponsive
but I remove the instance from my load
