[ 
https://issues.apache.org/jira/browse/AXIS2-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Lazarski closed AXIS2-5897.
----------------------------------
    Resolution: Duplicate

> Axis2 is creating /tmp folders in server temp directory and never cleaning it 
> up therefore causing high disk space usage
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-5897
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5897
>             Project: Axis2
>          Issue Type: Bug
>    Affects Versions: 1.6.2
>            Reporter: priyanka singh
>            Assignee: Robert Lazarski
>            Priority: Major
>
> Hi,
> Axis2 is creating .tmp folders and .lck files in server's temp folder and 
> never cleaning it up even after JVM shutdowns resulting in duplicate .tmp 
> folders and .lck files which causes high disk space usage.
> In AXIS2-3919 we found that the files are deployed to the temp folder each 
> time AXIS configuration context is created and never cleaning it up.
> We want to know that what all versions are affected by this issue? In 
> AXIS2-3919 I found that even 1.7 is affected. 
> There it is mention that it is getting fixed in the axis2 1.8 but when I saw 
> fixed issue list for 1.8 I couldn't found this issue there.
> Is this getting fixed in axis2 1.8?
> What is the release date for 1.8?
> I tried to get my answer by emailing to [email protected] but I am 
> not able to send my question.
> I am getting following failure notice.
> Hi. This is the qmail-send program at apache.org.
> I'm afraid I wasn't able to deliver your message to the following addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
> <[email protected]>:
> Thank you!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to