response=Gateway Timeout issue while running -PautoinstallPackage

ramaem12

12-08-2020

I am running below command to deploy my code package in aem instance 4502(which is up and running)

 

mvn clean install -PautoInstallPackage

 

but i am getting below error, any idea why it is happening?

[ERROR] Request to http://localhost:4502/crx/packmgr/service.jsp failed, response=Gateway Timeout

 

FYI- when i run mvn clean install it is showing success and i manually deployed in 4502 instance.

AEM version - 6.5.5

6.5 deployment maven

Accepted Solutions (1)

Accepted Solutions (1)

Answers (4)

Answers (4)

ChitraMadan

MVP

12-08-2020

Hi @ramaem12 ,

 

Can you please try to add <useProxy>false</useProxy> in the content package plugin

 

<!-- -->
<!-- V A U L T P A C K A G E P L U G I N -->
<!-- -->
<plugin>
<groupId>com.day.jcr.vault</groupId>
<artifactId>content-package-maven-plugin</artifactId>
<extensions>true</extensions>
<version>1.0.2</version>
<inherited>true</inherited>
<configuration>
<verbose>false</verbose>
<failOnError>true</failOnError>
<userId>${cq.username}</userId>
<password>${cq.password}</password>
<timeout>10</timeout>
<useProxy>false</useProxy>
</configuration>
</plugin>

Jörg_Hoh

Employee

13-08-2020

When you use the maven profile to deploy, do you see anything in the AEM logfile (error.log) which looks like that the package installation is running?

berliant

Employee

12-08-2020

A project root pom.xml file includes a connection properties

<properties>

        <aem.host>localhost</aem.host>

        <aem.port>4502</aem.port>

        <aem.publish.host>localhost</aem.publish.host>

        <aem.publish.port>4503</aem.publish.port>

        <sling.user>admin</sling.user>

        <sling.password>admin</sling.password>

        <vault.user>admin</vault.user>

        <vault.password>admin</vault.password>

 

Make sure, that your host, port, user, and password are properly defined.

Vaibhavi

MVP

12-08-2020

Hi @ramaem12 , 

Looks like server is not responding when you try to deploy snapshot. 

This could be a problem with snapshot as well. 

Can you please have a look at logs?