axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-3919) Temp folder being filled with files. Running out of disk space.
Date Mon, 14 Sep 2009 12:43:59 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Glen Daniels updated AXIS2-3919:
--------------------------------

    Fix Version/s: 1.6

We've replaced the referenced code with a TempFileManager class that does two things - 1)
puts all files for a particular instance of Axis2 into a specific subdirectory of tmp_file_dir,
and 2) ensures that old directories are cleaned up each time a new instance starts.  This
will solve the problem for the case where you're spinning up and down Axis2 instances... but
not for a long running process (since the cleanup code is in a static block that gets initialized
at JVM startup).

The right long-term solution is to periodically clean up the temporary files when they are
no longer needed - I think if we just store references to them in the appropriate context
objects, we should be able to clean them up when the contexts are destroyed.   I've targeted
this for 1.6.

> Temp folder being filled with files. Running out of disk space.
> ---------------------------------------------------------------
>
>                 Key: AXIS2-3919
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3919
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel, modules
>    Affects Versions: 1.4, 1.3, 1.2, 1.1.1, 1.1, 1.0
>         Environment: Windows XP, Linux
>            Reporter: Sujay Chauhan
>             Fix For: 1.6
>
>
> Hi
> We are seeing an issue and it is holding us up from moving to production as our production
servers would run out of disk space.
> This is in regards to a client that we are trying to implement using axis2-1.4 and rampart-1.3.
> We have a folder structure
> clientProjectFolder
>       --otherFolders
>       --....
>       --....
>       --axis2
>           --conf
>                 --axis2.xml
>            --modules
>                  --rampart1.3.mar
> our axis2.xml file contains the global module <module ref="rampart"/>
> In our client code, we make use of the fileSytemConfigurator to configure the client
stub before making the call to our service.
> Every time we are calling the service, files are added to the TEMP folder (see below)
> C:\TEMP\_axis2>dir
>  Directory of C:\TEMP\_axis2
> 07/16/2008 08:36 AM <DIR> .
> 07/16/2008 08:36 AM <DIR> ..
> 07/16/2008 08:36 AM 2,704 axis2473rampart-1.3.mar
>                1 File(s) 2,704 bytes
>                2 Dir(s) 103,722,340,352 bytes free
> The same issue is being duplicated on our prod servers which are not windows based but
linux based. the files get put in /tmp/_axis2 folder.
> Any advice on if there is a workaround for this?
> Thanks,
> Sujay 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message