Pavon,
On 11/13/25 3:01 AM, Mark Thomas wrote:
On 11/11/2025 20:35, Paymon wrote:
hello,
we seem to be having problem with some deployed apps. they stop
running and
server returns 404 for that app. we are trying to get the status of
each app
from `manager/status/all?JSON=true` endpoint.
i wrote a little script for that, returned json seems to list deployed
apps in
an array under tomcat.context.
problem is i don't know, and i can't tell from the docs, if this is
the list of
all apps, or just the ones "running"?
same with `manager/text/list`; it does list the apps but in the
examples in the
doc it never show the case where one of the apps has failed. they're
all marked
'running'
what should i excpect to see when an app has failed to run?
It isn't hard to test this yourself. Just create a directory under
webapps and add a META-INF/context.xml file with invalid content. Then
see what the Manager app shows you.
http://localhost:8080/manager/text/list
OK - Listed applications for virtual host [localhost]
/:running:0:ROOT
/examples:running:0:examples
/host-manager:running:0:host-manager
/test:stopped:0:test
/manager:running:0:manager
/docs:running:0:docs
http://localhost:8080/manager/status/all?JSON=true
Hmm. Invalid JSON. Looks like we have a bug. I'll take a look.
When an application does not start up properly, Tomcat uses an instance
of FailedContext to hold all of the JMX information about it.
It looks like this class is missing a handful of methods required to
support the manager's status.
It should be fixed in the next set of releases.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
