Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
I have currently realize a route where I get a message from WMQ, push the file locally to send it through SFTP (with a Proxy) to a distant server. To send the file through the proxy, I need to call a job and use the components tFTP<X> (Connection, Put, Rename...).
Individually all the flow is working well.
When I launch my route, I get the first message and the message is sent successfully to the distant server, I even got the last log message from my route. Nevertheless, after this message I got the following message (in talend_global.log)
2019-10-02T15:53:47,519 | ERROR | Camel (shop.elt01put_parts_0_1.Elt01_PUT_PARTS) thread #15 - JmsConsumer[MQ.APP.PART.SHOP.IN] | .DefaultMessageListenerContainer 947 | 228 - org.apache.servicemix.bundles.spring-jms - 4.3.14.RELEASE_1 | Could not refresh JMS Connection for destination 'MQ.APP.PART.SHOP.IN' - retrying using FixedBackOff{interval=5000, currentAttempts=581, maxAttempts=unlimited}. Cause: JMSWMQ0018: Failed to connect to queue manager 'FRMQ1' with connection mode 'Client' and host name 'frmq1.it.internal.net(1416)'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2538' ('MQRC_HOST_NOT_AVAILABLE').
The JMS connexion is not able anymore to connect to the queue WMQ.
The worse, if I use the route through Karaf, is that all the JMS connexions generate the same errors, if my route treats one message (the messages appear directly after the first treatment).
I have done some tests, if I remove the tftpConnection (and all the tftp components) and do an action (remove the input file for example), I do not got any error message.
I join a screenshot of the route and a screenshot of the job (please note that I have deactivate/reactivate the component to perform my test).
Thank for your help
Hello,
Can you please clarify in which Talend version/edition you are?
Best regards
Sabrina
Hello,
I am using Talend Studio 7.1.1
Additional test that we have performed:
Any help will be welcome to this specific case