Expand my Community achievements bar.

Applications for the 2024-2025 Adobe Experience Manager Champion Program are open!
SOLVED

Error while starting the aem publish instance

Avatar

Level 4

Hi all,

I'm using aem as cloud service 2023 version when i trying to setup publish instance on my local machine i'm getting this error while starting the aem jar file. 

Kindly give some ideas to resolve this issue.

HTTP ERROR 404 Not Found

URI:STATUS:MESSAGE:SERVLET:

/
404
Not Found
org.apache.felix.http.base.internal.dispatch.DispatcherServlet-40d5bc0c

 

Nandheswara_0-1685192634997.png

 

1 Accepted Solution

Avatar

Correct answer by
Level 3

 it means replication has been stopped check the replication agent what is blocking to replicate. and check error.log file in publish instance what is causing to open the instance

 

View solution in original post

6 Replies

Avatar

Community Advisor

Hi @Nandheswara,

 

Do you see any error in error.log file? If Yes, please share error you are getting.

Also, please try opening full URL of any page example localhost:4503/crx/de or any page of your website. 

 

Avatar

Level 4

Replication test to http://localhost:4503/bin/receive?sling:authRequestLogin=1

2023-05-28 21:15:14 - Create new HttpClient for Default Agent
2023-05-28 21:15:14 - * Auth User: admin
2023-05-28 21:15:14 - * HTTP Version: 1.1
2023-05-28 21:15:14 - * Connect Timeout: 900000
2023-05-28 21:15:14 - * Socket Timeout: 900000
2023-05-28 21:15:14 - adding header: Action:Test
2023-05-28 21:15:14 - adding header: Path:/content
2023-05-28 21:15:14 - adding header: Handle:/content
2023-05-28 21:15:14 - deserialize content for delivery
2023-05-28 21:15:14 - No message body: Content ReplicationContent.VOID is empty
2023-05-28 21:15:14 - Sending POST request to http://localhost:4503/bin/receive?sling:authRequestLogin=1
2023-05-28 21:15:14 - sent. Response: 404 Not Found
2023-05-28 21:15:14 - Replication (TEST) of /content not successful. Conversation follows
2023-05-28 21:15:14 - ------------------------------------------------
2023-05-28 21:15:14 - Sending message to localhost:4503
2023-05-28 21:15:14 - >> POST /bin/receive HTTP/1.0
2023-05-28 21:15:14 - >> Action: Test
2023-05-28 21:15:14 - >> Path: /content
2023-05-28 21:15:14 - >> Handle: /content
2023-05-28 21:15:14 - >> Referer: about:blank
2023-05-28 21:15:14 - >> Content-Length: 0
2023-05-28 21:15:14 - >> Content-Type: application/octet-stream
2023-05-28 21:15:14 - --
2023-05-28 21:15:14 - << HTTP/1.1 404 Not Found
2023-05-28 21:15:14 - << Cache-Control: must-revalidate,no-cache,no-store
2023-05-28 21:15:14 - << Content-Type: text/html;charset=iso-8859-1
2023-05-28 21:15:14 - << Content-Length: 438
2023-05-28 21:15:14 - <<
2023-05-28 21:15:14 - << <html>
2023-05-28 21:15:14 - << <head>
2023-05-28 21:15:14 - << <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
2023-05-28 21:15:14 - << <title>Error 404 Not Found</title>
2023-05-28 21:15:14 - << </head>
2023-05-28 21:15:14 - << <body><h2>HTTP ERROR 404 Not Found</h2>
2023-05-28 21:15:14 - << <table>
2023-05-28 21:15:14 - << <tr><th>URI:</th><td>/bin/receive</td></tr>
2023-05-28 21:15:14 - << <tr><th>STATUS:</th><td>404</td></tr>
2023-05-28 21:15:14 - << <tr><th>MESSAGE:</th><td>Not Found</td></tr>
2023-05-28 21:15:14 - << <tr><th>SERVLET:</th><td>org.apache.felix.http.base.internal.dispatch.DispatcherServlet-4fa39808</td></tr>
2023-05-28 21:15:14 - << </table>
2023-05-28 21:15:14 - << </body>
2023-05-28 21:15:14 - << </html>
2023-05-28 21:15:14 - Message sent.
2023-05-28 21:15:14 - ------------------------------------------------
2023-05-28 21:15:14 - Replication (TEST) of /content not successful.

Nandheswara_0-1685288902820.png

 

Avatar

Correct answer by
Level 3

 it means replication has been stopped check the replication agent what is blocking to replicate. and check error.log file in publish instance what is causing to open the instance

 

Avatar

Community Advisor

As publisher is not up, you wont be able to access publisher URL. Please check publisher logs. Once publisher is setup properly, replication test will work fine.

Avatar

Community Advisor

Hello @Nandheswara 

 

You might want to cross-check, if the local instance has started as author / publish.

I guess logs for "http://localhost:4503/bin/receive?sling:authRequestLogin=1", should only appear on author instance. 

 

Sometimes, server takes a little longer to start and we receive 404 error. Please check the status of all bundles in AEM, if they are active.


Aanchal Sikka

Avatar

Community Advisor

Check error.log of AEM running on port 4503.