Hello All,
Noticed when starting AEM jar for first time. After I see the quickstart folder, I go to bin and hit the start.bat the instance starts, but at the same time a file named as 'null' is created.
Below is a snapshot of the folder view.
Below is the content of null file if opened with text editor
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Unrecognized option: --add-modules
The instance works fine though.
Anyone faced similar issue?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
Please check Error while starting AEM 6.4 for the first time
Views
Replies
Total Likes
How are u starting the AEM instance ? Just because you said " when starting AEM jar for first time". If you are double clicking the jar and starting it , why are you doing it again in quickstart ? Is there any thing more on the logs ?
Views
Replies
Total Likes
Have you modified your default start.bat
Can you check it once what was those modifications were?
Views
Replies
Total Likes
Hi,
Please check Error while starting AEM 6.4 for the first time
Views
Replies
Total Likes
There were no modifications made when I started the instance and saw the null file.
Views
Replies
Total Likes
Thanks Arun. using nul instead of null fixes the issue related to null file.
However I didn't mention in primary question. I also see the same error as mentioned in the link you added. Below is what I see.
Exception in thread "sling-oak-5" java.lang.NullPointerException
at org.apache.sling.commons.threads.impl.DefaultThreadPool$LoggingThreadLocalChangeListener.changed(DefaultThreadPool.java:172)
at org.apache.sling.commons.threads.impl.ThreadLocalCleaner.changed(ThreadLocalCleaner.java:210)
at org.apache.sling.commons.threads.impl.ThreadLocalCleaner.diff(ThreadLocalCleaner.java:173)
at org.apache.sling.commons.threads.impl.ThreadLocalCleaner.cleanup(ThreadLocalCleaner.java:148)
at org.apache.sling.commons.threads.impl.ThreadPoolExecutorCleaningThreadLocals.afterExecute(ThreadPoolExecutorCleaningThreadLocals.java:75)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Will check for a day care ticket regarding this.
Thanks
Views
Likes
Replies
Views
Likes
Replies