[esb-issues] [JBoss JIRA] Commented: (JBESB-1803) MTOM support is broken

[Kevin Conner (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-1803?page=comments#action_12417565 ] 
            
Kevin Conner commented on JBESB-1803:
-------------------------------------

This is happening in the platform CP2 release and not our codebase.

The issue is related to the chunking of the client stream by JBoss Remoting (see SOA issue for the output)

Will continue to investigate.

> MTOM support is broken
> ----------------------
>
>                 Key: JBESB-1803
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1803
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>    Affects Versions: 4.2.1 CP3
>         Environment: Embedded CR1/FC8/PostgreSQL
>            Reporter: Jiri Pechanec
>         Assigned To: Kevin Conner
>             Fix For: 4.2.1 CP4
>
>
> Try to run MTOM quickstart. It reports exception
> 2008-06-11 08:56:05,898 INFO  [STDOUT] [<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header></env:Header><env:Body><ns1:echoImage xmlns:ns1='http://org.jboss.ws/xop/doclit'><data>iVBORw0KGgoAAAANSUhEUgAAAPkAAABOCAYAAADigLBdAAAJ1ElEQVR42u2dS4xURRSGZ+2KnXHHyoS4YWVYkmh0i3HhRuOsXBlCYsLCRzAmRIMSYngoBESUoAg6CBGFEAZB5OE4vAQEEcgMCEMI85BhhsdQ9n/jP9aUVXXr3u6Zfsz/JSfdffve6k7P/HVOnTpVt61NCCGEEEIIIYQQQgghhBBCCCGEEEII0RqM3Llvdm373Sx5c69557XdZs3SQ+byhVtGv4wQDcixW3fNopO3MuvoHU4S6oZVv2Tidu3a1SEJXYhGov3wDdO26eIEm7vnL9N/dywoVgjZJ3DY5vXHJXIhGoUFv978n8Bp8/ZfD4oVYXlI5PDw+mWFaBQCAqddun3fyJML0cTj8DyRd/aNBAWLRJtP5Eq+CdEgZGPuKkSO7LqdfEOW/fjRqxK4EJPNpYEB03m5J7O8c5FgCwl85rc9EqwQjSbuuRu/MG2Ll4zbjKUfmmVHukwsZJ+x9XJhLy6EmOrQe2TUzFyxeoLAbYsJHck1TKPBc0PwyKpn43UhROOwaP9PQYHTo6Mj0C8lRJMye+2nUZHDUsboQogGBZ46T+SxkF0I0eC4CTd5ciFajPUnTkUFniXlhBDNTfuOncGk27HrfRJ5A/DHhQsG1tPbq7+HKAey7EzCQdzztnTUROB3r1wxV1esrLn179ljHgxNj6Wpv50+Y7Zt324OHjpUedwhoYvGYujIUdM164lJs0uvv2HQkbS6F/9+165M3HjEa/1niWkjctixJ+eY4bNnTauLHI/w6BK5mHYip9BbNXxHuI5QHc879/2ocF1MT5HDbn7T0bL//BA2].
> 2008-06-11 08:56:05,900 ERROR [STDERR] [Fatal Error] :1:1020: XML document structures must start and end within the same entity.
> 2008-06-11 08:56:05,900 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception
> org.jboss.ws.core.CommonSOAPFaultException: org.xml.sax.SAXParseException: XML document structures must start and end within the same entity.
>         at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:93)
>         at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:262)
>         at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:185)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:389)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
>         at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:150)
>         at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
>         at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
>         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)
> 2008-06-11 08:56:05,900 ERROR [org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC] SOAP request exception
> javax.xml.rpc.soap.SOAPFaultException: org.xml.sax.SAXParseException: XML document structures must start and end within the same entity.
>         at org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC.exceptionToFaultMessage(SOAPFaultHelperJAXRPC.java:189)
>         at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:157)
>         at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104)
>         at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:645)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:430)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
>         at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:150)
>         at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
>         at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
>         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)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira