[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rampart-dev
Subject:    [jira] [Commented] (AXIS2-3919) Temp folder being filled with files. Running out of disk space.
From:       "Robert Lazarski (Jira)" <jira () apache ! org>
Date:       2021-02-03 20:05:01
Message-ID: JIRA.12400378.1216216473000.564390.1612382701243 () Atlassian ! JIRA
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin. \
system.issuetabpanels:comment-tabpanel&focusedCommentId=17278334#comment-17278334 ] 

Robert Lazarski commented on AXIS2-3919:
----------------------------------------

This issue remains open however all related code commits went out in 1.7.9. Best I \
can tell, no one is still having problems?

I run axis2 1.7.9 on quite a few servers and I can confirm that on normal JVM \
termination the standard Java feature of File.deleteOnExit() works as expected.

Abnormal JVM exit via "killall -9 java" or the Linux OOM killer can leave lck files \
open - nothing to do about that besides rely on cron or the OS to clean them up.

For ServiceClient invocations, I have projects that do tons but the JVM's are short \
lived so I see no such lingering tmp dir entries.

The  stackoverflow link from before 1.7.9 showed a static block around  \
createConfigurationContextFromFileSystem() but I think that's something that the user \
end client code would need to implement, if necessary.

For the axis2-wsdl2code-maven-plugin or wsdl2code.sh etc, I suppose that creates a \
tmp dir too for the axis2 repo though that should need to be run infrequently and \
should clean up on JVM exit.

So I am unaware of any issues after 1.7.9. Not sure why this issue is open still. I'd \
like to clear up any doubts on the current status and close the issue.

> 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.0, 1.1, 1.1.1, 1.2, 1.3, 1.4, 1.7.3
> Environment: Windows XP, Linux
> Reporter: Sujay Chauhan
> Priority: Major
> 
> 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 was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]