Unable to replicate a page

Avatar

Avatar

Niveshchandra

Avatar

Niveshchandra

Niveshchandra

07-07-2020

When am trying to activate one of my page. Getting following error "Replication (ACTIVATE) of /content/pagepath not successful: java.net.SocketException: Connection reset Conversation follows". 
Remaining all pages are replicating successfully. 
Anyone please help me on this issue.

 

Thanks in advance.

blocking page replication Replication Queue

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

vishakhav2

Avatar

vishakhav2

vishakhav2

07-07-2020

Hi @Niveshchandra ,

 

 "Replication (ACTIVATE) of /content/pagepath not successful: java.net.SocketException: Connection reset Conversation follows". - Connection reset error can be due to following issues:

1. Either your publish instance was closed abruptly

2. Network issues

Try restarting the system and test replication action. Test specifically for that particular page. Still if the issue persists try by increasing the socket timeout time. 

If the issue is because of socket timeout means you have to modify your page. 

In developer mode, analyse the components that takes more time for loading.

 

Answers (7)

Answers (7)

Avatar

Avatar

Nirmal_Jose

MVP

Avatar

Nirmal_Jose

MVP

Nirmal_Jose
MVP

07-07-2020

If you don't get a response from the target instance before the timeout, you may see this error. Is the page that is not getting replicated is a very heavy page compared to other pages?

You can validate the page performance using the developer view in author and compare with other pages. You can try increasing the socket timeout from the configuration below in replicate agent configuration. Try 10000

 

Screenshot 2020-07-07 at 18.01.05.png

 

If this is the issue, better to optimise the page rather than increasing the timeout config.

Avatar

Avatar

Arun_Patidar

MVP

Total Posts

(val/1000)?string[".0"]}K

Likes

958

Correct Answer

820

Avatar

Arun_Patidar

MVP

Total Posts

(val/1000)?string[".0"]}K

Likes

958

Correct Answer

820
Arun_Patidar
MVP

08-07-2020

I would suggest to check page and page permission and state as well on both author and publisher.

Avatar

Avatar

BrianKasingli

MVP

Avatar

BrianKasingli

MVP

BrianKasingli
MVP

07-07-2020

@Niveshchandra,

Can you share with us your replication configurations?

Avatar

Avatar

QueryResolved

Avatar

QueryResolved

QueryResolved

07-07-2020

As you mentioned , remaining pages are replicating successfully.
Can you verify :

Is there anything different in /content/pagepath with respect to other pages, delaying activation and causing timeout ?

Also check this out : https://helpx.adobe.com/experience-manager/kb/SocketConnectionTimeout.html

Avatar

Avatar

berliant

Employee

Avatar

berliant

Employee

berliant
Employee

07-07-2020

How did you configure a replication agent? Do you use an admin as a  user on a Transportation Tab of a replication agent configuration?

If it's not an admin, make sure that the user has sufficient ACL for that page location on publish.

Do you have any non cq:Page or dam:Asset type of nodes within the path to the page it failed to replicate?

 

Avatar

Avatar

Shashi_Mulugu

MVP

Avatar

Shashi_Mulugu

MVP

Shashi_Mulugu
MVP

07-07-2020

@Niveshchandra I can see three possible issues, 1. Network issue between AEM author and publishers, 2. AEM author restarted after replicating the page(could be code deployment as well) 3. AEM Publisher restarted after replicating the page(could be code deployment as well).

 

Is it happening everytime for that single page?

Avatar

Avatar

AshokNalamalapu

Avatar

AshokNalamalapu

AshokNalamalapu

07-07-2020

It should be due network issue. Is the issue persistent?