Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM upgrade 6.5 - Determining the correct upgrade start command not working

ashishkhadpe
Level 3
Level 3

Hi All,

 

As per the steps provided on adobe site I have determined the start command after repository migration as below : 

 

java -server -Xms2g -Xmx8g -Djava.awt.headless=true -Doak.queryLimitInMemory=500000 -Doak.queryLimitReads=100000 -Doak.fastQuerySize=true -javaagent:/opt/newrelic/newrelic.jar -Dcom.sun.management.jmxremote.port=10060 -Dcom.sun.management.jmxremote.authenticate=true -Dcom.sun.management.jmxremote.password.file=/app/aem/crx-quickstart/bin/jmx_pass -Dcom.sun.management.jmxremote.access.file=/app/aem/crx-quickstart/bin/jmx_user -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.rmi.port=10061 -Dsling.run.modes=publish,crx3,crx3tar -jar cq65-publish-p4503.jar start -c crx-quickstart -i launchpad -p 4503 -Dsling.properties=conf/sling.properties

 

But when I execute it I get below error :

Loading quickstart properties: default

Loading quickstart properties: instance

org.apache.commons.cli2.OptionException: Unexpected start while processing Use these options on the Quickstart command line.

at org.apache.commons.cli2.commandline.Parser.parse(Parser.java:99)

at com.adobe.granite.quickstart.base.impl.Main.<init>(Main.java:594)

at com.adobe.granite.quickstart.base.impl.Main.main(Main.java:981)

 

Any idea what can be the issue?

1 Accepted Solution
Vish_dhaliwal
Correct answer by
Employee
Employee

Hello Ashish,

 

I would recommend removing the extra params and try the startup command as described here:

https://experienceleague.adobe.com/docs/experience-manager-65/deploying/upgrading/in-place-upgrade.h...

 

You can add these params later in the startup script after the first start.

 

Regards,

Vishu

View solution in original post

3 Replies
Bhuwan_B
Community Advisor
Community Advisor

Check this article for step by step upgrade process to successfully transition into AEM version 6.5.

https://hashouttech.com/blog/How-to-Upgrade-Adobe-Experience-Manager-to-AEM-Version-6.5

 

Vish_dhaliwal
Correct answer by
Employee
Employee

Hello Ashish,

 

I would recommend removing the extra params and try the startup command as described here:

https://experienceleague.adobe.com/docs/experience-manager-65/deploying/upgrading/in-place-upgrade.h...

 

You can add these params later in the startup script after the first start.

 

Regards,

Vishu

View solution in original post

ashishkhadpe
Level 3
Level 3
HI Vishu, I tried that but it is giving me the same error where as if I change the jar file location from cq65-publish-p4503.jar to /app/cq-quickstart-6.5.0-standalone-quickstart.jar it works fine. So not sure if I can use the standalone jar file present at /app to start the AEM for the 1st time. Any idea on this?