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

Connection Timeout

Avatar

Avatar
Validate 1
Level 1
sgr01
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 1
sgr01
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
sgr01
Level 1

07-01-2018

When I am trying to test a connection for default publish or dispatcher flush, I get a connection timeout error. The servers were recently moved to Amazon AWS and initially, i thought it could be because of the security groups/network that may be causing the timeout as both author and publish were on different servers. Then i started to test dispatcher flush setting, as i have a temp webserver running on the same instance as the author and i still got a connection timeout. Here is the error i see in the error.log file on author.

/content not successful: java.net.ConnectException: Connection timed out (Connection timed out) Conversation follows

07.01.2018 15:43:50.455 *ERROR* [10.173.24.234 [1515339700995] GET /etc/replication/agents.author/flush.test.html HTTP/1.1] com.day.cq.replication.Agent.flush >> Content-Type: application/octet-stream

07.01.2018 15:43:50.457 *INFO* [10.173.24.234 [1515339700995] GET /etc/replication/agents.author/flush.test.html HTTP/1.1] com.day.cq.replication.impl.ReplicatorImpl Processed replication: setup 1ms, checked 2ms, pre 0ms, build 2ms, queued 129442ms, status 2ms, total 129449ms

Accepted Solutions (0)

Answers (2)

Answers (2)

Avatar

Avatar
Validate 1
Level 7
Hemant_arora
Level 7

Likes

92 likes

Total Posts

290 posts

Correct Reply

54 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 50
View profile

Avatar
Validate 1
Level 7
Hemant_arora
Level 7

Likes

92 likes

Total Posts

290 posts

Correct Reply

54 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 50
View profile
Hemant_arora
Level 7

08-01-2018

Please check if you have the correct URI & userid,pwd. if your machine is behind a proxy server, try updating the proxy settings.

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,113 likes

Total Posts

3,145 posts

Correct Reply

1,072 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,113 likes

Total Posts

3,145 posts

Correct Reply

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

07-01-2018

A connection timeout can have many reasons, which all are outside of AEM. Make sure that you are using the correct endpoint adresses, and then you need to start debugging the network.

Jörg