[
https://issues.apache.org/jira/browse/AXIS2C-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565966#action_12565966
]
Dave Meier commented on AXIS2C-941:
-----------------------------------
Hi Senaka,
I have reproduced the same problem using the mtom sample.
Steps:
1. Build Axis2C in release (non-debug) mode.
2. Turn on mtom in the axis2.xml in the deploy folder.
3. Set up IIS to point to the release mode deploy folder and follow all the
other IIS module instructions.
4. Start IIS.
5. Run the mtom sample with a small file to make sure that works to ensure
everything is set up correctly.
I used "mtom http://localhost/axis2/services/mtom math.exe davemath.exe
do_not_optimize"
This was successful and I found the "davemath.exe" file in my deploy/lib
directory.
6. Now run the mtom sample again with a 163KB or larger file. I used a pdf
file I test with.
Command was "mtom http://localhost/axis2/services/mtom tt.pdf ttdave.pdf
do_not_optimize" where tt.pdf is 163KB.
It fails on step 6 with either "mtom client invoke FAILED!" or a message saying
the element was NULL.
> IIS Module: fails with large data element
> -----------------------------------------
>
> Key: AXIS2C-941
> URL: https://issues.apache.org/jira/browse/AXIS2C-941
> Project: Axis2-C
> Issue Type: Bug
> Components: transport/http
> Affects Versions: Current (Nightly)
> Environment: Windows XP, IIS 5.1
> Reporter: Dave Meier
> Attachments: aewebservicesaxis70.wsdl
>
>
> I have a web service that takes the following as input. Here is the wsdl:
> <complexType name="FileAttachmentContents">
> <complexContent>
> <extension base="ae:FileAttachment">
> <sequence>
> <element name="checksum" type="xsd:long" minOccurs="1" maxOccurs="1"/>
> <element name="encodedContents" type="xsd:base64Binary" minOccurs="1"
> maxOccurs="1" nillable="false"/>
> </sequence>
> </extension>
> </complexContent>
> </complexType>
> With the axis2_http_server.exe it works fine with a 163KB file, where the
> contents of the file are written in base64 into the "encodedContents"
> element. But when I run the IIS module and run the same client test, I get
> back an error saying that the "encodedContents" element is NULL.
> I tried a 1KB file with the IIS module and that worked great. So there
> appears to be something limiting the sending of a large element when using
> the IIS module.
--
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]
