AEM 6.3 server deployment connection refused | Community
Skip to main content
CT1012
CT1012
Level 4
September 6, 2017
Solved

AEM 6.3 server deployment connection refused

  • September 6, 2017
  • 9 replies
  • 6078 views

The new maven project is pointing to localhost and throwing the below connection refused error when tried to deploy on dev server. We are using Archetype 11.

08:28:28,157 INFO - Installing XXXX.ui.apps (D:\workspacePolCIB\root\Maven\Builds\AdobeCMS\Promotions\Publish_To_Author_Instance\ui.apps\target\XXXX.ui.apps-0.0.1-SNAPSHOT.zip) to http://localhost:4502/crx/packmgr/service.jsp

08:28:29,277 INFO - I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect

08:28:29,278 INFO - java.net.ConnectException: Connection refused: connect

08:28:29,278 INFO -     at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)

    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 joerghoh

    If you use the parameters on the maven commandline, they are just valid during this call; it's not a persistent call. If you are using this POM only to deploy to this instance, it might be easier to adapt the pom.xml file.

    Jörg

    9 replies

    smacdonald2008
    smacdonald2008
    Level 10
    September 6, 2017

    Does 10 work for you?

    I am going to try 11 today and see if it works for me.

      VeenaVikraman
      Community Advisor
      VeenaVikramanCommunity Advisor
      Community Advisor
      September 6, 2017

      Was this working before ? What I see from your error logs seems like you are trying to install to your localhost:4502 and it is not up and running and throwing a connection refused.

      08:28:28,157 INFO - Installing XXXX.ui.apps (D:\workspacePolCIB\root\Maven\Builds\AdobeCMS\Promotions\Publish_To_Author_Instance\ui.a pps\target\XXXX.ui.apps-0.0.1-SNAPSHOT.zip) to http://localhost:4502/crx/packmgr/service.jsp

      08:28:29,277 INFO - I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect

      08:28:29,278 INFO - java.net.ConnectException: Connection refused: connect

      08:28:29,278 INFO -    at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)

      Are you sure your autoInstallPackage profile is pointing to the correct server.     

      How to Build AEM Projects using Apache Maven - docs.adobe.com

        CT1012
        CT1012Author
        Level 4
        September 6, 2017

        Haven't worked on 10.

        CT1012
        CT1012Author
        Level 4
        September 6, 2017

        Is it necessary to add profiles for ui-apps pom.xml?

        VeenaVikraman
        Community Advisor
        VeenaVikramanCommunity Advisor
        Community Advisor
        September 6, 2017

        By default the autoInstall will point to localhost if you are working on your local machine . You have to modify the pom to point it to the DEV servers.

          joerghoh
          Adobe Employee
          joerghohAdobe Employee
          Adobe Employee
          September 6, 2017

          You can also override the properties from the maven command line:

          $ mvn clean install -Daem.host=dev.server -Daem.port=6302

          (if your dev server has the hostname "dev.server" and AEM runs on port 6302).

          Jörg

            M
            martin_acn
            June 3, 2020
            Hi running mvn clean install -PautoInstallPackagePublish but i get a connection refused error and when i tried mvn clean install -Daem.host=dev.server -Daem.port=6302 it works.. Why is that? what is the difference between the two?
            CT1012
            CT1012Author
            Level 4
            September 6, 2017

            Is it a permanent change, or change during deployment ?  Should i override the properties before deploying?

            joerghoh
            Adobe Employee
            joerghohAdobe EmployeeAccepted solution
            Adobe Employee
            September 6, 2017

            If you use the parameters on the maven commandline, they are just valid during this call; it's not a persistent call. If you are using this POM only to deploy to this instance, it might be easier to adapt the pom.xml file.

            Jörg

              CT1012
              CT1012Author
              Level 4
              September 6, 2017

              Sure, Thank you

              Terms & ConditionsAccessibility statement

              Loading footer...