Re: Random errors with saxon.dom.DOMSender in v2008.01

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Random errors with saxon.dom.DOMSender in v2008.01

Jean-Baptiste Onofré
I think the error is the same as an underlying component uses saxon (I guess
validation maybe).

I take a look on the SM-1184 to see if I can do something.

Regards
JB
--
Jean-Baptiste Onofré
[hidden email]
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net

On Wed 17/12/08 17:11, avermout [hidden email] wrote:
>
> Hello,
>
> I have a Servicemix project using http, ftp, validation, camel and
> bean
components (all 2008.01), and servicemix 3.3, deployed under jboss
> 4.2.3GA.
> When I run some xml messages in my system, I sometimes got random
> errors
(see below). In fact, the errors are quite the same as SM-1184, but I
> don't
use saxon component. Like in the SM-1184, when I run the same XML file
> many
times, I don't always have an error.

>
> Can anyone help?
>
> Thanks very much!
>
>
> 1)
> java.lang.NullPointerException
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:138)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.send(DOMSender.java:97)
> at
> net.sf.saxon.dom.DOMObjectModel.sendSource(DOMObjectModel.java:255)
> at net.sf.saxon.event.Sender.send(Sender.java:243)
> at
> net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:30)
at
> com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.process(Va
> lidatorImpl.java:220)
at
> com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(V
> alidatorImpl.java:141)
at
> org.apache.servicemix.validation.ValidationEndpoint.doValidation(Validation
> Endpoint.java:294)
at
> org.apache.servicemix.validation.ValidationEndpoint.startValidation(Validat
> ionEndpoint.java:201)
at
> org.apache.servicemix.validation.ValidationEndpoint.processInOut(Validation
> Endpoint.java:164)
at
> org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEnd
> point.java:111)
at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycl
> e.java:600)
at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLi
> feCycle.java:554)
at
> org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBase
> LifeCycle.java:510)
at
> org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLif
> eCycleWrapper.java:60)
at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(Deli
> veryChannelImpl.java:620)
at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java
> :172)
at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:16
> 8)
at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>
at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.j
> ava:650)
at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
> 675)
at java.lang.Thread.run(Thread.java:595)
> 2)
> java.lang.StackOverflowError
> at
> org.xml.sax.helpers.NamespaceSupport$Context.processName(NamespaceSupport.j
> ava:642)
at
> org.xml.sax.helpers.NamespaceSupport.processName(NamespaceSupport.java:341)
>
at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:185)

> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
> at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
> at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
>
>
> --
> View this message in context:
http://www.nabble.com/Random-errors-with-saxon.dom.DOMSender-in
> -v2008.01-tp21055379p21055379.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Random errors with saxon.dom.DOMSender in v2008.01

avermout
Hello,

did you find anything related with it?

However, I don't think it have to do with the validator. In my project, the problem sometimes occurs at different places.

The stackstrace is often the following (see below). But more strange, I once received a 'cyclic' XML like this, continuing infinitely. Does anyone see where it could come from?

Thanks very much

<r:Date>
<r:Century></r:Century> 
<r:Year></r:Year> 
</r:Date>
 <r:Address>
 <r:ZipCode>6043</r:ZipCode> 
 ...
 </r:Date>
  <r:Address>
  <r:ZipCode>6043</r:ZipCode> 
  ...
  </r:Date>
   <r:Address>
   <r:ZipCode>6043</r:ZipCode> 
   ...
    </r:Date>
    <r:Address>
    ...

java.lang.StackOverflowError
        at java.util.Hashtable.get(Hashtable.java:336)
        at org.xml.sax.helpers.NamespaceSupport$Context.processName(NamespaceSupport.java:642)
        at org.xml.sax.helpers.NamespaceSupport.processName(NamespaceSupport.java:341)
        at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:185)
        at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)
        at net.sf.saxon.dom.DOMSender.outputElement(DOMSender.java:228)
        at net.sf.saxon.dom.DOMSender.walkNode(DOMSender.java:145)


Jean-Baptiste Onofré wrote
I think the error is the same as an underlying component uses saxon (I guess
validation maybe).

I take a look on the SM-1184 to see if I can do something.

Regards
JB
--
Jean-Baptiste Onofré
jb@nanthrax.net
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net