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 "Roy Willy Haug (JIRA)" <ji...@apache.org> on 2008/04/01 10:02:24 UTC
[jira] Created: (AXIS2-3686) Attachments larger than
Integer.MAX_VALUE (appr 2.1GB) fails
Attachments larger than Integer.MAX_VALUE (appr 2.1GB) fails
------------------------------------------------------------
Key: AXIS2-3686
URL: https://issues.apache.org/jira/browse/AXIS2-3686
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.3
Reporter: Roy Willy Haug
Fix For: 1.4
We have a well working file transfer service that works with files up to approximately 2.1 GB (probably Integer.MAX_VALUE: 2147483647 bytes?).
When transferring even larger files, Axis2 fails with the following message:
org.apache.axis2.AxisFault: Referenced Attachment not found in the MIME Message. ContentID:1.urn:uuid:A5D5C69F8A5ED5E2571206965262714@apache.org
What happens is:
The client transfers the complete file to the server.
The server correctly caches the file in the attachmentDIR folder.
The AxisFault is thrown.
The server-side cached file have the exact same byte-length as the file the client sent, so every byte has been transferred.
I am currently using Windows XP with NTFS and support for files much larger than 2.1 GB on both sides, Axis2 1.3, Tomcat 5.5.x, document-literal style, ADB, MTOM and caching to disk.
The DataHandler that is supplied to the client stub is generated like this:
FileDataSource datasource = new FileDataSource(localFile);
dh = new DataHandler(datasource);
Parts of my Axis2.xml file:
<parameter name="enableMTOM">true</parameter>
<parameter name="enableSwA">false</parameter>
<parameter name="cacheAttachments">true</parameter>
<parameter name="attachmentDIR">C:/TEMP/da_server_temp/</parameter>
<parameter name="sizeThreshold">50000</parameter>
Axis2 mailing list answers to my question:
On Mon, Mar 31, 2008 at 12:01 PM, Andreas Veithen <andreas veithen a t s k y n e t b e> wrote:
> Roy,
>
> This seems to be a limitation of AXIOM that uses the int type for all
> length variables in the org.apache.axiom.attachments.Attachments class
> and various other classes it depends on.
>
> Regards,
>
> Andreas
>
And:
> From: Thilina Gunarathne [csethil g m a i l c o m ]
> Sent: 1. april 2008 00:29
> To: axis-user@ws.apache.org
> Subject: Re: MTOM attachments larger than 2.1GB (Integer.MAX_VALUE?)
>
> Please log a Jira with all these details...
>
> I think the fix needs start from the FileAccessor getSize() onwards..
>
> thanks,
> Thilina
--
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
[jira] Resolved: (AXIS2-3686) Attachments larger than
Integer.MAX_VALUE (appr 2.1GB) fails
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas resolved AXIS2-3686.
-------------------------------------
Resolution: Fixed
looks like the underlying issue in axiom is already fixed. Please try latest svn of axis2 and axiom
thanks,
dims
> Attachments larger than Integer.MAX_VALUE (appr 2.1GB) fails
> ------------------------------------------------------------
>
> Key: AXIS2-3686
> URL: https://issues.apache.org/jira/browse/AXIS2-3686
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Roy Willy Haug
> Fix For: 1.4
>
>
> We have a well working file transfer service that works with files up to approximately 2.1 GB (probably Integer.MAX_VALUE: 2147483647 bytes?).
> When transferring even larger files, Axis2 fails with the following message:
> org.apache.axis2.AxisFault: Referenced Attachment not found in the MIME Message. ContentID:1.urn:uuid:A5D5C69F8A5ED5E2571206965262714@apache.org
> What happens is:
> The client transfers the complete file to the server.
> The server correctly caches the file in the attachmentDIR folder.
> The AxisFault is thrown.
> The server-side cached file have the exact same byte-length as the file the client sent, so every byte has been transferred.
> I am currently using Windows XP with NTFS and support for files much larger than 2.1 GB on both sides, Axis2 1.3, Tomcat 5.5.x, document-literal style, ADB, MTOM and caching to disk.
> The DataHandler that is supplied to the client stub is generated like this:
> FileDataSource datasource = new FileDataSource(localFile);
> dh = new DataHandler(datasource);
>
> Parts of my Axis2.xml file:
> <parameter name="enableMTOM">true</parameter>
> <parameter name="enableSwA">false</parameter>
> <parameter name="cacheAttachments">true</parameter>
> <parameter name="attachmentDIR">C:/TEMP/da_server_temp/</parameter>
> <parameter name="sizeThreshold">50000</parameter>
> Axis2 mailing list answers to my question:
> On Mon, Mar 31, 2008 at 12:01 PM, Andreas Veithen <andreas veithen a t s k y n e t b e> wrote:
> > Roy,
> >
> > This seems to be a limitation of AXIOM that uses the int type for all
> > length variables in the org.apache.axiom.attachments.Attachments class
> > and various other classes it depends on.
> >
> > Regards,
> >
> > Andreas
> >
> And:
> > From: Thilina Gunarathne [csethil g m a i l c o m ]
> > Sent: 1. april 2008 00:29
> > To: axis-user@ws.apache.org
> > Subject: Re: MTOM attachments larger than 2.1GB (Integer.MAX_VALUE?)
> >
> > Please log a Jira with all these details...
> >
> > I think the fix needs start from the FileAccessor getSize() onwards..
> >
> > thanks,
> > Thilina
--
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