cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

PI 7.31 receiving attachment in soap response errs

Former Member

on ‎05-07-2013 10:38 AM

0 Kudos

Hi

I have a synchronous scenario where PI sends a request to a SOAP receiver channel and the response is both an xml message plus an xml attachment. However I get the error:

SOAP: call failed: java.io.IOException: invalid syntax in MIME header:   ; HTTP 200 OK

I selected Keep Attachments" in the SOAP receiver channel.

I can make it work from SOAPUI where I can see this HTTP content regarding the response:

Tue May 07 11:16:08 CEST 2013:DEBUG:>> "</urn:FileDownloadRequestEnvelope>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:>> " </soapenv:Body>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:>> "</soapenv:Envelope>"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "HTTP/1.1 200 OK[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "HTTP/1.1 200 OK[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Date: Tue, 07 May 2013 09:16:07 GMT[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Server: Apache-Coyote/1.1[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-Type: multipart/related; type="text/xml"; boundary=_NextPart_000_0002_01C3E1CC.3BB37320; start="<TIBCO_START_PART>"[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-Length: 3434599[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Connection: close[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "--_NextPart_000_0002_01C3E1CC.3BB37320  [\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-transfer-encoding: binary [\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-type: text/xml; charset=utf-8; [\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-id: <TIBCO_START_PART>[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<soapenv:Envelope xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/'><soapenv:Header/> <soapenv:Body>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<ns0:FileDownloadResponseEnvelope xmlns:ns0="urn:nl:edsn:service:filedownloadresponse:env:1">[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "    <ns0:EDSNBusinessDocumentHeader>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        <ns0:CreationTimestamp>2013-05-07T11:16:07.87+02:00</ns0:CreationTimestamp>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        <ns0:Destination>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:Receiver>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:ContactTypeIdentifier>DDQ_O</ns0:ContactTypeIdentifier>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:ReceiverID>xxxx</ns0:ReceiverID>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            </ns0:Receiver>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        </ns0:Destination>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        <ns0:Manifest>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:ManifestItem>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:MimeTypeQualifierCode>text/plain</ns0:MimeTypeQualifierCode>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:UniformResourceIdentifier>/u01/env/UAT08/data/UAT08/fileexchange/storeCB/ADC_Verplichting/f15030ea-d3fd-44a3-a8ad-57e4"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "06356ae0</ns0:UniformResourceIdentifier>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            </ns0:ManifestItem>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:NumberofItems>1</ns0:NumberofItems>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        </ns0:Manifest>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        <ns0:MessageID>295613d6-689c-430a-b973-511ca417cb90</ns0:MessageID>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        <ns0:Source>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:Authority/>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:ContactTypeIdentifier>EDSN</ns0:ContactTypeIdentifier>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:SenderID>xxx</ns0:SenderID>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        </ns0:Source>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "    </ns0:EDSNBusinessDocumentHeader>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "    <ns0:FileDownloadResponseContent>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        <ns0:FileDownloadResponse_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:FileID>f15030ea-d3fd-44a3-a8ad-57e406356ae0</ns0:FileID>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:FileSize>3431793</ns0:FileSize>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:FileType>ADC Verplichting</ns0:FileType>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:Group>ADC</ns0:Group>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:ReceivingEntity_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:OrganisationID>xxxx</ns0:OrganisationID>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:OrganisationName>xxxx</ns0:OrganisationName>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            </ns0:ReceivingEntity_EDSN"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "FileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:SendingEntity_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:OrganisationID>xxxx</ns0:OrganisationID>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:OrganisationName>EDSN</ns0:OrganisationName>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            </ns0:SendingEntity_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:Status>Afgemeld</ns0:Status>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:UploadDate_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:DateTime>2013-03-07T18:25:37+01:00</ns0:DateTime>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            </ns0:UploadDate_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        </ns0:FileDownloadResponse_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "    </ns0:FileDownloadResponseContent>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "</ns0:FileDownloadResponseEnvelope></soapenv:Body></soapenv:Envelope>[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "--_NextPart_000_0002_01C3E1CC.3BB37320 [\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-transfer-encoding: "

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "binary [\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-type: application/octet-stream[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-id: <Attachment>[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<?xml version="1.0" encoding="windows-1252"?>[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<ccma:ObligationSpecificationEnvelope xmlns:ccma="urn:nedu:edsn:data:obligationspecification:2:standard">[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<ccma:EDSNBusinessDocumentHeader>[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<ccma:CreationTimestamp>2013-03-07T18:01:19Z</ccma:CreationTimestamp>[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<ccma:MessageID>1507</ccma:MessageID>[\r][\n]"

Is the response valid or is something missing?

BR Mikael

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (1)

Answers (1)

stefan_grube
Active Contributor
‎05-07-2013 12:30 PM
0 Kudos

I see the HTTP/1.1 200 OK twice.

The error message gives a hint that the SOAP adapter interpretes the second HTTP/1.1 200 OK as a mime header, which is of course not correct systax, as headers should be name=value

I think it is very odd to have HTTP/1.1 200 OK twice, you have to fix this on server.

Show replies
Show replies
Former Member
‎05-07-2013 1:23 PM
0 Kudos

Thank you so much for your answer, Stefan. I have informed the owner of the web service about the double entry.

/Mikael

Ask a Question