[
https://issues.apache.org/jira/browse/SYNAPSE-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468430#comment-13468430
]
Amila Chinthaka Suriarachchi commented on SYNAPSE-913:
------------------------------------------------------
Here is the exception I get.
2012-10-03 14:26:15,496 [-] [PassThroughMessageProcessor-2] ERROR
NativeWorkerPool Uncaught exception
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxEOFException: Unexpected
EOF; was expecting a close tag for element <emulov>
at [row,col {unknown-source}]: [4,788]
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:276)
at
org.apache.axiom.om.impl.llom.OMContainerHelper.buildNext(OMContainerHelper.java:162)
at
org.apache.axiom.om.impl.llom.OMNodeHelper.getNextOMSibling(OMNodeHelper.java:38)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.getNextOMSibling(OMNodeImpl.java:106)
at
org.apache.axiom.om.impl.traverse.OMChildrenIterator.getNextNode(OMChildrenIterator.java:36)
at
org.apache.axiom.om.impl.traverse.OMAbstractIterator.hasNext(OMAbstractIterator.java:69)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:555)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:790)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:556)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:790)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:556)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:790)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:556)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:790)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:218)
at
org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:97)
at
org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:85)
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:901)
at java.lang.String.valueOf(String.java:2826)
at java.lang.StringBuffer.append(StringBuffer.java:219)
at
org.apache.synapse.mediators.builtin.LogMediator.getFullLogMessage(LogMediator.java:184)
at
org.apache.synapse.mediators.builtin.LogMediator.getLogMessage(LogMediator.java:123)
at
org.apache.synapse.mediators.builtin.LogMediator.mediate(LogMediator.java:91)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:70)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:114)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:227)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:370)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:160)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:169)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:191)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:173)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF; was expecting a
close tag for element <emulov>
at [row,col {unknown-source}]: [4,788]
at
com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:677)
at
com.ctc.wstx.sr.BasicStreamReader.throwUnexpectedEOF(BasicStreamReader.java:5478)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2697)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1062)
at
org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
at
org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:34)
at
org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:646)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:189)
... 33 more
I beleve the problem is not building the message at the response path. Will
have a look.
> Pass Through HTTP Transport for Synapse and Using the Pass Through Transport
> by Default
> ---------------------------------------------------------------------------------------
>
> Key: SYNAPSE-913
> URL: https://issues.apache.org/jira/browse/SYNAPSE-913
> Project: Synapse
> Issue Type: Improvement
> Components: Core, Transports
> Environment: Any
> Reporter: Hiranya Jayathilaka
> Fix For: FUTURE
>
> Attachments: SYNAPSE_PASS_THRU_8.patch
>
>
> This improvement has 2 main aspects:
> 1. Contributing the pass through HTTP transport developed at WSO2 to Synapse
> 2. Modifying Synapse to use the pass through HTTP transport as the default
> (this requires some minor changes to the transport too)
> The pass through transport, as it stands now, can only be used for simple
> pass through, static routing and header based routing scenarios. It cannot be
> used for any scenario where content lookup or manipulation is required. This
> effort makes the pass through transport one of the core transports of
> Synapse, and modifies Synapse and the transport in a way so that the
> transport can be used in any scenario without restrictions.
> See the conversations at:
> http://old.nabble.com/Message-Relay-Support-for-Synapse-to33693068.html
> http://mail-archives.apache.org/mod_mbox/synapse-dev/201209.mbox/browser
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
