[
https://issues.apache.org/jira/browse/AXIS-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS-2813:
----------------------------------
Priority: Major (was: Blocker)
> getAttachmentsCount() in AttachmentsImpl takes too much time even if there is
> no attachment...
> ----------------------------------------------------------------------------------------------
>
> Key: AXIS-2813
> URL: https://issues.apache.org/jira/browse/AXIS-2813
> Project: Axis
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Java 1.5
> Reporter: Neeraj
> Fix For: 1.4.1
>
>
> The SOAP response takes too much of time while being processed by the AXIS at
> server side. I have debugged into the source and found that in getContentType
> of Message, mAttachments.getAttachmentCount() in following code takes too
> much of time.
> if (getSendType() != Attachments.SEND_TYPE_NONE && mAttachments !=
> null &&
> 0 != mAttachments.getAttachmentCount()) {
> ret = mAttachments.getContentType();
> }
> In AttachmentsImpl currentMessage is written to ByteArray Output Stream,
> which is taking too much of time. And since there is so attachment with the
> current message it is going to give 0 as count. I am wondering why should
> this happen in getAttachmentsCount().
> Total time taken to process the response by AXIS at server side is around 70
> seconds out of which around 30 seconds is taken while writting the message to
> Bytye Array Stream during getAttachmentsCount()
> Let me know if there is any workaround (or fix) to overcome this issue. Just
> to bypass from this, I tried overriding the AttachmentsImpl by mentioning
> the implemntation class in wsdd file but unfortunately default is being
> picked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
