Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <1590209543.1225781924404.JavaMail.jira@brutus>
Date: Mon, 3 Nov 2008 22:58:44 -0800 (PST)
From: "Jochen Wiedmann (JIRA)" <axis-dev@ws.apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Resolved: (AXIS-2574) Reading an attachment (slowly) can
 cause resource deleted error
In-Reply-To: <3114927.1161253055073.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AXIS-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Wiedmann resolved AXIS-2574.
-----------------------------------

    Resolution: Fixed
      Assignee: Jochen Wiedmann

Applied to the Axis trunk.


> 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.


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