Computing Magazine

Domain Not Available Error Cloudhub Redeployment Issue

Posted on the 02 August 2017 by Abhishek Somani @somaniabhi
While deploying an application which was deployed successfully to Cloudhub previously using maven, I got the following error :

[INFO] Deploying application MyApp-dev to Cloudhub
[ERROR] Domain MyApp-dev is not available. Aborting.
[ERROR] Failed to deploy MyApp-dev: Domain MyApp-dev is not available. Aborting.
org.mule.tools.maven.plugin.mule.DeploymentException: Domain MyApp-dev is not available. Aborting.
at org.mule.tools.maven.plugin.mule.cloudhub.CloudhubDeployer.deploy(CloudhubDeployer.java:89)
at org.mule.tools.maven.plugin.mule.DeployMojo.deployWithDeployer(DeployMojo.java:216)
at org.mule.tools.maven.plugin.mule.DeployMojo.cloudhub(DeployMojo.java:193)
at org.mule.tools.maven.plugin.mule.DeployMojo.doExecute(DeployMojo.java:179)
at org.mule.tools.maven.plugin.mule.AbstractMuleMojo.execute(AbstractMuleMojo.java:176)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
This error comes only when the application already exists in Cloudhub. Ideally, it should just update the existing application in Cloudhub. To rectify this error, you need to make sure that your application name in your pom file contains only lower case letters, because of a possible bug.

<applicationName>MyApp-${cloudHubAppSuffix}</applicationName>
So, the application name should be changed to :

<applicationName>myapp-${cloudHubAppSuffix}</applicationName>
Post Comments And Suggestions !!!

Back to Featured Articles on Logo Paperblog