Hallo Dietmar, Thanks for the help! I've set up the cMQConnectionFactory component as suggested: failover:(tcp://primaryHost:61616,tcp://secondaryHost:61616,tcp://localhost:61616)?initialReconnectDelay=20&maxReconnectDelay=500&randomize=false&maxReconnectAttempts=2 The "Use PooledConnectionFatory" checkbox was also checked. The result of this test is pretty much the same - the production of messages doesn't regain its original speed on failover. However, the sending of messages on failover using this Broker URI configuration is much slower than my initial entry (~10-15 seconds per message, compared to ~5 seconds in my initial test). I thought it could have had something to do with the maxReconnectAttempts=2, so I also tested: failover:(tcp://primaryHost:61616,tcp://secondaryHost:61616,tcp://localhost:61616)?initialReconnectDelay=20&maxReconnectDelay=500&randomize=false&maxReconnectAttempts=0 but this configuration is also much slower. Just to cover all the bases I also tested this (note the use of connectionTimeout): failover:(tcp://primaryHost:61616?connectionTimeout=3000,tcp://secondaryHost:61616?connectionTimeout=3000,tcp://localhost:61616)?initialReconnectDelay=20&maxReconnectDelay=500&randomize=false&maxReconnectAttempts=0 I know you said that connectionTimeout is an ActiveMQ parameter and isn't used in Camel - but it sure does seem like it has an effect in Talend Studio as the failover messages using this Broker URI configuration on a failover condition slow to a speed of ~5 seconds per message (quicker than the previous Broker URI configuration). Can you also produce this behaviour? Hopefully the findings above can help you to pinpoint the issue. If you need me to check other configurations, just let me know! Thanks, David.
... View more
Hi there, I've set up two servers with instances of ActiveMQ in a Master/Slave configuration with an Oracle database as the message store and lock mechanism. To test the failover I've created the following Route in Talend ESB Studio: cMQConnectionFactory contains (servers masked, but example Broker URI is below the picture): Broker URI example: "failover:(tcp://PrimaryHost:61616?connectionTimeout=3000,tcp://SecondaryHost:61616?connectionTimeout=3000,tcp://localhost:61616)?randomize=false&maxReconnectAttempts=0&useExponentialBackOff=false" cTimer contains (it's a performance test): cSetBody contains: cJMS contains: So the failover appears to work ok - in that when I kill the Master instance of ActiveMQ on PrimaryHost, the messages will be sent to SecondaryHost. But what I have noticed in the above Route is that on the failure of the Master instance, the messages are not produced as quickly as they were when the Master was active. When the Master instance was active, messages were capable of being produced as fast as the Route could send them. However, on failover condition, the message production slows to about one message per second or slower. I had expected a slight backlog of message production on failing over, but I also expected that message production would increase to the original speed after a time - this doesn't appear to be the case. So, my question: does anyone have an idea about what's causing this? Is the producer constantly trying to first send the message to the original Master instance each time, despite configuring maxReconnectAttempts=0? Is there any way to change this behaviour? Thanks! David. Edit: I've read https://activemq.apache.org/producer-flow-control.html and ensured that the JVM memoryLimit isn't being exceeded by enabling JMX monitoring of the Heap and had a look at systemUsage configuration regarding tempUsage and storeUsage which are also nowhere near being at their limits. I've also tried compiling the Route and deploying it within the Runtime, but the behaviour is the same. I'm at a loss as to what's causing this behaviour.
... View more
Hi Sabrina, I'm also experiencing this issue. Here are the steps to reproduce: * Unzip TOS V6.5.1 * Launch the Studio * Ensure proxy settings are set up * Window > Show View... > Talend > Modules * In the Talend Modules window, click the green download button * The download window appears but no libraries are shown * The download window may sometimes hang when you attempt to close it * Close the download window when it is no longer in a hanging state * Close the Studio * An error window appears stating: "An error has occured. See the log file" This is with a fresh unzip of TOS and so the issue couldn't be custom components.
... View more
Also experiencing issues with TOS 6.5.1 regarding connecting to the Talend Nexus through a proxy. Worked on 6.4.1 with the same settings as I'm testing 6.5.1 with. Here's an extract of the log: !ENTRY org.talend.platform.logging 4 0 2018-02-06 12:12:19.661
!MESSAGE 2018-02-06 12:12:18,614 ERROR org.talend.commons.exception.CommonExceptionHandler - Connection to https://talend-update.talend.com refused
org.apache.http.conn.HttpHostConnectException: Connection to https://talend-update.talend.com refused
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
... 19 more
... View more
Hi there, So I've been playing around with Talend Studio for Data Quality, Talend Administration Centre (version 6.1.1) and the integrated Git. It's promising, but it's not entirely clear how to take full advantage of it. I've read the guide found here: https://help.talend.com/search/all?query=Best+Practices%3A+Using+Git+with+Talend&content-lang=en and am aware that there are some limitations in terms of what sort of Git workflow can currently be supported. Is there any further information available on the following: 1. How does Talend manage local repositories in terms of directory structure? 2. Where are the local repositories created? 3. How is staging handled? (there doesn't seem to be any) 4. Is there no way to avoid a commit and push on each saving of the workspace? (how do I avoid pushing a potential buggy commit on my Development branch to the central repository when I just want to run a job to test it? - Changes are saved when you run a job) 5. How is the merging of branches achieved? From the link above: "Git: Create branches for each development (bug, new feature) and then merge it to the master and release branch. In Talend, a branch is created on the repository." Branching and merging is pretty much the heart of git and allows for a great development cycle to be implemented in Talend, but again, it's not obvious (at least to me) how to go about achieving it. If anyone could point me in the right direction or even better give answers to the questions above, it would be a great help! Thanks, David.
... View more