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

Replication test failed

Avatar

Avatar
Validate 1
Level 2
ybharath264
Level 2

Likes

3 likes

Total Posts

17 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
ybharath264
Level 2

Likes

3 likes

Total Posts

17 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
ybharath264
Level 2

24-05-2018

I click on "Test connection " button in Default Agent (publish). I got this error. Anyone know why, can you help me.? This is AEM 6.3.2.

24.05.2018 09:56:54 - Create new HttpClient for Default Agent

24.05.2018 09:56:54 - * Auth User: admin

24.05.2018 09:56:54 - * HTTP Version: 1.1

24.05.2018 09:56:54 - adding header: Action:Test

24.05.2018 09:56:54 - adding header: Path:/content

24.05.2018 09:56:54 - adding header: Handle:/content

24.05.2018 09:56:54 - deserialize content for delivery

24.05.2018 09:56:54 - No message body: Content ReplicationContent.VOID is empty

24.05.2018 09:56:54 - Sending POST request to http://h0001995:4503/bin/receive?sling:authRequestLogin=1

24.05.2018 09:56:54 - sent. Response: 503 ServletResolver service missing, cannot service requests

24.05.2018 09:56:54 - Replication (TEST) of /content not successful. Conversation follows

24.05.2018 09:56:54 - ------------------------------------------------

24.05.2018 09:56:54 - Sending message to h0001995:4503

24.05.2018 09:56:54 - >> POST /bin/receive HTTP/1.0

24.05.2018 09:56:54 - >> Action: Test

24.05.2018 09:56:54 - >> Path: /content

24.05.2018 09:56:54 - >> Handle: /content

24.05.2018 09:56:54 - >> Referer: about:blank

24.05.2018 09:56:54 - >> Content-Length: 0

24.05.2018 09:56:54 - >> Content-Type: application/octet-stream

24.05.2018 09:56:54 - --

24.05.2018 09:56:54 - << HTTP/1.1 503 ServletResolver service missing, cannot service requests

24.05.2018 09:56:54 - << Date: Thu, 24 May 2018 14:56:54 GMT

24.05.2018 09:56:54 - << X-Content-Type-Options: nosniff

24.05.2018 09:56:54 - << X-Frame-Options: SAMEORIGIN

24.05.2018 09:56:54 - << Cache-Control: must-revalidate,no-cache,no-store

24.05.2018 09:56:54 - << Content-Type: text/html; charset=ISO-8859-1

24.05.2018 09:56:54 - << Content-Length: 336

24.05.2018 09:56:54 - <<

24.05.2018 09:56:54 - << <html>

24.05.2018 09:56:54 - << <head>

24.05.2018 09:56:54 - << <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>

24.05.2018 09:56:54 - << <title>Error 503 </title>

24.05.2018 09:56:54 - << </head>

24.05.2018 09:56:54 - << <body>

24.05.2018 09:56:54 - << <h2>HTTP ERROR: 503</h2>

24.05.2018 09:56:54 - << <p>Problem accessing /bin/receive. Reason:

24.05.2018 09:56:54 - << <pre> ServletResolver service missing, cannot service requests</pre></p>

24.05.2018 09:56:54 - << <hr /><i><small>Powered by Jetty://</small></i>

24.05.2018 09:56:54 - << </body>

24.05.2018 09:56:54 - << </html>

24.05.2018 09:56:54 - Message sent.

24.05.2018 09:56:54 - ------------------------------------------------

24.05.2018 09:56:54 - Replication (TEST) of /content not successful.

Replies

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

24-05-2018

Make sure that the Pub is running and you configured the Agent property. Under the Transport tab - make sure that you specify the correct URI to the Pub instance,

See here --

Another thing to try is to setup a fresh AEM Pub instance and see if that is successful - this will tell us if issue is with your PUB instance or you have not configured something properly.

Avatar

Avatar
Give Back 50
Employee
Kunwar
Employee

Likes

65 likes

Total Posts

253 posts

Correct Reply

72 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Give Back 50
Employee
Kunwar
Employee

Likes

65 likes

Total Posts

253 posts

Correct Reply

72 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
Kunwar
Employee

25-05-2018

Response: 503 ServletResolver service missing, cannot service requests\

There should be a error/warn message in the error.log as well. Can you attach the same ?

Avatar

