| Author |
Message
|
| kirank |
 Posted: Tue Dec 11, 2012 4:09 pm Post subject: Error Handling for Configurable Services |
 |
|
Centurion
Joined: 10 Oct 2002
Posts: 136
Location: California
|
Hi,
We are using FTP Configurable Service to FTP files from File Output node to a remote server. At times the service experiences connectivity error with remote server. The configurable service seems to log error to broker log. We have our standard Error Sub flow connected to the Failure node of the File Output node. But nothing is routed to Failure node.
Is there something wrong with our setup or that's how configurable service behaves and we can NOT capture that exception in the flow?
Regards
Kiran |
|
| Back to top |
|
 |
| McueMart |
| Posted: Tue Dec 11, 2012 4:31 pm Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
| Please tell us the error you are seeing in the broker error log and we may be able to help! |
|
| Back to top |
|
|
| kirank |
| Posted: Tue Dec 11, 2012 5:12 pm Post subject: |
|
|
Centurion
Joined: 10 Oct 2002
Posts: 136
Location: California
|
Here is one if the errors from Broker Log
BIP3384E: File node 'FileOutput-TW' in message flow 'PROJECT_WARREN'. An unexpected reply has been received from 'FTP' server 'ftransfer.tw.com'. The command and reply are: 'STOR =>response: '. : BKLQAR01.9906bd4b-2a01-0000-0080-f1c9cf4b5b49: ComIbmFileOutputNode.java: 542: transferToFtpServer: : |
|
| Back to top |
|
|
| Esa |
| Posted: Wed Dec 12, 2012 1:06 am Post subject: Re: Error Handling for Configurable Services |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| kirank wrote: |
We are using FTP Configurable Service to FTP files from File Output node to a remote server. At times the service experiences connectivity error with remote server. The configurable service seems to log error to broker log. We have our standard Error Sub flow connected to the Failure node of the File Output node. But nothing is routed to Failure node.
Is there something wrong with our setup or that's how configurable service behaves and we can NOT capture that exception in the flow?
|
The name configurable service is quite misleading. Configurable services are just containers of parameters, not active components that would do things like exception handling or logging. It's the FileOutput node that is the active component in your case, it just fetches its configuration from the configurable service.
By the way, which Message Broker version are you using?
According to the InfoCenter the message should be propagated to the failure terminal  if "a failure is detected when a message is propagated".
In your case, you get a response, which means that no failure is detected when the message is propagated. It's just that the response is unexpected, but that is detected only after the call to PROPAGATE has returned... |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Dec 12, 2012 2:53 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Here is one if the errors from Broker Log |
Is that from a service trace? You do realise that service trace is intended for IBM Level 3 service, and not for end users? Message flow developers can ( and should, when necessary ) make use of user trace, possibly with the -d parameter for debugging detail.
If you find that the debugger + Activity Log + Trace nodes + user trace is not providing you with enough information to diagnose the problem...PMR time. |
|
| Back to top |
|
|
|
|
