You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by "saket arora (JIRA)" <xm...@xml.apache.org> on 2009/10/03 18:09:23 UTC
[jira] Created: (XMLBEANS-415) Xobj$ElementXobj object going in
cyclic referance and not getting released .
Xobj$ElementXobj object going in cyclic referance and not getting released .
-----------------------------------------------------------------------------
Key: XMLBEANS-415
URL: https://issues.apache.org/jira/browse/XMLBEANS-415
Project: XMLBeans
Issue Type: Bug
Components: XmlObject
Affects Versions: Version 2.4
Environment: oracle weblogic 9.2, Jrockit 27, Xml beans 2.4 + axis webservices + org.codehaus.mojo maven plugin + dozer 4.1 + spring framework.
Reporter: saket arora
Hello
We are running our web application on weblogic jrockit and having serious memory leaks , after around 4 hrs of load testing memory of server (having java heap of 2 GB) goes down 100% and than never comes down (though session timing out )
In the JRMC control when we saw what all objects are hanging in memory , we found there is about 1.5 GB of memory eatan up by char array , when further inspected almost most of them are created by Xobj$ElementXobj which are having almost 40000 cyclic refernces . Objects of this class are pointing back to itself and are never getting garbage collected..
We are using lots of xml parsing vis factory.parse method of xmlobject . I am not sure where this xobj$ElementXobj is used by xml beans and we are cluelass why its growing so much ..
any help would be god send.
Thanks
Saket
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-415) Xobj$ElementXobj object going in
cyclic referance and not getting released .
Posted by "saket arora (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764487#action_12764487 ]
saket arora commented on XMLBEANS-415:
--------------------------------------
Hello Cezar
Thanks for your reply , we found out the issue , it was not an issue with XML beans , issue was with our ehcache implementation , our flushing mechanism was not working and this caused those objects to be in memory for ever. The problem was in annotation based caching provided by spring which was killing our system .
PS: Dont use annotation based caching module of spring.
Thanks again of your reply.
Cheers
Saket
> Xobj$ElementXobj object going in cyclic referance and not getting released .
> -----------------------------------------------------------------------------
>
> Key: XMLBEANS-415
> URL: https://issues.apache.org/jira/browse/XMLBEANS-415
> Project: XMLBeans
> Issue Type: Bug
> Components: XmlObject
> Affects Versions: Version 2.4
> Environment: oracle weblogic 9.2, Jrockit 27, Xml beans 2.4 + axis webservices + org.codehaus.mojo maven plugin + dozer 4.1 + spring framework.
> Reporter: saket arora
>
> Hello
> We are running our web application on weblogic jrockit and having serious memory leaks , after around 4 hrs of load testing memory of server (having java heap of 2 GB) goes down 100% and than never comes down (though session timing out )
> In the JRMC control when we saw what all objects are hanging in memory , we found there is about 1.5 GB of memory eatan up by char array , when further inspected almost most of them are created by Xobj$ElementXobj which are having almost 40000 cyclic refernces . Objects of this class are pointing back to itself and are never getting garbage collected..
> We are using lots of xml parsing vis factory.parse method of xmlobject . I am not sure where this xobj$ElementXobj is used by xml beans and we are cluelass why its growing so much ..
> any help would be god send.
> Thanks
> Saket
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Resolved: (XMLBEANS-415) Xobj$ElementXobj object going in
cyclic referance and not getting released .
Posted by "saket arora (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
saket arora resolved XMLBEANS-415.
----------------------------------
Resolution: Fixed
> Xobj$ElementXobj object going in cyclic referance and not getting released .
> -----------------------------------------------------------------------------
>
> Key: XMLBEANS-415
> URL: https://issues.apache.org/jira/browse/XMLBEANS-415
> Project: XMLBeans
> Issue Type: Bug
> Components: XmlObject
> Affects Versions: Version 2.4
> Environment: oracle weblogic 9.2, Jrockit 27, Xml beans 2.4 + axis webservices + org.codehaus.mojo maven plugin + dozer 4.1 + spring framework.
> Reporter: saket arora
>
> Hello
> We are running our web application on weblogic jrockit and having serious memory leaks , after around 4 hrs of load testing memory of server (having java heap of 2 GB) goes down 100% and than never comes down (though session timing out )
> In the JRMC control when we saw what all objects are hanging in memory , we found there is about 1.5 GB of memory eatan up by char array , when further inspected almost most of them are created by Xobj$ElementXobj which are having almost 40000 cyclic refernces . Objects of this class are pointing back to itself and are never getting garbage collected..
> We are using lots of xml parsing vis factory.parse method of xmlobject . I am not sure where this xobj$ElementXobj is used by xml beans and we are cluelass why its growing so much ..
> any help would be god send.
> Thanks
> Saket
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Updated: (XMLBEANS-415) Xobj$ElementXobj object going in
cyclic referance and not getting released .
Posted by "Cezar Andrei (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cezar Andrei updated XMLBEANS-415:
----------------------------------
Saket,
At this point there isn't a know bug in XMLBeans for this. From your description though there are XMLBeans objects in memory, your application or one of the libraries might keep hard references to XMLBeans objects, not allowing these objects to be collected. In order to look at this problem we'd need at least more data or a stand alone reproducer.
> Xobj$ElementXobj object going in cyclic referance and not getting released .
> -----------------------------------------------------------------------------
>
> Key: XMLBEANS-415
> URL: https://issues.apache.org/jira/browse/XMLBEANS-415
> Project: XMLBeans
> Issue Type: Bug
> Components: XmlObject
> Affects Versions: Version 2.4
> Environment: oracle weblogic 9.2, Jrockit 27, Xml beans 2.4 + axis webservices + org.codehaus.mojo maven plugin + dozer 4.1 + spring framework.
> Reporter: saket arora
>
> Hello
> We are running our web application on weblogic jrockit and having serious memory leaks , after around 4 hrs of load testing memory of server (having java heap of 2 GB) goes down 100% and than never comes down (though session timing out )
> In the JRMC control when we saw what all objects are hanging in memory , we found there is about 1.5 GB of memory eatan up by char array , when further inspected almost most of them are created by Xobj$ElementXobj which are having almost 40000 cyclic refernces . Objects of this class are pointing back to itself and are never getting garbage collected..
> We are using lots of xml parsing vis factory.parse method of xmlobject . I am not sure where this xobj$ElementXobj is used by xml beans and we are cluelass why its growing so much ..
> any help would be god send.
> Thanks
> Saket
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org