You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "James H. H. Lampert" <ja...@touchtonecorp.com> on 2017/01/31 19:47:30 UTC
Question about catalina.out log entries, particularly from VersionLoggerListener
We're comparing a number of Tomcat installations at various customers,
trying to figure out why some of them are slow for no apparent reason.
We've started comparing the "JVM Version" entry in catalina.out, entries
on the order of:
> May 26, 2015 12:21:21 PM org.apache.catalina.startup.VersionLoggerListener log
> INFO: Java Home: /QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre
> May 26, 2015 12:21:21 PM org.apache.catalina.startup.VersionLoggerListener log
> INFO: JVM Version: jvmap3260sr16fp2-20141026_01
> May 26, 2015 12:21:21 PM org.apache.catalina.startup.VersionLoggerListener log
Java Home is fairly explicit, since it matches the known path to where
the JVM lives.
But what about the "JVM Version" entry?
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Question about catalina.out log entries, particularly from
VersionLoggerListener
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
James,
On 1/31/17 8:48 PM, James H. H. Lampert wrote:
> On 1/31/17, 2:32 PM, Christopher Schultz wrote:
>>> But what about the "JVM Version" entry?
>>
>> That comes directly from the "java.runtime.version" system
>> property, which I believe is read-only. (At least, you can't
>> override it when launching the JVM by providing a value for that
>> property using - -Djava.runtime.version=foobar). So that string
>> is coming from your JVM. It's opaque to Tomcat.
> . . .
>> If you do a "java -version" from the command-line, you'll
>> probably see that string in there, similar to what is shown on
>> this page:
>
> Thanks. That answered it.
>
> One other thing: I notice that in a couple of those customer
> installations, I'm not getting the "VersionLoggerListener" messages
> at all. Is that from some logging level setting?
I can think of a few reasons why those lines might not be in the log:
1. Log level set to higher than INFO
2. VersionLoggerListener is not enabled in server.xml
3. Tomcat version is old enough that VLL isn't included
I suspect it's #2, and that the server.xml configuration pre-dates the
addition of VLL to Tomcat, and nobody ever noticed that it was
available and not configured.
If your customers are anything like me, I don't do a diff on my
server.xml against the stock server.xml unless I'm switching between
major versions of Tomcat. So it would be easy to overlook the addition
of the VersionLoggerListener, which was added to a point-release at
some point to both Tomcat 7 and 8.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJYkffTAAoJEBzwKT+lPKRYZQAQALBz3fqpV4dybdFZsSqA4o3N
FxuQHy9W2OCukAfFqUbCyD13ivfhTOWoX8qjp4DaEIjPhTHP9FXBDB6KhFra/95S
4huU0sC1ilaG2Lw5c8aguvf//hCYet8hGXg5sw64zv+mYBFqlW8YrdsllyUt8LvU
vvchUMioi4r1bVoDwH7/RlFoRSFdVKKw7BCNRLnwhDkNnMRXf72pFWvbZnhJIe21
Z1jQAmGFVKA+k9IxdGgPWZuMvd6dkT2+Z8im6Lj+6/NGm5kHZBkxf0tpUE56dSLl
bQZtyregC2HMD+cCofoFo4WVJFFEy3Yf6Flb+MQHUJ4SOOcqBX4WUS2OD8evkwY5
eMfVoEZQbchm9CLUY2BEcDs/le/TSiL1jBsY8fC2lirOAw09EDrHFjl23HDHr4pS
tb7m1ChEd8sgstEYwMw8hH68aYPUkVafH+XAHbz4ofWqVkpOPqEOGl0wxMXV25bU
73iBe+K5Z66Xbs7zCkYvxPaeEGluY1tcvDMhhKSoEqZu6Rlagwc8eJ8LPQqrritX
3quIuSjU9yXLphWWjf9UF4PfUrGDpwf/VpDZOmogPoOtcFiNP7tHYGw2TptIHt+M
NVKcz2+fr4QpXLv4fJq7N4XeZrRS1VUGnBvgtYaxYegjZccMEkAccT+5HW3wYz5H
tFzRJMq+CDGvielyn5sa
=wVRH
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Question about catalina.out log entries, particularly from VersionLoggerListener
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com>.
On 1/31/17, 2:32 PM, Christopher Schultz wrote:
>> But what about the "JVM Version" entry?
>
> That comes directly from the "java.runtime.version" system property,
> which I believe is read-only. (At least, you can't override it when
> launching the JVM by providing a value for that property using
> - -Djava.runtime.version=foobar). So that string is coming from your
> JVM. It's opaque to Tomcat.
. . .
> If you do a "java -version" from the command-line, you'll probably see
> that string in there, similar to what is shown on this page:
Thanks. That answered it.
One other thing: I notice that in a couple of those customer
installations, I'm not getting the "VersionLoggerListener" messages at
all. Is that from some logging level setting?
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Question about catalina.out log entries, particularly from
VersionLoggerListener
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
James,
On 1/31/17 2:47 PM, James H. H. Lampert wrote:
> We're comparing a number of Tomcat installations at various
> customers, trying to figure out why some of them are slow for no
> apparent reason.
>
> We've started comparing the "JVM Version" entry in catalina.out,
> entries on the order of:
>
>> May 26, 2015 12:21:21 PM
>> org.apache.catalina.startup.VersionLoggerListener log INFO: Java
>> Home: /QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre May 26, 2015
>> 12:21:21 PM org.apache.catalina.startup.VersionLoggerListener
>> log INFO: JVM Version: jvmap3260sr16fp2-20141026_01 May
>> 26, 2015 12:21:21 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>
> Java Home is fairly explicit, since it matches the known path to
> where the JVM lives.
>
> But what about the "JVM Version" entry?
That comes directly from the "java.runtime.version" system property,
which I believe is read-only. (At least, you can't override it when
launching the JVM by providing a value for that property using
- -Djava.runtime.version=foobar). So that string is coming from your
JVM. It's opaque to Tomcat.
Here's the code:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/start
up/VersionLoggerListener.java?revision=1654159&view=markup#l103
If you do a "java -version" from the command-line, you'll probably see
that string in there, similar to what is shown on this page:
http://archive.midrange.com/midrange-l/201504/msg00568.html
(Searching Google for "jvmap3260sr16fp2-20141026_01" yields only 6
results. That's amazing.)
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJYkRCYAAoJEBzwKT+lPKRYc0UP/ihxQvahCXkPhvttmy+QzPKO
a2W48Ux69T153mpb0pquwOMPhPFmFu7pZWS8E13AGti3jxvncKkkqP6AP179aEzL
PqdW51dE4ud4DpTRxJ5894Pjb8lsCJG+ckNp1QGpsXYoAcVwbPwGdJ21eDGi2+Ii
VrRIJNcC63/2SCebkIygx/ijt/G5321WP/GPo4eaTo/WOcKqvV3uFZcg9HFWRPCq
KqqYsw9I/F9bVhIQj5fdsfBttqFjqVjL/zIX0pBsuQFI9fccQUuKJrYVuuIu0WyR
5IB9QOEgBsnBeEoYzHBbuUT7c9RR4i+PCv1SfHz1idbgDNI/sMkShvw4DiKCeDoD
WYEPIcjiIJH72lpOhJojlrX5jPzcE5ChK4OSzmWSZZqHTURm6HoBmyRuJDYaVfiG
lLL5cY/1vrdXNu6PYKtTm3EdmtQ6BYWxd7YNjC4HohisZokspCoYZWnolcTZqeVs
b/KONum3q3rHFihhia1XJRLbkNjEOacnLMO9r+KMSf2+ql9oqUUCGOr9VtxQDLzh
H/mPwozhPEuXUXME3TBAW/553vJRrR257AzGdFpdnxPfuM0Sg9zHUl3UFzTVBro3
glQOTRd18ibkla4Qm6PAVk4fPutnPYlQhuX/8CZn69G2QjNl6a5uKy6RibZEQ+nc
PQZymwHvV71gPA8kcCLl
=1S8h
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org