[
https://issues.apache.org/jira/browse/OODT-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-929.
------------------------------------
Resolution: Fixed
- fixed
{noformat}
LMC-053601:oodt mattmann$ git commit -m "Fix for OODT-929: EnvUtilities should
only load environment variables one time and statically cache them."
[master 6577722] Fix for OODT-929: EnvUtilities should only load environment
variables one time and statically cache them.
3 files changed, 27 insertions(+), 7 deletions(-)
LMC-053601:oodt mattmann$ git push -u origin master
Counting objects: 21, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (12/12), done.
Writing objects: 100% (21/21), 3.35 KiB | 0 bytes/s, done.
Total 21 (delta 5), reused 0 (delta 0)
remote: oodt git commit: Fix for OODT-929: EnvUtilities should only load
environment variables one time and statically cache them.
To https://git-wip-us.apache.org/repos/asf/oodt.git
94a1c72..6577722 master -> master
Branch master set up to track remote branch master from origin.
LMC-053601:oodt mattmann$
{noformat}
> EnvUtilities should only load environment variables one time and statically
> cache them
> --------------------------------------------------------------------------------------
>
> Key: OODT-929
> URL: https://issues.apache.org/jira/browse/OODT-929
> Project: OODT
> Issue Type: Bug
> Components: commons
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 1.1
>
>
> On BigTranslate (and on other projects for years), just getting the
> environment variable sand resolving them in EnvUtilities can leave a TON of
> open file handles. We should only load env variables once statically per JVM
> and then get the cached version after that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
