Common issues and debugging technique during Talend ESB installation

Overview

This article is intended to cover some of the common issues faced during Talend ESB installation and how to debug them.

 

Environment

This topic is not specific to a particular environment.

 

Symptoms/Description

TAC connectivity to Runtime
  1. TAC is not able to connect to Runtime.
  2. Server status is down in TAC.
  3. Not able to connect with the RMI server.
Deployment via TAC
  1. Not able to deploy using the TAC.

 

Resolution

TAC connectivity to Runtime

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.

  1. Check if you can access the karaf web console or not. Use the default userid/password tadmin/tadmin.
    http://hostname:8040/system/console

    If you are not able to login that means there are some problems in the Runtime installation. Check the runtime configuration.

  2. Once step 1 is successful, check the JMX connectivity between TAC and runtime via JCONSOLE. You need to do the following steps:
    • Login to the karaf console as described in Step1, go to the configuration tab and copy the service configuration, which is as follows:
      service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-trun
    • Start the JCONSOLE from the machine where TAC is installed

      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.

  3. Sometimes, the underlying cause is that there is no connectivity to the RMI server from TAC. You can get the following log in catalina.out.
    [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:

    -Djava.rmi.server.hostname=hostname

    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.

Deployment via TAC

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:

org.ops4j.pax.url.mvn.repositories=
Version history
Revision #:
11 of 11
Last update:
‎04-27-2017 11:57 AM
Updated by:
 
Tags (1)