[
https://issues.apache.org/jira/browse/SHINDIG-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789963#comment-13789963
]
Henry Saputra commented on SHINDIG-1935:
----------------------------------------
Did setting DeferredElementNSImpl to the ignore list solve the warning issue?
Maybe we could just create simple cache for the DOM element in Guava cache
which just requires the object to be in the heap I believe.
> Add org.apache.xerces.dom.DeferredElementNSImpl to sizeoffilter.txt to have
> EH Cache ignore this class
> ------------------------------------------------------------------------------------------------------
>
> Key: SHINDIG-1935
> URL: https://issues.apache.org/jira/browse/SHINDIG-1935
> Project: Shindig
> Issue Type: Bug
> Affects Versions: 2.5.0, 2.5.1, 2.5.0-update1
> Reporter: Ryan Baxter
> Assignee: Ryan Baxter
> Attachments: org.apache.xerces.dom.DeferredElementNSImpl.txt
>
>
> When rendering a gadget I am seeing a warning from EH Cache saying it had
> exceeded the 1000 object limit when traversing the object graph. After
> enabling additional EH Cache logging it looks like the class
> org.apache.xerces.dom.DeferredElementNSImpl has a pretty big object graph. I
> believe this class is used to represent DOM elements so it could be that the
> HTML for the gadget is fairly large making the object graph representing one
> of the elements pretty large as well. I think it is safe to ignore this
> class since classing the Java Object representation of the HTML is not as
> important as caching the HTML itself. I have attached the EH Cache debug
> with the details of the object graph.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
