[
https://issues.apache.org/jira/browse/XALANJ-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529603
]
Brian Minchau commented on XALANJ-2398:
---------------------------------------
Shereef, while both SUN and IBM repackage Xalan I don't know how you can know
that SUN's code is just a copy of the Apache classes, unless you work for SUN.
While I admit that the performance problem may be the same for Apache, there is
the possiblitity that it isn't the same, especially if SUN did something to
"improve" SAX2DOM. Perhaps fixing a bug in SAX2DOM with a side effect of
slowing it down. Who knows. In any case we can't persue this unless the
Apache code is used.
Michael G. : it is interesting that you point to a change in SAX2DOM in Apache
as being a possible culprit here. Is that just a guess?
> parsing big XMLs take very long time. A JAXRPC webservice request of soap
> size 2MB takes above 5 mins to complete parsing and start processing web
> service.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: XALANJ-2398
> URL: https://issues.apache.org/jira/browse/XALANJ-2398
> Project: XalanJ2
> Issue Type: Bug
> Components: transformation
> Environment: Operating System: All
> Platform: All
> Reporter: SHEREEF ABDULLA
> Attachments: JaxRPCProcessRequest.java, WrkingBigSOAP.txt
>
>
> parsing bix XMLs take very long time. A JAXRPC webservice request of soap
> size 2MB takes above 5 mins to complete parsing and start processing web
> service.
> Observed that the SOAP messages are read line by line and
> CharacterDataImpl.append() is getting called for each line. This appends each
> line to the string data which stores the previously read xml part. This call
> results in many string additions (say 20000+ for 1MB SOAP) of big string and
> the thread is most of the time blocked in StringBuilder.expandcapacity due to
> long string additions.
> JAX RPC webservice with SOAP messages bigger than 1MB take 5 mins and more
> just for the web service implementation to start working as the jaxrpc does a
> SOAPMessage.getenvelop call to do HandlerChainImpl.checkMustUnderstand()
> checking for the request message header. Same problem happens for response
> also. for time being we commented checkMustUnderstand method so that the
> parsing doesn't happen at all.
> String additions for each of the lines would have been avoided, either by
> creating the whole data single time or using string buffer instead of string.
> I tried to modify the data field to use StringBuffer instead of String but
> the underlying CoreDocumentImpl.modifiedCharacterData() and all underlying
> calls takes the string params so couldn't go ahead with it.
> bug # XERCESJ-102 looks like the same issue..
--
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]
