[
https://issues.apache.org/jira/browse/AXIS-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741610#action_12741610
]
Santu Ghosh edited comment on AXIS-2574 at 8/10/09 4:06 PM:
------------------------------------------------------------
I have the axis-2574.patch downloaded, also I have Axis1.4.jar. In the new
Call.java I can see following imports, and giving compilation error because new
imported classes are not found. Do I need to add any dependant jars?
import org.apache.axis.wsa.WSAConstants ;
import org.apache.axis.wsa.MIHeader ;
import org.apache.axis.wsa.EndpointReference ;
Can anyone please help me out here?
was (Author: santughosh):
I have the axis-2574.patch downloaded, also I have Axis1.4.jar. Now I want
to replace the old Call.java by new Call.java. The following import class are
not found. Do I need to add any dependant jar?
import org.apache.axis.wsa.WSAConstants ;
import org.apache.axis.wsa.MIHeader ;
import org.apache.axis.wsa.EndpointReference ;
Can anyone please help me out here?
> Reading an attachment (slowly) can cause resource deleted error
> ---------------------------------------------------------------
>
> Key: AXIS-2574
> URL: https://issues.apache.org/jira/browse/AXIS-2574
> Project: Axis
> Issue Type: Bug
> Components: Basic Architecture
> Affects Versions: 1.2.1
> Reporter: Steve Sowerby
> Assignee: Jochen Wiedmann
> Attachments: axis-2574.patch, Call.diff, Call.diff, Call.java
>
>
> When reading the data from an attachment we periodically get the following
> error:
> java.io.IOException: Resource has been deleted.
> at
> org.apache.axis.attachments.ManagedMemoryDataSource$Instream.read(ManagedMemoryDataSource.java:688)
> Having run this throught a debugger and had a brief look at the code it seems
> to me there is a race condition of sorts.
> The MemoryManagedDataSource that provides the InputStream has been marked as
> deleted by the finalize method of AttachmentPart.
> So basically if the client doesn't read off the attachment fast enough then
> the writer will have finished and the AttachmentPart gets finalized and blam,
> you've got a deleted MemoryManagedDataSource.
> I'm not sure what the best fix is. Perhaps the deletion should actually be
> some reference count rather than a simple boolean. That way the
> MemoryManagedDataSource gets deleted once all the writers and readers are
> done? Although perhaps then there would be an issue if the client was very
> slow to even open the attachment?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
