Continous Axis deployment forces Tomcat OutOfMemoryException

2004-08-10 Thread Martin Olsson

I'm developing a web service on Axis, and as I progress I continuously 
deploy versions of my code to a remote Tomcat/Axis server. I do this 
directly from my Ant build script by using ftp,reload,axis-admin tasks etc.

So everyday I'm coding, deploying, testing, coding, deploying, testing 
and so it goes until around 14.00, just after lunch. Then Tomcat stops 
working, the build script fails and I cannot even surf to the 
hostname:8080 to see the intro page (let alone restart axis).

So what I do is that I login using ssh, execute catalina.sh stop and 
then catalina.sh start and this usually makes Tomcat work again.

---
My guess is that somewhere in the deployment process (I never undeploy 
anything) there is a memory leak or something that grows, and after X 
deployments I get this error. Could it be a Tomcat bug?

So, does anyone have similar problems -- or better yet, a solution?
Regards,
Martin Olsson
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Continous Axis deployment forces Tomcat OutOfMemoryException

2004-08-10 Thread Shapira, Yoav

Hi,
If you search the archives you will see that this has been discussed
many times, though not specifically to Axis.  Generally, yes, continuous
redeployment results in monotonically increasing memory, for a variety
of less and more complex reasons.  Don't do it on a production server,
or if you must then restart Tomcat regularly (for example in the middle
of the night) to prevent OOMEs.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Martin Olsson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 10, 2004 12:41 PM
To: Tomcat Users List
Subject: Continous Axis deployment forces Tomcat OutOfMemoryException



I'm developing a web service on Axis, and as I progress I continuously
deploy versions of my code to a remote Tomcat/Axis server. I do this
directly from my Ant build script by using ftp,reload,axis-admin tasks
etc.

So everyday I'm coding, deploying, testing, coding, deploying, testing
and so it goes until around 14.00, just after lunch. Then Tomcat stops
working, the build script fails and I cannot even surf to the
hostname:8080 to see the intro page (let alone restart axis).

So what I do is that I login using ssh, execute catalina.sh stop and
then catalina.sh start and this usually makes Tomcat work again.

---

My guess is that somewhere in the deployment process (I never undeploy
anything) there is a memory leak or something that grows, and after X
deployments I get this error. Could it be a Tomcat bug?

So, does anyone have similar problems -- or better yet, a solution?


Regards,
Martin Olsson

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]