You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Edwanji <Au...@landisgyr.com> on 2009/12/21 20:32:10 UTC

java.lang.NullPointerException at net.sf.saxon.event.ReceivingContentHandler.getNameCode

I am experimenting with building a SOAP bridge with ServiceMix 3.3.1, but I
am running into a problem with a Saxon XSLT endpoint.  I have implemented
two others in the same project with no problems, but this one produces an
error.  
It looks like jira SM-819 which was supposedly fixed a year ago.  It doesn't
occur when I have logging set to DEBUG, only when it's set to INFO.  Is
there some update I need to get which includes the fix?

Exception log:

ERROR - SaxonComponent                 - Error processing exchange InOut[
  id: ID:127.0.1.1-125a359d9af-23:622
  status: Active
  role: provider
  service: {urn:com:zippy:binstream:collector}PlcCollectorService
  endpoint: MessageToSpu
  in: <?xml version="1.0" encoding="UTF-8"?><Message
xmlns="urn:com:zippy:binstream:collector"
MessageType="PlcCommand_GV"><Source>Command</Source><Destination>Collector:FROGSPU</Destination><SendDate>2009-12-21T17:23:58.7248979Z</SendDate><MessageId>Command_14907</MessageId></Message>
  out: null
]
java.lang.NullPointerException
	at
net.sf.saxon.event.ReceivingContentHandler.getNameCode(ReceivingContentHandler.java:407)
	at
net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingContentHandler.java:331)
	at
org.apache.servicemix.soap.util.stax.StaxSource.parse(StaxSource.java:115)
	at
org.apache.servicemix.soap.util.stax.StaxSource.parse(StaxSource.java:230)
	at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:404)
	at net.sf.saxon.event.Sender.send(Sender.java:193)
	at net.sf.saxon.event.Sender.send(Sender.java:50)
	at net.sf.saxon.Controller.transform(Controller.java:1611)
	at
org.apache.servicemix.saxon.XsltEndpoint.transformContent(XsltEndpoint.java:128)
	at
org.apache.servicemix.saxon.XsltEndpoint.transform(XsltEndpoint.java:101)
	at
org.apache.servicemix.saxon.SaxonEndpoint.processInOut(SaxonEndpoint.java:237)
	at
org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:111)
	at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:627)
	at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:581)
	at
org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java:535)
	at
org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.java:60)
	at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:623)
	at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:172)
	at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:168)
	at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
	at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:636)

-- 
View this message in context: http://old.nabble.com/java.lang.NullPointerException-at-net.sf.saxon.event.ReceivingContentHandler.getNameCode-tp26878748p26878748.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Re: java.lang.NullPointerException at net.sf.saxon.event.ReceivingContentHandler.getNameCode

Posted by Edwanji <Au...@landisgyr.com>.
Sorry this took me so long to get back.  Christmas vacation came up fast.

I can't load my SA into the 3.3.2 snapshot, because apparently something has
changed in xbeans:
ERROR - JmsComponent                   -
org.springframework.beans.factory.BeanDefinitionStoreException: Unrecognized
xbean namespace mapping: http://activemq.org/config/1.0

However, in trying to produce a minimal SA with which to test this, I
narrowed down the problem, or at least the symptoms.  The error doesn't
occur if I send the input file directly to the Saxon XSLT component. It only
happens if I send it through a message queue first.  I've produced a SA
which will read from two folders. One will send the file through a message
queue, the other sends it directly to the pipeline which pushes it through
the XSLT then to an output folder.  The input and output folders are
[ServiceMix]/tmp/CauseError, NoError, and ResultFiles. 

I'm sending the Maven project, since the jar it produces is over 4 MB, due
to the inclusion of some other JARs for no apparent reason...  I'm also
including the test file, and the expected result.

http://old.nabble.com/file/p27026734/ServiceTest.zip ServiceTest.zip 

Hopefully that upload thing works...


-- 
View this message in context: http://old.nabble.com/java.lang.NullPointerException-at-net.sf.saxon.event.ReceivingContentHandler.getNameCode-tp26878748p27026734.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Re: java.lang.NullPointerException at net.sf.saxon.event.ReceivingContentHandler.getNameCode

Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,

It looks like the same bug indeed - the version you have is supposed
to already have this fix.  Just to make sure, you can try to download
the latest 3.3.2-SNAPSHOT build from
https://repository.apache.org/content/repositories/snapshots/org/apache/servicemix/apache-servicemix/3.3.2-SNAPSHOT/
and give that a go, but I suspect you'll run into the same issue
(don't see any relevant commits/changes)

 Do you think you can create a SA that contains the failing conversion
that we can use to test with?  That would significantly ease the
process of fixing this.

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



2009/12/21 Edwanji <Au...@landisgyr.com>:
>
> I am experimenting with building a SOAP bridge with ServiceMix 3.3.1, but I
> am running into a problem with a Saxon XSLT endpoint.  I have implemented
> two others in the same project with no problems, but this one produces an
> error.
> It looks like jira SM-819 which was supposedly fixed a year ago.  It doesn't
> occur when I have logging set to DEBUG, only when it's set to INFO.  Is
> there some update I need to get which includes the fix?
>
> Exception log:
>
> ERROR - SaxonComponent                 - Error processing exchange InOut[
>  id: ID:127.0.1.1-125a359d9af-23:622
>  status: Active
>  role: provider
>  service: {urn:com:zippy:binstream:collector}PlcCollectorService
>  endpoint: MessageToSpu
>  in: <?xml version="1.0" encoding="UTF-8"?><Message
> xmlns="urn:com:zippy:binstream:collector"
> MessageType="PlcCommand_GV"><Source>Command</Source><Destination>Collector:FROGSPU</Destination><SendDate>2009-12-21T17:23:58.7248979Z</SendDate><MessageId>Command_14907</MessageId></Message>
>  out: null
> ]
> java.lang.NullPointerException
>        at
> net.sf.saxon.event.ReceivingContentHandler.getNameCode(ReceivingContentHandler.java:407)
>        at
> net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingContentHandler.java:331)
>        at
> org.apache.servicemix.soap.util.stax.StaxSource.parse(StaxSource.java:115)
>        at
> org.apache.servicemix.soap.util.stax.StaxSource.parse(StaxSource.java:230)
>        at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:404)
>        at net.sf.saxon.event.Sender.send(Sender.java:193)
>        at net.sf.saxon.event.Sender.send(Sender.java:50)
>        at net.sf.saxon.Controller.transform(Controller.java:1611)
>        at
> org.apache.servicemix.saxon.XsltEndpoint.transformContent(XsltEndpoint.java:128)
>        at
> org.apache.servicemix.saxon.XsltEndpoint.transform(XsltEndpoint.java:101)
>        at
> org.apache.servicemix.saxon.SaxonEndpoint.processInOut(SaxonEndpoint.java:237)
>        at
> org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:111)
>        at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:627)
>        at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:581)
>        at
> org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java:535)
>        at
> org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.java:60)
>        at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:623)
>        at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:172)
>        at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:168)
>        at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>        at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>        at java.lang.Thread.run(Thread.java:636)
>
> --
> View this message in context: http://old.nabble.com/java.lang.NullPointerException-at-net.sf.saxon.event.ReceivingContentHandler.getNameCode-tp26878748p26878748.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>