Mssrs. Kolinko and Schultz said:
2. The stack trace starts with "Bootstrap.main". I.e. it is the thread
that starts Tomcat.
I.e. this occurs when Tomcat starts up and has nothing to do with your
attempt to access the Manager web application.
3. The stack trace contains "org.apache.crimson".
Apache Crimson project was retired 11 years ago and should not be used
nowadays.
https://xml.apache.org/crimson/
https://attic.apache.org/projects/crimson.html
You have that library in Tomcat classpath? Where? Why?
Good catch.
The JVM has been bundled with a SAX parser for ages, now. You might ask
your application/engineering team if it's okay to try your application
without a bundled XML library.
You might also ask why it's being put into CATALINA_BASE/lib (or
endorsed-libs?) instead of in the application's WEB-INF/lib where it
belongs.
A bit more information:
Our application isn't even *installed* in the new Tomcat yet. As I said,
the *only* context currently in Webapps is manager; everything else was
stripped out, including the default ROOT, shortly after I unpacked the
Tomcat 8.5.68 ZIP file on the box.
Tomcat 7.0.93 continues to run just fine, under the same Java 8, after I
swapped it back in (and I'm definitely glad I do updates in a way that
makes that easy).
Last night, I was a bit lax in proofreading my initial post, and somehow
some critical information got left out.
The stacktrace included in the post was, of course, from the launch
process.
When I attempt to connect to manager, I get a "500-Internal Server
Error" page, that has a few stacktraces of its own (but adds nothing to
Catalina.out). Alas, I didn't save a copy of the error page, and it
could be several hours before I can swap the 8.5.68 back in and take
down the details.
Jon McAlexander suggested a possible bad JVM; while I wonder how that
could be, given that Tomcat 7.0.98 runs just fine, I will note that this
particular box is on a slightly different Java 8 JVM from what we see on
other customer boxes where we already have 8.5.6x running, and I think
we've already asked them to check on whether their Java PTFs (analogous
to what M$ calls "service packs") are current. The Tomcat 7 manager
reports their JVM version as "8.0.5.20 - pap6480sr5fp20-20180802_01(SR5
FP20)"
I just checked the Catalina.out of another customer we have on 8.5.68.
Nothing at all between
06-Jul-2021 19:11:49.841 INFO [main]
org.apache.catalina.startup.Catalina.load Initialization processed in
3303 ms
and
06-Jul-2021 19:11:49.905 INFO [main]
org.apache.catalina.core.StandardService.startInternal Starting service
[Catalina]
Is there any other information I could gather, without having to switch
the customer's Tomcat 8 live?
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org