On Wed, Jun 8, 2011 at 1:47 AM, Newman, John W <newma...@d3onc.com> wrote: > 1) Under very high load
What exactly is "high load" in your case? Is it number of users using your applications, number of threads sharing your objects or what? > an element will somehow lose nearly all of its children. This may be due to insufficient design within your application. You need to tell more about your application design and give us more specifics, for anyone to reason about the failures. > 2) Also under high load, I occasionally get this stack trace (this is > not the cause of or symptom of item 1, it is a separate issue occurring at > separate times) > java.lang.NullPointerException: > (no message) > at org.apache.xerces.dom.ParentNode.nodeListItem(Unknown Source) > at org.apache.xerces.dom.ParentNode.item(Unknown Source) > at freemarker.ext.dom.NodeListModel.<init>(NodeListModel.java:89) > at freemarker.ext.dom.NodeModel.getChildNodes(NodeModel.java:302) > at freemarker.ext.dom.ElementModel.get(ElementModel.java:124) > at freemarker.core.Dot._getAsTemplateModel(Dot.java:76) The null pointer originates from your framework/application classes (Dot.java -> ElementModel.java & so on). This may be an application issue. You may run a debug session to see, which object along this stack trace is null and on what data it is dependent on. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
