HTTPConnector timed out

vrx_noob

• June 20, 2012 00:00

• Answered

Follow

Hi,

Sorry...noob question :oops:
I newly use the HTTP Connector component, and get always timed out.

INFO [WatchDog] - [Clover] Post-execute phase finalization: 0
INFO [WatchDog] - [Clover] phase: 0 post-execute finalization successfully.
INFO [WatchDog] - Execution of phase [0] finished with error - elapsed time(sec): 84
ERROR [WatchDog] - !!! Phase finished with error - stopping graph run !!!
INFO [WatchDog] - -----------------------** Summary of Phases execution **---------------------
INFO [WatchDog] - Phase# Finished Status RunTime(sec) MemoryAllocation(KB)
INFO [WatchDog] - 0 ERROR 84 9288
INFO [WatchDog] - ------------------------------** End of Summary **---------------------------
INFO [WatchDog] - WatchDog thread finished - total execution time: 84 (sec)
INFO [main] - Freeing graph resources.
ERROR [main] - Execution of graph failed !

I'm not sure to comply with the set up of this component, but I tried to follow the few examples found.
I had the same issue on Kettle, and set up the proxy, but even with a proxy set up, I get no response.

Can someone tell me if my graph is OK ?

• GetXERates.grf

• 

  admin

  • June 20, 2012 12:20

  0

  Comment actions Permalink

  Hi vrx_noob,
  
  problem is that you need to configure proxy as part of URL. See http://doc.cloveretl.com/documentation/ ... aders.html section "Using Proxy in Readers".
• 

  vrx_noob

  • June 20, 2012 12:44

  0

  Comment actions Permalink

  Thank you very much,
  works perfectly now.

Please sign in to leave a comment.