Description:
This article provides resolutions for the scenarios where TIBCO API Exchange Gateway Engine(APIX-G) exits with no error details during startup.

The possible resolutions for such startup issues are:

1). Check if an EMS channel is enabled in the asg_core.cdd file. If enabled, verify that the asg-engine.tra file is configured with EMS_HOME and the asg.properties file has all of the properties properly configured for the enabled channel.

2). Change the log level to "Debug". Modify minLogLevel to "0" in asg.properties  and change the log levels in cdd to debug and start the asg-engine with the "--debug" parameter.

3). Try to start the engine with strace asg-engine and collect the trace logs and check the last classes loaded just before termination of the engine.

Example :

strace exits with 255 error code and the last two stat entries are :

stat("/opt/tibco_2.1/be/5.1/lib/com/tibco/be/util/GUIDGenerator.class", 0x7ffe7ad21f40) = -1 ENOENT (No such file or directory)

stat("/opt/tibco_2.1/tibcojre64/1.7.0/lib/amd64/libnet.so", {st_mode=S_IFREG|0755, st_size=115008, ...}) = 0

The cause is that the GUID Generators need an NS resolution of the machine to generate GUIDS. If nslookup of the machine fails, the same class loader fails.

4). Check and correct the /etc/hosts file for a consistent hostname resolution.