On 3/25/2018 3:15 AM, Olaf Kock wrote:
* 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
Thank you for your response!
I know that the Tomcat version is basically ours to use or replace.
Upgrading Tomcat may be perfectly safe for Liferay itself, but we cannot
be sure that it is completely safe for the applications we've written
using Liferay.
Qualifying an upgrade of a major component is a very slow and
time-consuming process. It's only been fairly recently that we have
concluded the problem MIGHT be in Tomcat. So we have not been pursuing
an upgrade. Before I start that process, I want to determine whether
our problem is caused by configuration or a bug. I always assume
configuration first. And if it is a bug, I always assume it's OUR
software that has the bug, because open source projects are quite good
at killing bugs early in a version's lifetime.
Part of the challenge is that this has only become my responsibility
recently, so I'm not completely up to speed on how everything is done.
We've had key personnel find their dream jobs and move on.
Many of our sites are still using Liferay 6.1. The customers on those
platforms are so risk-averse that they haven't allowed us to migrate
them to 6.2 yet. We want to get everything upgraded to the latest
Liferay version, but the upgrade from 6.1 to 6.2 was very challenging.
We expect an upgrade to 7.x to be more difficult.
I'm here because I need help with the configuration. I can't seem to
get a straight answer as to precisely how we SHOULD configure the pools,
and whether the Tomcat version we are using is capable of handling the
configuration. I know that the configuration we have does not seem to
actually be working. I do not know whether that's because the
configuration is wrong, or if there's another problem. I am working on
a new configuration that I want to try, but the system doesn't work when
we try to use that config. I'm waiting for permission to try the change
myself so I can have concrete information about what's happening.
If somebody can give me evidence to assure me that upgrading Tomcat and
using configuration X will solve the problem, then I will pursue that.
I can't justify an upgrade because it MIGHT fix the problem.
* 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.
We are using Liferay's configuration in portal-ext.properties for the
Liferay database. The pools configured in tomcat are used for our
application, not Liferay itself. The only complaint I have about
Liferay's pool is that it seems to use more connections than I think
should be necessary. But it IS re-using the pool (all connections are
idle less than one minute), so it's not on my radar at the moment. The
connections in the tomcat pools are NOT being re-used like I expect them to.
Can I configure additional pools in portal-ext.properties for our
application to use? If so, is that recommended? That will probably
require code changes, but if it solves our difficulties, I'm not opposed
to it. We already need to touch all of that code anyway to adjust how
we're closing JDBC resources. Maybe we should find a new way to handle
connection pooling.
* It might help looking at the pool/connection states through JMX, so
that you can determine which pool is active on which size.
Does JMX work for pools other than the one for Liferay? As soon as I
can work out exactly where to add the remote JMX properties, I can give
that a try. If it's easy for you to tell me best practices for
adjusting the java commandline for startup, please do.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
