All change requests are stalled or in open state in RSA Identity Governance and Lifecycle
2 years ago
Originally Published: 2019-01-25
Article Number
000044673
Applies To
RSA Product Set: Identity Governance and Lifecycle
RSA Version/Condition: 7.0.2
 
Issue
All change requests are stalled or in open state. User can no longer work on any activities as RSA Workflow Server is no longer able to connect to the database. As a result of this, Workflow server cannot validate the license and will not allow to perform any workflow related task.

The first instance of this issue always starts with following error in WorkPoint.log.
2018-04-11 05:16:48,052 [default task-110] ERROR com.workpoint.services.impl.GenericServiceImpl  - Exception occurred.
org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: javax.resource.ResourceException: IJ000460: Error checking for a transaction
	at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:80)
	at com.workpoint.server.ConnectContext.getConnection(Unknown Source)
	at com.workpoint.server.ConnectContext.connect(Unknown Source)
	at com.workpoint.services.impl.GenericServiceImpl.A(Unknown Source)
	at com.workpoint.services.impl.GenericServiceImpl.createServerContextForUpdate(Unknown Source)
	at com.workpoint.services.impl.JobUpdateServiceImpl.insertJobMonitors(Unknown Source)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
	at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:98)
	at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:266)
	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:95)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207)
	at com.sun.proxy.$Proxy125.insertJobMonitors(Unknown Source)
	at com.workpoint.server.monitor.MonitorHelper.insertJobMonitor(Unknown Source)
	at com.workpoint.server.WPServerController.A(Unknown Source)
	at com.workpoint.server.WPServerController.checkDBLicense(Unknown Source)

Once this occurs, the WorkPoint log repeatedly logs following error.
 
2018-04-11 05:16:48,063 [default task-110] ERROR com.workpoint.services.impl.GenericServiceImpl  - LicenseException occurred: 
The resource license for DSN WPDS could not be verified due to a database error. Please make sure the database connection is working properly. 
See the server log for error details. 
com.workpoint.common.exception.LicenseException: 
The resource license for DSN WPDS could not be verified due to a database error. 
Please make sure the database connection is working properly. See the server log for error details. 
	at com.workpoint.server.WPServerController.A(Unknown Source)
	at com.workpoint.server.WPServerController.checkDBLicense(Unknown Source)
	at com.workpoint.server.ServerProperties.checkDBLicense(Unknown Source)
	at com.workpoint.services.impl.WorkItemServiceImpl.queryByID(Unknown Source)
	at com.workpoint.client.WorkItemEntry.queryByID(Unknown Source)

 
Cause
RSA Workflow server can no longer validate a license as result of communication failure between server and the database.
 
Resolution
This has been resolved in following releases: 

7.02 P09 and higher
7.10 P02 and higher 
Workaround
Restart the application server.

For other workaround, contact RSA Support.