[
https://issues.apache.org/jira/browse/AXIS-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644661#action_12644661
]
Himanshu Arora commented on AXIS-2574:
--------------------------------------
Hi Jochen,
I'm new to patching, I did following but got exception.
D:\Projects\axis-src-1_4\axis-1_4\src\org\apache\axis\client>patch -d . -u -N
--verbose <axis-2574.patch
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|Index: src/org/apache/axis/client/Call.java
|===================================================================
|--- src/org/apache/axis/client/Call.java (revision 708095)
|+++ src/org/apache/axis/client/Call.java (working copy)
--------------------------
Patching file Call.java using Plan A...
Reversed (or previously applied) patch detected! Skipping patch.
Hunk #1 ignored at 62.
1 out of 1 hunk ignored -- saving rejects to file Call.java.rej
Hmm...missing header for unified diff at line 15 of patch
The next patch looks like a unified diff to me...
can't find file to patch at input line 15
Perhaps you should have used the -p or --strip option?
File to patch: Call.java
Patching file Call.java using Plan A...
Assertion failed: hunk, file ../patch-2.5.9-src/patch.c, line 354
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
------------------------------------------------------
Please help...
> 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
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
