[
https://issues.apache.org/jira/browse/AXIS2-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Weckx updated AXIS2-3139:
-----------------------------
Priority: Critical (was: Major)
> AxisClient creates large number of temporary files that never gets deleted in
> an appserver environment as long as the server is running
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-3139
> URL: https://issues.apache.org/jira/browse/AXIS2-3139
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.3, 1.2
> Environment: WinXP, Axis2-1.2 on jboss4.0.5
> Reporter: Shantanu Sen
> Priority: Critical
>
> The org.apache.axis2.deployment.DeploymentEngine.loadRepositoryFromURL
> invoked org.apache.axis2.deployment.util.Utils.createClassLoader that calls
> Utils.getURLsForAllJars that invokes Utils.createTempFile
> When we use an AxisClient with a
> WarBasedAxisConfiguration/URLBasedAxisConfiguration then these temp files are
> created but not removed once the client invocation is complete. For a large
> number of invocations a large number of files are being created in the temp
> space and after many calls e.g. 5000, the temp space is filled up.
> The temp file is being create with deleteOnExit being invoked on the file,
> but when running in an appserver this is not good enough to remove the files.
> There should be a mechanism to remove the temp files after a service
> invocation using axis client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
