You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by bu...@apache.org on 2003/10/29 01:06:16 UTC
DO NOT REPLY [Bug 24199] New: -
ManagedMemoryDataSource with large maxCached hang
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24199>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24199
ManagedMemoryDataSource with large maxCached hang
Summary: ManagedMemoryDataSource with large maxCached hang
Product: Axis
Version: 1.1
Platform: All
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Basic Architecture
AssignedTo: axis-dev@ws.apache.org
ReportedBy: markc@plumtree.com
This is a strange bug that I found while working with large attachments that I
did not want written to disk. Here is what is happening:
After creating a data handler by passing in a ManagedMemoryDataSource with a
large maxCached amount, say 1 megabyte, and subsequently calling
dataHandler.getName() - down the line when the SOAP call is invoked Axis hangs.
At first I thought the problem was simply that ManagedMemeoryDataSource was not
handling large maxCached sizes. But after investigating the code for a while I
did not think that was the case. Something strange is going on, as commenting
out dataHandler.getName() fixes the problem.
I no loner need to call dataHandler.getName() since I don't have to manually
delete the temp files anymore since I was able to up the maxCached size. Still,
this problem causes call.invoke() to completely hang so it should be fixed.