| Author |
Message
|
| Gaya3 |
 Posted: Wed Aug 27, 2008 7:57 pm Post subject: Error encountered during Call to external Web Service. |
 |
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
am having a flow
Broker V6.1
But i developed the flow on V6.0
input node -->process input message --> create soap message --> Http request --> Response Build
the following is the error we are getting now
Aug 27 01:40:03 WebSphere Broker v6101[29303]: ()[4]BIP2232E: Error detected whilst handling a previous error in node 'XXX_Error_HANDLER_FLOW.Throw'. : .4b712990-1a01-0000-0080-8735b6333211: /build/S610_P/src/DataFlowEngine/ImbDataFlowNode.cpp: 551: ImbDataFlowNode::logExceptionList: ComIbmThrowNode: FLOW#FCMComposite_1_11.ERROR_HANDLER_FLOW#FCMComposite_1_7
Aug 27 01:40:03 WebSphere Broker v6101[29303]: ()[4]BIP3001I: Exception thrown by throw node 'FLOW.Throw'; text is 'Error encounter during Call to external XXXX Web Service. Received SOAP Fault Response.'. : .4b712990-1a01-0000-0080-8735b6333211: /build/S610_P/src/DataFlowEngine/BasicNodes/ImbThrowNode.cpp: 265: ImbThrowNode::evaluate: ComIbmThrowNode: FLOW#FCMComposite_1_27
can any one figure out, what could be the issue here...
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
 |
| sandeep9678 |
| Posted: Wed Aug 27, 2008 8:40 pm Post subject: |
|
|
Apprentice
Joined: 04 Aug 2008
Posts: 41
Location: India
|
We were also getting same kind of error. Then we found that our External WebService was receiving the request. But there was problem in the data which they were expecting in some specific format and in CAPs only.
Is your external WebService is getting request from MB?
_________________
Cheers,
Sandeep |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Aug 27, 2008 9:44 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
how did you resolve this issue?
i am sending the request to external webservice?
and i am not least bothered about Response comes from that side
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| sandeep9678 |
| Posted: Wed Aug 27, 2008 9:57 pm Post subject: |
|
|
Apprentice
Joined: 04 Aug 2008
Posts: 41
Location: India
|
We worked with External WebService team. They said that there are problem in the way we are sending the data. WebService was expecting some field values in Capital letters only and some with fixed length, we we were not doing. We only had direct mappings. Because of that, webService was througing null pointer exceptions in its log and we were getting the error which you mentioned.
After resolving the issues told by WebService team, we resolved the issue.
_________________
Cheers,
Sandeep |
|
| Back to top |
|
|
| dilse |
| Posted: Fri Aug 29, 2008 9:06 am Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Gaya3,
Working with web service team is a good idea but if in any case you cannot reach them, try to catch the error response using failure and error terminals on HTTPRequest node. This info should give you enough information as to what happened...
Hope this helps.
DilSe.. |
|
| Back to top |
|
|
| paranoid221 |
| Posted: Fri Aug 29, 2008 12:50 pm Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 101
Location: USA
|
Like DilSe and Sandeep said, working with webservices team is a good place to start troubleshooting. On the broker side though, you could add a trace node right before your call to the WebService and ensure that the message that is being passed to the WebService is in the proper format they expect to receive including NameSpaces. I did run into this issue where the namespace declaration for one of the elements in my ESQL code was different than what was expected by the external webservice.
Once you are sure that the payload is in the exact format, it boils down to resolving any issues with the data that is being passed to the service.
Another consideration is to make sure that the external webservice isn't implementing any WS-Basic Auth for incoming calls in which case you'd also have to pass authorization credentials in the HTTPRequest Header along with your payload.
_________________
LIFE is a series of complex calculations, somewhere multiplied by ZERO. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Sun Aug 31, 2008 7:55 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
yes, thanks for the response, i resolved the issue by sitting with External WebService team.
Its a Data mapping issue.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
|
|
