[Anthill-pro] OutOfMemory exception
Steve Boone
sbb at urbancode.com
Mon Sep 10 10:47:40 CDT 2007
Uldis,
The directions for MySQL are below.
------
1. Create your MySQL database and Anthill user:
CREATE DATABASE anthill3;
GRANT ALL ON anthill3.* TO 'anthill3'@'%' IDENTIFIED BY 'password' WITH
GRANT OPTION;
2. Download and extract http://downloads.urbancode.com/mysql-export.zip to
the Anthill server directory, it should create a export directory in it.
3. Download the appropriate MySQL JDBC driver and copy it in to the
export/lib directory.
4. Edit the export/build.xml file and change the Derby settings and MySQL
properties as needed.
5. Export your existing Derby database to file by running the following in
the export directory (it will create a export.xml file and might take some
time):
ant db-export
6. Import the database file into the new MySQL database by running (this
will take even longer):
ant db-import
7. Edit your conf/server/installed.properties file. Change the
install.db.type to 'mysql' and the install.db.driver, install.db.user,
install.db.password, and install.db.url as needed.
9. Edit your conf/spring-server/base.xml. Change the url, username, password
in two locations.
10. Edit your conf/server/spy.properties. Change the realdriver setting to
the correct driver.
11. Start the server.
Let us know if you have any problems.
On 9/10/07, Uldis Karlovs-Karlovskis <uldisk at ctco.lv> wrote:
>
> We would like to migrate to Oracle. When you`re planning to write a script
> like that?
> For now it will be useful to get script for MySQL. Maybe I`ll found easy
> just to adjust it.
>
> Uldis, C. T. Co
> -----Original Message-----
> From: anthill-pro-bounces at lists.urbancode.com
> [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Ryan Smith
> Sent: pirmdiena, 2007. gada 10. septembrī 17:16
> To: AnthillPro user and support list.
> Subject: Re: [Anthill-pro] OutOfMemory exception
>
> Uldis, we have seen performance problems in the server when installations
> get to be a larger size. We found that this was caused by the Derby
> database. We hope to replace it as our default database soon now that we
> have found this out. We have helped several customer migrate to MySQL and
> they have seen performance improve greatly. Oracle is also an option if
> you
> have that though we are still working on the upgrade script. We have a
> script that will export your existing database and import it into MySQL.
>
> Ryan Smith
>
>
> Uldis Karlovs-Karlovskis wrote:
> > Yes, after complexing my full build more and more I`ve realized that I
> > need to run builds in separate folders. I`m not using CodeStation for
> now.
> >
> >
> >
> > My cleanup policy runs fine every 3 hours. What confuses me that
> > performance downgrade wasn`t for agent but for AntHill web (browsing the
> > web were very slow and raises cpu on server up to 100%) so there is not
> > any association with uncleaned Agent. Am I wrong?
> >
> >
> >
> > Also I have many custom scripts in buildLife but there is only one
> > script which creates objects. This is from Agent Filter script sample so
> > this is not the case too.
> >
> >
> >
> > Uldis, C. T. Co
> >
> > -----Original Message-----
> > *From:* anthill-pro-bounces at lists.urbancode.com
> > [mailto:anthill-pro-bounces at lists.urbancode.com] *On Behalf Of *Steve
> Boone
> > *Sent:* pirmdiena, 2007. gada 10. septembrī 16:28
> > *To:* AnthillPro user and support list.
> > *Subject:* Re: [Anthill-pro] OutOfMemory exception
> >
> >
> >
> > Uldis,
> >
> > If you are running out of space on an agent there is most likely two
> > causes. If you are using a different working directory for every
> > project you are building, this practice can take up a good portion of
> > space, especially if you are building a large number of projects. The
> > second cause could be your codestation cache has grown out of control.
> >
> > If you are using a different working directory for each project, you
> > will need to create a cleanup step, and have it run after your build
> > completes. This will ensure that the files created are removed.
> >
> > If this is not the case, and you are using cleanup steps within your
> > projects, then odds are your codestation cache has grown rather large.
> > Check your ~/.codestation/cache directory to see if that is what is
> > consuming the majority of your space. If it is, you can delete the
> > files from there, and to prevent this from happening in the future you
> > can turn the agent caching off.
> >
> > To do this, edit the codestation.properties file located in
> > ~/.codestation/ If the file does not exist, go ahead and create it.
> > Add the following line to the file.
> >
> > codstation.noCache=true
> >
> >
> > As for the Cleanup Policies, anytime they run, they will create a Misc.
> > Job that you will see on the dashboard (much like an email notification,
> > or other Misc Job) if you are not seeing any Misc Jobs for cleanup, then
> > they most likely are not running. You do not need to set both the "Days"
> > and "Count" fields, the Days field can be left empty if you choose to
> > keep the buildlife indefinitely.
> >
> > Cleanup Policies only clean the server, it will clean up logs when
> > corresponding job traces are deleted, but it does not delete working
> > directories for jobs. If this is the functionality you are looking for,
> > I would suggest adding a cleanup step to your individual jobs as you
> > find necessary. You could also create a cleanup workflow, and set it to
> > a trigger and have it cleanup only when you felt it was appropriate.
> >
> > Regards,
> > Steve Boone
> >
> > On 9/10/07, *Uldis Karlovs-Karlovskis* <uldisk at ctco.lv
> > <mailto:uldisk at ctco.lv>> wrote:
> >
> > Hello, this is a second time when my anthill server performance is
> > descended and on this time I see that there are OutOfMemory exceptions
> > in AntHill server log. I have server with 4GB ram so this can`t be an
> > issue. As I understand I can raise an JVM max memory in JAVA_OPTs. But
> > how long this will help if my server uptime is only 10 days? In this
> > moment the anthill server process is taking 518M of memory.
> >
> >
> >
> > //Uldis Karlovs - Karlovskis//
> >
> > //Build System and Deployment Administrator//
> >
> > //System Configuration Management//
> >
> > //C.T.Co <http://C.T.Co>//
> >
> > //Mobile: +371 29 345 210//
> >
> >
> >
> >
> > _______________________________________________
> > Anthill-pro mailing list
> > Anthill-pro at lists.urbancode.com <mailto:Anthill-pro at lists.urbancode.com>
> > http://lists.urbancode.com/mailman/listinfo/anthill-pro
> >
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Anthill-pro mailing list
> > Anthill-pro at lists.urbancode.com
> > http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
> --
> ===========================================================
> Ryan Smith. 2044 Euclid Ave., Suite 600
> Lead Developer Cleveland, Ohio 44115
> Urbancode, Inc.
> email: rws at urbancode.com
> web: www.urbancode.com phone: 216-858-9000
> web: www.anthillpro.com fax: 216-858-9602
> ===========================================================
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20070910/c550d4cb/attachment-0001.htm
More information about the Anthill-pro
mailing list