Issue while setting Up JMS connector
Hi All-
I am getting the belwo error while trying to setup JMS connector. Whot could be the issue. Please provide your views.
Failed to compile generated Java com.pegarules.generated.activity.ra_action_validateinfrastructurejndi_d809957bf1e427361ebab5ce32640211: ----------
1. ERROR in com/pegarules/generated/activity/ra_action_validateinfrastructurejndi_d809957bf1e427361ebab5ce32640211.java (at line 424)
javax.jms.ConnectionFactory connectionFactory = (javax.jms.ConnectionFactory) jndi.lookup("TestConnectionFactory");
^^^^^^^^^
javax.jms cannot be resolved to a type
----------
2. ERROR in com/pegarules/generated/activity/ra_action_validateinfrastructurejndi_d809957bf1e427361ebab5ce32640211.java (at line 424)
javax.jms.ConnectionFactory connectionFactory = (javax.jms.ConnectionFactory) jndi.lookup("TestConnectionFactory");
^^^^^^^^^^^^^^^^^^^^^^^^^^^
javax.jms.ConnectionFactory cannot be resolved to a type
----------
3. ERROR in com/pegarules/generated/activity/ra_action_validateinfrastructurejndi_d809957bf1e427361ebab5ce32640211.java (at line 426)
javax.jms.Connection connection = connectionFactory.createConnection();
^^^^^^^^^
javax.jms cannot be resolved to a type
----------
4. ERROR in com/pegarules/generated/activity/ra_action_validateinfrastructurejndi_d809957bf1e427361ebab5ce32640211.java (at line 433)
catch (javax.jms.JMSException ex) {
^^^^^^^^^
javax.jms cannot be resolved to a type
----------
4 problems (4 errors)
Regards,
Kesav.
The root cause here is that Pega does not have access to JMS API classes (jars). If you have deployed Pega on an enterprise application server such as Weblogic or Websphere, the JMS jars would have been in the classpath and you would not be seeing this error. However, if you have deployed Pega on Tomcat, you must ensure that the JMS API jars are made available to the Pega runtime classpath to resolve this error.