| Author |
Message
|
| my_mqmb |
 Posted: Wed Aug 24, 2011 1:21 am Post subject: SoapRequest Fault error |
 |
|
Voyager
Joined: 08 Jun 2011
Posts: 84
|
2011-08-24 12:16:53.123820 8521 UserTrace BIP3719I: Node 'UpdateCardStatus.Request' sending SOAP request via transport 'HTTP' ('10.37.2.6:9080') for operation 'UpdateCardStatus' 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-24 12:16:53.260744 8521 UserTrace BIP3720I: Node 'UpdateCardStatus.Request' received a SOAP response message via transport 'HTTP' ('10.37.2.6:9080') for operation 'UpdateCardStatus'.
The broker sent a SOAP request, and has received a response.
No action required.
2011-08-24 12:16:53.261036 8521 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'Stop_Card.InputProcessing.In' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2011-08-24 12:16:53.261156 8521 UserTrace BIP6061I: Parser type ''SOAP'' created on behalf of node 'Stop_Card.InputProcessing.In' to handle portion of incoming message of length '8' bytes beginning at offset '0'. Parser type selected based on value ''SOAP'' from previous parser.
2011-08-24 12:16:53.261180 8521 UserTrace BIP3903I: Node (class='ComIbmSOAPRequestNode', name='UpdateCardStatus.Request') propagating to 'fault' terminal.
The specified node is about to propagate a message to the specified terminal.
No user action required. This is an information message.
ANY CLUES ?? |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Aug 24, 2011 1:31 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Clues to what?
It would help if you asked a proper question.
What do you think is right/wrong/puzzling etc?
_________________
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 |
|
|
| Vitor |
| Posted: Wed Aug 24, 2011 4:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| smdavies99 wrote: |
| It would help if you asked a proper question. |
| smdavies99 wrote: |
| What do you think is right/wrong/puzzling etc? |
I suspect it's this:
| my_mqmb wrote: |
| Code: |
| 2011-08-24 12:16:53.261180 8521 UserTrace BIP3903I: Node (class='ComIbmSOAPRequestNode', name='UpdateCardStatus.Request') propagating to 'fault' terminal |
|
| my_mqmb wrote: |
| ANY CLUES ?? |
No.
There's nothing in your post of any help to us apart from the suspicion I give above; that you want the message to go to the out terminal not the fault terminal. You've said nothing about the circumstances, how the node is configured, the nature of the inbound message or any other information.
So no, there are no clues.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Aug 24, 2011 4:36 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| There's nothing in your post of any help to us |
While on the one hand, , on the other hand it's fairly obvious from the trace why the message went to the fault terminal.
There's no information at all about what would have caused the condition in question, however, and it's entirely likely that my_mqmb is looking at the wrong thing. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 24, 2011 4:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Vitor wrote: |
| There's nothing in your post of any help to us |
While on the one hand, , on the other hand it's fairly obvious from the trace why the message went to the fault terminal. |
Well yes, but as you say it's obvious. That's like asking "I can see smoke & flame coming from my bedroom window, is my house on fire?"
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| my_mqmb |
| Posted: Sat Aug 27, 2011 1:52 am Post subject: |
|
|
Voyager
Joined: 08 Jun 2011
Posts: 84
|
After the response from the Soap request the flow rollbacks to the first node that is the input processing with the following error :
Parser type ''Properties'' created on behalf of node 'Stop_Card.InputProcessing.In' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
length 0 bytes beginning at offset '0'. ???
When i post the same message using SOAP UI i get a valid response , but in the trace file i find such message ..
Is the response message '0' bytes ? if yes why ?
Sorry for late reply , i was out of office and yes my bedroom is on fire 
lol
 |
|
| Back to top |
|
|
| my_mqmb |
| Posted: Sun Jan 22, 2012 1:57 am Post subject: |
|
|
Voyager
Joined: 08 Jun 2011
Posts: 84
|
any clues as to when this scenario occurs ?
with soap ui the same message works fine ... |
|
| Back to top |
|
|
| Esa |
| Posted: Sun Jan 22, 2012 2:40 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| my_mqmb wrote: |
any clues as to when this scenario occurs ?
|
The fact that the message is propagated to 'fault' terminal indicates that the service that was called obviously returned a SOAPFault or something that the node interpreted as a fault.
You can connect the fault terminal to a passthrough node and set a breakpoint to it. In the debugger you can then examine the contents of the message. And - more importantly - the message that was actually sent by the SOAPRequest. That should be available in LocalEnvironment.WrittenDestination.
If you had read SOAPRequest node documentation in the InfoCenter, you could perhaps have figured this out yourself? |
|
| Back to top |
|
|
| my_mqmb |
| Posted: Sun Jan 22, 2012 3:20 am Post subject: |
|
|
Voyager
Joined: 08 Jun 2011
Posts: 84
|
| Esa wrote: |
| my_mqmb wrote: |
any clues as to when this scenario occurs ?
|
The fact that the message is propagated to 'fault' terminal indicates that the service that was called obviously returned a SOAPFault or something that the node interpreted as a fault.
You can connect the fault terminal to a passthrough node and set a breakpoint to it. In the debugger you can then examine the contents of the message. And - more importantly - the message that was actually sent by the SOAPRequest. That should be available in LocalEnvironment.WrittenDestination.
If you had read SOAPRequest node documentation in the InfoCenter, you could perhaps have figured this out yourself? |
yes i did figure out that it is going to the fault terminal , but the actual response message is complained to be of length '0' bytes ...
where do you suggest me to put the passthru node to check the request and response messages of the SOAP request ??
before the request node ? |
|
| Back to top |
|
|
| Esa |
| Posted: Sun Jan 22, 2012 3:40 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| my_mqmb wrote: |
where do you suggest me to put the passthru node to check the request and response messages of the SOAP request ??
before the request node ? |
| Esa wrote: |
You can connect the fault terminal to a passthrough node and set a breakpoint to it. |
I mean the fault terminal of the SOAPRequest node. So the answer is: after. |
|
| Back to top |
|
|
| my_mqmb |
| Posted: Sun Jan 22, 2012 11:24 pm Post subject: |
|
|
Voyager
Joined: 08 Jun 2011
Posts: 84
|
| Esa wrote: |
| my_mqmb wrote: |
where do you suggest me to put the passthru node to check the request and response messages of the SOAP request ??
before the request node ? |
| Esa wrote: |
You can connect the fault terminal to a passthrough node and set a breakpoint to it. |
I mean the fault terminal of the SOAPRequest node. So the answer is: after. |
thanks mate for your involvement ..
any way the problem was discovered where the webservice was hosted ..
i could figure out in their logs the cause of my problem ..
solution ::
my message did not confirm to their validation and hence they did not return a proper message ... |
|
| Back to top |
|
|
|
|
