As documented, when the JMS required channel(s) is(are) enabled:
- the relevant connection properties should be set the .properties file
and
- either EMS jars should be available in the engine's CLASSPATH or EMS_HOME should be set in the .tra file

This article provides inputs on troubleshooting connection and startup issues with APIX-G, when EMS Channels are enabled.

All Supported Platforms

Error:-
Engine does not startup and logs the below error:
"WRAPPER - start method threw an exception"

Resolution:-
Either the EMS jars are not available in the CLASSPATH or EMS_HOME is not properly set.
If EMS is not installed on the same machine as APIX-G, copy the jms(2.0).jar and tibjms.jar files to TIBCO_HOME/asg/x.y/lib/tpcl/ext folder.

Error:-
Engine logs the below error during startup:
------------------
WRAPPER - start method threw an exception
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/tibco/tibjms/naming/TibjmsInitialContextFactory : Unsupported major.minor version 52.0
-----------------------

Resolution:-
EMS jars used have been built with JRE1.8.0 and APIX is using JRE1.7.0.
Use a verison of APIX that supports JRE1.8.0: APIX2.2.1 or above

Error:-
Engine does not startup with the below error:-
javax.jms.JMSException: Failed to connect to the server at tcp://localhost1:7222

Resolution:-
APIX uses JNDI to connect to EMS Server. So please make sure the EMS Topic/QueueConnectionFactories are configured with correct EMS URLs.