For SAS^® 9.3, the following error messages appear in the JBoss server logs that are located in the JBoss-home-directory/server/SASServer1/log directory:

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'queueConnectionFactory': Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: jms not bound
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1420)

. . .more message lines. . .

Caused by: javax.naming.NameNotFoundException: jms not bound
	at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)

These messages occur when the sas.eventsgenerationframework.war file is deployed on a JBoss server that does not contain the SAS Web Infrastructure Platform. The saseventsgenerationframework.war file is normally contained inside the SAS^® BI Dashboard EAR file. If the installation is configured as a cluster and saseventsgenerationframework.war is split from SAS BI Dashboard, this error will occur when the Web Infrastructure Platform is not installed on the same server.

To resolve these errors, you need to configure an ExternalContext resource on the server where the events-generation framework application is deployed. Then, use the jndiName attribute that is configured in the ExternalContext resource in the Event Generator’s jboss-web.xml file, which is located in WEB-INF/.

1. Add the following ExternalContext resource to the JNDI section of conf/jboss-service.xml:

   <mbean code="org.jboss.naming.ExternalContext" name="jboss.jndi:service=ExternalContext,jndiName=JNDI-name">
      <attribute name="JndiName">SASServer1JNDI</attribute> 
      <attribute name="Properties"> 
   	java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
   	java.naming.provider.url=jnp://SASServer1-ip-address:1099
      </attribute>
      <attribute name="RemoteAccess">true</attribute> 
      <depends>jboss:service=Naming</depends>
   </mbean>

   Note: In this example, whatever value you use for JNDI-name should also be used for the JNDI name in the next step.

2. Update the value for the JNDI name in the <jboss-web> element in JBoss-home-directory/server/SASServer1/deploy_sas/sas.bidashboard4.3.ear/sas.eventsgenerationframework.war/WEB-INF/jboss-web.xml, as follows:

   <jboss-web>
       <resource-ref>
           <res-ref-name>jms/AlertQueue</res-ref-name>
           <res-type>javax.jms.Queue</res-type>
       <jndi-name>JNDI-name/sas/jms/AlertQueue</jndi-name>
       </resource-ref>
       <resource-ref>
         <res-ref-name>jms/QueueConnectionFactory</res-ref-name>
         <res-type>javax.jms.QueueConnectionFactory</res-type>
         <jndi-name>JNDI-name/sas/jms/QueueConnectionFactory</jndi-name>
       </resource-ref>
       <context-root>BIEventGen</context-root>
   </jboss-web>

   Note: The element <context-root>BIEventGen</context-root> might be different if the WAR files are removed from the SAS BI Dashboard EAR file.

For SAS^® 9.4 the following error messages appear in the SAS Web Application Server logs that are located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServerX_1/logs directory:

[localhost-startStop-1] ERROR [%s%u] org.springframework.web.context.ContextLoader - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'queueConnectionFactory': Invocation of init method failed;
 nested exception is javax.naming.NameNotFoundException: Name [jms/ConnectionFactory] is not bound in this Context. Unable to find [jms].
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1455)

. . .more message lines. . .

Caused by: javax.naming.NameNotFoundException: Name [jms/ConnectionFactory] is not bound in this Context. Unable to find [jms].

To resolve these errors, you need to add the missing resources to the server.xml file for the server where the events-generation framework application is deployed. The server.xml file is located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServerX_1/conf directory.

Add the following <Resource> elements after the last existing <Resource> element in the file:

<Resource auth="Container" factory="com.sas.vfabrictcsvr.atomikos.BeanFactory" maxPoolSize="20" name="sas/jms/QueueConnectionFactory" 
          type="com.atomikos.jms.AtomikosConnectionFactoryBean" uniqueResourceName="sas/jms/QueueConnectionFactory"
          xaConnectionFactoryClassName="org.apache.activemq.ActiveMQXAConnectionFactory"
          xaProperties.brokerURL="tcp://xxx.xxx.xxx.xxx:61616"/>


<Resource auth="Container" description="AlertQueue" factory="org.apache.activemq.jndi.JNDIReferenceFactory" name="sas/jms/AlertQueue" 
          physicalName="sas.jms.AlertQueue" type="org.apache.activemq.command.ActiveMQQueue"/>


<Resource auth="Container" driverClassName="org.postgresql.Driver" factory="com.sas.vfabrictcsvr.atomikos.BeanFactory" maxPoolSize="100"
          minPoolSize="10" name="sas/jdbc/SharedServices" password="${pw.sas.jdbc.SharedServices}" 
          testQuery="select 1" type="com.atomikos.jdbc.nonxa.AtomikosNonXADataSourceBean" uniqueResourceName="sas/jdbc/SharedServices" 
          url="jdbc:postgresql://xxx.xxx.xxx.xxx:9432/SharedServices" user="SharedServices"/>

In these elements, you should replace xxx.xxx.xxx.xxx with the host name of the server on which the SAS JMS Broker is running.

Operating System and Release Information