[ http://issues.apache.org/jira/browse/AXIS2C-447?page=all ]
Samisa Abeysinghe updated AXIS2C-447:
-------------------------------------
Fix Version/s: 1.0.0
This issues reflects one of the areas that we have challenges in memory leak
management.
In case of REST invocations, this kind of a leak persists and the stax builder
becomes ophened.
We need to re-think the free model here.
> AXIOM_STAX_BUILDER_FREE releases built document
> -----------------------------------------------
>
> Key: AXIS2C-447
> URL: http://issues.apache.org/jira/browse/AXIS2C-447
> Project: Axis2-C
> Issue Type: Bug
> Components: xml/parser
> Affects Versions: Current (Nightly)
> Environment: Linux / simple_http_client
> Reporter: Marc Giger
> Fix For: 1.0.0
>
>
> In my webservice I build a document with the stax_builder (as in the
> documentation explained):
> builder = axiom_stax_builder_create(env, reader);
> document = AXIOM_STAX_BUILDER_GET_DOCUMENT(builder, env);
> payload = AXIOM_DOCUMENT_GET_ROOT_ELEMENT(document, env);
> AXIOM_DOCUMENT_BUILD_ALL(document, env);
> then I return the root node back to the client.
> If I call the Macro AXIOM_STAX_BUILDER_FREE to release the resources from
> stax_builder it releases
> the built document too, and the axis engine tries to serialize the freed
> OM-Tree.
> If I don't call AXIOM_STAX_BUILDER_FREE, I have memory leaks...
> Shouldn't the document be freed in a separate step if needed?
> Thanks
> Marc
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
