[
https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921335#action_12921335
]
shivendra tripathi commented on AXIS2-3919:
-------------------------------------------
I have analyzed the issue and here is my finding.
Issue is because we create configurationContext in every call instead of
caching it once created. We cache ConfigurationContext in 1.5/ 1.6 so this
issue is not reproducible there. Here the modified code. This is similar to
axis2 1.5 where issue is fixed.
ServiceClient#configureServiceClient
if (configContext == null) {
if (ListenerManager.defaultConfigurationContext == null) {
configContext = ConfigurationContextFactory.
createConfigurationContextFromFileSystem(null, null);
ListenerManager.defaultConfigurationContext = configContext;
createConfigCtx = true;
} else {
configContext = ListenerManager.defaultConfigurationContext;
}
}
Above will fix generation of temp file for subsequent call. For deleting temp
file on server start up call ServiceClient#cleanup().
@Amila please review this so that I can provide the patch for previous versions
(before 1.5) of axis2.
> 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.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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
