Skip to main content

ApplicationFailedEvent code example

ApplicationFailedEvent executes when application is failed to start. For example if application port is already in use or any other error during start. We can use this event listener to email the error or executing any script upon failure. In this example we will try to run the application twice to generate the failed event.

SpringBootTutorialApplication

@SpringBootApplication
public class SpringBootTutorialApplication{

 public static void main(String[] args) {
  SpringApplication app = new SpringApplication(SpringBootTutorialApplication.class);
  
  //register ApplicationFailedEvent event
  app.addListeners((ApplicationFailedEvent event)->{
   System.out.println("Executing ApplicationFailedEvent...");
  });
  //start the application
  app.run(args);
 }
}

Try to run the application twice on the same port so in second attempt it will generate the error during start as one instance is already running on that port.

Output

Failed event execution statement is highlighted at the end of below output. 
2019-10-26 15:59:12.523 ERROR 13982 --- [           main] org.apache.catalina.util.LifecycleBase   : Failed to start component [Connector[HTTP/1.1-8080]]

org.apache.catalina.LifecycleException: Protocol handler start failed
 at org.apache.catalina.connector.Connector.startInternal(Connector.java:1008) ~[tomcat-embed-core-9.0.26.jar:9.0.26]
 at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ~[tomcat-embed-core-9.0.26.jar:9.0.26]
 at org.apache.catalina.core.StandardService.addConnector(StandardService.java:227) [tomcat-embed-core-9.0.26.jar:9.0.26]
 at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.addPreviouslyRemovedConnectors(TomcatWebServer.java:263) [spring-boot-2.1.9.RELEASE.jar:2.1.9.RELEASE]
 at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.start(TomcatWebServer.java:195) [spring-boot-2.1.9.RELEASE.jar:2.1.9.RELEASE]
 at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.startWebServer(ServletWebServerApplicationContext.java:297) [spring-boot-2.1.9.RELEASE.jar:2.1.9.RELEASE]
 at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:163) [spring-boot-2.1.9.RELEASE.jar:2.1.9.RELEASE]
 at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:552) [spring-context-5.1.10.RELEASE.jar:5.1.10.RELEASE]
 at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) [spring-boot-2.1.9.RELEASE.jar:2.1.9.RELEASE]
 at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:744) [spring-boot-2.1.9.RELEASE.jar:2.1.9.RELEASE]
 at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:391) [spring-boot-2.1.9.RELEASE.jar:2.1.9.RELEASE]
 at org.springframework.boot.SpringApplication.run(SpringApplication.java:312) [spring-boot-2.1.9.RELEASE.jar:2.1.9.RELEASE]
 at com.demo.SpringBootTutorialApplication.main(SpringBootTutorialApplication.java:57) [classes/:na]
Caused by: java.net.BindException: Address already in use
 at sun.nio.ch.Net.bind0(Native Method) ~[na:1.8.0_161]
 at sun.nio.ch.Net.bind(Net.java:433) ~[na:1.8.0_161]
 at sun.nio.ch.Net.bind(Net.java:425) ~[na:1.8.0_161]
 at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[na:1.8.0_161]
 at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[na:1.8.0_161]
 at org.apache.tomcat.util.net.NioEndpoint.initServerSocket(NioEndpoint.java:230) ~[tomcat-embed-core-9.0.26.jar:9.0.26]
 at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:213) ~[tomcat-embed-core-9.0.26.jar:9.0.26]
 at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1124) ~[tomcat-embed-core-9.0.26.jar:9.0.26]
 at org.apache.tomcat.util.net.AbstractEndpoint.start(AbstractEndpoint.java:1210) ~[tomcat-embed-core-9.0.26.jar:9.0.26]
 at org.apache.coyote.AbstractProtocol.start(AbstractProtocol.java:585) ~[tomcat-embed-core-9.0.26.jar:9.0.26]
 at org.apache.catalina.connector.Connector.startInternal(Connector.java:1005) ~[tomcat-embed-core-9.0.26.jar:9.0.26]
 ... 12 common frames omitted

2019-10-26 15:59:12.540  INFO 13982 --- [           main] o.apache.catalina.core.StandardService   : Stopping service [Tomcat]
2019-10-26 15:59:12.555  INFO 13982 --- [           main] ConditionEvaluationReportLoggingListener : 

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
Executing ApplicationFailedEvent...

Labels:

Comments

  1. Layne Harris28 September 2021 at 14:40

    Great article by the great author, it is very massive and informative but still preaches the way to sounds like that it has some beautiful thoughts described so I really appreciate this article. Best Event App service provider.

    ReplyDelete
    Replies
    1. de9 October 2026 at 13:40

      The ApplicationFailedEvent example demonstrates a useful Spring Boot mechanism for reacting when an application cannot complete its startup process. The port-conflict scenario makes the behavior easy to understand: when a second application instance attempts to bind to the same port, the startup fails and the registered listener executes, providing a clear place for failure-specific actions.

      This event-driven approach can be useful for operational tasks such as sending an alert, recording diagnostic information, or triggering a script when startup fails. A Spring Boot ReactJS Full Stack Online Course is relevant for developers learning how Spring Boot applications are initialized and how application lifecycle events can be incorporated into a broader REST-based application.

      Delete
    2. de9 October 2026 at 13:40

      The example also shows why application lifecycle events can be valuable for monitoring and deployment scenarios, where startup failures need to be detected without placing custom checks throughout the application code. A Spring Boot Angular Full Stack Online Course provides a related full-stack context for integrating Spring Boot services with Angular applications while handling backend application lifecycle concerns.

      Delete
  2. Unknown21 March 2022 at 13:29

    I will provide you with main features that your app for conferences should include, and our developers can give you some tips concerning ways to enrich your app and make it really competitive. But first things first. More info https://www.cleveroad.com/blog/mobile-app-for-conferences--guide-to-development

    ReplyDelete
  3. Anonymous27 July 2025 at 09:33

    A4649F4572
    kiralık hacker
    hacker arıyorum
    belek
    kadriye
    serik

    ReplyDelete
  4. Anonymous29 July 2026 at 03:38

    40E4DB48
    Çankırı
    Karaman
    Kastamonu
    Mardin
    Iğdır
    Trabzon
    MuÄŸla
    Antep
    Yozgat

    ReplyDelete
  5. Anonymous7 September 2026 at 05:42

    DAA9C791
    Karasu
    Ortaca
    Araban
    Akçay
    Buharkent
    Kalkan
    Aksu
    Serik
    Konak

    ReplyDelete
  6. Anonymous8 September 2026 at 04:35

    A3C68948
    Alpu
    Åžirinyer
    Hendek
    Bafra
    Yıldırım
    Erdek
    Karasu
    Kulu
    İçmeler

    ReplyDelete

Post a Comment

Popular Posts

Setting up kerberos in Mac OS X

Kerberos in MAC OS X Kerberos authentication allows the computers in same domain network to authenticate certain services with prompting the user for credentials. MAC OS X comes with Heimdal Kerberos which is an alternate implementation of the kerberos and uses LDAP as identity management database. Here we are going to learn how to setup a kerberos on MAC OS X which we will configure latter in our application. Installing Kerberos In MAC we can use Homebrew for installing any software package. Homebrew makes it very easy to install the kerberos by just executing a simple command as given below. brew install krb5 Once installation is complete, we need to set the below export commands in user's profile which will make the kerberos utility commands and compiler available to execute from anywhere. Open user's bash profile: vi ~/.bash_profile Add below lines: export PATH=/usr/local/opt/krb5/bin:$PATH export PATH=/usr/local/opt/krb5/sbin:$PATH export LDFLAGS=...
108 comments
Read more

jaxb2-maven-plugin to generate java code from XSD schema

In this tutorial I will show how to generate the Java source code from XSD schema. I will use jaxb2-maven-plugin to generate the code using XSD file which will be declared in pom.xml to make it part of build, so when maven build is executed it will generate the java code using XSD. Class generation can be controlled in plugin configuration. Maven changes (pom.xml) Include below plugin in your pom.xml. Here we have done some configuration under configuration section as given below. schemaDirectory : This is the directory where I keep my schema (XSD file). outputDirectory : This is the java source location where I want to generate the Java files. If it is not given then by default it will be generate inside target folder. clearOutputDir : If this property is true then it will generate the classes on each build otherwise it will generate only if output directory is empty. <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>jaxb2-maven-plugin</art...
89 comments
Read more

Multiple data source with Spring boot, batch and cloud task

Here we will see how we can configure different datasource for application and batch. By default, Spring batch stores the job details and execution details in database. If separate data source is not configured for spring batch then it will use the available data source in your application if configured and create batch related tables there. Which may be the unwanted burden on application database and we would like to configure separate database for spring batch. To overcome this situation we will configure the different datasource for spring batch using in-memory database, since we don't want to store batch job details permanently. Other thing is the configuration of  spring cloud task in case of multiple datasource and it must point to the same data source which is pointed by spring batch. In below sections, we will se how to configure application, batch and cloud task related data sources. Application Data Source Define the data source in application properties or yml con...
78 comments
Read more

SpringBoot - @ConditionalOnProperty example for conditional bean initialization

@ConditionalOnProperty annotation is used to check if specified property available in the environment or it matches some specific value so it can control the execution of some part of code like bean creation. It may be useful in many cases for example enable/disable service if specific property is available. Below are the attributes which can be used for property check. havingValue - Provide the value which need to check against specified property otherwise it will check that value should not be false. matchIfMissing - If true it will match the condition and execute the annotated code when property itself is not available in environment. name - Name of the property to be tested. If you want to test single property then you can directly put the property name as string like "property.name" and if you have multiple properties to test then you can put the names like {"prop.name1","prop.name2"} prefix - It can be use when you want to apply some prefix to ...
64 comments
Read more