Maven build failure: Socket write error | Community
Skip to main content
T
tahir1601
New Participant
July 6, 2019
Solved

Maven build failure: Socket write error

  • July 6, 2019
  • 5 replies
  • 6542 views

Hi All,

I am getting below error when trying to deploy.(mvn clean install -PautoInstallBundle)

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time:  17.688 s

[INFO] Finished at: 2019-07-06T11:03:18+05:30

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.sling:maven-sling-plugin:2.2.0:install (install-bundle) on project jacobdelafon.core: Installation on http://localhost:4502/system/console/apps/kohler/jacobdelafon/install/ failed, cause: Software caused connection abort: socket write error -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.sling:maven-sling-plugin:2.2.0:install (install-bundle) on project jacobdelafon.core: Installation on http://localhost:4502/system/console/apps/kohler/jacobdelafon/install/ failed, cause: Software caused connection abort: socket write error

Can Someone tell what could the issue be??

smacdonald2008​Arun Patidar​Joerg Hoh​@

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by tahir1601

    Ive got the soultion for this
    in pom.xml i replaced below lines

    <slingUrl>http://${aem.host}:${aem.port}/system/console</slingUrl>

    <deploymentMethod>WebConsole</deploymentMethod>

    with below

    <slingUrl>http://${aem.host}:${aem.port}/crx/repository/crx.default</slingUrl>

    <deploymentMethod>WebDAV</deploymentMethod>

    Not sure how this worked. Let me know technical reason behind this

    5 replies

    T
    tahir1601Author
    New Participant
    July 11, 2019

    Nope. I made above changes in pom and it worked.

    joerghoh
    joerghoh
    Employee
    July 6, 2019

    Have you tried it again? Have you re-started your AEM instance?

    T
    tahir1601AuthorAccepted solution
    New Participant
    July 6, 2019

    Ive got the soultion for this
    in pom.xml i replaced below lines

    <slingUrl>http://${aem.host}:${aem.port}/system/console</slingUrl>

    <deploymentMethod>WebConsole</deploymentMethod>

    with below

    <slingUrl>http://${aem.host}:${aem.port}/crx/repository/crx.default</slingUrl>

    <deploymentMethod>WebDAV</deploymentMethod>

    Not sure how this worked. Let me know technical reason behind this

    anujg3325839
    anujg3325839
    Employee
    July 6, 2019

    The path is seems incorrect,  you need check the pom.xml file for the server settings. you can find the details [1]

    if you are trying to deploy directly provided .jar file , in system console. you need to treat it as simple package and put in maven project and follow standard installation approach.

    [1] How to Build AEM Projects using Apache Maven

      Nirmal_Jose
      Nirmal_Jose
      Employee
      July 6, 2019

      Hi,

      Can you check you have 'install' folder in /apps/kohler/jacobdelafon/ path. If not, please go to crxde and create one and try again.

      The path you mentioned seems a wrong one too - It should be just http://localhost:4502/apps/kohler/jacobdelafon/install/

      Did you create the project using maven archetype ?

        Terms & ConditionsAccessibility statement

        Loading footer...