CruiseControl leaking JMX threads
Ben Butler-Cole <[email protected]>
| Newsgroups | gmane.comp.java.cruise-control.user |
|---|---|
| Message-ID | <[email protected]> |
Hello I am seeing a problem with my CruiseControl 2.8.2 installation where the memory usage increases rapidly and irreversibly while builds are running. The memory is being consumed by hundreds of threads that appear to be created by MX4J. Turning off the JMX interface by removing the related configuration options form the launch script stops the problem. The leak only happens when a build is running and only starts about half-way through the 20 minute build while JUnit tests are running. Is this a known problem? Is there a way to work around it without losing the JMX cababilities? Thanks Ben ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com