When you edit and publish rule flows in SAS Business Rules Manager 3.3_M2 on SAS 9.4M8 (TS1M8), the following occurs:

• When you start SASServer7_1, a message similar to the following occurs in the server.log:

INFO  (localhost-startStop-1) [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASDecisionManager]] Initializing Spring root WebApplicationContext

... more lines
[jar:file:/opt/config94/Lev1/Web/WebAppServer/SASServer7_1/sas_webapps/
sas.dcm.shell.war/WEB-INF/lib/sas.decisionbuilder.service.jar!/META-INF/
decisionbuilder-services-config.xml]: Initialization of bean failed;
nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'entityManagerFactory' defined in URL [jar:file:/opt/config94/Lev1/Web/WebAppServer/SASServer7_1/sas_webapps/
sas.dcm.shell.war/WEB-INF/lib/sas.decisionbuilder.service.jar!/META-INF/
decisionbuilder-data-config.xml]: Invocation of init method failed;
nested exception is javax.persistence.PersistenceException: 

• The SASBusinessRulesManager3.3.log contains messages similar to the following:

ERROR (tomcat-http--1) [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASBusinessRulesManagerWeb].[rest]] Servlet.service() for servlet [rest] in context
with path [/SASBusinessRulesManagerWeb] threw exception [Request processing failed;
nested exception is org.springframework.orm.jpa.JpaSystemException: Unable to
acquire JDBC Connection; nested exception is org.hibernate.exception.GenericJDBCException:
Unable to acquire JDBC Connection]with root cause
com.atomikos.jdbc.internal.AtomikosSQLException: Connection pool exhausted
- try increasing 'maxPoolSize' and/or 'borrowConnectionTimeout' on the DataSourceBean.
    at com.atomikos.jdbc.internal.AtomikosSQLException.
    throwAtomikosSQLException(AtomikosSQLException.java:29) ~[transactions-jdbc.jar:?]

• The HAR file shows a bad request:
  https://<HOST:Port>/SASBusinessRulesManagerWeb/sasui/ruleFlows/10035
  400 Bad Request
  httpStatusCode 400
  message: "javax.persistence.PersistenceException:
  org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection"

There is no workaround for this issue.