axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dirk Vanhalle (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-3919) Temp folder being filled with files. Running out of disk space.
Date Fri, 04 Dec 2009 09:37:20 GMT

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

Dirk Vanhalle commented on AXIS2-3919:
--------------------------------------

We too were filling up /var/tmp using an axis2 1.4 client application and this resulted in
the system administrators removing our rights to write into that directory. Other than a warning
in the logs, our client application did not encounter any problem.

After some investigation, we found that the classloaders created for the modules first try
to unpack the modules. Although org.apache.axis2.deployment.util.Utils.createClassLoader has
a boolean parameter extractJars, the method is always called with this parameter set to true.
We changed it to false in org.apache.axis2.deployment.DeploymentEngine and org.apache.axis2.deployment.repository.util.DeploymentFileData.

There is 1 issue with this solution: Axis2 tries to deploy any services that might be included
in the module (even if you use a module on the client side). It looks for the resource aars/aars.list
in the module and all jars located in lib/ inside the module. This caused long load times
of our own module, but removing the libs from the module solved this too.


> 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