In a standalone application the Actuator HTTP port defaults to the same as the main HTTP
port. To make the application listen on a different port set the external property
management.port. To listen on a completely different network address (e.g. if you have
an internal network for management and an external one for user applications) you can
management.address to a valid IP address that the server is able to bind to.
For more detail look at the
source code and
Section 50.2, “Customizing the management server port”
in the ‘Production-ready features’ section.
Spring Boot installs a ‘whitelabel’ error page that you will see in browser client if you encounter a server error (machine clients consuming JSON and other media types should see a sensible response with the right error code).
Overriding the error page with your own depends on the templating technology that you are
using. For example, if you are using Thymeleaf you would add an
error.html template and
if you are using FreeMarker you would add an
error.ftl template. In general what you
need is a
View that resolves with a name of
error, and/or a
@Controller that handles
/error path. Unless you replaced some of the default configuration you should find
BeanNameViewResolver in your
ApplicationContext so a
@Bean with id
be a simple way of doing that. Look at
ErrorMvcAutoConfiguration for more options.
See also the section on Error Handling for details of how to register handlers in the servlet container.
Actuator HTTP endpoints are only available for Spring MVC-based applications. If you want
to use Jersey and still use the actuator you will need to enable Spring MVC (by depending
spring-boot-starter-web, for example). By default, both Jersey and the Spring MVC
dispatcher servlet are mapped to the same path (
/). You will need to change the path for
one of them (by configuring
server.servlet.path for Spring MVC or
spring.jersey.application-path for Jersey). For example, if you add
application.properties, the actuator HTTP endpoints
will be available under