| Author |
Message
|
| sguerin |
 Posted: Wed Sep 15, 2010 10:08 am Post subject: WMB6.0 : Empty or invalid header (WS SwA call) |
 |
|
Newbie
Joined: 14 Sep 2010
Posts: 5
|
Hi,
I work with WMB 6.0 and I need to call a Web service which responds back with SwA. Because of WMB 6.0, I use a HTTP Request node, and I specified MIME as Domain.
My message flow is the following: MQ Input -> Compute -> HTTP Request -> Trace -> Compute1 -> MQ Reply
The problem is I get a fine response from the service (HTTP Status Code 200) but I have the error "a Empty or invalid header found at position: &1".
If I put a debug point just after the HTTP Request Node, I see throw the Variables view:
| Quote: |
- Message
+ Properties
+ HTTPResponseHeader
MIME
Empty or invalid header found at position: &1.
- Environnement_local
+ Environnement
- ListeExceptions |
Here is a user trace, after the Web Service Call, with the content of ${root} (the trace is complete):
| Quote: |
(
(0x01000000):Properties = (
(0x03000000):MessageSet = ''
(0x03000000):MessageType = ''
(0x03000000):MessageFormat = ''
(0x03000000):Encoding = 546
(0x03000000):CodedCharSetId = 1208
(0x03000000):Transactional = FALSE
(0x03000000):Persistence = FALSE
(0x03000000):CreationTime = GMTTIMESTAMP '2010-09-15 17:20:46.782'
(0x03000000):ExpirationTime = -1
(0x03000000):Priority = 0
(0x03000000):ReplyIdentifier = X'000000000000000000000000000000000000000000000000'
(0x03000000):ReplyProtocol = 'MQ'
(0x03000000):Topic = NULL
(0x03000000):ContentType = 'text/xml; charset=utf-8'
)
(0x01000000):HTTPResponseHeader = (
(0x03000000):X-Original-HTTP-Status-Line = 'HTTP/1.1 200 OK'
(0x03000000):X-Original-HTTP-Status-Code = 200
(0x03000000):Date = 'Wed, 15 Sep 2010 17:20:52 GMT'
(0x03000000):Server = 'Apache/2.0.50 (Win32) mod_ssl/2.0.50 OpenSSL/0.9.7d PHP/4.3.10'
(0x03000000):Content-Length = '2543'
(0x03000000):Connection = 'close'
(0x03000000):Content-Type = 'multipart/related; boundary="MIME_boundary"; type="text/xml"; start="<cid:titi.xml@toto.fr>"'
)
(0x01000000):MIME = |
From the service trace:
| Quote: |
2010-09-15 19:49:10.732299 1048 UserTrace BIP4007I: Message transmis au terminal 'out' du noeud 'WSTEST_MFP1.WSTEST_MFP1.Compute'.
2010-09-15 19:49:11.058754 1048 UserTrace BIP4007I: Message transmis au terminal 'out' du noeud 'WSTEST_MFP1.WSTEST_MFP1.HTTP Request'.
2010-09-15 19:49:11.058801 1048 UserTrace BIP6060I: Le type d'analyseur syntaxique ''Properties'' a été créé au nom du noeud 'WSTEST_MFP1.WSTEST_MFP1.HTTP Request' pour gérer la partie de message entrant d'une longueur de 0 octets à partir de la position '0'.
2010-09-15 19:49:11.058893 1048 UserTrace BIP6061I: Le type d'analyseur syntaxique ''HTTPResponseHeader'' a été créé au nom du noeud 'WSTEST_MFP1.WSTEST_MFP1.HTTP Request' pour gérer la partie de message entrant d'une longueur de 284 octets à partir de la position '0'.Le type d'analyseur syntaxique a été sélectionné sur la base de la valeur ''WSRSPHDR'' provenant de l'analyseur précédent.
2010-09-15 19:49:11.058950 1048 UserTrace BIP6061I: Le type d'analyseur syntaxique ''MIME'' a été créé au nom du noeud 'WSTEST_MFP1.WSTEST_MFP1.HTTP Request' pour gérer la partie de message entrant d'une longueur de 2543 octets à partir de la position '284'.Le type d'analyseur syntaxique a été sélectionné sur la base de la valeur ''MIME'' provenant de l'analyseur précédent.
2010-09-15 19:49:11.059000 1048 UserTrace BIP2540I: Noeud 'WSTEST_MFP1.WSTEST_MFP1.Trace' : fin de l'évaluation de l'expression ''CURRENT_TIMESTAMP'' à la position ('', '3.3'). Le résultat était ''TIMESTAMP '2010-09-15 19:49:11.058777'''.
2010-09-15 19:49:11.059022 1048 UserTrace BIP2539I: Noeud 'WSTEST_MFP1.WSTEST_MFP1.Trace' : Evaluation de l'expression ''Root'' sur ('', '4.3'). Cela a été converti vers ''Root''. Le résultat est le suivant : ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2010-09-15 19:49:11.059512 1048 Error BIP2230E: Erreur détectée lors du traitement d'un message dans le noeud 'WSTEST_MFP1.WSTEST_MFP1.Trace'.
Le courtier de messages a détecté une erreur lors du traitement d'un message dans le noeud 'WSTEST_MFP1.WSTEST_MFP1.Trace'. Une exception a été générée pour interrompre le traitement du message.
Pour plus de détails, consultez les messages suivants.
2010-09-15 19:49:11.059519 1048 RecoverableException BIP3156S: Une erreur a été détectée lors de l'analyse des données d'en-tête 'MIME'. Un nom d'en-tête 'MIME' est vide ou contient des caractères non valides à la position : 0.
Un nom d'en-tête 'MIME' ne peut ni être vide ni contenir des caractères non valides.
2010-09-15 19:49:11.059554 1048 UserTrace BIP4067I: Message propagé vers le terminal de sortie pour le noeud Trace 'WSTEST_MFP1.WSTEST_MFP1.Trace'.
Le noeud Trace 'WSTEST_MFP1.WSTEST_MFP1.Trace' a reçu un message et le propage à tous les noeuds connectés à son terminal de sortie.
Aucune intervention de l'utilisateur n'est requise.
|
Below is the raw response from soapUI, anonymized and with the XML data shortened:
| Quote: |
HTTP/1.1 200 OK
Date: Wed, 15 Sep 2010 12:33:08 GMT
Server: Apache/2.0.50 (Win32) mod_ssl/2.0.50 OpenSSL/0.9.7d PHP/4.3.10
Content-Length: 2573
Content-Type: multipart/related; boundary="MIME_boundary"; type="text/xml"; start="<cid:titi.xml@toto.fr>"
--MIME_boundary
Content-Type: text/xml; charset=utf-8
Content-Transfer-Encoding: binary
Content-ID: <cid:titi.xml@toto.fr>
<?xml version="1.0" encoding="ISO-8859-1"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns2="www.toto.fr/wsdl/rpcenc/wsdl/" xmlns:ns1="http://schemas.xmlsoap.org/wsdl/"><SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><ns1:InterrogationResponse><REP_TOTO><REQUETE_TOTO_RETOUR><INFO1>INFO</INFO1><INFO2>INFO</INFO2><REP ID="titiXXX" href="cid:titi.xml@toto.fr"></REP></REQUETE_TOTO_RETOUR></REP_TOTO></ns1:InterrogationResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
--MIME_boundary
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: binary
Content-ID: <titi.xml@toto.fr>
<INFOSUP><INFOSUP1>1</INFOSUP1><INFOSUP2>111153</INFOSUP2></INFOSUP>
--MIME_boundary-- |
Another point is the content length is not the same between soapUI and the toolkit.
Any help appreciated, thanks by advance. |
|
| Back to top |
|
 |
| mgk |
| Posted: Thu Sep 16, 2010 12:55 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1647
|
Hi.
Given that the content-length is different between SOAP UI and the call from Broker, is it possible that the response is somehow cut short when it is returned to Broker? One way to check would be to use an HTTP trafic monitor to look at the data on the wire between Broker and the Server. If this should that this is not happening however, then I think you need to raise a PMR to get this looked at by IBM service as this should work...
Kind Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| sguerin |
| Posted: Thu Sep 16, 2010 1:42 am Post subject: |
|
|
Newbie
Joined: 14 Sep 2010
Posts: 5
|
Thanks for the answer.
I found out the length difference: there was a different namespace for the soap envelope, and a additionnal optional empty parameter in the request that generated an extra parameter in the answer... So the request wasn't exactly the same!
With exactly the same request, the length of the WS answer is of 2543 within the toolkit and soapUI. |
|
| Back to top |
|
|
| mgk |
| Posted: Thu Sep 16, 2010 1:47 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1647
|
Does it work now or is it still failing?
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| sguerin |
| Posted: Thu Sep 16, 2010 1:57 am Post subject: |
|
|
Newbie
Joined: 14 Sep 2010
Posts: 5
|
I only changed the soapUI request.
So I have always the issue with the toolkit. |
|
| Back to top |
|
|
| mgk |
| Posted: Thu Sep 16, 2010 3:12 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1647
|
So the next step here is to raise a PMR...
Kind Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| sguerin |
| Posted: Thu Sep 16, 2010 7:10 am Post subject: |
|
|
Newbie
Joined: 14 Sep 2010
Posts: 5
|
I think the PMR will be the next step.
By the way, the MIME parser was new in the V6.0 version but I don't find any example or testimony of MIME parsing... was it really used (within HTTP Request node or with the creation of a field with domain Mime)? |
|
| Back to top |
|
|
| mgk |
| Posted: Thu Sep 16, 2010 9:00 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1647
|
| Quote: |
| By the way, the MIME parser was new in the V6.0 version but I don't find any example or testimony of MIME parsing... was it really used (within HTTP Request node or with the creation of a field with domain Mime)? |
Yes, it can be used for both these cases...
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| cadenza |
| Posted: Mon Aug 19, 2013 8:21 am Post subject: Did this issue get resolved via PMR? |
|
|
Apprentice
Joined: 01 Jun 2004
Posts: 48
|
Hi - I am encountering intermittent issues with the same error message. I am on v8 Fix2.
Do we know if a PMR was created and this issue was resolved? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Aug 19, 2013 8:36 am Post subject: Re: Did this issue get resolved via PMR? |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| cadenza wrote: |
Hi - I am encountering intermittent issues with the same error message. I am on v8 Fix2.
Do we know if a PMR was created and this issue was resolved? |
There is no relationship between your problem and the original post. Don't open years old posts, especially on runtime versions that are seven years old. Do your OWN work, create your OWN post.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| satendranegi |
| Posted: Sat Jul 16, 2016 12:18 pm Post subject: |
|
|
Newbie
Joined: 30 Sep 2015
Posts: 6
|
This rest web service was working fine with 9.0.0.0 Version, updated toolkit to 9.0.0.3 , now getting this error, any idea about this guys ?
RecoverableException
File:CHARACTER:F:\build\slot1\S000_P\src\WebServices\WSLibrary\ImbWSRFC822HeaderParser.cpp
Line:INTEGER:446
Function:CHARACTER:ImbRFC822HeaderParser::parseLine
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3156
Text:CHARACTER:Empty or invalid header found at position: &1.
Insert
Type:INTEGER:2
Text:CHARACTER:96
Insert
Type:INTEGER:14
Text:CHARACTER:HTTP
RecoverableException
File:CHARACTER:F:\build\slot1\S000_P\src\WebServices\WSLibrary\ImbWSRFC822HeaderParser.cpp
Line:INTEGER:707
Function:CHARACTER:ImbWSRFC822HeaderParser::throwInvalidCharacterException
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3168
Text:CHARACTER:invalid character in header field
Insert
Type:INTEGER:14
Text:CHARACTER:X-Frame-Options
Insert
Type:INTEGER:2
Text:CHARACTER:32
Insert
Type:INTEGER:2
Text:CHARACTER:16
Insert
Type:INTEGER:14
Text:CHARACTER:HTTP |
|
| Back to top |
|
|
| adubya |
| Posted: Sat Jul 16, 2016 12:46 pm Post subject: |
|
|
Partisan
Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK
|
This thread relates to a MB v6 issue and is very old.
I suggest opening a new thread with your IIB v9 issue, refer to this thread if necessary.
_________________
Independent Middleware Consultant
andy@knownentity.com |
|
| Back to top |
|
|
|
|
