| Author |
Message
|
| nukalas2010 |
 Posted: Thu Dec 09, 2010 4:20 am Post subject: |
 |
|
Master
Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....
|
hii Guys,
I have the message flow like this:
SOAPInputNode(ConsumerRequest) -> SubflowOperation -> ComputeNode (Here I am constructing provider message)
-> SOAPRequestNode (the service which is running in server) -> computenode (modify request) -> SOAPReply (for response)
while I am testing this flow using SOAPUI tool.. I am getting the "problem creating SOAP tree from bitstream"
after once the service comes out of SOAPRequestNode.
I try to find out this using Trace Node..
I put the Trace node after SoapRequestNode and get the Output as follows:
| Code: |
( ['SOAPRoot' : 0x1cd1b6b8]
(0x01000000:Name ):Properties = ( ['SOAPPROPERTYPARSER' : 0x14552f90]
(0x03000000:NameValue):MessageSet = 'MOH_LS_Set' (CHARACTER)
(0x03000000:NameValue):MessageType = '' (CHARACTER)
(0x03000000:NameValue):MessageFormat = '' (CHARACTER)
(0x03000000:NameValue):Encoding = 546 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 1208 (INTEGER)
(0x03000000:NameValue):Transactional = FALSE (BOOLEAN)
(0x03000000:NameValue):Persistence = FALSE (BOOLEAN)
(0x03000000:NameValue):CreationTime = GMTTIMESTAMP '2010-12-09 12:23:40.138' (GMTTIMESTAMP)
(0x03000000:NameValue):ExpirationTime = -1 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):ReplyIdentifier = X'000000000000000000000000000000000000000000000000' (BLOB)
(0x03000000:NameValue):ReplyProtocol = 'SOAP_AXIS2' (CHARACTER)
(0x03000000:NameValue):Topic = NULL
(0x03000000:NameValue):ContentType = 'text/xml;charset=utf-8' (CHARACTER)
(0x03000000:NameValue):IdentitySourceType = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceToken = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourcePassword = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceIssuedBy = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedType = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedToken = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedPassword = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedIssuedBy = '' (CHARACTER)
)
(0x01000000:Name ):HTTPResponseHeader = ( ['WSRSPHDR' : 0x145b8a48]
(0x03000000:NameValue):X-Original-HTTP-Status-Line = 'HTTP/1.1 200 OK' (CHARACTER)
(0x03000000:NameValue):X-Original-HTTP-Status-Code = 200 (INTEGER)
(0x03000000:NameValue):Server = 'Apache-Coyote/1.1' (CHARACTER)
(0x03000000:NameValue):X-Powered-By = 'Servlet 2.5; JBoss-5.0/JBossWeb-2.1' (CHARACTER)
(0x03000000:NameValue):Content-Type = 'text/xml;charset=utf-8' (CHARACTER)
(0x03000000:NameValue):Transfer-Encoding = 'chunked' (CHARACTER)
(0x03000000:NameValue):Date = 'Thu, 09 Dec 2010 12:24:11 GMT' (CHARACTER)
)
(0x01000000:Folder):SOAP =
|
|
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Dec 09, 2010 4:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The http status code 200 points to success however you have a blank SOAP folder. Could it be that the called service is not setting the http return code for failures?
Like Kimbert said, the trace node here is not enough. You need to take a user trace 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| nukalas2010 |
| Posted: Fri Dec 10, 2010 3:58 am Post subject: |
|
|
Master
Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....
|
Hi This is the Usertrace at normal level for my flow...
| Quote: |
Timestamps are formatted in local time, 480 minutes before GMT.
Trace written by version ; formatter version 7000 (build S000-L91028)
2010-12-10 03:56:39.849239 4976 UserTrace BIP4040I: The Execution Group ''Suresh'' 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.
2010-12-10 03:56:39.852199 4976 UserTrace BIP2638I: The MQ output node '.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''NGIQMGR''. The MQCC was '0' and the MQRC was '0'.
2010-12-10 03:56:39.852294 4976 UserTrace BIP2622I: Message successfully output by output node '.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''NGIQMGR''.
2010-12-10 03:56:39.852516 4976 Information BIP2154I: Execution group finished with Configuration message.
A command response will be sent to the broker.
No user action required.
2010-12-10 03:57:59.116840 4976 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node '.InputNode'.
2010-12-10 03:57:59.116966 4976 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'.
2010-12-10 03:57:59.116996 4976 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.
2010-12-10 03:57:59.117038 4976 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.
2010-12-10 03:57:59.117126 4976 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node '.InputNode' to handle portion of incoming message of length '22821' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
2010-12-10 03:57:59.117366 4976 Information BIP2152I: Configuration message received from broker.
An execution group received a command from the Broker.
No user action required.
2010-12-10 03:57:59.117481 4976 Information BIP2153I: About to ''change'' an execution group.
An execution group is about to perform an action.
No user action required.
2010-12-10 03:58:01.353490 4976 UserTrace BIP2265I: Attribute in message flow ''MOH_LS_Flow'' (uuid=''18f7efce-2c01-0000-0080-c68a56f5aecb'') successfully changed.
The message broker received a configuration message containing an instruction to change an attribute in the message flow ''MOH_LS_Flow'' (uuid=''18f7efce-2c01-0000-0080-c68a56f5aecb'') and successfully performed this action.
No user action required.
2010-12-10 03:58:01.370342 4976 UserTrace BIP3484E: ''Stopping Coyote HTTP/1.1 on http-7800''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:01.371816 4976 Information BIP3133I: The HTTP Listener has stopped listening on port ''7800'' for ''http'' connections.
The HTTP Listener process is no longer listening on the broker-specific TCPIP port ''7800'' for connections of type ''http''.
No user action required.
2010-12-10 03:58:02.372070 4976 UserTrace BIP3484E: ''Dispatcher org.apache.axis2.engine.SOAPActionBasedDispatcher is now deprecated.''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:02.372195 4976 UserTrace BIP3484E: ''Please edit axis2.xml and replace with the same class in org.apache.axis2.dispatchers package''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:02.372499 4976 UserTrace BIP3484E: ''Dispatcher org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher is now deprecated.''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:02.372607 4976 UserTrace BIP3484E: ''Please edit axis2.xml and replace with the same class in org.apache.axis2.dispatchers package''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:02.372912 4976 UserTrace BIP3484E: ''Dispatcher org.apache.axis2.engine.SOAPActionBasedDispatcher is now deprecated.''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:02.373020 4976 UserTrace BIP3484E: ''Please edit axis2.xml and replace with the same class in org.apache.axis2.dispatchers package''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:02.373189 4976 UserTrace BIP3484E: ''Dispatcher org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher is now deprecated.''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:02.373310 4976 UserTrace BIP3484E: ''Please edit axis2.xml and replace with the same class in org.apache.axis2.dispatchers package''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:03.480343 4976 UserTrace BIP3484E: ''Initializing Coyote HTTP/1.1 on http-7800''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:03.481651 4976 UserTrace BIP3484E: ''Starting Coyote HTTP/1.1 on http-7800''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:03.481894 4976 Information BIP3132I: The HTTP Listener has started listening on port ''7800'' for ''http'' connections.
The HTTP Listener process is currently listening on the broker-specific TCPIP port ''7800'' for connections of type ''http''
No user action required.
2010-12-10 03:58:03.482003 4976 UserTrace BIP2254I: Message flow node ''ConsumerRequest'' (uuid=''MOH_LS_Flow#FCMComposite_1_1'') type ''ComIbmSOAPInputNode'' in message flow 'MOH_LS_Flow' successfully created.
The message broker received a configuration message containing an instruction to create a message flow node in the message flow and successfully performed this action.
No user action required.
2010-12-10 03:58:03.482618 4976 UserTrace BIP2254I: Message flow node ''OPerationsSubFlow.Extract'' (uuid=''MOH_LS_Flow#FCMComposite_1_2.gen/MOH_Live_MsgSetService_MOH_LS_Flow#FCMComposite_1_1'') type ''ComIbmSOAPExtractNode'' in message flow 'MOH_LS_Flow' successfully created.
The message broker received a configuration message containing an instruction to create a message flow node in the message flow and successfully performed this action.
No user action required.
2010-12-10 03:58:03.482681 4976 UserTrace BIP2254I: Message flow node ''OPerationsSubFlow.ws_LiveStatusServiceRequest'' (uuid=''MOH_LS_Flow#FCMComposite_1_2.gen/MOH_Live_MsgSetService_MOH_LS_Flow#FCMComposite_1_2'') type ''ComIbmLabelNode'' in message flow 'MOH_LS_Flow' successfully created.
The message broker received a configuration message containing an instruction to create a message flow node in the message flow and successfully performed this action.
No user action required.
2010-12-10 03:58:03.482738 4976 UserTrace BIP2254I: Message flow node ''ResponseToConsumer'' (uuid=''MOH_LS_Flow#FCMComposite_1_3'') type ''ComIbmSOAPReplyNode'' in message flow 'MOH_LS_Flow' successfully created.
The message broker received a configuration message containing an instruction to create a message flow node in the message flow and successfully performed this action.
No user action required.
2010-12-10 03:58:03.482831 4976 UserTrace BIP2254I: Message flow node ''ConstructProviderMessage'' (uuid=''MOH_LS_Flow#FCMComposite_1_4'') type ''ComIbmComputeNode'' in message flow 'MOH_LS_Flow' successfully created.
The message broker received a configuration message containing an instruction to create a message flow node in the message flow and successfully performed this action.
No user action required.
2010-12-10 03:58:03.488641 4976 UserTrace BIP3484E: ''Dispatcher org.apache.axis2.engine.SOAPActionBasedDispatcher is now deprecated.''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:03.488754 4976 UserTrace BIP3484E: ''Please edit axis2.xml and replace with the same class in org.apache.axis2.dispatchers package''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:03.489046 4976 UserTrace BIP3484E: ''Dispatcher org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher is now deprecated.''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:03.489150 4976 UserTrace BIP3484E: ''Please edit axis2.xml and replace with the same class in org.apache.axis2.dispatchers package''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:03.489448 4976 UserTrace BIP3484E: ''Dispatcher org.apache.axis2.engine.SOAPActionBasedDispatcher is now deprecated.''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:03.489551 4976 UserTrace BIP3484E: ''Please edit axis2.xml and replace with the same class in org.apache.axis2.dispatchers package''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:03.489717 4976 UserTrace BIP3484E: ''Dispatcher org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher is now deprecated.''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:03.489820 4976 UserTrace BIP3484E: ''Please edit axis2.xml and replace with the same class in org.apache.axis2.dispatchers package''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2010-12-10 03:58:04.564973 4976 UserTrace BIP2254I: Message flow node ''CallProviderService'' (uuid=''MOH_LS_Flow#FCMComposite_1_5'') type ''ComIbmSOAPRequestNode'' in message flow 'MOH_LS_Flow' successfully created.
The message broker received a configuration message containing an instruction to create a message flow node in the message flow and successfully performed this action.
No user action required.
2010-12-10 03:58:04.565252 4976 UserTrace BIP2254I: Message flow node ''ModifyReply'' (uuid=''MOH_LS_Flow#FCMComposite_1_6'') type ''ComIbmComputeNode'' in message flow 'MOH_LS_Flow' successfully created.
The message broker received a configuration message containing an instruction to create a message flow node in the message flow and successfully performed this action.
No user action required.
2010-12-10 03:58:04.565375 4976 UserTrace BIP2254I: Message flow node ''Trace'' (uuid=''MOH_LS_Flow#FCMComposite_1_11'') type ''ComIbmTraceNode'' in message flow 'MOH_LS_Flow' successfully created.
The message broker received a configuration message containing an instruction to create a message flow node in the message flow and successfully performed this action.
No user action required.
2010-12-10 03:58:04.565476 4976 UserTrace BIP2255I: Message flow connection successfully created between node ''ConsumerRequest'' (uuid=''MOH_LS_Flow#FCMComposite_1_1'') terminal ''out'' and node ''OPerationsSubFlow.Extract'' (uuid=''MOH_LS_Flow#FCMComposite_1_2.gen/MOH_Live_MsgSetService_MOH_LS_Flow#FCMComposite_1_1'') terminal ''in''.
The message broker received a configuration message containing an instruction to create a connection between two nodes, and successfully performed this action.
No user action required.
2010-12-10 03:58:04.565568 4976 UserTrace BIP2255I: Message flow connection successfully created between node ''OPerationsSubFlow.ws_LiveStatusServiceRequest'' (uuid=''MOH_LS_Flow#FCMComposite_1_2.gen/MOH_Live_MsgSetService_MOH_LS_Flow#FCMComposite_1_2'') terminal ''out'' and node ''ConstructProviderMessage'' (uuid=''MOH_LS_Flow#FCMComposite_1_4'') terminal ''in''.
The message broker received a configuration message containing an instruction to create a connection between two nodes, and successfully performed this action.
No user action required.
2010-12-10 03:58:04.565608 4976 UserTrace BIP2255I: Message flow connection successfully created between node ''ModifyReply'' (uuid=''MOH_LS_Flow#FCMComposite_1_6'') terminal ''out'' and node ''ResponseToConsumer'' (uuid=''MOH_LS_Flow#FCMComposite_1_3'') terminal ''in''.
The message broker received a configuration message containing an instruction to create a connection between two nodes, and successfully performed this action.
No user action required.
2010-12-10 03:58:04.565649 4976 UserTrace BIP2255I: Message flow connection successfully created between node ''ConstructProviderMessage'' (uuid=''MOH_LS_Flow#FCMComposite_1_4'') terminal ''out'' and node ''CallProviderService'' (uuid=''MOH_LS_Flow#FCMComposite_1_5'') terminal ''in''.
The message broker received a configuration message containing an instruction to create a connection between two nodes, and successfully performed this action.
No user action required.
2010-12-10 03:58:04.565687 4976 UserTrace BIP2255I: Message flow connection successfully created between node ''CallProviderService'' (uuid=''MOH_LS_Flow#FCMComposite_1_5'') terminal ''out'' and node ''Trace'' (uuid=''MOH_LS_Flow#FCMComposite_1_11'') terminal ''in''.
The message broker received a configuration message containing an instruction to create a connection between two nodes, and successfully performed this action.
No user action required.
2010-12-10 03:58:04.565730 4976 UserTrace BIP2255I: Message flow connection successfully created between node ''Trace'' (uuid=''MOH_LS_Flow#FCMComposite_1_11'') terminal ''out'' and node ''ModifyReply'' (uuid=''MOH_LS_Flow#FCMComposite_1_6'') terminal ''in''.
The message broker received a configuration message containing an instruction to create a connection between two nodes, and successfully performed this action.
No user action required.
2010-12-10 03:58:04.569305 4976 UserTrace BIP2265I: Attribute in message flow ''MOH_LS_Flow'' (uuid=''18f7efce-2c01-0000-0080-c68a56f5aecb'') successfully changed.
The message broker received a configuration message containing an instruction to change an attribute in the message flow ''MOH_LS_Flow'' (uuid=''18f7efce-2c01-0000-0080-c68a56f5aecb'') and successfully performed this action.
No user action required.
2010-12-10 03:58:05.011507 4976 UserTrace BIP4040I: The Execution Group ''Suresh'' 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.
2010-12-10 03:58:05.012450 4976 UserTrace BIP2638I: The MQ output node '.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''NGIQMGR''. The MQCC was '0' and the MQRC was '0'.
2010-12-10 03:58:05.012465 4976 UserTrace BIP2622I: Message successfully output by output node '.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''NGIQMGR''.
2010-12-10 03:58:05.012681 4976 Information BIP2154I: Execution group finished with Configuration message.
A command response will be sent to the broker.
No user action required.
2010-12-10 03:58:05.383680 4976 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node '.InputNode'.
2010-12-10 03:58:05.383801 4976 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'.
2010-12-10 03:58:05.383831 4976 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.
2010-12-10 03:58:05.383873 4976 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.
2010-12-10 03:58:05.383913 4976 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node '.InputNode' to handle portion of incoming message of length '255' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
2010-12-10 03:58:05.459976 4976 UserTrace BIP4040I: The Execution Group ''Suresh'' 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.
2010-12-10 03:58:05.460558 4976 UserTrace BIP2638I: The MQ output node '.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''NGIQMGR''. The MQCC was '0' and the MQRC was '0'.
2010-12-10 03:58:05.460577 4976 UserTrace BIP2622I: Message successfully output by output node '.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''NGIQMGR''.
2010-12-10 03:58:17.106788 4420 UserTrace BIP3630I: The broker has received an HTTP message on port '7800' with URL path '/MOH_Live_MsgSetSOAP_HTTP_Service'.
The broker is listening on port '7800' and has received a message sent by a client using URL path '/MOH_Live_MsgSetSOAP_HTTP_Service'. This message will be sent on to either a SOAP Input Node or a SOAP Asynchronous Response Node.
No action required.
2010-12-10 03:58:17.107717 2116 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'MOH_LS_Flow.ConsumerRequest' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2010-12-10 03:58:17.107748 2116 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.
2010-12-10 03:58:17.107818 2116 UserTrace BIP6061I: Parser type ''SOAP'' created on behalf of node 'MOH_LS_Flow.ConsumerRequest' to handle portion of incoming message of length '4' bytes beginning at offset '0'. Parser type selected based on value ''SOAP'' from previous parser.
2010-12-10 03:58:17.107839 2116 UserTrace BIP3907I: Message received and propagated to 'out' terminal of input node 'MOH_LS_Flow.ConsumerRequest'.
2010-12-10 03:58:19.878282 2116 UserTrace BIP3904I: Invoking the evaluate() method of node (class='ComIbmSOAPExtractNode', name='MOH_LS_Flow#FCMComposite_1_2.gen/MOH_Live_MsgSetService_MOH_LS_Flow#FCMComposite_1_1').
About to pass a message to the evaluate() method of the specified node.
No user action required.
2010-12-10 03:58:19.880136 2116 UserTrace BIP4220I: Message propagated to out terminal from node 'MOH_LS_Flow.OPerationsSubFlow.ws_LiveStatusServiceRequest'.
A label node has received a message and is propagating it to any nodes connected to its out terminal.
No user action required.
2010-12-10 03:58:21.005624 2116 UserTrace BIP4015I: Message propagated to the 'out' terminal of node 'MOH_LS_Flow.ConstructProviderMessage' with the following message trees: ''.
2010-12-10 03:58:25.197221 2116 UserTrace BIP3719I: Node '' sending SOAP request via transport 'HTTP' ('172.18.3.20:8080') for operation 'retrieveLiveStatus' 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.
2010-12-10 03:58:25.198053 2116 UserTrace BIP3633I: Node '' sending HTTP data to URL '/NGIServices_LiveStatus_MOH/services/LiveStatusServiceSOAP' at host '172.18.3.20' (port 8080).
The broker is sending data via HTTP to a remote server at host '172.18.3.20' (port 8080) using URL '/NGIServices_LiveStatus_MOH/services/LiveStatusServiceSOAP'. See subsequent messages for success or failure messages relating to this request.
No action required.
2010-12-10 03:58:25.750101 2116 UserTrace BIP3634I: Node '' received HTTP data from host '172.18.3.20' with status code of 200.
The broker has received data via HTTP from a remote server at host '172.18.3.20' 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.
2010-12-10 03:58:25.750782 2116 UserTrace BIP3720I: Node '' received a SOAP response message via transport 'HTTP' ('172.18.3.20:8080') for operation 'retrieveLiveStatus'.
The broker sent a SOAP request, and has received a response.
No action required.
2010-12-10 03:58:25.751081 2116 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'MOH_LS_Flow.ConsumerRequest' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2010-12-10 03:58:25.751113 2116 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.
2010-12-10 03:58:25.751192 2116 UserTrace BIP6061I: Parser type ''SOAP'' created on behalf of node 'MOH_LS_Flow.ConsumerRequest' to handle portion of incoming message of length '4' bytes beginning at offset '0'. Parser type selected based on value ''SOAP'' from previous parser.
2010-12-10 03:58:25.751277 2116 UserTrace BIP3903I: Node (class='ComIbmSOAPRequestNode', name='CallProviderService') propagating to 'out' terminal.
The specified node is about to propagate a message to the specified terminal.
No user action required. This is an information message.
2010-12-10 03:58:25.754575 2116 UserTrace BIP5025E: XML schema validation error ''cvc-complex-type.2.4.e: Unexpected element. Element "retrieveLiveStatusResponse" is not one of the choices.'' on line '1' column '305' when parsing element ''/XMLNSC/http://schemas.xmlsoap.org/soap/envelope/:Envelope/http://schemas.xmlsoap.org/soap/envelope/:Body''.
Internal error codes: 5008, 2.
This error was reported by the XMLNSC parser. The XML document being parsed is not valid according to the message definitions in the message set.
The XML document has violated the rules expressed in the message definition files in the message set.
2010-12-10 03:58:29.171482 2116 UserTrace BIP5025E: XML schema validation error ''cvc-complex-type.2.4.e: Unexpected element. Element "retrieveLiveStatusResponse" is not one of the choices.'' on line '1' column '305' when parsing element ''/XMLNSC/http://schemas.xmlsoap.org/soap/envelope/:Envelope/http://schemas.xmlsoap.org/soap/envelope/:Body''.
Internal error codes: 5008, 2.
This error was reported by the XMLNSC parser. The XML document being parsed is not valid according to the message definitions in the message set.
The XML document has violated the rules expressed in the message definition files in the message set.
2010-12-10 03:58:29.171693 2116 UserTrace BIP4060I: Data ''( ['SOAPRoot' : 0x14556ec8]
(0x01000000:Name ):Properties = ( ['SOAPPROPERTYPARSER' : 0x1451ea38]
(0x03000000:NameValue):MessageSet = 'MOH_LS_Set' (CHARACTER)
(0x03000000:NameValue):MessageType = '' (CHARACTER)
(0x03000000:NameValue):MessageFormat = '' (CHARACTER)
(0x03000000:NameValue):Encoding = 546 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 1208 (INTEGER)
(0x03000000:NameValue):Transactional = FALSE (BOOLEAN)
(0x03000000:NameValue):Persistence = FALSE (BOOLEAN)
(0x03000000:NameValue):CreationTime = GMTTIMESTAMP '2010-12-10 11:58:03.482' (GMTTIMESTAMP)
(0x03000000:NameValue):ExpirationTime = -1 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):ReplyIdentifier = X'000000000000000000000000000000000000000000000000' (BLOB)
(0x03000000:NameValue):ReplyProtocol = 'SOAP_AXIS2' (CHARACTER)
(0x03000000:NameValue):Topic = NULL
(0x03000000:NameValue):ContentType = 'text/xml;charset=utf-8' (CHARACTER)
(0x03000000:NameValue):IdentitySourceType = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceToken = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourcePassword = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceIssuedBy = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedType = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedToken = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedPassword = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedIssuedBy = '' (CHARACTER)
)
(0x01000000:Name ):HTTPResponseHeader = ( ['WSRSPHDR' : 0x1455b850]
(0x03000000:NameValue):X-Original-HTTP-Status-Line = 'HTTP/1.1 200 OK' (CHARACTER)
(0x03000000:NameValue):X-Original-HTTP-Status-Code = 200 (INTEGER)
(0x03000000:NameValue):Server = 'Apache-Coyote/1.1' (CHARACTER)
(0x03000000:NameValue):X-Powered-By = 'Servlet 2.5; JBoss-5.0/JBossWeb-2.1' (CHARACTER)
(0x03000000:NameValue):Content-Type = 'text/xml;charset=utf-8' (CHARACTER)
(0x03000000:NameValue):Transfer-Encoding = 'chunked' (CHARACTER)
(0x03000000:NameValue):Date = 'Fri, 10 Dec 2010 11:58:25 GMT' (CHARACTER)
)
(0x01000000:Folder):SOAP = '' from trace node 'MOH_LS_Flow.Trace'.
The trace node 'MOH_LS_Flow.Trace' has output the specified trace data.
This is an information message provided by the message flow designer. The user response will be determined by the local environment.
2010-12-10 03:58:30.941204 2116 Error BIP2628E: Exception condition detected on input node 'MOH_LS_Flow.ConsumerRequest'.
The input node 'MOH_LS_Flow.ConsumerRequest' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2010-12-10 03:58:30.941236 2116 RecoverableException BIP2230E: Error detected whilst processing a message in node 'MOH_LS_Flow.Trace'.
The message broker detected an error whilst processing a message in node 'MOH_LS_Flow.Trace'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2010-12-10 03:58:30.941246 2116 ParserException BIP3614E: A SOAP logical tree cannot be built from the message bitstream.
The bitstream is not a valid Web service message.
Review further error messages for an indication to the cause of the error.
2010-12-10 03:58:30.941253 2116 ParserException BIP5009E: XML Parsing Errors have occurred.
Errors have occurred during parsing of XML.
Review further error messages for an indication to the cause of the errors.
2010-12-10 03:58:30.941263 2116 ParserException BIP5025E: XML schema validation error ''cvc-complex-type.2.4.e: Unexpected element. Element "retrieveLiveStatusResponse" is not one of the choices.'' on line '1' column '305' when parsing element ''/XMLNSC/http://schemas.xmlsoap.org/soap/envelope/:Envelope/http://schemas.xmlsoap.org/soap/envelope/:Body''.
Internal error codes: 5008, 2.
This error was reported by the XMLNSC parser. The XML document being parsed is not valid according to the message definitions in the message set.
The XML document has violated the rules expressed in the message definition files in the message set.
2010-12-10 03:58:30.971260 2116 UserTrace BIP3724I: Node '' sending a SOAP fault 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.
2010-12-10 04:01:12.971891 4976 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node '.InputNode'.
2010-12-10 04:01:12.971998 4976 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'.
2010-12-10 04:01:12.972024 4976 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.
2010-12-10 04:01:12.972069 4976 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.
2010-12-10 04:01:12.972117 4976 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node '.InputNode' to handle portion of incoming message of length '228' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
Threads encountered in this trace:
2116 4420 4976
|
|
|
| Back to top |
|
|
| mgk |
| Posted: Fri Dec 10, 2010 4:06 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi, as you may have noticed, this is the error:
| Code: |
2010-12-10 03:58:25.754575 2116 UserTrace BIP5025E: XML schema validation error ''cvc-complex-type.2.4.e: Unexpected element. Element "retrieveLiveStatusResponse" is not one of the choices.'' on line '1' column '305' when parsing element ''/XMLNSC/http://schemas.xmlsoap.org/soap/envelope/:Envelope/http://schemas.xmlsoap.org/soap/envelope/:Body''.
Internal error codes: 5008, 2.
This error was reported by the XMLNSC parser. The XML document being parsed is not valid according to the message definitions in the message set.
The XML document has violated the rules expressed in the message definition files in the message set.
2010-12-10 03:58:29.171482 2116 UserTrace BIP5025E: XML schema validation error ''cvc-complex-type.2.4.e: Unexpected element. Element "retrieveLiveStatusResponse" is not one of the choices.'' on line '1' column '305' when parsing element ''/XMLNSC/http://schemas.xmlsoap.org/soap/envelope/:Envelope/http://schemas.xmlsoap.org/soap/envelope/:Body''.
Internal error codes: 5008, 2.
This error was reported by the XMLNSC parser. The XML document being parsed is not valid according to the message definitions in the message set.
The XML document has violated the rules expressed in the message definition files in the message set. |
If you turn off validation of the SOAPRequest node you should be able to see the message that came back in the trace. As to the error itself, it is saying that the response message does not match the schema that came from the WSDL for this message. You need to check that the schema for the message is correct...
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 |
|
|
| kimbert |
| Posted: Fri Dec 10, 2010 4:49 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Focusing down on this part of the error:
| Code: |
| Element "retrieveLiveStatusResponse" is not one of the choices.'' on line '1' column '305' when parsing element ''/XMLNSC/http://schemas.xmlsoap.org/soap/envelope/:Envelope/http://schemas.xmlsoap.org/soap/envelope/:Body''. |
...it looks as if the soap body is not being recognized as a valid body.
First step is to check your WSDL and your XML and make sure that you haven't got the namespace wrong or something like that. If you can' track it down, post again and we'll take a look at the actual xsds that have been deployed. |
|
| Back to top |
|
|
| nukalas2010 |
| Posted: Sun Dec 12, 2010 7:43 pm Post subject: |
|
|
Master
Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....
|
Hi Kimbert... Please have a look at the following XSD's and WSDL's
Request XSD:
| Code: |
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://moh.com">
<xsd:complexType name="LiveStatusServiceRequest">
<xsd:sequence>
<xsd:element minOccurs="1" name="CPRNo" type="xsd:integer"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema> |
Response XSD:
| Code: |
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://moh.com">
<xsd:complexType name="LiveStatusServiceResponse">
<xsd:sequence>
<xsd:element minOccurs="1" name="CPRNo" type="xsd:integer"/>
<xsd:element minOccurs="0" name="LiveStatus" type="xsd:boolean">
</xsd:element>
<xsd:element minOccurs="0" name="DateOfDeath" type="xsd:date">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema> |
And the Deployable WSDL (SoapInputNode):
| Code: |
<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions name="MOH_Live_MsgSet" targetNamespace="http://tempuri.org/MOH_Live_MsgSet" xmlns:Q1="http://moh.com" xmlns:Q2="http://ngi.com" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://tempuri.org/MOH_Live_MsgSet" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xsd:schema targetNamespace="http://tempuri.org/MOH_Live_MsgSet" xmlns:mrm="http://tempuri.org/MOH_Live_MsgSet">
<xsd:import namespace="http://moh.com" schemaLocation="LiveStatusServiceRequest.xsd"/>
<xsd:import namespace="http://ngi.com" schemaLocation="ExceptionMessage.xsd"/>
<xsd:import namespace="http://moh.com" schemaLocation="LiveStatusServiceResponse.xsd"/>
<xsd:element name="ExceptionMessage" type="Q2:ExceptionMessage"/>
<xsd:element name="LiveStatusServiceRequest" type="Q1:LiveStatusServiceRequest">
</xsd:element>
<xsd:element name="LiveStatusServiceResponse" type="Q1:LiveStatusServiceResponse">
</xsd:element>
</xsd:schema>
</wsdl:types>
<wsdl:message name="retrieveLiveStatus_in">
<wsdl:part element="tns:LiveStatusServiceRequest" name="LiveStatusServiceRequest"/>
</wsdl:message>
<wsdl:message name="retrieveLiveStatus_out">
<wsdl:part element="tns:LiveStatusServiceResponse" name="LiveStatusServiceResponse"/>
</wsdl:message>
<wsdl:message name="retrieveLiveStatus_fault1">
<wsdl:part element="tns:ExceptionMessage" name="ExceptionMessage"/>
</wsdl:message>
<wsdl:portType name="MOH_Live_MsgSetPortType">
<wsdl:operation name="retrieveLiveStatus">
<wsdl:input message="tns:retrieveLiveStatus_in" name="retrieveLiveStatus_Input"/>
<wsdl:output message="tns:retrieveLiveStatus_out" name="retrieveLiveStatus_Output"/>
<wsdl:fault message="tns:retrieveLiveStatus_fault1" name="retrieveLiveStatus_Fault"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="MOH_Live_MsgSetSOAP_HTTP_Binding" type="tns:MOH_Live_MsgSetPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="retrieveLiveStatus">
<soap:operation soapAction="http://moh.com/RetrieveLiveStatusService/retrieveLiveStatus"/>
<wsdl:input name="retrieveLiveStatus_Input">
<soap:body parts="LiveStatusServiceRequest" use="literal"/>
</wsdl:input>
<wsdl:output name="retrieveLiveStatus_Output">
<soap:body parts="LiveStatusServiceResponse" use="literal"/>
</wsdl:output>
<wsdl:fault name="retrieveLiveStatus_Fault">
<soap:fault name="retrieveLiveStatus_Fault" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="MOH_Live_MsgSetSOAP_HTTP_Service">
<wsdl:port binding="tns:MOH_Live_MsgSetSOAP_HTTP_Binding" name="SOAP_HTTP_Port">
<soap:address location="http://localhost:7800/MOH_Live_MsgSetSOAP_HTTP_Service"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions> |
and the WSDL file (SoapRequestNode) where the service is running in another server:
| Code: |
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<wsdl:definitions xmlns:bons3="http://ngi.com" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://moh.com/RetrieveLiveStatusService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="RetrieveLiveStatusService" targetNamespace="http://moh.com/RetrieveLiveStatusService/">
<wsdl:types>
<xsd:schema xmlns:bons0="http://moh.com" targetNamespace="http://moh.com/RetrieveLiveStatusService/">
<xsd:import namespace="http://moh.com" schemaLocation="LiveStatusServiceResponse.xsd"/>
<xsd:import namespace="http://moh.com" schemaLocation="LiveStatusServiceRequest.xsd"/>
<xsd:import namespace="http://ngi.com" schemaLocation="ExceptionMessage.xsd"/>
<xsd:element name="retrieveLiveStatus">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="retrieveLiveStatusRequest" type="bons0:LiveStatusServiceRequest"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="retrieveLiveStatusResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="retrieveLiveStatusResponse" type="bons0:LiveStatusServiceResponse"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="retrieveLiveStatusFault" nillable="true" type="bons3:ExceptionMessage"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="retrieveLiveStatusRequest">
<wsdl:part element="tns:retrieveLiveStatus" name="parameters"/>
</wsdl:message>
<wsdl:message name="retrieveLiveStatusResponse">
<wsdl:part element="tns:retrieveLiveStatusResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="retrieveLiveStatus_retrieveLiveStatusFaultMsg">
<wsdl:part element="tns:retrieveLiveStatusFault" name="retrieveLiveStatusFault"/>
</wsdl:message>
<wsdl:portType name="LiveStatusService">
<wsdl:operation name="retrieveLiveStatus">
<wsdl:input message="tns:retrieveLiveStatusRequest"/>
<wsdl:output message="tns:retrieveLiveStatusResponse"/>
<wsdl:fault message="tns:retrieveLiveStatus_retrieveLiveStatusFaultMsg" name="retrieveLiveStatusFault"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="LiveStatusServiceSOAP" type="tns:LiveStatusService">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="retrieveLiveStatus">
<soap:operation soapAction="http://moh.com/RetrieveLiveStatusService/retrieveLiveStatus"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="retrieveLiveStatusFault">
<soap:fault name="retrieveLiveStatusFault" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="LiveStatus">
<wsdl:port binding="tns:LiveStatusServiceSOAP" name="LiveStatusServiceSOAP">
<soap:address location="http://localhost:8080/NGIServices_LiveStatus_MOH/services/LiveStatusServiceSOAP"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions> |
and in the Compute Node before SoapRequestNode the code as follows:
| Code: |
DECLARE ns1 NAMESPACE 'http://tempuri.org/MOH_Live_MsgSet';
DECLARE ns2 NAMESPACE 'http://moh.com/RetrieveLiveStatusService';
CREATE COMPUTE MODULE MOH_LS_Flow_Compute
CREATE FUNCTION Main() RETURNS BOOLEAN
BEGIN
SET OutputRoot.XMLNSC.ns2:retrieveLiveStatus.retrieveLiveStatusRequest.CPRNo =
InputRoot.XMLNSC.ns1:LiveStatusServiceRequest.CPRNo;
RETURN TRUE;
END;
END MODULE; |
Thanks in advance...
Last edited by nukalas2010 on Mon Dec 13, 2010 2:38 am; edited 1 time in total |
|
| Back to top |
|
|
| harish_td |
| Posted: Mon Dec 13, 2010 12:57 am Post subject: |
|
|
Master
Joined: 13 Feb 2006
Posts: 236
|
As kimbert and mgk have already pointed out, the response coming back is giving you trouble.
Why don't you directly call the back-end web service from soapUI and validate (by right-clicking in the response pane and selecting validate) the response that you receive from the back-end?
Something that fails validation there would also fail validation in WMB. |
|
| Back to top |
|
|
| nukalas2010 |
| Posted: Mon Dec 13, 2010 1:04 am Post subject: |
|
|
Master
Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....
|
| harish_td wrote: |
Why don't you directly call the back-end web service from soapUI and validate (by right-clicking in the response pane and selecting validate) the response that you receive from the back-end?
|
Yeah Hairsh... I already tried that one also..
When Calling that backend service from SOAPUI I am getting the proper Response back.. |
|
| Back to top |
|
|
| harish_td |
| Posted: Mon Dec 13, 2010 2:16 am Post subject: |
|
|
Master
Joined: 13 Feb 2006
Posts: 236
|
| nukalas2010 wrote: |
| When Calling that backend service from SOAPUI I am getting the proper Response back.. |
If the response as received on soapUI passes validation and fails on the message broker, i get the feeling that the WSDL that you have uploaded in the Message Broker and soapUI are different versions. Can you recheck?
When i upload a WSDL file to soapUI, i usually upload the deployable wsdl from the Message Broker workspace. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Dec 13, 2010 2:23 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
nukalas2010: Please use [code] not [quote] when quoting source code. Your xsds and wsdl are hard to read because the leading spaces have been lost.
The next step is to look inside the BAR file and find out what the deployed xsds look like. Unzip the BAR file, then unzip the messageSetName.xsdzip and find the parts that relate to this problem. |
|
| Back to top |
|
|
| nukalas2010 |
| Posted: Mon Dec 13, 2010 2:58 am Post subject: |
|
|
Master
Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....
|
| Quote: |
[quote="kimbert"]nukalas2010: Please use [ code ] not
| Quote: |
| when quoting source code. Your xsds and wsdl are hard to read because the leading spaces have been lost. |
yeah sorry kimbert... now have a look at those XSD's and WSDL's...
| Quote: |
| The next step is to look inside the BAR file and find out what the deployed xsds look like. Unzip the BAR file, then unzip the messageSetName.xsdzip and find the parts that relate to this problem. |
|
Yeah I did the same mentioned by you.. then I got the same XSD's of Request and Response and also the following files in specified folder named as:
-> messagesetname.xsd
-> messagesetname.wsdl
->messagesetname_Inlineschema.xsd
The messagesetname.xsd code is as follows:
| Code: |
<?xml version="1.0" encoding="UTF-8"?><xsd:schema targetNamespace="http://tempuri.org/MOH_Live_MsgSet" xmlns:Q1="http://moh.com" xmlns:Q2="http://ngi.com" xmlns:tns="http://tempuri.org/MOH_Live_MsgSet" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/envelope/" schemaLocation="../../xmlsoap/schemas/soap/envelope/soapenv11.xsd"/>
<xsd:include schemaLocation="MOH_Live_MsgSetService_InlineSchema1.xsd"/>
<!-- BEGIN Global group petaining to all wsdl:message definitions -->
<!-- END Global group -->
<!-- BEGIN Message Definitions for the wsdl:operations -->
<!-- END Message Definitions -->
</xsd:schema> |
the messagesetname.wsdl file contains the code as follows:
| Code: |
<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions name="MOH_Live_MsgSet" targetNamespace="http://tempuri.org/MOH_Live_MsgSet" xmlns:Q1="http://moh.com" xmlns:Q2="http://ngi.com" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://tempuri.org/MOH_Live_MsgSet" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:documentation>
<wsdl:appinfo source="WMQI_APPINFO">
<MRWSDLAppInfo imported="true">
<generatedMXSD location="MOH_Live_MsgSetService_InlineSchema1.mxsd"/>
<binding hasEncoding="false" imported="true" name="MOH_Live_MsgSetSOAP_HTTP_Binding" originalBindingStyle="document"/>
</MRWSDLAppInfo>
</wsdl:appinfo>
</wsdl:documentation>
<wsdl:types>
<xsd:schema targetNamespace="http://tempuri.org/MOH_Live_MsgSet" xmlns:mrm="http://tempuri.org/MOH_Live_MsgSet">
<xsd:import namespace="http://moh.com" schemaLocation="../../../com/moh/LiveStatusServiceRequest.xsd"/>
<xsd:import namespace="http://ngi.com" schemaLocation="../../../com/ngi/ExceptionMessage.xsd"/>
<xsd:import namespace="http://moh.com" schemaLocation="../../../com/moh/LiveStatusServiceResponse.xsd"/>
<xsd:include schemaLocation="MOH_Live_MsgSetService_InlineSchema1.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="retrieveLiveStatus_in">
<wsdl:part element="tns:LiveStatusServiceRequest" name="LiveStatusServiceRequest"/>
</wsdl:message>
<wsdl:message name="retrieveLiveStatus_out">
<wsdl:part element="tns:LiveStatusServiceResponse" name="LiveStatusServiceResponse"/>
</wsdl:message>
<wsdl:message name="retrieveLiveStatus_fault1">
<wsdl:part element="tns:ExceptionMessage" name="ExceptionMessage"/>
</wsdl:message>
<wsdl:portType name="MOH_Live_MsgSetPortType">
<wsdl:operation name="retrieveLiveStatus">
<wsdl:input message="tns:retrieveLiveStatus_in" name="retrieveLiveStatus_Input"/>
<wsdl:output message="tns:retrieveLiveStatus_out" name="retrieveLiveStatus_Output"/>
<wsdl:fault message="tns:retrieveLiveStatus_fault1" name="retrieveLiveStatus_Fault"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="MOH_Live_MsgSetSOAP_HTTP_Binding" type="tns:MOH_Live_MsgSetPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="retrieveLiveStatus">
<soap:operation soapAction="http://moh.com/RetrieveLiveStatusService/retrieveLiveStatus"/>
<wsdl:input name="retrieveLiveStatus_Input">
<soap:body parts="LiveStatusServiceRequest" use="literal"/>
</wsdl:input>
<wsdl:output name="retrieveLiveStatus_Output">
<soap:body parts="LiveStatusServiceResponse" use="literal"/>
</wsdl:output>
<wsdl:fault name="retrieveLiveStatus_Fault">
<soap:fault name="retrieveLiveStatus_Fault" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="MOH_Live_MsgSetSOAP_HTTP_Service">
<wsdl:port binding="tns:MOH_Live_MsgSetSOAP_HTTP_Binding" name="SOAP_HTTP_Port">
<soap:address location="http://localhost:7800/MOH_Live_MsgSetSOAP_HTTP_Service"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
|
and the messagesetname_Inlineshema.xsd is as follows:
| Code: |
<?xml version="1.0" encoding="UTF-8"?><xsd:schema targetNamespace="http://tempuri.org/MOH_Live_MsgSet" xmlns:Q1="http://moh.com" xmlns:Q2="http://ngi.com" xmlns:mrm="http://tempuri.org/MOH_Live_MsgSet" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://tempuri.org/MOH_Live_MsgSet" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://moh.com" schemaLocation="../../../com/moh/LiveStatusServiceRequest.xsd"/>
<xsd:import namespace="http://ngi.com" schemaLocation="../../../com/ngi/ExceptionMessage.xsd"/>
<xsd:import namespace="http://moh.com" schemaLocation="../../../com/moh/LiveStatusServiceResponse.xsd"/>
<xsd:element name="ExceptionMessage" type="Q2:ExceptionMessage">
</xsd:element>
<xsd:element name="LiveStatusServiceRequest" type="Q1:LiveStatusServiceRequest">
</xsd:element>
<xsd:element name="LiveStatusServiceResponse" type="Q1:LiveStatusServiceResponse">
</xsd:element>
</xsd:schema> |
along with these files I also get the SOAP.XSD file which is as follows:
| Code: |
<?xml version="1.0" encoding="UTF-8"?><xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:group name="MIME_header_fields">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="Content-Type">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="boundary" type="xsd:string"/>
<xsd:attribute name="type" type="xsd:string"/>
<xsd:attribute name="start" type="xsd:string"/>
<xsd:attribute name="start-info" type="xsd:string"/>
<xsd:attribute name="charset" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="Content-Transfer-Encoding">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="7bit"/>
<xsd:enumeration value="8bit"/>
<xsd:enumeration value="binary"/>
<xsd:enumeration value="quoted-printable"/>
<xsd:enumeration value="base64"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="Content-Id" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Content-Description" type="xsd:string"/>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="MIME_Headers_type">
<xsd:sequence>
<xsd:group ref="MIME_header_fields"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Attachment_type">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="MIME_Headers" type="MIME_Headers_type"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Data" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="SOAP_Msg_type">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="Context">
<xsd:complexType>
<xsd:sequence maxOccurs="1" minOccurs="1">
<xsd:element maxOccurs="1" minOccurs="0" name="SOAP_Version">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="1.1"/>
<xsd:enumeration value="1.2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="Namespace">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="_XmlDeclaration">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="Version" type="xsd:string"/>
<xsd:attribute name="Encoding" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="XmlRoot">
<xsd:complexType>
<xsd:sequence maxOccurs="1" minOccurs="1">
<xsd:element maxOccurs="1" minOccurs="1" name="Envelope">
<xsd:complexType>
<xsd:sequence maxOccurs="1" minOccurs="0">
<xsd:element maxOccurs="1" minOccurs="0" name="Header" type="xsd:anyType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Body" type="xsd:anyType"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="MIME_Headers" type="MIME_Headers_type"/>
</xsd:sequence>
<xsd:attribute name="port" type="xsd:string"/>
<xsd:attribute name="portType" type="xsd:string"/>
<xsd:attribute name="portTypeNamespace" type="xsd:string"/>
<xsd:attribute name="operation" type="xsd:string"/>
<xsd:attribute name="operationType" type="xsd:string"/>
<xsd:attribute name="service" type="xsd:string"/>
<xsd:attribute name="serviceNamespace" type="xsd:string"/>
<xsd:attribute name="fileName" type="xsd:string"/>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="Header">
<xsd:complexType>
<xsd:sequence maxOccurs="unbounded">
<xsd:sequence>
<xsd:any maxOccurs="unbounded" minOccurs="0" processContents="lax"/>
</xsd:sequence>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="1" name="Body">
<xsd:complexType>
<xsd:sequence maxOccurs="1">
<xsd:sequence>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="http://schemas.xmlsoap.org/soap/envelope/ http://ngi.com http://moh.com http://tempuri.org/MOH_Live_MsgSet" processContents="lax"/>
</xsd:sequence>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="Attachment">
<xsd:complexType>
<xsd:sequence maxOccurs="unbounded" minOccurs="0">
<!-- xsd:element name="your-content-ID" type="Attachment_type"/ -->
<xsd:any namespace="##any" processContents="lax"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="SOAP_Domain_Msg" type="SOAP_Msg_type">
</xsd:element>
</xsd:schema>
|
|
|
| Back to top |
|
|
| nukalas2010 |
| Posted: Tue Dec 14, 2010 10:31 pm Post subject: |
|
|
Master
Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....
|
have anyone got sloution for this problem...  |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Dec 15, 2010 1:43 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
There are still some unknowns. In your SOAPRequestNode WSDL you have this definition
| Code: |
<wsdl:message name="retrieveLiveStatusResponse">
<wsdl:part element="tns:retrieveLiveStatusResponse" name="parameters"/>
</wsdl:message> |
and the target namespace of the WSDL is declared as
| Code: |
| <wsdl:definitions xmlns:bons3="http://ngi.com" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://moh.com/RetrieveLiveStatusService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="RetrieveLiveStatusService" targetNamespace="http://moh.com/RetrieveLiveStatusService/">" |
I think that means that a your SOAP body for the RetrieveLiveStatusService must contain a tag with namespace "http://moh.com/RetrieveLiveStatusService/" and name "RetrieveLiveStatusService"
The error message does not quote the namespace, so you will have to capture the response from the SOAPRequest node and trace it. Switch off validation temporarily to ensure that the message reaches the Trace node. |
|
| Back to top |
|
|
| junzi88 |
| Posted: Fri Sep 27, 2013 1:26 pm Post subject: |
|
|
Novice
Joined: 25 Sep 2013
Posts: 16
|
Same problem is happening in my flow with SOAP Request node. After SOAP Request node, under Message, there is message "creating SOAP tree from bitstream". Then went to trace node, the trace show all the value well. Then went to SOAP Extract Node which generated Execption list as following. Most post suggested the response do not follow schema definition. But below message is strange. The two strange are same. What else can I look into?
| Code: |
RecoverableException
File:CHARACTER:F:\build\slot1\S800_P\src\DataFlowEngine\ImbDataFlowNode.cpp
Line:INTEGER:1154
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmTryCatchNode
Name:CHARACTER:UpdatePolicy#FCMComposite_1_2.com/xxx/shrcbill/SHRCBILL#FCMComposite_1_2
Label:CHARACTER:UpdatePolicy.Try Catch
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
RecoverableException
File:CHARACTER:F:\build\slot1\S800_P\src\DataFlowEngine\ImbTraceNode.cpp
Line:INTEGER:362
Function:CHARACTER:ImbTraceNode::evaluate
Type:CHARACTER:ComIbmTraceNode
Name:CHARACTER:UpdatePolicy#FCMComposite_1_2.com/xxx/shrcbill/SHRCBILL#FCMComposite_1_8
Label:CHARACTER:UpdatePolicy.Trace1
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
ParserException
File:CHARACTER:F:\build\slot1\S800_P\src\WebServices\WSLibrary\ImbSOAPParser.cpp
Line:INTEGER:2141
Function:CHARACTER:ImbSOAPParser::createSoapShapedTree
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3614
Text:CHARACTER:problem creating SOAP tree from bitstream
ParserException
File:CHARACTER:F:\build\slot1\S800_P\src\MTI\MTIforBroker\GenXmlParser4\ImbXMLNSCParser.cpp
Line:INTEGER:1011
Function:CHARACTER:ImbXMLNSCParser::parseFirstChild
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:5009
Text:CHARACTER:XML Parsing Errors have occurred
ParserException
File:CHARACTER:F:\build\slot1\S800_P\src\MTI\MTIforBroker\GenXmlParser4\ImbXMLNSCDocHandler.cpp
Line:INTEGER:702
Function:CHARACTER:ImbXMLNSCDocHandler::handleParseErrors
Type:CHARACTER:ComIbmSOAPInputNode
Name:CHARACTER:UpdatePolicy#FCMComposite_1_1
Label:CHARACTER:UpdatePolicy.SOAP Input
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:5025
Text:CHARACTER:A schema validation error has occurred while parsing the XML document
Insert
Type:INTEGER:2
Text:CHARACTER:5004
Insert
Type:INTEGER:2
Text:CHARACTER:2
Insert
Type:INTEGER:2
Text:CHARACTER:1
Insert
Type:INTEGER:2
Text:CHARACTER:270
Insert
Type:INTEGER:5
Text:CHARACTER:cvc-complex-type.2.4.a: Expecting element with local name "SHRCBILLResult" but saw "SHRCBILLResult". |
|
|
| Back to top |
|
|
| kimbert |
| Posted: Sat Sep 28, 2013 9:43 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Text:CHARACTER:cvc-complex-type.2.4.a: Expecting element with local name "SHRCBILLResult" but saw "SHRCBILLResult". |
I agree that this error message could be a lot more useful. As I explained previously, the most likely explanation is that SHRCBILLResult is not in the expected namespace ( or perhaps not in any namespace at all ).
You will need to do some careful investigation now
1. Find out what the expected namespace is for SHRCBILLResult
2. Find out what namespace the message flow is assigning to SHRCBILLResult. A Trace node is an excellent way to do this.
3. Adjust the message flow ( if necessary ) based on the results of the investigation
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
|
|
