This article is intended to cover some of the common issues faced during Talend ESB installation and how to debug them.
This topic is not specific to a particular environment.
While doing some activity using the TAC, you are not getting the desired result. One of the main reasons might be that you don't have proper connectivity from TAC to Runtime.
If you are not able to login that means there are some problems in the Runtime installation. Check the runtime configuration.
Check the remote process.
Copy the service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-trun into the input box and specify the userid/password as tadmin/tadmin.
Go to the mbean tab and check if the value org.apache.karaf exists.
[Root exception is java.rmi.ConnectException: Connection refused to host: 192.168.100.162; nested exception is: java.net.ConnectException: Connection refused]
You can set the following properties in trun.bat in JAVA_OPTS:
The reason to set up the above properties is because when you execute an RMI lookup, the server generates a stub and sometime hardcodes its own address in it. The stub is then transferred to the client and the address generated by the server is used for method remoting. The address hardcoded in the stub has nothing to do with the address you used for a lookup. That's why it ends up in failure.
Sometimes, deployment fails because of a wrong repository setting. Check org.ops4j.pax.url.mvn.cfg and ensure that the following property is set properly: