In the previous post I have explained on how to fix the “bind exception” that occurred because we are trying to run an application on the same port that other application is running and advised to move the configuration section for listeners/requests to Domain project if the other application is also a Mule application.

After moving the configuration section for listeners/requests to a Domain project and when everything was running fine, one bad day you see the following exception:

RROR 2016-09-05 22:33:10,371 [main] org.mule.module.launcher.DefaultArchiveDeployer: 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Failed to deploy artifact 'anotherapp', see below        +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
org.mule.module.launcher.DeploymentInitException: NoSuchBeanDefinitionException: No bean named 'HTTP_Listener_Configuration' is defined
	at org.mule.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:205) ~[mule-module-launcher-3.8.0.jar:3.8.0]
	at org.mule.module.launcher.artifact.ArtifactWrapper$2.execute(ArtifactWrapper.java:63) ~[mule-module-launcher-3.8.0.jar:3.8.0]
	at org.mule.module.launcher.artifact.ArtifactWrapper.executeWithinArtifactClassLoader(ArtifactWrapper.java:136) ~[mule-module-launcher-3.8.0.jar:3.8.
0]

If you ever see the exception saying “No bean named ‘HTTP_Listener_Configuration’ is defined” and if http configuration is defined the Domain project, first do not blame your application. It is not your application’s fault. You may have to verify if the Domain project is deployed or not. If it is not deployed, then the culprit is the Domain project.

Action: Since the error is related to HTTP Listener, check if any other application is running on the same port that the listener is configured to run. Sort out the issue either by stopping the other application or changing the port in the listener configuration.