[
https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278350#comment-17278350
]
Aaron Burgemeister commented on AXIS2-3919:
-------------------------------------------
I agree; this seems to be well and truly fixed and can be closed.
The only thing I will point out, not having found documentation after barely
looking, is that any documentation on this class may benefit from pointing out
to new users that using a static block for a single resource that can then be
used over and over, or at least not making new resources in any kind of looping
logic, may be good for the reasons covered in this bug (build up of files) as
mentioned in the StackOverflow thread above.
Sailpoint's IdentityIQ product uses this class, and the problem with it wasn't
so much disk space usage as it was file handle usage, and since just increasing
the open files ulimit for the process is a silly hack the code really needed to
be fixed by creating a resource and using it over and over, not making a new
one per TCP connection to an endpoint. For new developers, that may be
unclear, thus documentation.
> 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, 1.7.3
> Environment: Windows XP, Linux
> Reporter: Sujay Chauhan
> Priority: Major
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
