Multipart messages through the HTTP BC

5 messages Options
Embed this post
Permalink
Mikael Beermann

Multipart messages through the HTTP BC

Reply Threaded More More options
Print post
Permalink
I have an EJB based web service returning a file as an mime attachment using a mime:multipartRelated as output. This works fine if the web service is deployed directly to the EJB. However, if I add it to a composite application and deploy it and try to call it via the HTTP BC instead, I get the following exception:

[#|2009-10-06T16:35:31.349+0200|WARNING|sun-appserver9.1|com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider|_ThreadID=48;_ThreadName=HTTPBC-OutboundReceiver-2;_RequestID=d0133f29-33aa-4b36-9a66-3a91235709dd;|HTTPBC-E00799: Message denormalization failed
javax.jbi.messaging.MessagingException: javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message denormalization failed
        at com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:108)
        at com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider.onReply(AsyncJBIProvider.java:274)
        at com.sun.jbi.httpsoapbc.MessageExchangeSupport.notifyOfReply(MessageExchangeSupport.java:126)
        at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:424)
        at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:242)
        at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
        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:619)
Caused by: javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message denormalization failed
        at com.sun.jbi.httpsoapbc.Soap11Denormalizer.denormalize(Soap11Denormalizer.java:221)
        at com.sun.jbi.httpsoapbc.SoapDenormalizerImpl.denormalize(SoapDenormalizerImpl.java:28)
        at com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:98)
        ... 8 more
Caused by: com.sun.jbi.nms.wsdl11wrapper.WrapperProcessingException: The normalized message contains less parts than are defined in the WSDL message definition
        at com.sun.jbi.nms.wsdl11wrapper.impl.WrapperParserImpl.parse(WrapperParserImpl.java:142)
        at com.sun.jbi.httpsoapbc.Soap11Denormalizer.denormalize(Soap11Denormalizer.java:196)
        ... 10 more
|#]

[#|2009-10-06T16:35:31.352+0200|FINEST|sun-appserver9.1|com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider|_ThreadID=48;_ThreadName=HTTPBC-OutboundReceiver-2;ClassName=com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider;MethodName=onReply;_RequestID=d0133f29-33aa-4b36-9a66-3a91235709dd;|Decremented pending message exchange replies; endpoint 'http://j2ee.netbeans.org/wsdl/TestAttachmentEJB/AttachmentTest,AttachmentTestService,AttachmentTestPort,Consumer'|#]

[#|2009-10-06T16:35:31.354+0200|WARNING|sun-appserver9.1|com.sun.jbi.httpsoapbc.OutboundMessageProcessor|_ThreadID=48;_ThreadName=HTTPBC-OutboundReceiver-2;_RequestID=d0133f29-33aa-4b36-9a66-3a91235709dd;|HTTPBC-E00759: An exception occured while processing a reply message. javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message denormalization failed
javax.jbi.messaging.MessagingException: javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message denormalization failed
        at com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:108)
        at com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider.onReply(AsyncJBIProvider.java:274)
        at com.sun.jbi.httpsoapbc.MessageExchangeSupport.notifyOfReply(MessageExchangeSupport.java:126)
        at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:424)
        at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:242)
        at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
        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:619)
Caused by: javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message denormalization failed
        at com.sun.jbi.httpsoapbc.Soap11Denormalizer.denormalize(Soap11Denormalizer.java:221)
        at com.sun.jbi.httpsoapbc.SoapDenormalizerImpl.denormalize(SoapDenormalizerImpl.java:28)
        at com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:98)
        ... 8 more
Caused by: com.sun.jbi.nms.wsdl11wrapper.WrapperProcessingException: The normalized message contains less parts than are defined in the WSDL message definition
        at com.sun.jbi.nms.wsdl11wrapper.impl.WrapperParserImpl.parse(WrapperParserImpl.java:142)
        at com.sun.jbi.httpsoapbc.Soap11Denormalizer.denormalize(Soap11Denormalizer.java:196)
        ... 10 more
|#]


[#|2009-10-06T16:35:31.370+0200|WARNING|sun-appserver9.1|javax.enterprise.system|_ThreadID=42;_ThreadName=Thread-64;_RequestID=689c8d2f-6165-4360-bbeb-5b561da8a277;|JavaEE Service Engine received unsupported Message Exchange       ExchangeId: 202205714571982-24421-134741325312930014
        Pattern: http://www.w3.org/2004/08/wsdl/in-out
        Role: PROVIDER

        Provider: Null
        Consumer: Null  Index: 5  SynchState: NONE
        EndpointLink: Null
        Status: ERROR  Location: LOCAL
        Transaction:   None
        Service: null
        Endpoint:http://j2ee.netbeans.org/wsdl/TestAttachmentEJB/AttachmentTest,AttachmentTestService,javaee_AttachmentTestPort        Operation: {http://j2ee.netbeans.org/wsdl/TestAttachmentEJB/AttachmentTest}AttachmentTestOperation
        Interface: null
        Properties Count: 0
        DeltaProperties Count: 2
          Name: com.sun.jbi.messaging.messageid
          Value: 3
          Name: com.sun.jbi.messaging.groupid
          Value: a8a6c0cf-0c97-4a89-b883-cc3828e01c21
        Message Count:   1
          Message Name: in
            Message Content(Type): javax.xml.transform.dom.DOMSource
            Properties Count:   4
              Name: org.glassfish.openesb.inbound.http.headers
              Value(Type): java.util.HashMap
              Name: org.glassfish.openesb.inbound.address.url
              Value: http://mikbee-2.tickstar.local:9080/AttachmentTestService/AttachmentTestPort
              Name: org.glassfish.openesb.messaging.groupid
              Value: a8a6c0cf-0c97-4a89-b883-cc3828e01c21
              Name: org.glassfish.openesb.messaging.messageid
              Value: 3
            Attachments Count:  0
|#]

Does this mean it isn't possible to send multipart messages (SOAP Attachment) using the HTTP BC?

/Mikael

SherryWeng

Re: Multipart messages through the HTTP BC

Reply Threaded More More options
Print post
Permalink
Could you please file an issue and attach the project, or at least the
WSDL and the server log?

Thanks
--Sherry

Mikael Beermann wrote:

> I have an EJB based web service returning a file as an mime attachment using
> a mime:multipartRelated as output. This works fine if the web service is
> deployed directly to the EJB. However, if I add it to a composite
> application and deploy it and try to call it via the HTTP BC instead, I get
> the following exception:
>
> [#|2009-10-06T16:35:31.349+0200|WARNING|sun-appserver9.1|com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider|_ThreadID=48;_ThreadName=HTTPBC-OutboundReceiver-2;_RequestID=d0133f29-33aa-4b36-9a66-3a91235709dd;|HTTPBC-E00799:
> Message denormalization failed
> javax.jbi.messaging.MessagingException:
> javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message
> denormalization failed
> at
> com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:108)
> at
> com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider.onReply(AsyncJBIProvider.java:274)
> at
> com.sun.jbi.httpsoapbc.MessageExchangeSupport.notifyOfReply(MessageExchangeSupport.java:126)
> at
> com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:424)
> at
> com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:242)
> at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
> 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:619)
> Caused by: javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message
> denormalization failed
> at
> com.sun.jbi.httpsoapbc.Soap11Denormalizer.denormalize(Soap11Denormalizer.java:221)
> at
> com.sun.jbi.httpsoapbc.SoapDenormalizerImpl.denormalize(SoapDenormalizerImpl.java:28)
> at
> com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:98)
> ... 8 more
> Caused by: com.sun.jbi.nms.wsdl11wrapper.WrapperProcessingException: The
> normalized message contains less parts than are defined in the WSDL message
> definition
> at
> com.sun.jbi.nms.wsdl11wrapper.impl.WrapperParserImpl.parse(WrapperParserImpl.java:142)
> at
> com.sun.jbi.httpsoapbc.Soap11Denormalizer.denormalize(Soap11Denormalizer.java:196)
> ... 10 more
> |#]
>
> [#|2009-10-06T16:35:31.352+0200|FINEST|sun-appserver9.1|com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider|_ThreadID=48;_ThreadName=HTTPBC-OutboundReceiver-2;ClassName=com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider;MethodName=onReply;_RequestID=d0133f29-33aa-4b36-9a66-3a91235709dd;|Decremented
> pending message exchange replies; endpoint
> 'http://j2ee.netbeans.org/wsdl/TestAttachmentEJB/AttachmentTest,AttachmentTestService,AttachmentTestPort,Consumer'|#]
>
> [#|2009-10-06T16:35:31.354+0200|WARNING|sun-appserver9.1|com.sun.jbi.httpsoapbc.OutboundMessageProcessor|_ThreadID=48;_ThreadName=HTTPBC-OutboundReceiver-2;_RequestID=d0133f29-33aa-4b36-9a66-3a91235709dd;|HTTPBC-E00759:
> An exception occured while processing a reply message.
> javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message
> denormalization failed
> javax.jbi.messaging.MessagingException:
> javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message
> denormalization failed
> at
> com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:108)
> at
> com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider.onReply(AsyncJBIProvider.java:274)
> at
> com.sun.jbi.httpsoapbc.MessageExchangeSupport.notifyOfReply(MessageExchangeSupport.java:126)
> at
> com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:424)
> at
> com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:242)
> at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
> 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:619)
> Caused by: javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message
> denormalization failed
> at
> com.sun.jbi.httpsoapbc.Soap11Denormalizer.denormalize(Soap11Denormalizer.java:221)
> at
> com.sun.jbi.httpsoapbc.SoapDenormalizerImpl.denormalize(SoapDenormalizerImpl.java:28)
> at
> com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:98)
> ... 8 more
> Caused by: com.sun.jbi.nms.wsdl11wrapper.WrapperProcessingException: The
> normalized message contains less parts than are defined in the WSDL message
> definition
> at
> com.sun.jbi.nms.wsdl11wrapper.impl.WrapperParserImpl.parse(WrapperParserImpl.java:142)
> at
> com.sun.jbi.httpsoapbc.Soap11Denormalizer.denormalize(Soap11Denormalizer.java:196)
> ... 10 more
> |#]
>
>
> [#|2009-10-06T16:35:31.370+0200|WARNING|sun-appserver9.1|javax.enterprise.system|_ThreadID=42;_ThreadName=Thread-64;_RequestID=689c8d2f-6165-4360-bbeb-5b561da8a277;|JavaEE
> Service Engine received unsupported Message Exchange       ExchangeId:
> 202205714571982-24421-134741325312930014
>         Pattern: http://www.w3.org/2004/08/wsdl/in-out
>         Role: PROVIDER
>
>         Provider: Null
>         Consumer: Null  Index: 5  SynchState: NONE
>         EndpointLink: Null
>         Status: ERROR  Location: LOCAL
>         Transaction:   None
>         Service: null
>        
> Endpoint:http://j2ee.netbeans.org/wsdl/TestAttachmentEJB/AttachmentTest,AttachmentTestService,javaee_AttachmentTestPort       
> Operation:
> {http://j2ee.netbeans.org/wsdl/TestAttachmentEJB/AttachmentTest}AttachmentTestOperation
>         Interface: null
>         Properties Count: 0
>         DeltaProperties Count: 2
>           Name: com.sun.jbi.messaging.messageid
>           Value: 3
>           Name: com.sun.jbi.messaging.groupid
>           Value: a8a6c0cf-0c97-4a89-b883-cc3828e01c21
>         Message Count:   1
>           Message Name: in
>             Message Content(Type): javax.xml.transform.dom.DOMSource
>             Properties Count:   4
>               Name: org.glassfish.openesb.inbound.http.headers
>               Value(Type): java.util.HashMap
>               Name: org.glassfish.openesb.inbound.address.url
>               Value:
> http://mikbee-2.tickstar.local:9080/AttachmentTestService/AttachmentTestPort
>               Name: org.glassfish.openesb.messaging.groupid
>               Value: a8a6c0cf-0c97-4a89-b883-cc3828e01c21
>               Name: org.glassfish.openesb.messaging.messageid
>               Value: 3
>             Attachments Count:  0
> |#]
>
> Does this mean it isn't possible to send multipart messages (SOAP
> Attachment) using the HTTP BC?
>
> /Mikael
>
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Mikael Beermann

Re: Multipart messages through the HTTP BC

Reply Threaded More More options
Print post
Permalink
Hi Sherry!

Where do I file an issue?

Regards
Mikael
jbaragry

Re: Multipart messages through the HTTP BC

Reply Threaded More More options
Print post
Permalink
Hi Mikael,

Here is the issue tracker for openeb
https://open-esb.dev.java.net/servlets/ProjectIssues
(you need to be registered and logged in to submit a new issue).

rgds
Jason

On Wed, Oct 7, 2009 at 8:41 AM, Mikael Beermann
<[hidden email]> wrote:

>
> Hi Sherry!
>
> Where do I file an issue?
>
> Regards
> Mikael
>
> --
> View this message in context: http://n2.nabble.com/Multipart-messages-through-the-HTTP-BC-tp3775532p3780072.html
> Sent from the OpenESB Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Mikael Beermann

Re: Multipart messages through the HTTP BC

Reply Threaded More More options
Print post
Permalink
Thanks,

/Mikael