[
https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831098#action_12831098
]
Keith Roberts commented on AXIS2-3919:
--------------------------------------
I'm also running in to this issue. What I'm seeing is each time my app server
deploys ears with axis2 in them, a temp directory and a temp lock file is
created (for each one).
I see in the code where it creates the lock file (in TempFileManager.java)
// Create a lock before creating the directory so
// there is no race condition with another application trying
// to clean your temp dir.
File lockFile = new File(tmpDirName, tmpDir.getName() + ".lck");
lockFile.createNewFile();
// Set the lock file to delete on exit so it is properly cleaned
// by the JVM. This will allow the TempFileManager to clean
// the overall temp directory next time.
lockFile.deleteOnExit();
And then in the static block
// Create a file to represent the lock and test.
File lockFile = new File(tmpFile.getParent(), tmpFile.getName() +
".lck");
if (!lockFile.exists()) {
// delete the temp directory
However, the lock file is not getting deleted by the JVM, and so my temp
directory fills with these directories over time each time the app server is
restarted.
>From the javadocs:
http://java.sun.com/javase/6/docs/api/java/io/File.html#createNewFile%28%29
Note: this method should not be used for file-locking, as the resulting
protocol cannot be made to work reliably. The FileLock facility should be used
instead.
> Temp folder being filled with files. Running out of disk space.
> ---------------------------------------------------------------
>
> Key: AXIS2-3919
> URL: https://issues.apache.org/jira/browse/AXIS2-3919
> Project: 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.
