When remote service are not reachable, logging can go crazy

Steps to reproduce

Steps to reproduce:

1. Run a distributed cluster and take the httpd in front of a worker down

Actual Results:

Many log messages saying that the remote service cannot be reached:

2013-10-01 19:13:17 WARN (RemoteBase:181) - Service at http://localhost:8080/inspection/enrich returned unexpected response code 405
2013-10-01 19:13:17 WARN (RemoteBase:196) - No service of type 'org.opencastproject.inspection' is currently readily available
2013-10-01 19:13:17 WARN (RemoteBase:181) - Service at http://localhost:8080/inspection/enrich returned unexpected response code 405
2013-10-01 19:13:17 WARN (RemoteBase:196) - No service of type 'org.opencastproject.inspection' is currently readily available
2013-10-01 19:13:17 WARN (RemoteBase:181) - Service at http://localhost:8080/inspection/enrich returned unexpected response code 405
2013-10-01 19:13:17 WARN (RemoteBase:196) - No service of type 'org.opencastproject.inspection' is currently readily available

Expected Results:

One log message telling us that the services are all offline.

Status

Assignee

Tobias Wunden

Reporter

Tobias Wunden

Severity

Operations

Tags (folksonomy)

Components

Fix versions

Affects versions

Priority

Major
Configure