Not sure if this helps...we are using ant do builds with and each time we
build / deploy, Orion deploys the new files without failure. It appears to
me that Orion is triggering a re-deploy based on the timestamp of the ear
file changing. However, I don't think this on-the-fly deployment is a good
thing and here is why:
When we first deploy our app, the JVM memory footprint is 11.9Mbytes.
After the first compile / redeploy, the memory is 22.4Mbytes.
After the third compile / redeploy, the memory is 24.8Mbytes.
The memory usage continues to climb with each auto-deploy. As far as I can
tell, the memory is never reclaimed for re-use. Not quite sure why it works
that way, but it could be dangerous in a production environment. I know the
standard developer answer is to allocate more memory, but that is just
hiding the problem.
-----Original Message-----
From: Ozzie Gurkan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 10:08 AM
To: Orion-Interest
Subject: JSP/Bean not reloading after re-deploy
I have searched through all of orion-interest list and still have not found
a solution that works for me. I am talking about the "reload" problem with
changing of JSPs and its bean classes withouth restarting the server. I
understand that the server should never be restarted, but I can't seem to
get anything working without actually doing just that. I have touched the
web.xml file before it is ear'd up to be deployed, but that didn't work.
Does anyone have a solution to this problem? I must be missing something
very simple.
Thanks,
Ozzie Gurkan
