Bug 1150123

Summary:	BPM cluster produces huge server logs containing helix communication
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Radovan Synek <rsynek>
Component:	Business Central	Assignee:	Marco Rietveld <mrietvel>
Status:	CLOSED WORKSFORME	QA Contact:	Radovan Synek <rsynek>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	6.1.0	CC:	alazarot, kverlaen, mrietvel, porcelli, rsynek, smcgowan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-26 13:02:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Radovan Synek 2014-10-07 13:29:00 UTC

Description of problem:
Having a BPM cluster with 2 nodes and working with it (authoring, process execution), server logs grow to tenth MB after several minutes. Majority of the content are helix communication messages with INFO log level.

Version-Release number of selected component (if applicable):
6.1.0.DR3

Steps to Reproduce:
1. configure BPM cluster with 2 nodes
2. clone there a repository, start any process - just work with it
3. see both server logs growing

Expected results:
INFO messages about helix/zookeeper communication could be switched to DEBUG or TRACE level.

Comment 2 Marco Rietveld 2015-02-19 22:56:02 UTC

Radovan, 

Could you attach a copy of the log? I'm unfamiliar with setting up the BPM cluster. 

If I get a copy of the log, I can figure out what we need to add the logging settings for EAP. I've already asked Tom Hauser to modify the log settings for another logging bug, 1193129, so doing this as well will be relative little work. 

Thanks!

Comment 3 Radovan Synek 2015-02-23 15:05:20 UTC

Marco,

unfortunately I don't have any log. But the good thing is I cannot obtain a new one. The issue is fixed - helix provides reasonable amount of logging messages (server log is not growing). My opinion is the issue can be connected with bug 1159278 or bug 1153674, i.e. the problem was not the logging itself, but utilization of helix. There were some bigger changes to cluster recently, seems at least this issues has been fixed by them. I am willing to close this issue, wdyt?

Comment 4 Marco Rietveld 2015-02-26 13:02:55 UTC

Sounds fine, thank you Radovan! 

Closed with "WORKSFORME".