Author&publisher attempting to use same port AEM 6.3 | Community
Skip to main content
Adobeaspirant
Adobeaspirant
Level 3
June 21, 2017

Author&publisher attempting to use same port AEM 6.3

  • June 21, 2017
  • 4 replies
  • 4849 views

A sling file was created in publisher and author  that is attempting to use the same ports org.osgi.service.http.port=8080

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

    4 replies

    R
    RobertBailey1
    Level 4
    July 6, 2017

    I have the same problem on AEM 6.3.   Cannot publish (activate) pages from 6.3 Author server to 6.3 Publish server.

    It works on 6.2 (previous version) but it does not work on 6.3 (newest version).

    No information in the documentation.

      viveksachdeva
      Community Advisor
      viveksachdevaCommunity Advisor
      Community Advisor
      July 11, 2017

      I see no issue in Replication on Vanila AEM 6.3 instance.. Have you ensured that the replication agent is configured properly. By default it is pointed to 4503.. So if you are running publish on a separate port, you need to change it in the replication agent setting

      O
      Adobe Employee
      ogillAdobe Employee
      Adobe Employee
      July 11, 2017

      Do you have both instances on the same machine?

      Adobeaspirant
      AdobeaspirantAuthor
      Level 3
      July 12, 2017

      Both instances were on same server. We are not even publishing as of now. Suddenly our author environment shutdown.

      zeeshanKhan0786
      zeeshanKhan0786
      Level 5
      July 12, 2017

      Hi gowtham,

      Could you check that port 4502 and 4503 is block or using by some other application.

      or

      Check your AEM Configuration Apache Felix Jetty Based Http Service. in this check http port in Both AEM Instance.If they are pointing to same port.Change one of the Port.

        Adobeaspirant
        AdobeaspirantAuthor
        Level 3
        August 30, 2017

        Thank you. It is helpful

        Terms & ConditionsAccessibility statement

        Loading footer...