-
Bug
-
Resolution: Not A Defect
-
Major
-
HP DL380 G7
Xeon E5649 x 2
32G memory
CentOS 6.2 x86_64
Our log file is over 20MB, when using a self defined parser to parsing it, it always shows out of memory exceptions even if I add the -Xmx4096m parameter.
And I tried to split the log files into several small ones but it seems like warnings plugin collect all of then and parse them together. I think at least this procedure can be adjusted to parsing each file one by one and collect parsing result together in order to save memory.
Can you please wrap code and expressions in {noformat} or {code} blocks (see Confluence help on macros).