[
https://issues.apache.org/jira/browse/QPID-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912258#action_12912258
]
Robbie Gemmell commented on QPID-2857:
--------------------------------------
I also added/increased the Xmx setting for the FindBugs ant task added to the
build system, as it would consistently OOM quickly when run otherwise. The
FindBugs task catches this OOM itself and the ant build completes
'successfully' as a result. I viewed peak memory usage of around 350MB, so set
Xmx to 512MB.
> [Java] Running FindBugs against Java codebase reveals room for improvement
> --------------------------------------------------------------------------
>
> Key: QPID-2857
> URL: https://issues.apache.org/jira/browse/QPID-2857
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Broker MessageStore - DerbyStore, Java
> Client, Java Clustering, Java Common, Java Management : CLI Tool, Java
> Management : JMX Console, Java Management : JMX Interface, Java Management :
> QMan, Java Management : QMF, Java Performance Tests, Java Tests, Java Tools
> Affects Versions: 0.6
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Fix For: 0.7
>
> Attachments: findbugs.html, findbugs.html, report.html.zip
>
>
> FindBugs (http://findbugs.sourceforge.net/) is a program which uses static
> analysis to look for bugs in Java code
> Ideally we should incorporate Findbugs into our ant build such that we can be
> informed when new critical issues may have been introduced.
> In the interim findbugs can be run manually.
> Where critical issues are discovered by findbugs we should correct these
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