Avatar
Validate 1
Level 2
ybharath264
Level 2

Likes

3 likes

Total Posts

17 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
ybharath264
Level 2

Likes

3 likes

Total Posts

17 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
ybharath264
Level 2

25-05-2018

Thanks for the reply, here is the error log

25.05.2018 09:15:29.437 *ERROR* [10.30.52.60 [1527257729437] GET /favicon.ico HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl ServletResolver service missing, cannot service requests , sending status 503

25.05.2018 09:15:51.521 *ERROR* [10.157.163.5 [1527257751521] POST /bin/receive HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl ServletResolver service missing, cannot service requests , sending status 503

25.05.2018 09:15:56.698 *ERROR* [10.30.52.60 [1527257756698] GET /favicon.ico HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl ServletResolver service missing, cannot service requests , sending status 503

25.05.2018 09:16:12.971 *ERROR* [10.30.52.60 [1527257772971] GET /favicon.ico HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl ServletResolver service missing, cannot service requests , sending status 503

Avatar

Avatar
Give Back 50
Employee
Kunwar
Employee

Likes

65 likes

Total Posts

253 posts

Correct Reply

72 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Give Back 50
Employee
Kunwar
Employee

Likes

65 likes

Total Posts

253 posts

Correct Reply

72 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
Kunwar
Employee

25-05-2018

I wasn't expecting this one. Can you check the error.log at publish instance http://h0001995:4503​ once you do this test connection

Avatar

Avatar
Validate 1
Level 2
ybharath264
Level 2

Likes

3 likes

Total Posts

17 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
ybharath264
Level 2

Likes

3 likes

Total Posts

17 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
ybharath264
Level 2

25-05-2018

Well actually the log above is the log from Publish instance itself. 

The author instance error log basically shows the same thing that I first posted.

Avatar

Avatar
Give Back 50
Employee
Kunwar
Employee

Likes

65 likes

Total Posts

253 posts

Correct Reply

72 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Give Back 50
Employee
Kunwar
Employee

Likes

65 likes

Total Posts

253 posts

Correct Reply

72 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
Kunwar
Employee

25-05-2018

That doesn't help either and looks like there is something bigger to just replication. Can do the following or maybe open a support case with Adobe as this might require deeper investigation

- Stop the instance

- Rename the logs folder

- Start the instance

- Share the error, stdout.log

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,118 likes

Total Posts

3,149 posts

Correct Reply

1,073 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,118 likes

Total Posts

3,149 posts

Correct Reply

1,073 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

27-05-2018

Hi,

from the replication log is quite clear, that this message is sent as response from the publish instance:

24.05.2018 09:56:54 - << HTTP/1.1 503 ServletResolver service missing, cannot service requests

24.05.2018 09:56:54 - << Date: Thu, 24 May 2018 14:56:54 GMT

24.05.2018 09:56:54 - << X-Content-Type-Options: nosniff

24.05.2018 09:56:54 - << X-Frame-Options: SAMEORIGIN

24.05.2018 09:56:54 - << Cache-Control: must-revalidate,no-cache,no-store

24.05.2018 09:56:54 - << Content-Type: text/html; charset=ISO-8859-1

24.05.2018 09:56:54 - << Content-Length: 336

24.05.2018 09:56:54 - <<

24.05.2018 09:56:54 - << <html>

24.05.2018 09:56:54 - << <head>

24.05.2018 09:56:54 - << <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>

24.05.2018 09:56:54 - << <title>Error 503 </title>

24.05.2018 09:56:54 - << </head>

24.05.2018 09:56:54 - << <body>

24.05.2018 09:56:54 - << <h2>HTTP ERROR: 503</h2>

24.05.2018 09:56:54 - << <p>Problem accessing /bin/receive. Reason:

24.05.2018 09:56:54 - << <pre> ServletResolver service missing, cannot service requests</pre></p>

24.05.2018 09:56:54 - << <hr /><i><small>Powered by Jetty://</small></i>

24.05.2018 09:56:54 - << </body>

24.05.2018 09:56:54 - << </html>

That indicates that the publish instance has some issues, most probably a problem with the repository (a typical reason why such messages occurr).

regards,

Jörg

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

28-05-2018

As kunwar and Joerg suggests - this looks like there is an issue with the Pub instance, Please open a support ticket.