Product: Talend Enterprise Edition ESB v5.6.2 Background / Explanation: I am running 1 VM as an "administrator", allowing me to utilize 1 TAC, 1 Nexus (Artifact Repo), and 1 SVN (Source Control Repo) for all of my runtime containers. Each of my runtime containers are on a separate VM. The services installed on each are as follows (recommendation by Talend rep): talendAdmin: Talend Administration Center Talend Log Server Talend Command Line Talend Job Server Talend Server Services Talend ESB Runtime Containers: Talend Runtime Talend Server Services I have verified, using nmap command, that firewall access is open, allowing talendAdmin to communicate with each runtime container on port 8888. $ nmap runtime-1 -p 8888 -Pn Starting Nmap 5.51 ( ) at 2015-08-14 08:12 CDT Nmap scan report for runtime-1 (IP) Host is up (0.0092s latency). PORT STATE SERVICE 8888/tcp open sun-answerbook I keep getting the following errors/warnings in my tac technical log: ERROR TalendRuntimeServerStateChecker - Connection timed out WARN JMXClient - Timeout when trying to connect to JMX URL 'service:jmx:jmxmp://runtime-1:8888': null WARN JMXClient - Attempted to close a null JMX connector: service:jmx:jmxmp://runtime-1:8888 WARN JMXClient - Socket closed I understand that port 8888 is the JobServer monitoring port and that I do not have that running on my runtime containers. I am sure that is what is causing the failed connections, as the service is not running on that port. I have no real use for the job server as I am only deploying routes to the runtime containers, so I do not want to have to install and run a service I don't need. Question: How can I get Talend Administration Center to stop trying to hit that port/service?
... View more