Error when trying to upload package using maven build

[rajeev_yadav]

I am getting below error when trying to install package using maven build. Sometime install works fine while many a time it fails with below error.

            <div id="Status">200</div>

</td>

        </tr>

        <tr>

<td>Message</td>

<td>

            <div id="Message">OK</div>

</td>

        </tr>

        <tr>

<td>Location</td>

<td>

            <a href="https://forums.adobe.com/crx/packmgr/service.jsp" id="Location">/crx/packmgr/service.jsp</a>

</td>

        </tr>

        <tr>

<td>Parent Location</td>

<td>

            <a href="https://forums.adobe.com/crx/packmgr" id="ParentLocation">/crx/packmgr</a>

          </td>

        </tr>

        <tr>

<td>Path</td>

<td>

            <div id="Path">/crx/packmgr/service.jsp</div>

</td>

        </tr>

        <tr>

<td>Referer</td>

<td>

            <div id="Referer">about:blank</div>

</td>

        </tr>

        <tr>

<td>ChangeLog</td>

<td>

            <div id="ChangeLog">&lt;pre&gt;modified(&quot;/crx/packmgr/service.jsp/file/jcr:lastModified&quot;);&lt;br/&gt;modified(&quot;/crx/packmgr/service.jsp/file/jcr:mimeType&quot;);&lt;br/&gt;modified(&quot;/crx/packmgr/service.jsp/file/jcr:data&quot;);&lt;br/&gt;modified(&quot;/crx/packmgr/service.jsp/install&quot;);&lt;br/&gt;&lt;/pre&gt;</div>

</td>

        </tr>

</tbody>

    </table>

    <p>

      <a href="https://forums.adobe.com/crx/packmgr/service.jsp">Modified Resource</a>

    </p>

    <p>

      <a href="https://forums.adobe.com/crx/packmgr">Parent of Modified Resource</a>

    </p>

  </body>

</html>

[Ratna_Kumar]

Hi Rajeev,

May I know which command you are trying to use.

Are you using mvn -PautoInstallPackage install command to install/uploading the package?

Thanks,

Ratna Kumar.

[smacdonald2008]

In addition to Ratna answer - consult with How to Build AEM Projects using Apache Maven

[rajeev_yadav]

I am using Jenkins to build the code. I am using clean install goal. Packages are built fine but issue seems to be happening when installing the package on AEM. Sometimes it works and sometimes it fails.

[smacdonald2008]

Try to use only Maven - mvn -PautoInstallPackage install -- that works everytime

[rajeev_yadav]

Will -PautoInstallPackage work even if I have not defined this profile for my jenkins build? I  don't think it will but let me give a try.

[Ratna_Kumar]

Hi Rajeev,

Please try following this article, AEM continuous integration with Jenkins: Experiencing Adobe Experience Manager - Day CQ: AEM - Continuous Integration with Jenkins

Here it explains step to step, in Jenkins, specify the relative path of pom.xml; the goal autoInstallPackage builds, installs packages to provided CQ instance.

Hope this helps!!

Thanks,

Ratna Kumar.

[rajeev_yadav]

Hi Ratna,

Here I don't think it is the issue with jenkins setup as sometimes packages are getting installed and in next job runs getting the error. I am not sure if the previous package uploads sometimes triggers the package manager service restart and by the time next module package is getting installed, service is still down.. I am just guessing as this issues happens from 2nd module onwards.. I tried to setting timeout in package content plugin to 10 mins still it is not fixing the issue... Same error now and then..

Thanks,
Rajeev

[Jörg_Hoh]

The output you get is the standard output format of the Sling Post Servlet. That means that your post is not handled by the package manager, but instead by the Sling Post Servlet.

This has 2 consequences:

* The package is not being installed

* You have now a node in the repository at /crx/packmgr/index.jsp

The only way to handle this is to check before you do the POST that the package manager is available and responsive.

Jörg

[rajeev_yadav]

Hi Jorg,

I am using content package plugin in mvn to install the package. If this is being handled by sling post servlet, how can we check the availability of package manager in mvn script before post servlet tries to install.

[Jörg_Hoh · Accepted solution]

With maven ... probably not that easy. You might want to follow [1] for bundles; for content-packages you can either raise a Daycare ticket; and/or post a comment to the maven archetype you use and raise attention to your problem. I am sure that others are affected as well.

Jörg

[1] [SLING-7562] Installing a bundle should check for successful deployment - ASF JIRA