Excellent. I downloaded the latest JAVA update and the problem is gone. Thanks a lot!
--- On Fri, 3/19/10, Andreas Veithen <[email protected]> wrote: From: Andreas Veithen <[email protected]> Subject: Re: Axiom exception To: [email protected] Date: Friday, March 19, 2010, 10:58 PM Mats, This is actually a bug in Sun's StAX implementation [1]. You have several options to work around this: 1. If you are using the StAX implementation that comes with Java 1.6, try to upgrade to a more recent version. 2. Use Woodstox [2]: this is the recommended StAX implementation for Axiom. If you are currently using the StAX implementation form the JRE, just add the Woodstox JARs to the classpath. If you have SJSXP in your classpath, replace it by Woodstox. 3. Try with a snapshot version of Axiom [3]. In the current trunk, we have implemented a feature that deals with broken parsers. In particular, Axiom now has a workaround for this particular issue in SJSXP. Andreas [1] https://sjsxp.dev.java.net/issues/show_bug.cgi?id=28 [2] http://woodstox.codehaus.org/ [3] http://people.apache.org/maven-snapshot-repository/org/apache/ws/commons/axiom/ On Fri, Mar 19, 2010 at 20:55, Mats Eklund <[email protected]> wrote: > Well, it was the first time I tried this code. No heavy load. I would say > it's predictable. > > Any idea? I did find one other similar report on the web, but no answer. > > --- On Fri, 3/19/10, Andreas Veithen <[email protected]> wrote: > > From: Andreas Veithen <[email protected]> > Subject: Re: Axiom exception > To: [email protected] > Date: Friday, March 19, 2010, 8:42 PM > > Mats, > > Is this exception predictable or does it occur randomly under heavy load? > > Andreas > > On Thu, Mar 18, 2010 at 23:07, Mats Eklund <[email protected]> wrote: >> Resending... >> >> --- On Thu, 3/18/10, Mats Eklund <[email protected]> wrote: >> >> From: Mats Eklund <[email protected]> >> Subject: Axiom exception >> To: [email protected] >> Date: Thursday, March 18, 2010, 11:06 PM >> >> Hi, >> >> When calling OMElement.serialize(...), an exception is thrown with the >> following stack trace: >> >> java.lang.NullPointerException >> >> com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.getProperty(Unknown >> Source) >> >> org.apache.axiom.om.impl.MTOMXMLStreamWriter.getProperty(MTOMXMLStreamWriter.java:291) >> >> org.apache.axiom.om.impl.util.OMSerializerUtil.isSetPrefixBeforeStartElement(OMSerializerUtil.java:187) >> >> org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializerUtil.java:274) >> >> org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializerUtil.java:228) >> >> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:949) >> >> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:937) >> org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:387) >> moe.exist.atom.modules.Batch.doPost(Batch.java:179) >> org.exist.atom.modules.AtomModuleBase.process(AtomModuleBase.java:55) >> org.exist.atom.http.AtomServlet.service(AtomServlet.java:445) >> javax.servlet.http.HttpServlet.service(HttpServlet.java:729) >> >> org.securityfilter.filter.SecurityFilter.doFilter(SecurityFilter.java:165) >> moe.revproxyauthfilter.RPAFilter.doFilter(RPAFilter.java:67) >> >> What am I missing here? >> >> Thanks, >> Mats >> >> >> >> >> >> >> > > > >
