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

Olivier Vanekem commented on AXIS2-3919:
----------------------------------------

I also had the same kind of issues of .tmp directories not cleanly removed 
using Axis/2 1.6.2 under Oracle Weblogic Application Server. What I did 
ultimately as a work around is create a shell script that looks which folder 
contains 'orphaned' AAR files and delete those folders with the .lck file 
linked to it. My script parses the axis tmp folders and look if the aar for 
version is in use by a user (the application server in fact), if not, it 
deletes the folder. Works for me.

Below is my script:
{code}
for entry in /tmp/axis2*.tmp
do
        echo "Checking $entry"
        for jar in "$entry"/axis2*version-1.6.2.aar
        do
                echo "Found $jar"
                if fuser -vu "$jar" 2> /dev/null 
                then
                        echo "Will not delete $entry"
                else 
                        echo "Will delete $entry"
                        rm -R "$entry"
                        rm "$entry".lck
                        break
                fi 
        done
done
{code}

> 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
>         Environment: Windows XP, Linux
>            Reporter: Sujay Chauhan
>             Fix For: 1.7.0
>
>
> 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
(v6.1#6144)

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

Reply via email to