Mitigating serialization issues in AEM | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
KunwarsalujaAccepted solution
Employee
Jul 19, 2018 6:45 PM UTC

by default you don't need to do anything and dynamic loading of the serialization agent would take care of everything. If incase things fails, add (1) to your startup script (start.bat or terminal along with other jvm arguments) where you adjust the path of the notsoserial.jar per your deployment directory

(1) : -javaagent:<aem-installation-folder>/crx-quickstart/opt/notsoserial/notsoserial.jar

4 replies

smacdonald2008
Level 10
Jul 20, 2018 12:33 AM UTC

Great answer!

Translate
KunwarsalujaAccepted solution
Employee
Jul 19, 2018 6:45 PM UTC

by default you don't need to do anything and dynamic loading of the serialization agent would take care of everything. If incase things fails, add (1) to your startup script (start.bat or terminal along with other jvm arguments) where you adjust the path of the notsoserial.jar per your deployment directory

(1) : -javaagent:<aem-installation-folder>/crx-quickstart/opt/notsoserial/notsoserial.jar

Translate
Ratna_Kumar
Level 10
Jul 19, 2018 6:36 PM UTC

Hi,

Look into this thread: How to start AEM 6.2 in debug mode by clicking on jar file

In that thread it says, how to pass parameters via argument[Option 2]..So that will let you do JVM  start-up parameters of CQ Jar.

Thanks,

Ratna Kumar.

Translate
jantzen_b
Employee
Jul 19, 2018 4:46 PM UTC

I'll move your question into the Adobe Experience Manager​ community.

Translate