ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » IIB9 HTTPRequest Node: BLOB UnknownParserName

Post new topic  Reply to topic
 IIB9 HTTPRequest Node: BLOB UnknownParserName « View previous topic :: View next topic » 
Author Message
akil
PostPosted: Thu Sep 18, 2014 1:14 am    Post subject: IIB9 HTTPRequest Node: BLOB UnknownParserName Reply with quote

Partisan

Joined: 27 May 2014
Posts: 338
Location: Mumbai
Hi

I've a flow that has the following nodes
HttpInput --> HttpRequest --> Trace --> HttpReply

HttpInput, is configured for at /xfer , it is just to trigger the flow.
HttpRequest, is configured to make a GET call to fetch an image, the URL specified is http://upload.wikimedia.org/wikipedia/commons/9/9a/TajMinaret1.jpg
The flow works in the sense that when I invoke the flow, I see the image fetched by HttpRequest and copied to OutputRoot which is then returned by HttpReply.

But when I look at the Trace output ( I am printing ${Root} ), I see the following :

Code:

                                         (0x01000000:Name):HTTPResponseHeader = ( ['WSRSPHDR' : 0x7f2608537750]
                                           (0x03000000:NameValue):X-Original-HTTP-Status-Line   = 'HTTP/1.1 200 OK' (CHARACTER)
                                           (0x03000000:NameValue):X-Original-HTTP-Status-Code   = 200 (INTEGER)
                                           (0x03000000:NameValue):X-Object-Meta-Sha1base36      = 'moseo882tskshttmz91s5s7skjuyokh' (CHARACTER)
                                           (0x03000000:NameValue):Last-Modified                 = 'Sun, 06 Oct 2013 17:08:01 GMT' (CHARACTER)
                                           (0x03000000:NameValue):ETag                          = 'edbe6169c14d5dd6748ad38ce21d0086' (CHARACTER)
                                           (0x03000000:NameValue):X-Timestamp                   = '1381079280.84648' (CHARACTER)
                                           (0x03000000:NameValue):Content-Type                  = 'image/jpeg' (CHARACTER)
                                           (0x03000000:NameValue):X-Trans-Id                    = 'txc3638a1e75db4f77939c8-00541a2452' (CHARACTER)
                                           (0x03000000:NameValue):X-Varnish                     = '1419144544 1378032171, 3644640485' (CHARACTER)
                                           (0x03000000:NameValue):Via                           = '1.1 varnish, 1.1 varnish' (CHARACTER)
                                           (0x03000000:NameValue):Content-Length                = '208535' (CHARACTER)
                                           (0x03000000:NameValue):Accept-Ranges                 = 'bytes' (CHARACTER)
                                           (0x03000000:NameValue):Date                          = 'Thu, 18 Sep 2014 06:19:21 GMT' (CHARACTER)
                                           (0x03000000:NameValue):Age                           = '21784' (CHARACTER)
                                           (0x03000000:NameValue):X-Cache                       = 'cp1064 hit (17), cp1061 frontend miss (0)' (CHARACTER)
                                           (0x03000000:NameValue):Access-Control-Allow-Origin   = '*' (CHARACTER)
                                           (0x03000000:NameValue):Access-Control-Expose-Headers = 'Age, Content-Length, Date, X-Cache, X-Varnish' (CHARACTER)
                                           (0x03000000:NameValue):Expires                       = 'Fri, 19 Sep 2014 06:19:21 GMT' (CHARACTER)
                                           (0x03000000:NameValue):Connection                    = 'close' (CHARACTER)
                                         )
                                         (0x01000000:Name):BLOB               = ( ['none' : 0x7f2608537a40]
                                           (0x03000000:NameValue):UnknownParserName = '' (CHARACTER)
                                           (0x03000000:NameValue):BLOB              = X'ffd8ffe11e8045786966000049492a00080000000b000f0102000800000092000000100102001f0000009a0000001201030001000000010000001


Note the 'UnknownParserName'.

Now, when I change the 'Response Message Parsing/Parser Options' to 'Complete', ( the default is OnDemand ), the trace output is better, it does not contain the UnknownParserName, as seen below.

Code:

                                         (0x01000000:Name):HTTPResponseHeader = ( ['WSRSPHDR' : 0x7f26084819b0]
                                           (0x03000000:NameValue):X-Original-HTTP-Status-Line   = 'HTTP/1.1 200 OK' (CHARACTER)
                                           (0x03000000:NameValue):X-Original-HTTP-Status-Code   = 200 (INTEGER)
                                           (0x03000000:NameValue):X-Object-Meta-Sha1base36      = 'moseo882tskshttmz91s5s7skjuyokh' (CHARACTER)
                                           (0x03000000:NameValue):Last-Modified                 = 'Sun, 06 Oct 2013 17:08:01 GMT' (CHARACTER)
                                           (0x03000000:NameValue):ETag                          = 'edbe6169c14d5dd6748ad38ce21d0086' (CHARACTER)
                                           (0x03000000:NameValue):X-Timestamp                   = '1381079280.84648' (CHARACTER)
                                           (0x03000000:NameValue):Content-Type                  = 'image/jpeg' (CHARACTER)
                                           (0x03000000:NameValue):X-Trans-Id                    = 'txc3638a1e75db4f77939c8-00541a2452' (CHARACTER)
                                           (0x03000000:NameValue):X-Varnish                     = '1419142020 1378032171, 658157759 658037561' (CHARACTER)
                                           (0x03000000:NameValue):Via                           = '1.1 varnish, 1.1 varnish' (CHARACTER)
                                           (0x03000000:NameValue):Content-Length                = '208535' (CHARACTER)
                                           (0x03000000:NameValue):Accept-Ranges                 = 'bytes' (CHARACTER)
                                           (0x03000000:NameValue):Date                          = 'Thu, 18 Sep 2014 06:20:30 GMT' (CHARACTER)
                                           (0x03000000:NameValue):Age                           = '21853' (CHARACTER)
                                           (0x03000000:NameValue):X-Cache                       = 'cp1064 hit (16), cp1049 frontend hit (1)' (CHARACTER)
                                           (0x03000000:NameValue):Access-Control-Allow-Origin   = '*' (CHARACTER)
                                           (0x03000000:NameValue):Access-Control-Expose-Headers = 'Age, Content-Length, Date, X-Cache, X-Varnish' (CHARACTER)
                                           (0x03000000:NameValue):Expires                       = 'Fri, 19 Sep 2014 06:20:30 GMT' (CHARACTER)
                                           (0x03000000:NameValue):Connection                    = 'close' (CHARACTER)
                                         )
                                         (0x01000000:Name):BLOB               = ( ['none' : 0x7f2608518d10]
                                           (0x03000000:NameValue):BLOB              = X'ffd8ffe11e8045786966000049492a00080000000b000f0102000800000092000000100102001f0000009a0000001201030001000000010000001



I thought that the Parser Options applied only to XMLNSC parser (That's what the property window says).

1. Does the Parser Option apply to BLOB as well?
2. Why does UnknownParser come in the first place when I've set the Message Domain as BLOB?
3. The UnknownParser does not seem to impact the result of the flow, I can see the image returned in both the cases?

I stumbled upon this, as I am trying to figure out how to write a flow that picks up images from a URL and stores them in a database, so I wrote this flow to see the HTTPRequest part, and my next step would have been to serialise the BLOB ...
_________________
Regards
Back to top
View user's profile Send private message Visit poster's website
akil
PostPosted: Thu Sep 18, 2014 4:08 am    Post subject: Reply with quote

Partisan

Joined: 27 May 2014
Posts: 338
Location: Mumbai
It is documented that a message in the BLOB domain will have 2 elements, one called BLOB and the other UnknownParserName.

http://www-01.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ad09650_.htm

When I debugged the flow, I see that the UnknownParserName is present in both cases, for some reason the Trace node was not writing the UnknownParserName when I set the Parser Options, but the element exists when I see it in debug, I guess I can ignore it.
_________________
Regards
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » IIB9 HTTPRequest Node: BLOB UnknownParserName
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.