| Author |
Message
|
| kotagiriaashish |
 Posted: Sat Aug 13, 2011 6:36 am Post subject: SOAP Async Request Reply [Unsolved] |
 |
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
Well..
I m just doing a scenario on SOAP Async Request Reply nodes, the problem i am facing is, The message reaches soap Input node from the soap async Request node but the reply from the soap reply never reaches soap async resp node
i also tried:
SET OutputLocalEnvironment.Destination.SOAP.Request.WSA.ReplyTo = 'http://localhost:7800/svr';
Trace:
| Code: |
Timestamps are formatted in local time, 330 minutes past GMT.
Trace written by version ; formatter version 7000 (build S000-L91028)
2011-08-13 19:59:37.847743 3200 UserTrace BIP4040I: The Execution Group ''default'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2011-08-13 19:59:37.848197 3200 UserTrace BIP2638I: The MQ output node '.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''MB7QMGR''. The MQCC was '0' and the MQRC was '0'.
2011-08-13 19:59:37.848217 3200 UserTrace BIP2622I: Message successfully output by output node '.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''MB7QMGR''.
2011-08-13 19:59:37.848480 3200 Information BIP2154I: Execution group finished with Configuration message.
A command response will be sent to the broker.
No user action required.
2011-08-13 19:59:49.126811 3200 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node '.InputNode'.
2011-08-13 19:59:49.126926 3200 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node '.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2011-08-13 19:59:49.126956 3200 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node '.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2011-08-13 19:59:49.127010 3200 UserTrace BIP6069W: The broker is not capable of handling a message of data type ''''.
The message broker received a message that requires the handling of data of type '''', but the broker does not have the capability to handle data of this type.
Check both the message being sent to the message broker and the configuration data for the node. References to the unsupported data type must be removed if the message is to be processed by the broker.
2011-08-13 19:59:49.127109 3200 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node '.InputNode' to handle portion of incoming message of length '232' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
Threads encountered in this trace:
3200
|
Last edited by kotagiriaashish on Fri Aug 19, 2011 11:55 am; edited 1 time in total |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Sat Aug 13, 2011 6:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Your trace doesn't show anything relevant to the execution of your flow. |
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Sat Aug 13, 2011 7:02 am Post subject: |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
ya...thats what im thinking too...
is there anything wrong with this?
| Code: |
2011-08-13 19:59:49.127010 3200 UserTrace BIP6069W: The broker is not capable of handling a message of data type ''''.
The message broker received a message that requires the handling of data of type '''', but the broker does not have the capability to handle data of this type. |
|
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Sat Aug 13, 2011 7:16 am Post subject: |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
| mqjeff wrote: |
| Your trace doesn't show anything relevant to the execution of your flow. |
I tried doing the trace again, the same trace is being generated... |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Aug 13, 2011 7:36 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| kotagiriaashish wrote: |
ya...thats what im thinking too...
is there anything wrong with this?
| Code: |
2011-08-13 19:59:49.127010 3200 UserTrace BIP6069W: The broker is not capable of handling a message of data type ''''.
The message broker received a message that requires the handling of data of type '''', but the broker does not have the capability to handle data of this type. |
|
There is nothing wrong fatally with this.
Take a look at the class of error.
W = Warning.
If there was an 'E' type error I'd be more concerned.
This error (IIRC) is from an incorrectly (but not fatally) configured Input Node.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Aug 13, 2011 7:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| kotagiriaashish wrote: |
| mqjeff wrote: |
| Your trace doesn't show anything relevant to the execution of your flow. |
I tried doing the trace again, the same trace is being generated... |
You are stopping the trace too soon.
Start the trace.
Send your message.
Wait for something to show up in an error log or otherwise as a bad request.
Then collect the trace. |
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Sat Aug 13, 2011 7:50 am Post subject: |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
| mqjeff wrote: |
| kotagiriaashish wrote: |
| mqjeff wrote: |
| Your trace doesn't show anything relevant to the execution of your flow. |
I tried doing the trace again, the same trace is being generated... |
You are stopping the trace too soon.
Start the trace.
Send your message.
Wait for something to show up in an error log or otherwise as a bad request.
Then collect the trace. |
I type in
| Code: |
mqsichangetrace MB7BROKER -u -e default -l debug -r
mqsireadlog MB7BROKER -u -e default -o C:\Books\Trace.xml |
and then i run the flow then i run
| Code: |
| mqsiformatlog -i C:\Books\Trace.xml -o C:\Books\Trace.txt |
i have been doing this all the time i dont know whats wrong with it....
one more point: there is no exception or anything with the flow.... the message never shows up at the soap async reply node... i have configured the unique identifier as "svr for both".... is there anything else to do?  |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Aug 13, 2011 8:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Don't run the mqsireadlog until *after* you run the flow.
The mqsiREADlog is what READS the LOG to GATHER the trace.
The mqsiFORMATlog is what FORMATS the log data to make it readable. |
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Sat Aug 13, 2011 8:10 am Post subject: |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
| mqjeff wrote: |
Don't run the mqsireadlog until *after* you run the flow.
The mqsiREADlog is what READS the LOG to GATHER the trace.
The mqsiFORMATlog is what FORMATS the log data to make it readable. |
Thanks... i mean i dint know how to do it all this time.... thats soo dumb... ok hears the trace
| Code: |
Timestamps are formatted in local time, 330 minutes past GMT.
Trace written by version ; formatter version 7000 (build S000-L91028)
2011-08-13 21:38:20.532814 3200 UserTrace BIP4040I: The Execution Group ''default'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2011-08-13 21:38:20.533523 3200 UserTrace BIP2638I: The MQ output node '.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''MB7QMGR''. The MQCC was '0' and the MQRC was '0'.
2011-08-13 21:38:20.533544 3200 UserTrace BIP2622I: Message successfully output by output node '.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''MB7QMGR''.
2011-08-13 21:38:20.533775 3200 Information BIP2154I: Execution group finished with Configuration message.
A command response will be sent to the broker.
No user action required.
2011-08-13 21:38:28.993455 4772 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ASYNC_Pair.MQInput'.
2011-08-13 21:38:28.993612 4772 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ASYNC_Pair.MQInput' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2011-08-13 21:38:28.993684 4772 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ASYNC_Pair.MQInput' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2011-08-13 21:38:28.993783 4772 UserTrace BIP6069W: The broker is not capable of handling a message of data type ''MQSTR''.
The message broker received a message that requires the handling of data of type ''MQSTR'', but the broker does not have the capability to handle data of this type.
Check both the message being sent to the message broker and the configuration data for the node. References to the unsupported data type must be removed if the message is to be processed by the broker.
2011-08-13 21:38:28.993833 4772 UserTrace BIP6061I: Parser type ''XMLNSC'' created on behalf of node 'ASYNC_Pair.MQInput' to handle portion of incoming message of length '670' bytes beginning at offset '364'. Parser type selected based on value ''XMLNSC'' from previous parser.
2011-08-13 21:38:32.070995 4772 UserTrace BIP3719I: Node '' sending SOAP request via transport 'HTTP' ('localhost:7800') for operation 'Operation1' of type 'request-response'.
See subsequent messages for success or failure messages relating to this request, and for any transport-specific messages.
No action required.
2011-08-13 21:38:32.073280 4772 UserTrace BIP3633I: Node '' sending HTTP data to URL '/MS_WSDLSOAP_HTTP_Service' at host 'localhost' (port 7800).
The broker is sending data via HTTP to a remote server at host 'localhost' (port 7800) using URL '/MS_WSDLSOAP_HTTP_Service'. See subsequent messages for success or failure messages relating to this request.
No action required.
2011-08-13 21:38:32.073886 2144 UserTrace BIP3630I: The broker has received an HTTP message on port '7800' with URL path '/MS_WSDLSOAP_HTTP_Service'.
The broker is listening on port '7800' and has received a message sent by a client using URL path '/MS_WSDLSOAP_HTTP_Service'. This message will be sent on to either a SOAP Input Node or a SOAP Asynchronous Response Node.
No action required.
2011-08-13 21:38:32.076496 184 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'SERVER.SOAP Input' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2011-08-13 21:38:32.076534 184 UserTrace BIP6069W: The broker is not capable of handling a message of data type ''''.
The message broker received a message that requires the handling of data of type '''', but the broker does not have the capability to handle data of this type.
Check both the message being sent to the message broker and the configuration data for the node. References to the unsupported data type must be removed if the message is to be processed by the broker.
2011-08-13 21:38:32.076614 184 UserTrace BIP6061I: Parser type ''SOAP'' created on behalf of node 'SERVER.SOAP Input' to handle portion of incoming message of length '4' bytes beginning at offset '0'. Parser type selected based on value ''SOAP'' from previous parser.
2011-08-13 21:38:32.077152 184 UserTrace BIP3907I: Message received and propagated to 'out' terminal of input node 'SERVER.SOAP Input'.
2011-08-13 21:38:32.899269 184 UserTrace BIP2537I: Node 'SERVER.Compute': Executing statement ''BEGIN ... END;'' at ('.SERVER_Compute.Main', '2.2').
2011-08-13 21:38:32.899322 184 UserTrace BIP2537I: Node 'SERVER.Compute': Executing statement ''CopyEntireMessage();'' at ('.SERVER_Compute.Main', '4.3').
2011-08-13 21:38:32.899375 184 UserTrace BIP2538I: Node 'SERVER.Compute': Evaluating expression ''CopyEntireMessage()'' at ('.SERVER_Compute.Main', '4.8').
2011-08-13 21:38:32.899406 184 UserTrace BIP2537I: Node 'SERVER.Compute': Executing statement ''BEGIN ... END;'' at ('.SERVER_Compute.CopyEntireMessage', '1.39').
2011-08-13 21:38:32.899429 184 UserTrace BIP2537I: Node 'SERVER.Compute': Executing statement ''SET OutputRoot = InputRoot;'' at ('.SERVER_Compute.CopyEntireMessage', '2.3').
2011-08-13 21:38:32.900131 184 UserTrace BIP2539I: Node 'SERVER.Compute': Evaluating expression ''InputRoot'' at ('.SERVER_Compute.CopyEntireMessage', '2.20'). This resolved to ''InputRoot''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2011-08-13 21:38:32.900157 184 UserTrace BIP2568I: Node 'SERVER.Compute': Copying sub-tree from ''InputRoot'' to ''OutputRoot''.
2011-08-13 21:38:32.900318 184 UserTrace BIP2537I: Node 'SERVER.Compute': Executing statement ''SET OutputLocalEnvironment.Destination.SOAP.Request.WSA.ReplyTo = 'http://localhost:7800/svr';'' at ('.SERVER_Compute.Main', '5.3').
2011-08-13 21:38:32.900833 184 UserTrace BIP2566I: Node 'SERVER.Compute': Assigning value '''http://localhost:7800/svr''' to field / variable ''OutputLocalEnvironment.Destination.SOAP.Request.WSA.ReplyTo''.
2011-08-13 21:38:32.900871 184 UserTrace BIP2537I: Node 'SERVER.Compute': Executing statement ''RETURN TRUE;'' at ('.SERVER_Compute.Main', '6.3').
2011-08-13 21:38:32.900978 184 UserTrace BIP4015I: Message propagated to the 'out' terminal of node 'SERVER.Compute' with the following message trees: ''.
2011-08-13 21:38:33.576412 184 UserTrace BIP6068W: A request was made to serialize a bitstream from element ''SOAP'' using parser ''SOAP''. The result was zero bytes long.
The node or ESQL ASBITSTREAM function requested that an element serialize its bitstream and this resulted in no bytes being written.
If the output bitstream should not have been zero bytes long, ensure that the correct element was specified.
If the parser name is blank or set to a root parser, associate an owning parser with the element:
If created in ESQL, the DOMAIN clause of the CREATE statement can be used.
If created using the user-defined extension API use a method that allows a parser to be specified.
2011-08-13 21:38:33.576503 184 UserTrace BIP3722I: Node '' sending a SOAP reply message to the originating client.
See subsequent messages for success or failure messages relating to this reply, and for any transport-specific messages.
No action required.
2011-08-13 21:38:33.577053 4772 UserTrace BIP3634I: Node '' received HTTP data from host 'localhost' with status code of 200.
The broker has received data via HTTP from a remote server at host 'localhost' with an HTTP status code of 200. Status codes beginning with a 2 indicate success; others imply errors in either client or server.
No action required.
2011-08-13 21:38:33.577133 4772 UserTrace BIP3721I: Node '' received a SOAP acknowledge message via transport 'HTTP' ('localhost:7800') for operation 'Operation1'.
The broker sent a SOAP request, and has received an acknowledgement from the server that the request was received. This may be because the message was sent as an asynchronous request, and therefore the response message will be sent elsewhere, or because the request message was a one-way message exchange pattern, and therefore no response message should be expected.
No action required.
2011-08-13 21:38:49.763404 3200 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node '.InputNode'.
2011-08-13 21:38:49.763542 3200 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node '.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2011-08-13 21:38:49.763572 3200 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node '.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2011-08-13 21:38:49.763626 3200 UserTrace BIP6069W: The broker is not capable of handling a message of data type ''''.
The message broker received a message that requires the handling of data of type '''', but the broker does not have the capability to handle data of this type.
Check both the message being sent to the message broker and the configuration data for the node. References to the unsupported data type must be removed if the message is to be processed by the broker.
2011-08-13 21:38:49.763664 3200 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node '.InputNode' to handle portion of incoming message of length '232' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
Threads encountered in this trace:
184 2144 3200 4772
|
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Aug 13, 2011 8:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| kotagiriaashish wrote: |
2011-08-13 21:38:33.576412 184 UserTrace BIP6068W: A request was made to serialize a bitstream from element ''SOAP'' using parser ''SOAP''. The result was zero bytes long.
The node or ESQL ASBITSTREAM function requested that an element serialize its bitstream and this resulted in no bytes being written.
If the output bitstream should not have been zero bytes long, ensure that the correct element was specified.
If the parser name is blank or set to a root parser, associate an owning parser with the element:
If created in ESQL, the DOMAIN clause of the CREATE statement can be used.
If created using the user-defined extension API use a method that allows a parser to be specified. |
So the flow that is supposed to provide the response is not doing so properly. |
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Sat Aug 13, 2011 8:25 am Post subject: |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
OKk...let me look into this.
Mmmm.. there is nothing wrong with the flow, i am able to see the data tree structure before the assembly reaches the soap reply node, it looks fine..
| Code: |
Message
Properties
MessageSet MS_WSDL
MessageType
MessageFormat
Encoding 546
CodedCharSetId 1208
Transactional false
Persistence false
CreationTime 2011-08-13 16:30:50.773
ExpirationTime -1
Priority 0
ReplyIdentifier 000000000000000000000000000000000000000000000000
ReplyProtocol SOAP_AXIS2
Topic
ContentType text/xml; charset=utf-8
IdentitySourceType
IdentitySourceToken
IdentitySourcePassword
IdentitySourceIssuedBy
IdentityMappedType
IdentityMappedToken
IdentityMappedPassword
IdentityMappedIssuedBy
HTTPInputHeader
X-Original-HTTP-Command POST http://localhost:7800/MS_WSDLSOAP_HTTP_Service HTTP/1.1
Content-Length 1508
Content-Type text/xml; charset=utf-8
Host localhost:7800
SOAPAction ""
Connection keep-alive
X-Remote-Addr 127.0.0.1
X-Remote-Host 127.0.0.1
X-Server-Name localhost
X-Server-Port 7800
X-Query-String
SOAP
Context
operation Operation1
operationType REQUEST_RESPONSE
portType MS_WSDLPortType
portTypeNamespace http://tempuri.org/MS_WSDL
port SOAP_HTTP_Port
service MS_WSDLSOAP_HTTP_Service
fileName C:\\Documents and Settings\\All Users\\Application Data\\IBM\\MQSI\\components\\MB7BROKER\\5d68d633-3001-0000-0080-bcc3e80e3b8e\\config\\XSD\\MS_WSDL/MS_WSDLService.wsdl
SOAP_Version 1.1
Namespace
soapenv http://schemas.xmlsoap.org/soap/envelope/
xsd http://www.w3.org/2001/XMLSchema
xsi http://www.w3.org/2001/XMLSchema-instance
q0 http://tempuri.org/PurchaseOrderSchema.xsd
_XmlDeclaration
Version 1.0
Encoding utf-8
Header
wsa http://www.w3.org/2005/08/addressing
To http://localhost:7800/MS_WSDLSOAP_HTTP_Service
mustUnderstand 1
ReplyTo
mustUnderstand 1
Address http://192.168.50.1:7800/WMB/Async/Response/Node/svr?context=534f41500100000000000000000000002c13000000000000×tamp=20513
ReferenceParameters
context
wmb http://www.ibm.com/wmb/2007/05/rp
operationName Operation1
timeStamp 20513
MessageID urn:uuid:AADA6185B57F8EF9761313253206980
mustUnderstand 1
Action http://tempuri.org/MS_WSDL/MS_WSDLPortType/Operation1_Input
mustUnderstand 1
Body
PurchaseOrder
OrderDate 2011-08-12
ShipTo
country US
name trrte
street tret
city ertretr
state etertret
zip 4354
BillTo
country US
name sddsfsf
street dsfegvgh
city dsfewdsg
state gsdgsdfsd
zip 234
|
|
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Mon Aug 15, 2011 4:59 am Post subject: |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
| !!! |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 15, 2011 5:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kotagiriaashish wrote: |
| !!! |
- we're not a help desk with an SLA on responses
- many of us don't work weekends and don't check the forum either
So yowling that you posted on Saturday & no-one's answered yet is only likely to annoy us. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 15, 2011 5:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kotagiriaashish wrote: |
| i am able to see the data tree structure before the assembly reaches the soap reply node, it looks fine.. |
Is that the request going out, or the response coming back? If it's the request going out (which is what it looks like) then see the earlier comment of my most worthy associate.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Mon Aug 15, 2011 7:02 am Post subject: |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
| Vitor wrote: |
| kotagiriaashish wrote: |
| i am able to see the data tree structure before the assembly reaches the soap reply node, it looks fine.. |
Is that the request going out, or the response coming back? If it's the request going out (which is what it looks like) then see the earlier comment of my most worthy associate. |
thats the request coming back, this is just before reaching the soap reply node
Mq Input>Soap Async Request>Soap Input>Compute>***>Soap Reply
*** is the message you are seeing above...
and after entering the soap reply the message never comes out to SOAP async Resp node, Please Help. |
|
| Back to top |
|
|
|
|
