You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Kannan Jayaprakasam <ka...@arcot.com> on 2010/08/13 17:25:35 UTC
DataHandler for mime attachment returns junk data
It was a perfectly working code and I haven't touched anything. But all of a sudden datahandler in the axis2 webservice for the mime attachment is always returning a junk of 9 characters. The SOAP client is sending a 75 KB attachment.
DataHandler dh = doc.getBase64Binary(); (doc is a ContentDocument)
outputStream = new ByteArrayOutputStream();
dh.writeTo(outputStream);
I'm completely clueless; I have monitored the HTTP traffic and verified that a valid attachment is indeed getting sent, and its CID is correctly referenced for the attachment in the SOAP body.
Has anyone faced this bizarre problem and how to go about it?
In the past I have noticed that the datahandler would return a junk if the CID was referenced in the SOAP body but no mime attachment with that CID actually was received. But in my setup the mime attachment indeed is being sent.
Thanks.
kannan
RE: DataHandler for mime attachment returns junk data
Posted by Kannan Jayaprakasam <ka...@arcot.com>.
That bug doesn’t seem to be what I’m facing. The same content attachment file used to work in the past.
I did catch the HTTP traffic (attached).
Thanks
Kannan
________________________________
From: Yogesh.Dhake@mizuhocbus.com [mailto:Yogesh.Dhake@mizuhocbus.com]
Sent: Friday, August 13, 2010 9:30 PM
To: java-user@axis.apache.org
Subject: Re: DataHandler for mime attachment returns junk data
Please see https://issues.apache.org/jira/browse/WSCOMMONS-328
Check if this size specific issue. we faced it earlier but we got extra CRLF only not a junk.
If possible post your SOAP message using tcpmon.
Regards
Yogesh Dhake
Desk - 201 626 9623
Kannan Jayaprakasam <ka...@arcot.com>
08/13/2010 11:26 AM
Please respond to
java-user@axis.apache.org
To
"java-user@axis.apache.org" <ja...@axis.apache.org>
cc
Subject
DataHandler for mime attachment returns junk data
It was a perfectly working code and I haven’t touched anything. But all of a sudden datahandler in the axis2 webservice for the mime attachment is always returning a junk of 9 characters. The SOAP client is sending a 75 KB attachment.
DataHandler dh = doc.getBase64Binary(); (doc is a ContentDocument)
outputStream = new ByteArrayOutputStream();
dh.writeTo(outputStream);
I’m completely clueless; I have monitored the HTTP traffic and verified that a valid attachment is indeed getting sent, and its CID is correctly referenced for the attachment in the SOAP body.
Has anyone faced this bizarre problem and how to go about it?
In the past I have noticed that the datahandler would return a junk if the CID was referenced in the SOAP body but no mime attachment with that CID actually was received. But in my setup the mime attachment indeed is being sent.
Thanks.
kannan
________________________________
This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group ("Mizuho"). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained.
E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information.
If you have any questions, or if you no longer wish to receive e-mail in accordance with Japanese Act on Regulation of the Transmission of Specified Electronic Mail, please contact the sender of this e-mail.
お問い合わせまたは特定電子メール法に 基づく送信停止のご要望等は、本電子メールの送信者にその旨ご連絡ください。
Re: DataHandler for mime attachment returns junk data
Posted by Yo...@mizuhocbus.com.
Please see https://issues.apache.org/jira/browse/WSCOMMONS-328
Check if this size specific issue. we faced it earlier but we got extra
CRLF only not a junk.
If possible post your SOAP message using tcpmon.
Regards
Yogesh Dhake
Desk - 201 626 9623
Kannan Jayaprakasam <ka...@arcot.com>
08/13/2010 11:26 AM
Please respond to
java-user@axis.apache.org
To
"java-user@axis.apache.org" <ja...@axis.apache.org>
cc
Subject
DataHandler for mime attachment returns junk data
It was a perfectly working code and I haven’t touched anything. But all of
a sudden datahandler in the axis2 webservice for the mime attachment is
always returning a junk of 9 characters. The SOAP client is sending a 75
KB attachment.
DataHandler dh = doc.getBase64Binary(); (doc is a ContentDocument)
outputStream = new ByteArrayOutputStream();
dh.writeTo(outputStream);
I’m completely clueless; I have monitored the HTTP traffic and verified
that a valid attachment is indeed getting sent, and its CID is correctly
referenced for the attachment in the SOAP body.
Has anyone faced this bizarre problem and how to go about it?
In the past I have noticed that the datahandler would return a junk if the
CID was referenced in the SOAP body but no mime attachment with that CID
actually was received. But in my setup the mime attachment indeed is being
sent.
Thanks.
kannan
======================================================================================================
This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group ("Mizuho"). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained.
E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information.
If you have any questions, or if you no longer wish to receive e-mail in accordance with Japanese Act on Regulation of the Transmission of Specified Electronic Mail, please contact the sender of this e-mail.
お問い合わせまたは特定電子メール法に 基づく送信停止のご要望等は、本電子メールの送信者にその旨ご連絡ください。