| Author |
Message
|
| mrgate |
 Posted: Mon Jan 21, 2008 3:55 pm Post subject: HttpRequest Node problem. |
 |
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
Hello All,
I am working on windows xp platform on MB6.0.
From my flow, I am calling a web service.
My flow is:
(MqInput)-->(Compute)-->(HttpRequest)-->(Compute)-->(MqOutput)
In the HttpRequest node,set Message Domain to 'xml'
]
WebService flow is:
(HttpInput)-->(Compute)-->(Mqoutput)-->(Mqget)-->(Compute)-->(HttpReply)
Getting data from mqget node and sending as webservice response data.
Everything is working fine with web service flow. Problem is with HttpRequest node where response data is xml parsing error have occured.
can anyone resolve problem.
_________________
MQSeries terrorist |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Jan 21, 2008 4:59 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Please don't use the XML domain. Please use XMLNS or XMLNSC instead.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Mon Jan 21, 2008 7:51 pm Post subject: Re: HttpRequest Node problem. |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| mrgate wrote: |
Problem is with HttpRequest node where response data is xml parsing error have occured.
|
implies that message is not correctly formed XML and hence MB is not able to parse it.
_________________
Cheers |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jan 22, 2008 1:58 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| parsing error have occured |
Quote the error message in full. Nobody can help unless you tell us what the problem is.
Using the XML domain in a web services message flow is very bad practice. It does not support namespaces, and it is deprecated. Use XMLNS or XMLNSC. |
|
| Back to top |
|
|
| mrgate |
| Posted: Tue Jan 22, 2008 2:42 am Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
Hello All,
Now, I have changed the domain to XMLNSC in all the nodes and esql and have kept the trace before HttpReply node and after HttpRequest node but still getting same problem.
Trace before HttpReply node is:
PROPERTIES:(
(0x03000000):MessageSet = ''
(0x03000000):MessageType = ''
(0x03000000):MessageFormat = ''
(0x03000000):Encoding = 546
(0x03000000):CodedCharSetId = 437
(0x03000000):Transactional = FALSE
(0x03000000):Persistence = FALSE
(0x03000000):CreationTime = GMTTIMESTAMP '2008-01-22 21:10:58.060'
(0x03000000):ExpirationTime = -1
(0x03000000):Priority = 0
(0x03000000):ReplyIdentifier = X'000000000000000000000000000000000000000000000000'
(0x03000000):ReplyProtocol = 'SOAP-HTTP'
(0x03000000):Topic = NULL
(0x03000000):ContentType = ''
)
***************************************************************************************************
ROOT:(
(0x01000000):Properties = (
(0x03000000):MessageSet = ''
(0x03000000):MessageType = ''
(0x03000000):MessageFormat = ''
(0x03000000):Encoding = 546
(0x03000000):CodedCharSetId = 437
(0x03000000):Transactional = FALSE
(0x03000000):Persistence = FALSE
(0x03000000):CreationTime = GMTTIMESTAMP '2008-01-22 21:10:58.060'
(0x03000000):ExpirationTime = -1
(0x03000000):Priority = 0
(0x03000000):ReplyIdentifier = X'000000000000000000000000000000000000000000000000'
(0x03000000):ReplyProtocol = 'SOAP-HTTP'
(0x03000000):Topic = NULL
(0x03000000):ContentType = ''
)
(0x01000000):MQMD = (
(0x03000000):SourceQueue = ''
(0x03000000):Transactional = FALSE
(0x03000000):Encoding = 546
(0x03000000):CodedCharSetId = 437
(0x03000000):Format = ' '
(0x03000000):Version = 2
(0x03000000):Report = 0
(0x03000000):MsgType = 8
(0x03000000):Expiry = -1
(0x03000000):Feedback = 0
(0x03000000):Priority = 0
(0x03000000):Persistence = 0
(0x03000000):MsgId = X'414d51205742524b365f44454641554cb252964720005405'
(0x03000000):CorrelId = X'000000000000000000000000000000000000000000000000'
(0x03000000):BackoutCount = 0
(0x03000000):ReplyToQ = ' '
(0x03000000):ReplyToQMgr = 'WBRK6_DEFAULT_QUEUE_MANAGER '
(0x03000000):UserIdentifier = 'Michael '
(0x03000000):AccountingToken = X'16010515000000fe33ebce1b7605e768c9199fee03000000000000000000000b'
(0x03000000):ApplIdentityData = ' '
(0x03000000):PutApplType = 11
(0x03000000):PutApplName = 'ael\My Documents\rfhUtil.exe'
(0x03000000):PutDate = DATE '2008-01-22'
(0x03000000):PutTime = GMTTIME '21:10:58.060'
(0x03000000):ApplOriginData = ' '
(0x03000000):GroupId = X'000000000000000000000000000000000000000000000000'
(0x03000000):MsgSeqNumber = 1
(0x03000000):Offset = 0
(0x03000000):MsgFlags = 0
(0x03000000):OriginalLength = -1
)
(0x01000000):XMLNSC = (
(0x01000000):STUDENT = (
(0x01000000):A = (
(0x03000000):B = 'HELLO'
)
(0x03000000):B = 'http://localhost:7080/SERVICE1'
)
)
)
***************************************************************************************************
DESTINATION LIST:
***************************************************************************************************
LOCAL ENVIRONMENT:
***************************************************************************************************
ENVIRONMENT:
Trace after HttpRequest node is:
PROPERTIES:(
(0x03000000):MessageSet = ''
(0x03000000):MessageType = ''
(0x03000000):MessageFormat = ''
(0x03000000):Encoding = 546
(0x03000000):CodedCharSetId = 1208
(0x03000000):Transactional = FALSE
(0x03000000):Persistence = FALSE
(0x03000000):CreationTime = GMTTIMESTAMP '2008-01-22 21:10:41.350'
(0x03000000):ExpirationTime = -1
(0x03000000):Priority = 0
(0x03000000):ReplyIdentifier = X'000000000000000000000000000000000000000000000000'
(0x03000000):ReplyProtocol = 'MQ'
(0x03000000):Topic = NULL
(0x03000000):ContentType = 'text/xml;charset=utf-8'
)
***************************************************************************************************
ROOT:(
(0x01000000):Properties = (
(0x03000000):MessageSet = ''
(0x03000000):MessageType = ''
(0x03000000):MessageFormat = ''
(0x03000000):Encoding = 546
(0x03000000):CodedCharSetId = 1208
(0x03000000):Transactional = FALSE
(0x03000000):Persistence = FALSE
(0x03000000):CreationTime = GMTTIMESTAMP '2008-01-22 21:10:41.350'
(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):Content-Type = 'text/xml;charset=utf-8'
(0x03000000):Content-Length = '441'
(0x03000000):Date = 'Tue, 22 Jan 2008 21:11:13 GMT'
(0x03000000):Server = 'Apache-Coyote/1.1'
(0x03000000):Connection = 'close'
)
(0x01000000):XMLNSC =
)
***************************************************************************************************
DESTINATION LIST:(
(0x01000000):Destination = (
(0x01000000):HTTP = (
(0x03000000):RequestURL = 'http://localhost:7080/SERVICE1'
)
)
)
***************************************************************************************************
LOCAL ENVIRONMENT:(
(0x01000000):Destination = (
(0x01000000):HTTP = (
(0x03000000):RequestURL = 'http://localhost:7080/SERVICE1'
)
)
)
***************************************************************************************************
ENVIRONMENT:
Need some ones help to resolve the problem.
_________________
MQSeries terrorist |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 22, 2008 2:59 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mrgate wrote: |
| still getting same problem. |
Yes, but what problem? What's the error message? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mrgate |
| Posted: Tue Jan 22, 2008 3:21 am Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
xml parsing error have occured when the message is coming from HttpRequest node.
_________________
MQSeries terrorist |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 22, 2008 3:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mrgate wrote: |
| xml parsing error have occured when the message is coming from HttpRequest node. |
And that's the text of the message: "xml parsing error have occured"? No BIP number, no additional diagnostics?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mrgate |
| Posted: Tue Jan 22, 2008 3:47 am Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
Yes, No BIP number and after the result in the final output queue is:
Msg read from TEST.FINALOUT.QUEUE length=0
_________________
MQSeries terrorist |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 22, 2008 3:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
So there's a missing or invalid reply being returned. Application error.
(If the XML being returned was badly formed, there should be a BIP error from the broker reporting a parsing error. This just gives you an empty message tree as per the "after" trace)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mrgate |
| Posted: Tue Jan 22, 2008 4:01 am Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
| Vitor wrote: |
So there's a missing or invalid reply being returned. Application error.
(If the XML being returned was badly formed, there should be a BIP error from the broker reporting a parsing error. This just gives you an empty message tree as per the "after" trace) |
What I am trying to do is I am sending response data retrieved from the middle of flow using mqget node and not from HttpInput node. You can see from the trace file before the HttpReply node under XMLNSC domain well formed. upto my knowledge It was well formed. can anyone give me response for this one.
_________________
MQSeries terrorist |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 22, 2008 4:27 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Why is there an MQMD and no HTTP (see trace) going into the HTTP reply ? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mrgate |
| Posted: Tue Jan 22, 2008 6:19 am Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
| fjb_saper wrote: |
| Why is there an MQMD and no HTTP (see trace) going into the HTTP reply ? |
I thing that wont cause any problem where HttpReply node will create default header.
_________________
MQSeries terrorist |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jan 22, 2008 6:36 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Fact : WMB never reports an XML parsing error except as part of a BIP message. If you are attempting to diagnose this problem using the flow debugger, you will sometimes get a partial error message.
Please take a user trace - it will contain the full text of all error messages, and the problem should become obvious immediately. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jan 22, 2008 6:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| mrgate wrote: |
| fjb_saper wrote: |
| Why is there an MQMD and no HTTP (see trace) going into the HTTP reply ? |
I thing that wont cause any problem where HttpReply node will create default header. |
I think you are wrong, as I'm quite sure the HTTPReply node will include the MQMD in the HTTP body that it sends.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
