This error could be due to maintenance performed by your on-premises infrastructure team, that affected your database nodes.
Checking your IriusRisk logs you can find something like this:
2024-04-18 05:20:08.179 314966567 [http-nio-127.0.0.1-8080-exec-5] ERROR org.springframework.boot.web.servlet.support.ErrorPageFilter - Forwarding to error page from request [/saml/SSO/alias/ciso-174466-iriusrisk] due to exception [JDBC exception on Hibernate data access: SQLException for SQL [insert into refresh_token_whitelist (version, last_used_timestamp, http_session_id, expiry_timestamp, user_id, user_agent, issue_timestamp, refresh_token_hash, uuid) values (?, ?, ?, ?, ?, ?, ?, ?, ?)]; SQL state [25006]; error code [0]; could not execute batch; nested exception is org.hibernate.exception.GenericJDBCException: could not execute batch]
org.springframework.orm.hibernate5.HibernateJdbcException: JDBC exception on Hibernate data access: SQLException for SQL [insert into refresh_token_whitelist (version, last_used_timestamp, http_session_id, expiry_timestamp, user_id, user_agent, issue_timestamp, refresh_token_hash, uuid) values (?, ?, ?, ?, ?, ?, ?, ?, ?)]; SQL state [25006]; error code [0]; could not execute batch; nested exception is org.hibernate.exception.GenericJDBCException: could not execute batch
at org.springframework.orm.hibernate5.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:219)
at org.grails.orm.hibernate.GrailsHibernateTemplate.doExecute(GrailsHibernateTemplate.java:305)
at org.grails.orm.hibernate.GrailsHibernateTemplate.execute(GrailsHibernateTemplate.java:241)
at org.grails.orm.hibernate.GrailsHibernateTemplate.execute(GrailsHibernateTemplate.java:120)
at org.grails.orm.hibernate.AbstractHibernateGormInstanceApi.performSave(AbstractHibernateGormInstanceApi.groovy:247)
at org.grails.orm.hibernate.AbstractHibernateGormInstanceApi.save(AbstractHibernateGormInstanceApi.groovy:164)
(...)
Caused by: java.sql.BatchUpdateException: Batch entry 0 insert into refresh_token_whitelist (version, last_used_timestamp, http_session_id, expiry_timestamp, user_id, user_agent, issue_timestamp, refresh_token_hash, uuid) values (0, '2024-04-18 05:20:08.179', 'A36F59C8886722FBA1E6A8E38B7ECE77', '2024-04-18 05:20:08.179', 91819, 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36 Edg/121.0.0.0', '2024-04-18 05:20:08.179', '3isN7tw5lolYo6Ji/LRK6Gfv+eFe2DP/5eb0wpGgk6A=', 'fe12bb94-cf6a-2112-a3db-b0e5ef77ac1e') was aborted: ERROR: cannot execute INSERT in a read-only transaction Call getNextException to see other errors in the batch.
(...)
Your IriusRisk service was connected to a read-only node (replica) of your DB cluster. By restarting or recreating the IriusRisk service, the connection should be restored, pointing to your primary node.
For example, for a docker deployment:
docker restart iriusrisk-tomcat
Or:
docker-compose down && docker-compose up -d
Comments
0 comments
Please sign in to leave a comment.