You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Jeff Peterson <j....@gmail.com> on 2008/12/01 05:53:20 UTC
Re: cxfbc provider :HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted!!!!???
Can you post the full stack trace?
- Jeff
On Fri, Nov 28, 2008 at 4:32 AM, Andrea Zoppello <zo...@tiscali.it> wrote:
> Thank you for the response,
>
> I've seen this, but is there a patch for this???
>
> raulvk.soa ha scritto:
>>
>> Andrea,
>>
>> There is a very similar thread from a few months ago. Check
>>
>> http://cwiki.apache.org/SM/discussion-forums.html#nabble-td19656853|a19667244.
>>
>> It is an issue related to whitespaces in the input message.
>>
>> I came across it when using soapUI but it is known to affect other use
>> cases
>> too.
>>
>> Hope that helps.
>>
>>
>> Andrea Zoppello-2 wrote:
>>
>>>
>>> Is there any fix for this???
>>>
>>> Andrea
>>>
>>>
>>>
>>
>>
>
>
Re: cxfbc provider :HIERARCHY_REQUEST_ERR: An attempt was made to
insert a node where it is not permitted!!!!???
Posted by Freeman Fang <fr...@gmail.com>.
Hi Jeff,
Yes, it is used both in request flow on server side and response flow on
client side, which means it's used for incoming message both for client
and server side.
Freeman
Jeff Peterson wrote:
> Im not too familiar with the CXF BC. Just a thought, is the
> JbiInWsdl1Interceptor supposed to be used in the response flow?
>
> - Jeff
>
> On Mon, Dec 1, 2008 at 12:30 AM, Andrea Zoppello <zo...@tiscali.it> wrote:
>
>> Hi,
>>
>> Here the staktrace:
>> This is the soap response the cxf-bc-provider:
>> HTTP/1.1 200 OK
>> Content-Type: application/soap+xml; charset=UTF-8
>> Content-Length: 621
>> Server: Jetty(6.1.6)
>>
>> <soap:Envelope
>> xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><RelatesTo
>> xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:B5AAE5716469A68D5C1227796067318</RelatesTo><Action
>> xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:RegisterDocumentSet-bResponse</Action></soap:Header><soap:Body>
>> <rs:RegistryResponse
>> status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success"
>> xmlns:SOAP-SEC="http://schemas.xmlsoap.org/soap/security/2000-12"
>> xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
>> xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
>> /></soap:Body></soap:Envelope>
>>
>> As you could see there's nothing wrong.... with that soap response.
>>
>> But the exception is the same with or without ssl i've this exception:
>> 27-nov-2008 15.28.19 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
>> INFO: Interceptor has thrown exception, unwinding now
>> org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to
>> insert a node where it is n
>> t permitted.
>> at org.apache.xerces.dom.ParentNode.internalInsertBefore(Unknown
>> Source)
>> at org.apache.xerces.dom.ParentNode.insertBefore(Unknown Source)
>> at org.apache.xerces.dom.CoreDocumentImpl.insertBefore(Unknown Source)
>> at org.apache.xerces.dom.NodeImpl.appendChild(Unknown Source)
>> at
>> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:719)
>> at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:605)
>> at
>> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.getBodyElement(JbiInWsdl1
>> nterceptor.java:306)
>> at
>> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.handleMessage(JbiInWsdl1I
>> terceptor.java:143)
>> at
>> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.handleMessage(JbiInWsdl1I
>> terceptor.java:59)
>> at
>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
>> at
>> org.apache.servicemix.cxfbc.CxfBcProviderMessageObserver.onMessage(CxfBcProviderMessageO
>> server.java:137)
>> at
>> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit
>> java:2029)
>> at
>> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:186
>> )
>> at
>> org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:249)
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:600)
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:
>>
>>
>> Freeman Fang ha scritto:
>>
>>> Hi Andrea,
>>> What kind of the external server you are using?
>>> Could you post the soap message you get from tcp monitor? and the cxf bc
>>> endpoint configuration, also the wsdl you are using if possible.
>>> Could you check your response soap message has no tab character for intent
>>> since I don't think cxf can handle such tab character.
>>>
>>> Freeman
>>>
>>> Andrea Zoppello wrote:
>>>
>>>> I've the following stack trace when the CxfProvider when the soap
>>>> response is
>>>> received by CxfBcProvider:
>>>>
>>>> INFO: Interceptor has thrown exception, unwinding now
>>>> org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to
>>>> insert a node where it is no
>>>> t permitted.
>>>> at org.apache.xerces.dom.ParentNode.internalInsertBefore(Unknown
>>>> Source)
>>>> at org.apache.xerces.dom.ParentNode.insertBefore(Unknown Source)
>>>> at org.apache.xerces.dom.CoreDocumentImpl.insertBefore(Unknown
>>>> Source)
>>>> at org.apache.xerces.dom.NodeImpl.appendChild(Unknown Source)
>>>> at
>>>> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:721)
>>>> at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:607)
>>>> at
>>>> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.getBodyElement(JbiInWsdl1I
>>>> nterceptor.java:306)
>>>> at
>>>> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.handleMessage(JbiInWsdl1In
>>>> terceptor.java:143)
>>>> at
>>>> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.handleMessage(JbiInWsdl1In
>>>> terceptor.java:59)
>>>> at
>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
>>>> at
>>>> org.apache.servicemix.cxfbc.CxfBcProviderMessageObserver.onMessage(CxfBcProviderMessageOb
>>>> server.java:137)
>>>> at
>>>> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.
>>>> java:2029)
>>>> at
>>>> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1865
>>>> )
>>>> at
>>>> org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:261)
>>>> at
>>>> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:600)
>>>> at
>>>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:5
>>>> 54)
>>>> at
>>>> org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java
>>>> :510)
>>>> at
>>>> org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.
>>>> java:60)
>>>> at
>>>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImp
>>>> l.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:168)
>>>> at
>>>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>>>> at java.lang.Thread.run(Thread.java:595)
>>>>
>>>> Any idea??
>>>>
>>>> Andrea
>>>>
>>>>
>>>
>> Jeff Peterson ha scritto:
>>
>>> Can you post the full stack trace?
>>>
>>> - Jeff
>>>
>>> On Fri, Nov 28, 2008 at 4:32 AM, Andrea Zoppello <zo...@tiscali.it>
>>> wrote:
>>>
>>>
>>>> Thank you for the response,
>>>>
>>>> I've seen this, but is there a patch for this???
>>>>
>>>> raulvk.soa ha scritto:
>>>>
>>>>
>>>>> Andrea,
>>>>>
>>>>> There is a very similar thread from a few months ago. Check
>>>>>
>>>>>
>>>>> http://cwiki.apache.org/SM/discussion-forums.html#nabble-td19656853|a19667244.
>>>>>
>>>>> It is an issue related to whitespaces in the input message.
>>>>>
>>>>> I came across it when using soapUI but it is known to affect other use
>>>>> cases
>>>>> too.
>>>>>
>>>>> Hope that helps.
>>>>>
>>>>>
>>>>> Andrea Zoppello-2 wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Is there any fix for this???
>>>>>>
>>>>>> Andrea
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
>
Re: cxfbc provider :HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted!!!!???
Posted by Jeff Peterson <j....@gmail.com>.
Im not too familiar with the CXF BC. Just a thought, is the
JbiInWsdl1Interceptor supposed to be used in the response flow?
- Jeff
On Mon, Dec 1, 2008 at 12:30 AM, Andrea Zoppello <zo...@tiscali.it> wrote:
> Hi,
>
> Here the staktrace:
> This is the soap response the cxf-bc-provider:
> HTTP/1.1 200 OK
> Content-Type: application/soap+xml; charset=UTF-8
> Content-Length: 621
> Server: Jetty(6.1.6)
>
> <soap:Envelope
> xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><RelatesTo
> xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:B5AAE5716469A68D5C1227796067318</RelatesTo><Action
> xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:RegisterDocumentSet-bResponse</Action></soap:Header><soap:Body>
> <rs:RegistryResponse
> status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success"
> xmlns:SOAP-SEC="http://schemas.xmlsoap.org/soap/security/2000-12"
> xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
> xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
> /></soap:Body></soap:Envelope>
>
> As you could see there's nothing wrong.... with that soap response.
>
> But the exception is the same with or without ssl i've this exception:
> 27-nov-2008 15.28.19 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
> INFO: Interceptor has thrown exception, unwinding now
> org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to
> insert a node where it is n
> t permitted.
> at org.apache.xerces.dom.ParentNode.internalInsertBefore(Unknown
> Source)
> at org.apache.xerces.dom.ParentNode.insertBefore(Unknown Source)
> at org.apache.xerces.dom.CoreDocumentImpl.insertBefore(Unknown Source)
> at org.apache.xerces.dom.NodeImpl.appendChild(Unknown Source)
> at
> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:719)
> at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:605)
> at
> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.getBodyElement(JbiInWsdl1
> nterceptor.java:306)
> at
> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.handleMessage(JbiInWsdl1I
> terceptor.java:143)
> at
> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.handleMessage(JbiInWsdl1I
> terceptor.java:59)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
> at
> org.apache.servicemix.cxfbc.CxfBcProviderMessageObserver.onMessage(CxfBcProviderMessageO
> server.java:137)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit
> java:2029)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:186
> )
> at
> org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:249)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:600)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:
>
>
> Freeman Fang ha scritto:
>>
>> Hi Andrea,
>> What kind of the external server you are using?
>> Could you post the soap message you get from tcp monitor? and the cxf bc
>> endpoint configuration, also the wsdl you are using if possible.
>> Could you check your response soap message has no tab character for intent
>> since I don't think cxf can handle such tab character.
>>
>> Freeman
>>
>> Andrea Zoppello wrote:
>>>
>>> I've the following stack trace when the CxfProvider when the soap
>>> response is
>>> received by CxfBcProvider:
>>>
>>> INFO: Interceptor has thrown exception, unwinding now
>>> org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to
>>> insert a node where it is no
>>> t permitted.
>>> at org.apache.xerces.dom.ParentNode.internalInsertBefore(Unknown
>>> Source)
>>> at org.apache.xerces.dom.ParentNode.insertBefore(Unknown Source)
>>> at org.apache.xerces.dom.CoreDocumentImpl.insertBefore(Unknown
>>> Source)
>>> at org.apache.xerces.dom.NodeImpl.appendChild(Unknown Source)
>>> at
>>> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:721)
>>> at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:607)
>>> at
>>> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.getBodyElement(JbiInWsdl1I
>>> nterceptor.java:306)
>>> at
>>> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.handleMessage(JbiInWsdl1In
>>> terceptor.java:143)
>>> at
>>> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.handleMessage(JbiInWsdl1In
>>> terceptor.java:59)
>>> at
>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
>>> at
>>> org.apache.servicemix.cxfbc.CxfBcProviderMessageObserver.onMessage(CxfBcProviderMessageOb
>>> server.java:137)
>>> at
>>> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.
>>> java:2029)
>>> at
>>> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1865
>>> )
>>> at
>>> org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:261)
>>> at
>>> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:600)
>>> at
>>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:5
>>> 54)
>>> at
>>> org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java
>>> :510)
>>> at
>>> org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.
>>> java:60)
>>> at
>>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImp
>>> l.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:168)
>>> at
>>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>>> at java.lang.Thread.run(Thread.java:595)
>>>
>>> Any idea??
>>>
>>> Andrea
>>>
>>
>>
>
>
> Jeff Peterson ha scritto:
>>
>> Can you post the full stack trace?
>>
>> - Jeff
>>
>> On Fri, Nov 28, 2008 at 4:32 AM, Andrea Zoppello <zo...@tiscali.it>
>> wrote:
>>
>>>
>>> Thank you for the response,
>>>
>>> I've seen this, but is there a patch for this???
>>>
>>> raulvk.soa ha scritto:
>>>
>>>>
>>>> Andrea,
>>>>
>>>> There is a very similar thread from a few months ago. Check
>>>>
>>>>
>>>> http://cwiki.apache.org/SM/discussion-forums.html#nabble-td19656853|a19667244.
>>>>
>>>> It is an issue related to whitespaces in the input message.
>>>>
>>>> I came across it when using soapUI but it is known to affect other use
>>>> cases
>>>> too.
>>>>
>>>> Hope that helps.
>>>>
>>>>
>>>> Andrea Zoppello-2 wrote:
>>>>
>>>>
>>>>>
>>>>> Is there any fix for this???
>>>>>
>>>>> Andrea
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: cxfbc provider :HIERARCHY_REQUEST_ERR: An attempt was made to
insert a node where it is not permitted!!!!???
Posted by Andrea Zoppello <zo...@tiscali.it>.
Hi,
Here the staktrace:
This is the soap response the cxf-bc-provider:
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=UTF-8
Content-Length: 621
Server: Jetty(6.1.6)
<soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><RelatesTo
xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:B5AAE5716469A68D5C1227796067318</RelatesTo><Action
xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:RegisterDocumentSet-bResponse</Action></soap:Header><soap:Body>
<rs:RegistryResponse
status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success"
xmlns:SOAP-SEC="http://schemas.xmlsoap.org/soap/security/2000-12"
xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
/></soap:Body></soap:Envelope>
As you could see there's nothing wrong.... with that soap response.
But the exception is the same with or without ssl i've this exception:
27-nov-2008 15.28.19 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
INFO: Interceptor has thrown exception, unwinding now
org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to
insert a node where it is n
t permitted.
at org.apache.xerces.dom.ParentNode.internalInsertBefore(Unknown
Source)
at org.apache.xerces.dom.ParentNode.insertBefore(Unknown Source)
at org.apache.xerces.dom.CoreDocumentImpl.insertBefore(Unknown
Source)
at org.apache.xerces.dom.NodeImpl.appendChild(Unknown Source)
at
org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:719)
at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:605)
at
org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.getBodyElement(JbiInWsdl1
nterceptor.java:306)
at
org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.handleMessage(JbiInWsdl1I
terceptor.java:143)
at
org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.handleMessage(JbiInWsdl1I
terceptor.java:59)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
at
org.apache.servicemix.cxfbc.CxfBcProviderMessageObserver.onMessage(CxfBcProviderMessageO
server.java:137)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit
java:2029)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:186
)
at
org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:249)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:600)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:
Freeman Fang ha scritto:
> Hi Andrea,
> What kind of the external server you are using?
> Could you post the soap message you get from tcp monitor? and the cxf
> bc endpoint configuration, also the wsdl you are using if possible.
> Could you check your response soap message has no tab character for
> intent since I don't think cxf can handle such tab character.
>
> Freeman
>
> Andrea Zoppello wrote:
>> I've the following stack trace when the CxfProvider when the soap
>> response is
>> received by CxfBcProvider:
>>
>> INFO: Interceptor has thrown exception, unwinding now
>> org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made
>> to insert a node where it is no
>> t permitted.
>> at
>> org.apache.xerces.dom.ParentNode.internalInsertBefore(Unknown Source)
>> at org.apache.xerces.dom.ParentNode.insertBefore(Unknown Source)
>> at org.apache.xerces.dom.CoreDocumentImpl.insertBefore(Unknown
>> Source)
>> at org.apache.xerces.dom.NodeImpl.appendChild(Unknown Source)
>> at
>> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:721)
>> at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:607)
>> at
>> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.getBodyElement(JbiInWsdl1I
>>
>> nterceptor.java:306)
>> at
>> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.handleMessage(JbiInWsdl1In
>>
>> terceptor.java:143)
>> at
>> org.apache.servicemix.cxfbc.interceptors.JbiInWsdl1Interceptor.handleMessage(JbiInWsdl1In
>>
>> terceptor.java:59)
>> at
>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
>>
>> at
>> org.apache.servicemix.cxfbc.CxfBcProviderMessageObserver.onMessage(CxfBcProviderMessageOb
>>
>> server.java:137)
>> at
>> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.
>>
>> java:2029)
>> at
>> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1865
>>
>> )
>> at
>> org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:261)
>>
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:600)
>>
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:5
>>
>> 54)
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java
>>
>> :510)
>> at
>> org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.
>>
>> java:60)
>> at
>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImp
>>
>> l.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:168)
>>
>> at
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>>
>> at java.lang.Thread.run(Thread.java:595)
>>
>> Any idea??
>>
>> Andrea
>>
>
>
Jeff Peterson ha scritto:
> Can you post the full stack trace?
>
> - Jeff
>
> On Fri, Nov 28, 2008 at 4:32 AM, Andrea Zoppello <zo...@tiscali.it> wrote:
>
>> Thank you for the response,
>>
>> I've seen this, but is there a patch for this???
>>
>> raulvk.soa ha scritto:
>>
>>> Andrea,
>>>
>>> There is a very similar thread from a few months ago. Check
>>>
>>> http://cwiki.apache.org/SM/discussion-forums.html#nabble-td19656853|a19667244.
>>>
>>> It is an issue related to whitespaces in the input message.
>>>
>>> I came across it when using soapUI but it is known to affect other use
>>> cases
>>> too.
>>>
>>> Hope that helps.
>>>
>>>
>>> Andrea Zoppello-2 wrote:
>>>
>>>
>>>> Is there any fix for this???
>>>>
>>>> Andrea
>>>>
>>>>
>>>>
>>>>
>>>
>>
>
>