[jira] [Comment Edited] (AXIS2-3919) Temp folder being filled with files. Running out of disk space.

["Anton Khitrenovich (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899296#comment-13899296 ] 

Anton Khitrenovich edited comment on AXIS2-3919 at 2/12/14 5:18 PM:
--------------------------------------------------------------------

We found a workaround for that. 
Actually, the files are deployed to the temp folder each time AXIS configuration context is created. Also, it appears that the generated Stub can accept existing configuration object via the constructor. So, the following Spring configuration helped us to solve the issue (irrelevant bean and class names dropped):

{code}
<bean id="....Stub" factory-bean="...." factory-method="...." scope="request">
	<!-- this next element effects the proxying of the surrounding bean, 
		needed because .... will try to set the stub out of request scope -->
	<aop:scoped-proxy/>
	<constructor-arg index="0" >
		<!-- The WS stub is created here, and passed to the factory-method of ... as a parameter -->
		<bean class="com......ws.....Stub" scope="prototype">
			<constructor-arg ref="axisConfigContext" />
		</bean>
	</constructor-arg>
</bean>
	
<!-- Exists to avoid deployment of axis jar into temp dir for each request. See AXIS2-3919 for more details. -->
<bean id="axisConfigContext" 
		class="org.apache.axis2.context.ConfigurationContextFactory" 
		factory-method="createConfigurationContextFromFileSystem">
	<constructor-arg index="0"><null /></constructor-arg>
	<constructor-arg index="1"><null /></constructor-arg>
</bean>
{code}


was (Author: khitrenovich):
We found a workaround for that. 
Actually, the files are deployed to the temp folder each time AXIS configuration context is created. So, the following Spring configuration helped us to solve the issue (irrelevant bean and class names dropped):

{code}
<bean id="....Stub" factory-bean="...." factory-method="...." scope="request">
	<!-- this next element effects the proxying of the surrounding bean, 
		needed because .... will try to set the stub out of request scope -->
	<aop:scoped-proxy/>
	<constructor-arg index="0" >
		<!-- The WS stub is created here, and passed to the factory-method of ... as a parameter -->
		<bean class="com......ws.....Stub" scope="prototype">
			<constructor-arg ref="axisConfigContext" />
		</bean>
	</constructor-arg>
</bean>
	
<!-- Exists to avoid deployment of axis jar into temp dir for each request. See AXIS2-3919 for more details. -->
<bean id="axisConfigContext" 
		class="org.apache.axis2.context.ConfigurationContextFactory" 
		factory-method="createConfigurationContextFromFileSystem">
	<constructor-arg index="0"><null /></constructor-arg>
	<constructor-arg index="1"><null /></constructor-arg>
</bean>
{code}

> 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.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org