You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2008/08/06 20:22:44 UTC
[jira] Resolved: (AXIS2-3965) JAXWS: Parser is not closed
[ https://issues.apache.org/jira/browse/AXIS2-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-3965.
-----------------------------------
Resolution: Fixed
683353
> JAXWS: Parser is not closed
> ---------------------------
>
> Key: AXIS2-3965
> URL: https://issues.apache.org/jira/browse/AXIS2-3965
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> History:
> Pull parsing requires that the last consumer closes the parser. We have had a number of defects related to failures in closing the parser. This leads to open resources and memory leakage.
> Problem:
> Sandy Kao has provided a fix for yet another scenario where the parser is not being closed.
> The patch is to the MessageImpl code in JAXWS:
> ByteArrayOutputStream outStream = new ByteArrayOutputStream();
> element.serialize(outStream);
>
> + // In some cases (usually inbound) the builder will not be closed after
> + // serialization. In that case it should be closed manually.
> + if (element.getBuilder() != null && !element.getBuilder().isCompleted()) {
> + element.close(false);
> + }
>
> byte[] bytes = outStream.toByteArray();
> I have tested and will commit the patch soon.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org