On 24.03.2018 05:08, Shawn Heisey wrote:
This message is long. Lots of details, a fair amount of history.
The primary Tomcat version we've got is 7.0.42. Specifically, it is
the Tomcat that's included with Liferay 6.2. This is why we haven't
attempted an upgrade even though the version we're running is five
years old -- we don't want to rock the boat too hard and risk
everything not working. Liferay is battle-tested with that version of
Tomcat.
other have answered on different pool implementations already, I'd like
to comment on the mentioned Liferay heritage:
* Liferay comes (optionally) bundled with Tomcat to ease installation,
however, the tomcat in there will be your own and is up to you to
upgrade. Yes, new versions of Liferay will come with new versions of
Tomcat, but new versions of Liferay won't be released because a new
version of Tomcat is available. Running on an old Tomcat is your
decision, not Liferay's. And the tomcat committers have done a great job
providing drop-in-backwards-compatible newer versions. Of course, you'll
need to validate, but the bundled version is no excuse to not upgrade Tomcat
* Liferay 6.2 (CE) is no longer maintained - there's no new tomcat
version expected for it
* Liferay's default configuration (as configured through the setup
wizard) configures the database with an internal connection, not using
an appserver-configured pool. Please confirm that you manually
configured Liferay for the appserver-provided pool.
* It might help looking at the pool/connection states through JMX, so
that you can determine which pool is active on which size.
Olaf
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
