OK... good news i found the leak. Was a matter of making sure the wicket
tester instance is destroyed in test tear down. Bad news is the build is
still failing because of some issues in the jdbc security module. Those
tests arent actually supposed to be running, i put them in a profile to
explicitly be run. Again... will have to pick this up tomorrow. And
again... apologies for inconvenience.
On Wed, Apr 4, 2012 at 8:26 AM, Justin Deoliveira <[email protected]>wrote:
> Hi all,
>
>
> The security work has been committed. The settings on the build server
> (256M of heap for tests) have brought out a memory leak. I run with 512m
> locally (the default defined in the root pom) so I didn't see this before.
> I spent a while looking for the leak tonight but haven't come up with
> anything yet. I will have to pick this back up tomorrow, it will be my top
> priority.
>
> For now i have upped the test heap on the server to 512m as a temporary
> measure to try and get the build back. Hopefully that fixes it.
>
> Again I will pick this back up first thing tomorrow. I apologize for
> the inconvenience.
>
> -Justin
>
> --
> Justin Deoliveira
> OpenGeo - http://opengeo.org
> Enterprise support for open source geospatial.
>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
