You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commons-dev@ws.apache.org by "Ajith Harshana Ranabahu (JIRA)" <ji...@apache.org> on 2007/10/22 18:57:50 UTC

[jira] Commented: (WSCOMMONS-223) OOM in Axis2 - AXIS2-2968

    [ https://issues.apache.org/jira/browse/WSCOMMONS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536743 ] 

Ajith Harshana Ranabahu commented on WSCOMMONS-223:
---------------------------------------------------

I see the original issue being marked as fixed. However this patch has not been commited. Any idea whether we should go ahead with this change ?

> OOM in Axis2 - AXIS2-2968
> -------------------------
>
>                 Key: WSCOMMONS-223
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-223
>             Project: WS-Commons
>          Issue Type: Bug
>          Components: XmlSchema
>            Reporter: Davanum Srinivas
>            Assignee: Ajith Harshana Ranabahu
>         Attachments: oom.diff
>
>
> As mentioned in AXIS2-2968, XmlSchema seems to hang onto original DOM objects. See enclosed patch that reduces this behavior.

-- 
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: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org