Darious,
On 10/24/22 04:10, Strib wrote:
Due to the security echelon of the network, I can not send the entire
stacktrace.
However, I can say that it also states the web app archives are not
starting. (IllegalStateException: Error starting child).
Prominent "caused by" lines state bean creation errors, or instantiating
[org.grails.orm.hibernate.HibernateDatastore]: Constructor threw exception;
nested exception is
org.hibernate.tool.schema.extract.spi.SchemaExtractionException...
This could be almost anything.
Tomcat does not package Hibernate, so this is something your application
is trying to do. Maybe there is an error extracting a schema or something?
If you can't share the stack trace with this community, than this
community will be unable to help you. You will have to get help from
internal corporate resources.
-chris
On Mon, Oct 24, 2022 at 4:31 PM Mark Thomas <ma...@apache.org> wrote:
On 24/10/2022 08:01, Strib wrote:
Hello and thank you,
The error message reads as follows:
'org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/APPWARFILE]]'
And the rest of that message? What does the stack trace show?
There may also be earlier errors in the logs that are relevant.
Mark
There are two app files trying to start, and both are getting the same
error. The weird part is, these app packages were not touched since
before
the summer. Server patches have happened since, but this is the first
month
where Tomcat is doing this So, two key notes:
1: app packages have not been changed.
2: hot and warm servers have been patched, but only hot servers received
this Tomcat error. This is the first month I've seen Tomcat not start
properly, which makes me believe it's Tomcat.
Also, just FYI, this is for Tomcat 8.
Very respectfully,
Darious
On Mon, Oct 24, 2022 at 3:28 PM Thomas Hoffmann (Speed4Trade GmbH)
<thomas.hoffm...@speed4trade.com.invalid> wrote:
Hello,
-----Ursprüngliche Nachricht-----
Von: Strib <darious.stribl...@gmail.com>
Gesendet: Montag, 24. Oktober 2022 08:10
An: users@tomcat.apache.org
Betreff: Apache Tomcat started, but error 404
Hello, trying to see if anyone else had this issue. After a reboot of
hot and
warm servers, my sites using Tomcat throws the error 404 only on the
hot
servers. I've stopped and started Tomcat services, nothing. In the
logs,
there
were 2 errors. One was Catalina. But even though the error happened on
hot
and warm servers, warm sites are still working, so I'm thinking that's
not it. The
other error on the hot servers says startup error. Is it just luck of
the draw, of
starting/stopping Tomcat services?
Is it something else, entirely? Frustrating that Tomcat does not have a
UI to
make this easier. Thanks in advance.
Very respectfully,
Darious
Could you past the error message about startup issue?
404 sounds like your application failed to start but Tomcat is running.
So it might be an issue with the application.
In the log files there are usually information about the reason.
Greetings, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
