Bug 1150123 - BPM cluster produces huge server logs containing helix communication
Summary: BPM cluster produces huge server logs containing helix communication
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: ---
Assignee: Marco Rietveld
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-07 13:29 UTC by Radovan Synek
Modified: 2016-09-20 05:05 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-26 13:02:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1153674 0 urgent CLOSED BPM cluster's first node utilizes CPU over 70% without any real load 2021-02-22 00:41:40 UTC

Internal Links: 1153674

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".


Note You need to log in before you can comment on or make changes to this bug.