[ http://issues.apache.org/jira/browse/AXIS2-861?page=all ]
Thilina Gunarathne resolved AXIS2-861.
--------------------------------------
Resolution: Fixed
resolved in the latest SVN Head...
http://svn.apache.org/viewvc?rev=438087&view=rev
> cache setting is not working in Nightly build Jun 22,06
> -------------------------------------------------------
>
> Key: AXIS2-861
> URL: http://issues.apache.org/jira/browse/AXIS2-861
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0
> Environment: Axis2 1.0, nightly build version 22 Jun 06
> Jetty 6.0.0 beta 16
> linux environment
> java language
> Reporter: Wan Kaveevivitchai
> Assigned To: Thilina Gunarathne
>
> There is the problem of file caching, it doesn't working in nightly build
> version released on June 22, 06. Eventhough, the cache properties in
> axis2.xml already been set.
> Is there any solution for this? Is it a bug?
> I was writing some email earlier about problem in sending large file ~ 10 MB
> and got broken pipe exception. And there was the suggestion to use the new
> nightly release which is the 22 Jun 06 release and the broken pipe problem
> was solve.
> So i moved on to test with 100 MB size attachment, and i got
> java.lang.OutOfMemory error, so i did some setting about cache on axis2.xml
> as following
> <parameter name="cacheAttachments" locked="false">true</parameter>
> <parameter name="attachmentDIR"
> locked="false">/users/alice3/home/</parameter>
> <parameter name="sizeThreshold" locked="false">4000</parameter>
> but it seems like it still cache into the memory, also when i check at the
> home directory, there is no cached file at all. So we tried extend the memory
> size and the attachment is received fine but it isn't the good way to do it,
> i supposed. So i think the problem is about cache is not working.
> The same setting is working fine with the other nightly build version
> released on 4 Jun 06 but that one has the problem about broken pipe in
> sending large file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
