Jelastic maven插件会在部署目标

时间:2017-07-30 08:31:38

标签: maven spring-boot jelastic

我使用jelastic来构建和部署具有许多类的spring-boot应用程序。 jelastic需要几分钟才能重新部署此应用程序。但是当插件执行后环境开始重新加载时 - 插件会引发网关超时。

以下是插件配置:

                <plugin>
                    <groupId>com.jelastic</groupId>
                    <artifactId>jelastic-maven-plugin</artifactId>
                    <version>${jelastic-maven-plugin.version}</version>
                    <executions>
                        <execution>
                            <phase>install</phase>
                            <goals>
                                <goal>deploy</goal>
                            </goals>
                        </execution>
                    </executions>
                    <configuration>
                        <email>${jelastic-maven-plugin.login}</email>
                        <password>${jelastic-maven-plugin.password}</password>
                        <context>${jelastic-maven-plugin.context}</context>
                        <environment>${jelastic-maven-plugin.environment-name}</environment>
                        <comment />
                        <api_hoster>${jelastic-maven-plugin.hoster-api}</api_hoster>
                    </configuration>
                </plugin>

这是来自控制台的日志(我从此跟踪中删除了文件URL,但我已经检查过 - 它是有效的):

[INFO] [94%]
[INFO] [95%]
[INFO] [96%]
[INFO] [97%]
[INFO] [98%]
[INFO] [99%]
[INFO] [100%]
[INFO]       File UpLoad : SUCCESS
[INFO]          File URL : http://{{host}}/xssu/rest/download/{{fileid}}
[INFO]         File size : 61768307
[INFO] ------------------------------------------------------------------------
[INFO] File registration : SUCCESS
[INFO]   Registration ID : 16518
[INFO]      Developer ID : 1431
[INFO] ------------------------------------------------------------------------
[ERROR] Gateway Time-out
org.apache.http.client.HttpResponseException: Gateway Time-out
    at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:67)
    at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:55)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:945)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:919)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:910)
    at com.jelastic.JelasticMojo.deploy(JelasticMojo.java:667)
    at com.jelastic.DeployMojo.execute(DeployMojo.java:40)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
    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:84)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
    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:290)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
    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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:18.859s
[INFO] Finished at: Sun Jul 30 11:26:03 MSK 2017
[INFO] Final Memory: 13M/309M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.jelastic:jelastic-maven-plugin:1.8.1:deploy (default-cli) on project dance-form: Execution default-cli of goal com.jelastic:jelastic-maven-plugin:1.8.1:deploy failed. NullPointerException -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException

我在控制台中检查了由于执行而重新加载了环境。 如何增加jelastic maven插件的超时时间?

0 个答案:

没有答案