You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by de...@geronimo.apache.org on 2004/10/03 15:09:31 UTC
[jira] Created: (GERONIMO-350) Reclaim disk space when deploying updated app version
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-350
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-350
Summary: Reclaim disk space when deploying updated app version
Type: Improvement
Status: Unassigned
Priority: Major
Project: Apache Geronimo
Components:
deployment
Versions:
1.0-M3
Assignee:
Reporter: Aaron Mulder
Created: Sun, 3 Oct 2004 6:09 AM
Updated: Sun, 3 Oct 2004 6:09 AM
Description:
When redeploying an EAR with deployer.jar --install, it creates a new directory in the config-store, and updates the index to point to the new directory. It does not delete the old directory, which means over time, you get dozens of copies of the application, only one of which is being used in the server.
For now, it's probably sufficient to delete the old directory once the new directory has been successfully deployed. In any case it should certainly be safe to keep no more than two copies.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-350) Reclaim disk space when deploying
updated app version
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-350?page=all ]
Vamsavardhana Reddy closed GERONIMO-350.
----------------------------------------
> Reclaim disk space when deploying updated app version
> -----------------------------------------------------
>
> Key: GERONIMO-350
> URL: http://issues.apache.org/jira/browse/GERONIMO-350
> Project: Geronimo
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 1.0-M3
> Reporter: Aaron Mulder
> Fix For: 1.0-M5
>
>
> When redeploying an EAR with deployer.jar --install, it creates a new directory in the config-store, and updates the index to point to the new directory. It does not delete the old directory, which means over time, you get dozens of copies of the application, only one of which is being used in the server.
> For now, it's probably sufficient to delete the old directory once the new directory has been successfully deployed. In any case it should certainly be safe to keep no more than two copies.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-350) Reclaim disk space when deploying updated app version
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-350?page=all ]
Aaron Mulder resolved GERONIMO-350:
-----------------------------------
Fix Version: 1.0-M5
(was: 1.0)
Resolution: Fixed
This was fixed before.
> Reclaim disk space when deploying updated app version
> -----------------------------------------------------
>
> Key: GERONIMO-350
> URL: http://issues.apache.org/jira/browse/GERONIMO-350
> Project: Geronimo
> Type: Improvement
> Components: deployment
> Versions: 1.0-M3
> Reporter: Aaron Mulder
> Fix For: 1.0-M5
>
> When redeploying an EAR with deployer.jar --install, it creates a new directory in the config-store, and updates the index to point to the new directory. It does not delete the old directory, which means over time, you get dozens of copies of the application, only one of which is being used in the server.
> For now, it's probably sufficient to delete the old directory once the new directory has been successfully deployed. In any case it should certainly be safe to keep no more than two copies.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-350) Reclaim disk space when deploying updated app version
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-350?page=all ]
Aaron Mulder updated GERONIMO-350:
----------------------------------
Fix Version: 1.0
Description:
When redeploying an EAR with deployer.jar --install, it creates a new directory in the config-store, and updates the index to point to the new directory. It does not delete the old directory, which means over time, you get dozens of copies of the application, only one of which is being used in the server.
For now, it's probably sufficient to delete the old directory once the new directory has been successfully deployed. In any case it should certainly be safe to keep no more than two copies.
was:
When redeploying an EAR with deployer.jar --install, it creates a new directory in the config-store, and updates the index to point to the new directory. It does not delete the old directory, which means over time, you get dozens of copies of the application, only one of which is being used in the server.
For now, it's probably sufficient to delete the old directory once the new directory has been successfully deployed. In any case it should certainly be safe to keep no more than two copies.
Environment:
> Reclaim disk space when deploying updated app version
> -----------------------------------------------------
>
> Key: GERONIMO-350
> URL: http://issues.apache.org/jira/browse/GERONIMO-350
> Project: Geronimo
> Type: Improvement
> Components: deployment
> Versions: 1.0-M3
> Reporter: Aaron Mulder
> Fix For: 1.0
>
> When redeploying an EAR with deployer.jar --install, it creates a new directory in the config-store, and updates the index to point to the new directory. It does not delete the old directory, which means over time, you get dozens of copies of the application, only one of which is being used in the server.
> For now, it's probably sufficient to delete the old directory once the new directory has been successfully deployed. In any case it should certainly be safe to keep no more than two copies.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira