[MAGNOLIA-3350] Timeout for activation requests Created: 01/Nov/10  Updated: 20/Feb/15  Resolved: 08/Nov/10

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 4.3.8
Fix Version/s: 4.4

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MAGNOLIA-3424 Activation Read Timeout is too short Closed
dependency
is depended upon by MGNLXAA-22 Use connection connect and read timeo... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

Unless I'm missing something, the current activation http requests never timeout.
Since java 1.5, URLConnection supports setting both a connect timeout and read timeout; we should set those - currently, when a public server can't be reached, the activation http request hangs forever, potentially starving the author server.


Generated at Mon Feb 12 03:45:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.