Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 409954

Summary:	Limit log file size / make use of rolling log appender to avoid large logging files
Product:	[Technology] Jubula	Reporter:	Markus Tiede <markus.tiede>
Component:	Core	Assignee:	Project Inbox <jubula.core-inbox>
Status:	CLOSED FIXED	QA Contact:	Oliver Goetz <Oliver.Goetz>
Severity:	critical
Priority:	P3	CC:	Achim.Loerke, alexandra.schladebeck, zeb.ford-reitz
Version:	unspecified	Keywords:	triaged
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Markus Tiede

2013-06-05 08:33:03 EDT

Jubula should use limits for log file sizes or make use of rolling log appender to avoid large logging files.

I've just seen a customers "rc_swing"-log file which size was round about ~2.2GB (BTW - it got sent via mail being compressed with 7z which significantly reduced the size to 5.8MB). This also indicates that many similar problems are being logged.

Comment 1 Achim Loerke

2013-06-07 05:20:23 EDT

@Triaged:+

Comment 2 Zeb Ford-Reitz

2013-06-07 06:07:05 EDT

Just so we don't forget: Fixing this bug will require changing the Log Viewer (Help -> Show Client Log / Show AUT Agent Log) implementation(s) to correctly handle the new log file paths. This brings up the question of how the logs should be displayed (or requested by the support team). For example: 
 * Should the most recently changed log file with the specified prefix be shown?
 * Should all existing logs be offered in a cascading menu?

Comment 3 Alexandra Schladebeck

2014-10-26 08:15:34 EDT

This has been implemented.

Comment 4 Oliver Goetz

2014-10-28 03:36:19 EDT

This has been tested in the context of a seperate Jira task