[
https://issues.apache.org/jira/browse/CXF-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-1972.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.3
2.1.6
Assignee: Daniel Kulp
Implemented a workaround to lock the attachments and cache them.
> cannot send MTOM attachment over 64K when server schema validation on
> ---------------------------------------------------------------------
>
> Key: CXF-1972
> URL: https://issues.apache.org/jira/browse/CXF-1972
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.1.3
> Environment: RedHat Linux 2.6.9-42.ELsmp
> Reporter: Lisa Penninger
> Assignee: Daniel Kulp
> Fix For: 2.1.6, 2.2.3
>
> Attachments: Server.java, stack.txt
>
>
> I'm using MTOM with CXF 2.1.3 to send an attachment to the server, with
> validation turned on in the server. Everything is working fine, as long as
> the attachment data is 64K or less. One byte over 64K, and the stream
> returned by getDataSource().getInputStream() is empty. The stream is created
> okay with all the data, but in DocLiteralInInterceptor.handleMessage it
> eventually calls Base64Data.get, which does a close on the stream. This is
> only a problem if the stream is a FileInputStream, which it will be if the
> data is over 64K, and this particular codepath is only taken if validation is
> turned on. I've been able to reproduce this with the mtom sample code. I
> will attach my changes to Server.java to turn on validation, and the stack
> trace showing where the problem occurs.
> Thanks, Lisa
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
