[ http://issues.apache.org/jira/browse/AXIS2-483?page=all ]
Srinath Perera updated AXIS2-483:
---------------------------------
Attachment: axis2_streaming_test.zip
Upload on behalf of the reporter
> Memory foot print on server is very high while streaming XML in Axis2
> ---------------------------------------------------------------------
>
> Key: AXIS2-483
> URL: http://issues.apache.org/jira/browse/AXIS2-483
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: om
> Versions: 0.94
> Environment: Windows XP, JDK 1.5.05
> Reporter: Lakshmi Chaparala
> Attachments: axis2_streaming_test.zip
>
> Our Axis2 service is currently implemented as suggested and the xml is
> streaming back to the client ok. The problem we're having is that the memory
> footprint on the server is larger than we'd like.
> We are creating a large xml result for a query in our Axis2 service
> implementation. So we end up with a large xml result in a
> ByteArrayOutputStream that we need to send back to the client. Using the
> standard implementation suggested below doubles the memory footprint on the
> server to create the OMElement that is returned by the service implementation
> method. We'd like to be able to send the xml we have in memory over the wire
> without creating the OMElment objects. Even better, we'd like to start
> streaming back the xml result as it is being created. Is there any way to
> implement an Axis2 service that either has OMElement caching off when it
> streams back to the client or streams a result back to the client as it is
> being created?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
