0005740: exchange should terminate to be restarted after handling $N requests

ID	Project	Category	View Status	Date Submitted	Last Update
0005740	Taler	other	public	2019-05-29 15:28	2019-12-20 18:11

Reporter	Florian Dold	Assigned To	Christian Grothoff	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	normal	Severity	feature	Reproducibility	have not tried
Status	closed	Resolution	fixed
Product Version	git (master)
Target Version	0.6	Fixed in Version	0.6

Summary	0005740: exchange should terminate to be restarted after handling $N requests
Description	This achieves two things: 1. it tests whether the exchange process is supervised correctly 2. it makes us resilient against memory leaks and fragmentation
Tags	No tags attached.

Date Modified	Username	Field	Change
2019-05-29 15:28	Florian Dold	New Issue
2019-11-14 21:47	Christian Grothoff	Assigned To	=> Christian Grothoff
2019-11-14 21:47	Christian Grothoff	Status	new => assigned
2019-11-14 21:47	Christian Grothoff	Product Version	=> git (master)
2019-11-14 21:47	Christian Grothoff	Target Version	=> 0.6
2019-11-14 21:51	Christian Grothoff	Severity	minor => feature
2019-12-01 12:34	Christian Grothoff	Status	assigned => informing
2019-12-01 12:34	Christian Grothoff	Resolution	open => fixed
2019-12-01 12:34	Christian Grothoff	Fixed in Version	=> 0.6
2019-12-01 12:34	Christian Grothoff	Note Added: 0015114
2019-12-20 18:11	Christian Grothoff	Status	informing => closed

Christian Grothoff 2019-12-01 12:34 manager ~0015114	The new MAX_REQUESTS option adds this feature. By default it is set to ULONG_LONG_MAX, effectively disabling the logic. 97afbf1e..f1639c09 implements this.