[
https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499451#comment-14499451
]
Matthew Lunnon commented on AXIS2-3919:
---------------------------------------
I have come across this exact problem recently and it is a show stopper for us.
I have a couple of solutions:
1. Set the java.io.tmpdir to a directory that does not exist. There may be some
undesirable consequences to this!
2. Create a bespoke version of org.apache.axis2.deployment.util.Utils and edit
the createClassLoader function. Deploy this in the class path before the axis
library. This function takes a boolean extractJars which causes the file to be
copied, if that is not possible (e.g. if the tmp dir does not exist) then the
class loader will work off the original copy of the jar. Again there may be
some undesirable consequences to this. There are a number of variations on this
theme, I also looked at adding some code to create just a single copy of the
jar but I think this solution is nicer since it uses the existing
functionality. Here is my version of the function:
public static ClassLoader createClassLoader (URL[] urls,
ClassLoader serviceClassLoader,
boolean extractJars,
File tmpDir,
boolean isChildFirstClassLoading) {
List embedded_jars = Utils.findLibJars(urls[0]);
return createDeploymentClassLoader(urls, serviceClassLoader,
embedded_jars, isChildFirstClassLoading);
}
I hope this helps.
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
