aem-publish-p4503.jar is starting on port 4502?

Avatar

Avatar

nutmix

Avatar

nutmix

nutmix

03-12-2020

I followed these steps: https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/development/set-up-a-loc...

On windows and it works.

Then I setup two ubunutu boxes with oracle java 11, one runing the author, and one runing the publisher.  Author starts correctly on port 4502, but publisher starts incorrectly on port 4502 intstead of 4503.

The jar is called: /home/aem/publish/aem-publish-p4503.jar

I unpacked it like this:

$ java -jar *.jar -unpack

Then I run it like this:

$ /home/aem/publish/crx-quickstart/bin

However, when I do ps -ef | grep java I get this:

aem 16589 1 33 13:11 pts/0 00:10:03 java -server -Xmx1024m -XX:MaxPermSize=256M -Djava.awt.headless=true -Dsling.run.modes=author,crx3,crx3tar -Djava.locale.providers=CLDR,JRE,SPI -jar crx-quickstart/app/cq-quickstart-6.5.0-standalone-quickstart.jar start -c crx-quickstart -i launchpad -p 4502 -Dsling.properties=conf/sling.properties

When I try to hit the site on 4503 i get connection refused.

when i connecto the publisher server on 4502, I get the author UI, not the site.

 

I dont see anything obvious in error.log.

 

NOTE: I start it via start script because if I just run the jar, it always fails.

 

Is this normal behaviour?

 

Are there some manual switches to force it to run as publisher on port 4503?

 

I tried $ ./start -p 4503 but this is not picked up. I undestand I can edit the conf/sling.properties, or setup some env vars, but what shoudl the be?

 

I see the author run mode is -Dsling.run.modes=author,crx3,crx3tar  What should he publish run mode be, and how to I best set it?

 

$ java -version
java version "11.0.9" 2020-10-20 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.9+7-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.9+7-LTS, mixed mode)

 

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Vaibhavi

MVP

Avatar

Vaibhavi

MVP

Vaibhavi
MVP

03-12-2020

Hi @nutmix , 

 

Reason is sling runmode is set to author in sling.properties file. 

Please update the below property to publish and restart the server that should fix the issue

Dsling.run.modes=publish,crx3,crx3tar

 

If you are starting the instance using start.bat file, 

please set the CQ_RUNMODE flag to publish and CQ_PORT to 4503 ( anyport number which you want to start your server. 

 

If you are starting AEM by double clicking on jar file , naming convention for jar is aem-publish-p4503.jar for publish. 

 

There are 3 ways to start the server. 

Please check the below documents for more details. 

https://helpx.adobe.com/in/experience-manager/kb/RunModeSetUp.html

https://helpx.adobe.com/in/experience-manager/6-3/sites/deploying/using/configure-runmodes.html

 

Answers (1)

Answers (1)

Avatar

Avatar

Anudeep_Garnepudi

Avatar

Anudeep_Garnepudi

Anudeep_Garnepudi

03-12-2020

Hi @nutmix 

When you run(double click) the jar file, it will read the the jar file name and will pick port number from file name itself. If you don't follow jar file naming conversion (-p4502/-p4503), if port 4502 is available then it will take port 4502.

If you are executing/running bath file, you should change the port explicitly by opening it in any text editor.

Screenshot 2020-12-03 at 11.20.12 PM.png

Update the CQ_PORT in start.bat/quickstart.bat before running it.

-AG